OK, I got it now :)  (Connected to gmail via wimax as I type this message
...)

Much thanks to everyone.

I think my dhcp/route problems were caused by when I get built the patched
dhclient version that was needed in the 1.3 version before and installed its
files, which then tainted my dhclient configuration.

So I "apt-get purge"'d and re-instaled the dhcp3-client package and things
now work as expected and already described by Paul in his success reports.

Also to get the wimax daemon to run automatically at startup, I did
   update-rc.d  wimax defaults
to tie that down.

Config details:

Network: XOHM (connected using profile 4)
Device: Lenovo y530 with Intel 5350 card
Linux details: Ubuntu 8.10 Intrepid desktop, with custom kernel 2.6.29-rc6,
32 bit version
Intel Wimax Software: v 1.4.0 built as kernel module and added seperately
into linux (i.e. I didn't select wimax in my rc6 kernel make menuconfig
process)

Command line outputs

cough...@y530:/tmp$ ifconfig wmx0
wmx0      Link encap:Ethernet  HWaddr 00:1d:e1:02:20:21
          inet addr:68.25.50.79  Mask:255.255.255.255
          inet6 addr: fe80::21d:e1ff:fe02:2021/64 Scope:Link
          UP RUNNING NOARP  MTU:1400  Metric:1
          RX packets:8705 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6453 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:5
          RX bytes:10130965 (10.1 MB)  TX bytes:995104 (995.1 KB)

cough...@y530:/tmp$ netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt
Iface
99.207.212.72   0.0.0.0         255.255.255.255 UH        0 0          0
wmx0
0.0.0.0         99.207.212.72   0.0.0.0         UG        0 0          0
wmx0

cough...@y530:/tmp$ wimaxcu status connect
Connected.
Network Info:
    ID       : 4
    Name     : XOHM
    Realm    : xohm.com
    Signal   : Fair
    RSSI     : -77 dBm
    CINR     : 4 dB
    Activated: Yes
    Network Type  : Home network
    Connection Time: 00:10:04








On Thu, Feb 26, 2009 at 10:14 AM, Paul Donohue <[email protected]> wrote:

> This works fine for me in Ubuntu Intrepid, so I'm not sure why it wouldn't
> work for you:
>
> $ ifconfig wmx0
> wmx0      Link encap:Ethernet  HWaddr 00:1d:e1:02:37:89
>          inet addr:68.25.50.212  Mask:255.255.255.255
>          inet6 addr: fe80::21d:e1ff:fe02:3789/64 Scope:Link
>           UP RUNNING NOARP  MTU:1400  Metric:1
>           RX packets:4695 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:4913 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:5
>          RX bytes:3371952 (3.3 MB)  TX bytes:708232 (708.2 KB)
>
> $ route -n
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use
> Iface
> 99.207.212.72   0.0.0.0         255.255.255.255 UH    0      0        0
> wmx0
> 0.0.0.0         99.207.212.72   0.0.0.0         UG    0      0        0
> wmx0
> $
>
> And launchpad bug 139217 is either invalid or has already been fixed, as my
> /sbin/dhclient-script does the following starting at line 194:
>            ifconfig $interface inet $new_ip_address $new_subnet_arg \
>                $new_broadcast_arg $mtu_arg
>
>            # point to point
>            if [ "$new_subnet_mask" == "255.255.255.255" ]; then
>                for router in $new_routers; do
>                    route add -host $router dev $interface
>                done
>            fi
>
>            for router in $new_routers; do
>                route add default dev $interface gw $router $metric_arg
>            done
>
> On Wed, Feb 25, 2009 at 04:49:34PM -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:
> >
> > 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

Reply via email to