On Wed, 2009-02-25 at 16:49 -0500, The Hereweb wrote: > Actually, I think this issue is because XOHM wants to set a default > gateway that is outside my subnet of the IP/netmask assigned by XOHM. > Here's what I get when I connect my other laptop to XOHM using a WiMAX > usb donble under Windows:
Many places do this, usually hotel wifi networks and such under the false assumption that it's more "secure". In WiMAX it might be, but certainly not on wifi. In any case, whatever dhclient script you're using to actually set up routes and IP addresses should be handling this for you, otherwise that script is broken. You usually just add a host route directly to the gateway, then add set your default route pointed at the gateway. Dan > ipconfig > > Ethernet adapter Local Area Connection 6: > > Connection-specific DNS Suffix . : > Description . . . . . . . . . . . : Samsung USB mWiMAX Adapter > #3 > Physical Address. . . . . . . . . : 00-1B-98-10-10-82 > Dhcp Enabled. . . . . . . . . . . : Yes > Autoconfiguration Enabled . . . . : Yes > IP Address. . . . . . . . . . . . : 68.25.50.179 > Subnet Mask . . . . . . . . . . . : 255.255.255.255 > Default Gateway . . . . . . . . . : 99.207.212.72 > > netstat -rn > =========================================================================== > Interface List > 0x1 ........................... MS TCP Loopback interface > 0x2 ...00 16 e3 9d e7 0f ...... Atheros AR5006X Wireless Network > Adapter - Nomad Miniport > 0x3 ...00 17 42 1d 86 fb ...... Realtek RTL8139 Family PCI Fast > Ethernet NIC - Packet Scheduler Miniport > 0x10005 ...00 1b 98 10 10 82 ...... Samsung USB mWiMAX Adapter #3 - > Packet Scheduler Miniport > =========================================================================== > =========================================================================== > Active Routes: > Network Destination Netmask Gateway Interface > Metric > 0.0.0.0 0.0.0.0 99.207.212.72 68.25.50.179 > 1 > 68.25.50.179 255.255.255.255 127.0.0.1 127.0.0.1 > 20 > 68.255.255.255 255.255.255.255 68.25.50.179 68.25.50.179 > 20 > 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 > 1 > 224.0.0.0 240.0.0.0 68.25.50.179 68.25.50.179 > 1 > 255.255.255.255 255.255.255.255 68.25.50.179 2 > 1 > 255.255.255.255 255.255.255.255 68.25.50.179 3 > 1 > 255.255.255.255 255.255.255.255 68.25.50.179 68.25.50.179 > 1 > Default Gateway: 99.207.212.72 > =========================================================================== > Persistent Routes: > None > > Route Table > > > So what is needed in linux is a host route to the gateway IP "route > add -host 99.207.212.72 wmx0" in addition to the intended default > gateway route. This bug has been around for a while, (e.g. > https://bugs.launchpad.net/ubuntu/+source/dhcp3/+bug/139217) so I'm > not sure where it should be addressed in this case. > > Hope this clarifies, thanks > > - Brian > > > On Wed, Feb 25, 2009 at 3:27 PM, Inaky Perez-Gonzalez > <[email protected]> wrote: > On Tuesday 24 February 2009, The Hereweb wrote: > > and my resolv.conf looks OK > > > > $ more /etc/resolv.conf > > nameserver 99.207.212.85 > > nameserver 99.207.212.87 > > > > but my routing table is empty > > > > r...@y530:~$ netstat -rn > > Kernel IP routing table > > Destination Gateway Genmask Flags MSS > Window irtt > > Iface > > r...@y530:~$ > > > > Any ideas? > > > > I may try to manually create a default route next, but to > get this far but > > not get that is weird. > > > What happens if you run dhclient manually? > > dhclient wmx0 > > As well, can you post the contents of your /etc/dhclient.conf > or any > /etc/dhcp*/dhclient.conf? > > Thanks, > > -- > Inaky > > _______________________________________________ > wimax mailing list > [email protected] > http://www.linuxwimax.org/mailman/listinfo/wimax _______________________________________________ wimax mailing list [email protected] http://www.linuxwimax.org/mailman/listinfo/wimax
