Mailing List os2-wireless_users@2rosenthals.com Archived Message #6678

From:	"Lewis G Rosenthal" <os2-wireless_users@2rosenthals.com>	Full Headers Undecoded message
Subject:	Re: [OS2Wireless] Hotel problem with Asus wl-330ge
Date:	Thu, 18 Mar 2010 11:40:21 -0400
To:	OS/2 Wireless Users Mailing List <os2-wireless_users@2rosenthals.com>

On 03/17/10 06:40 pm, Dave Saville thus wrote : On Wed, 17 Mar 2010 16:18:07 -0700 Bob wrote: ** Reply to message from "Stan Sidlov" <os2-wireless_users@2rosenthals.com> on Wed, 17 Mar 2010 13:48:38 -0400 This could be one of those issues where the IP connection is limited until you open a browser to acknowledge the terms of use, copy your mac address, etc. I've been to a number of hotels and such where this is required before they grant you a full ride to the web. Unfortunately they seem to like to launch/only work with IE (but you can try mozilla). I have had to go through those special logon procedures without problems using Firefox. In the problem I had Firefox could not connect to a router where the logon web page would be located if they use one and could not get to any web page. No the problem is the Thinkpad never gets an IP via the Asus but does via the Artem. There is no point opening a browser if netstat -r says there is no IP etc. Indeed, if you're just passing DHCP broadcasts through (bridge mode), and it works one way and not the other, the only way to tell the difference would be to capture packets on the far side (read: outside your machine) via Wireshark or something and then compare what's being sent. Dollars to doughnuts (Dave, where you are, is that "Pounds to doughnuts?" :-) ) the server is ignoring the packets sent through the one and responding properly to the other. Now, whether the underlying cause is something in the Intel driver for the wired NIC (or does that one have a 3Com in it?) vs something in the Artem driver or whether the "noise" (figuratively speaking) was introduced by the Asus, I couldn't say, except that AIUI, you've otherwise had no problems with the bridge device. If it were a case of the vendor class issue, you can bet that the same issue would have been present on *all* interfaces, unless the DHCP configuration was changed from one to the other (and that assumes facts not in evidence). Weird. Just chalk it up, I 'spose. -- Lewis ------------------------------------------------------------- Lewis G Rosenthal, CNA, CLP, CLE Rosenthal & Rosenthal, LLC www.2rosenthals.com Need a managed Wi-Fi hotspot? www.hautspot.com visit my IT blog www.2rosenthals.net/wordpress -------------------------------------------------------------

Subscribe: Feed, Digest, Index.
Unsubscribe
Mail to ListMaster