If no DNS lookup is being done, there should be absolutely NO
oppertunity for a redirect.

This is incorrect. A router with sufficient features can redirect whatever
it likes. It's quite common for hotspot types of setups to do just that.
So it doesn't matter if you have a static address, vpn or anything else.
Any packets that hit the router can be manipulated to return anything the
router dictates. Even at the ARP level. So your machine does an ARP lookup
trying to find your static address (or route) and it's given the router's
address; this is normal. But at the same time the router now knows your MAC
address (also normal). You use your browser and your MAC address then sends
other packets, the hotspot router understands this as HTTP traffic and
returns the redirected HTML content. Try any other static addresses and
you'll get the exact same thing.

Bill Kearney wrote:

If no DNS lookup is being done, there should be absolutely NO
oppertunity for a redirect.


This is incorrect. A router with sufficient features can redirect whatever
it likes. It's quite common for hotspot types of setups to do just that.
So it doesn't matter if you have a static address, vpn or anything else.
Any packets that hit the router can be manipulated to return anything the
router dictates. Even at the ARP level. So your machine does an ARP lookup
trying to find your static address (or route) and it's given the router's
address; this is normal. But at the same time the router now knows your MAC
address (also normal). You use your browser and your MAC address then sends
other packets, the hotspot router understands this as HTTP traffic and
returns the redirected HTML content. Try any other static addresses and
you'll get the exact same thing.

YES, but if Skip is attempting to access (port 80 HTTP) an IP address
LOCAL TO HIS ONBOARD LAN, *HOW* is the router at the hotspot
intercepting it? It shouldn't have any interest in any local addresses
on the LAN side of Skip's bridge. You obviously have a better than
obvious grasp of what's going on so can you provide an explanation or
suggest the next troubleshooting step Skip should try?




--
Ian Malcolm. London, ENGLAND. (NEWSGROUP REPLY PREFERRED)
ianm[at]the[dash]malcolms[dot]freeserve[dot]co[dot]uk
[at]=@, [dash]=- & [dot]=. *Warning* HTML & 32K emails -- NUL:
'Stingo' Albacore #1554 - 15' Early 60's, Uffa Fox designed,
All varnished hot moulded wooden racing dinghy.

YES, but if Skip is attempting to access (port 80 HTTP) an IP address
LOCAL TO HIS ONBOARD LAN, *HOW* is the router at the hotspot
intercepting it? It shouldn't have any interest in any local addresses
on the LAN side of Skip's bridge. You obviously have a better than
obvious grasp of what's going on so can you provide an explanation or
suggest the next troubleshooting step Skip should try?

Skip's networking has been fraught with screw ups, largely borne of his own
failure to actually pay attention to, and use, the advice a number of
networking experts have offered. Here an in alt.internet.wireless.

My advice then, and now, continues to be "get the right gear". And stop
wasting his and everyone else's time.