There was a complaint about a guy no longer able to use his hanset for
VPN access.

In terms of WAP, stuff has definitely changed.

When a WAP request is handled by the WAP gateway (APN), it is converted
to an HTTP request with special headers by the gateway.

Here is what it looked like in the past:
--------------------------------------------------------------------------------
  #HTTP_PRAGMA          no-cache
  #HTTP_ACCEPT
  application/vnd.wap.wmlc;Type=4365,application/vnd.wap.wmlc,applicatio
  n/vnd.wap.wmlscriptc,application/vnd.wap.multipart.related,application
  /vnd.wap.multipart.mixed,application/octet-stream,text/plain,text/css,
  image/bmp,image/gif,image/jpeg,image/png,image/vnd.wap.wbmp,applicatio
  n/vnd.wap.sic,application/vnd.wap.slc,application/vnd.wap.coc,applicat
  ion/vnd.wap.xhtml+xml,application/xhtml+xml;profile="http://www.wapfor
  um.org/xhtml",text/html,application/smil,application/vnd.wap.mms-messa
  ge,audio/midi,audi
  #HTTP_USER_AGENT      SIE-M55/09 UP.Browser/6.1.0.5.c.6 (GUI) MMP/1.0
  #HTTP_ACCEPT_CHARSET  UTF-8,*;q=0.001
  #HTTP_ACCEPT_LANGUAGE en
  #HTTP_ACCEPT_ENCODING *;q=0.001
  #HTTP_VIA             1.1 squid.fido.ca:3128 (Squid/2.3.STABLE5)
  #HTTP_X_FORWARDED_FOR 205.151.11.27
  #HTTP_HOST            vaxination.dyndns.org
  #HTTP_CACHE_CONTROL   max-age=259200
  #HTTP_CONNECTION      keep-alive

----------------------------------------------------------------------------------

Here is what it looks now with last weeks changes:

#HTTP_HOST        wap.vaxination.ca
#HTTP_ACCEPT
               application/vnd.wap.wmlc;Type=4365, application/vnd.wap.wmlc,
               application/vnd.wap.wmlscriptc,
               application/vnd.wap.multipart.related,
               application/vnd.wap.multipart.mixed,
               application/vnd.phonecom.mmc-wbxml, application/octet-stream,
               application/vnd.openwave.pp, text/plain, text/css, image/bmp,
               image/gif, image/jpeg, image/png, image/vnd.wap.wbmp,
               application/vnd.wap.sic, application/vnd.wap.slc,
               application/vnd.wap.coc, application/vnd.wap.xhtml+xml,
               application/xhtml+xml;profile="http://www.wapforum.org
#HTTP_ACCEPT_CHARSET      utf-8,*
#HTTP_ACCEPT_LANGUAGE      en
#HTTP_ENCODING_VERSION       1.3, 10 1.3
#HTTP_USER_AGENT          SIE-M55/09 UP.Browser/6.1.0.5.c.6 (GUI) MMP/1.0 UP.Link/6.2.3.15.0
#HTTP_X_UP_DEVCAP_CHARSET   utf-8
#HTTP_X_UP_DEVCAP_MAX_PDU  53248
#HTTP_X_UP_UPLINK          montrealpush.gprs.rogers.com
#HTTP_X_WAP_PROFILE          "http://communication-market.siemens.de/UAProf/M55_09.xml"
#HTTP_X_UP_SUBNO         15145551212_montrealpush.gprs.rogers.com
#HTTP_VIA              1.1 mo2magproxy1.int.gprs.rogers.com
#HTTP_CONNECTION          close

The IP of the request is still 205.205.50.30, so I *assume* that it is
NATted. I find it odd that my handset would have kept the same IP all
this time. (is it possible ?)

The User Agent: field was modified, with the MMP having different version.
The UPLINK is new, pointing to rogers.com
the VIA is different, pointing to rogers and not fido.

the UP_SUBNO is new, and contains the telephone number of the hanset
(replaced above with 555-1212). This is a big improvement since scripts
can now authorize based on the telephone number of the subscriber. This
was previously not possible. It is not known if the total SUBNO string
changes if you roam (eg: if I travel to vancouver). Also, the specs
allow for some random but unique string to didentify a customer (thus
not revealing person's phone number). Rogers seems to have chosen to
reveal the telephone numbers.

the PROFILE field is also new. This is an XML document which contains an
XML document describing capabilities of the handset (such as screen
size).  

Note that Rogers doesn't provide a "forwarded for" which contains the
actual IP of the handset. (if this is NATed, such IP would be useless
since it would be unreachable from the net.

With the chances, is it possible that Rogers would allow push MMS
messages ? (eg: a computer on the net sending an MMS message to a
handset (as opposed to hansets pulling info from the server)

To those who have laptops connected to the handset: if you could find
out what IP the network now gives you
(ifconfig -a from the command line), it might help understand how they
set this up.