From: rketcham <Ric...@gm...> - 2009-01-21 22:33:36
|
Hello, I have a device the forwards Ethernet traffic over the cell network (AirLink Communications Raven X). I have tried attaching my Verdex/NetCF-vx gumstix boards to it via the Ethernet jack but it is unable to ping www.google.com or it's ip 64.233.161.147. It gets the correct IP address (the Ethernet to Cell device only assigns one IP) but despite that, I am unable to ping any web page. I have used the device successfully with my Windows XP Desktop and another Windows Vista Desktop. This same Gumstix boards work well when connected to my LAN rather than the RavenX, so I'm not sure what the problem is. Does anyone know what could be the issue? Do you have any suggestions on how to troubleshoot this problem? Rich P.S. Relevant information is below: root@gumstix-custom-verdex:/bin$ cat /etc/gumstix-version Revision 318M Built on Mon May 12 10:24:06 PDT 2008 Build machine: otto Target machine: gumstix-custom-verdex libc: glibc root@gumstix-custom-verdex:~$ ifconfig eth0 Link encap:Ethernet HWaddr 00:15:C9:08:91:90 inet addr:68.25.157.115 Bcast:68.255.255.255 Mask:255.255.255.255 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5 errors:0 dropped:0 overruns:0 frame:0 TX packets:15 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:854 (854.0 B) TX bytes:5881 (5.7 KiB) Interrupt:131 DMA chan:ff lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) root@gumstix-custom-verdex:~$ ping www.google.com ping: www.google.com: Host name lookup failure root@gumstix-custom-verdex:~$ ping 64.233.161.147 PING 64.233.161.147 (64.233.161.147): 56 data bytes ping: sendto: Network is unreachable root@gumstix-custom-verdex:~$ cat /etc/resolv.conf search local nameserver 68.28.114.91 nameserver 68.28.122.93 root@gumstix-custom-verdex:~$ route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface -- View this message in context: http://www.nabble.com/Help-with-ethernet-settings-tp21593619p21593619.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: rketcham <Ric...@gm...> - 2009-01-21 22:35:39
|
Hello, I have a device the forwards Ethernet traffic over the cell network (AirLink Communications Raven X). I have tried attaching my Verdex/NetCF-vx gumstix boards to it via the Ethernet jack but it is unable to ping www.google.com or it's ip 64.233.161.147. It gets the correct IP address (the Ethernet to Cell device only assigns one IP) but despite that, I am unable to ping any web page. I have used the device successfully with my Windows XP Desktop and another Windows Vista Desktop. This same Gumstix boards work well when connected to my LAN rather than the RavenX, so I'm not sure what the problem is. Does anyone know what could be the issue? Do you have any suggestions on how to troubleshoot this problem? Rich P.S. Relevant information is below: root@gumstix-custom-verdex:/bin$ cat /etc/gumstix-version Revision 318M Built on Mon May 12 10:24:06 PDT 2008 Build machine: otto Target machine: gumstix-custom-verdex libc: glibc root@gumstix-custom-verdex:~$ ifconfig eth0 Link encap:Ethernet HWaddr 00:15:C9:08:91:90 inet addr:68.25.157.115 Bcast:68.255.255.255 Mask:255.255.255.255 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5 errors:0 dropped:0 overruns:0 frame:0 TX packets:15 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:854 (854.0 B) TX bytes:5881 (5.7 KiB) Interrupt:131 DMA chan:ff lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) root@gumstix-custom-verdex:~$ ping www.google.com ping: www.google.com: Host name lookup failure root@gumstix-custom-verdex:~$ ping 64.233.161.147 PING 64.233.161.147 (64.233.161.147): 56 data bytes ping: sendto: Network is unreachable root@gumstix-custom-verdex:~$ cat /etc/resolv.conf search local nameserver 68.28.114.91 nameserver 68.28.122.93 root@gumstix-custom-verdex:~$ route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface -- View this message in context: http://www.nabble.com/Help-with-ethernet-settings-tp21593623p21593623.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Dave H. <dhy...@gm...> - 2009-01-21 22:46:51
|
Hi Rich, ...snip... > Does anyone know what could be the issue? Do you have any suggestions on how > to troubleshoot this problem? ...snip... > root@gumstix-custom-verdex:~$ ifconfig > eth0 Link encap:Ethernet HWaddr 00:15:C9:08:91:90 > inet addr:68.25.157.115 Bcast:68.255.255.255 > Mask:255.255.255.255 Having a mask of 255.255.255.255 means that any request for ANY off-board IP address needs to be directed to the gateway. > root@gumstix-custom-verdex:~$ route > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use > Iface Unfortunately, no gateway's are shown here, so there's no place to send the packets. Normally the gateway information gets sent by the DHCP server. Perhaps it's using some extension that udhcp doesn't support? You'll probably need to capture the DHCP transactions to see what's going on. -- Dave Hylands Shuswap, BC, Canada http://www.DaveHylands.com/ |
From: rketcham <Ric...@gm...> - 2009-01-23 16:02:42
|
Hi Dave! I think you're right; udhcpc is somehow not getting the gateway IP. I read up on what the udhcpc error I received when starting udhcpc: root@gumstix-custom-verdex:~$ udhcpc udhcpc (v1.2.1) started Sending discover... Sending select for 68.25.157.115... Lease of 68.25.157.115 obtained, lease time 14400 route: SIOC[ADD|DEL]RT: Network is unreachable adding dns 68.28.114.91 adding dns 68.28.122.93 From: http://www.daemon-systems.org/man/route.8.html route Network is unreachable An attempt to add a route failed because the gateway listed was not on a directly-connected network. The next-hop gateway must be given. I might be wrong, but I'm guessing that the gateway IP must be looking kind of strange so route just dumps it. Although, when I connected with my windows machine IP Address: 68.25.157.115 Subnet Mask: 255.255.255.255 Default Gateway: 68.25.157.1 DHCP Server: 192.168.13.31 Lease Obtained: 1/22/2009 10:14:22 PM Lease Expires: 1/23/2009 2:14:22 AM DNS Servers: 68.28.114.91, 68.28.122.93 WINS Server: 192.168.13.31 Actually, the gateway doesn't look strange at all. Is there a way that I could set this up manually instead of relying on udhcpc? Also, is there an alternate dhcp client within the buildroot that I could use that doesn't rely on route? Using wireshark to monitor traffic over a router with the gumstix and the Airlink RavenX connected, these are the packets sent: 1 0.000000 AirlinkC_01:2e:e8 Broadcast ARP Gratuitous ARP for 192.168.13.31 (Request) 2 2.993985 AirlinkC_01:2e:e8 Broadcast ARP Gratuitous ARP for 192.168.13.31 (Request) 3 5.988144 AirlinkC_01:2e:e8 Broadcast ARP Gratuitous ARP for 192.168.13.31 (Request) 4 24.234328 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0xf86f3a01 5 24.294234 0.0.0.0 255.255.255.255 DHCP DHCP Request - Transaction ID 0xf86f3a01 5 24.294234 0.0.0.0 255.255.255.255 DHCP DHCP Request - Transaction ID 0xf86f3a01 Protocols in frame: eth:ip:udp:bootp Packet 4 is sent when I give this command: root@gumstix-custom-verdex:~$ udhcpc After the fifth packet, no more packets are sent or received. I also found this reference to a similar problem http://osdir.com/ml/2003-12/msg00284.html BusyBox udhcpc Thanks for the help! Rich Dave Hylands wrote: > > Hi Rich, > > ...snip... >> Does anyone know what could be the issue? Do you have any suggestions on >> how >> to troubleshoot this problem? > ...snip... > >> root@gumstix-custom-verdex:~$ ifconfig >> eth0 Link encap:Ethernet HWaddr 00:15:C9:08:91:90 >> inet addr:68.25.157.115 Bcast:68.255.255.255 >> Mask:255.255.255.255 > > Having a mask of 255.255.255.255 means that any request for ANY > off-board IP address needs to be directed to the gateway. > >> root@gumstix-custom-verdex:~$ route >> Kernel IP routing table >> Destination Gateway Genmask Flags Metric Ref Use >> Iface > > Unfortunately, no gateway's are shown here, so there's no place to > send the packets. Normally the gateway information gets sent by the > DHCP server. Perhaps it's using some extension that udhcp doesn't > support? You'll probably need to capture the DHCP transactions to see > what's going on. > > -- > Dave Hylands > Shuswap, BC, Canada > http://www.DaveHylands.com/ > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://www.nabble.com/Help-with-ethernet-settings-tp21593619p21627182.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Dave H. <dhy...@gm...> - 2009-01-23 16:28:59
|
Hi Rich, > I think you're right; udhcpc is somehow not getting the gateway IP. I read > up on what the udhcpc error I received when starting udhcpc: > > root@gumstix-custom-verdex:~$ udhcpc > udhcpc (v1.2.1) started > Sending discover... > Sending select for 68.25.157.115... > Lease of 68.25.157.115 obtained, lease time 14400 > route: SIOC[ADD|DEL]RT: Network is unreachable > adding dns 68.28.114.91 > adding dns 68.28.122.93 > > From: http://www.daemon-systems.org/man/route.8.html route > > Network is unreachable > An attempt to add a route failed because the gateway listed was > not on a directly-connected network. The next-hop gateway must > be given. > > I might be wrong, but I'm guessing that the gateway IP must be looking kind > of strange so route just dumps it. Although, when I connected with my > windows machine I had the following IPs in my configuration: > > IP Address: 68.25.157.115 > Subnet Mask: 255.255.255.255 > Default Gateway: 68.25.157.1 > DHCP Server: 192.168.13.31 > Lease Obtained: 1/22/2009 10:14:22 PM > Lease Expires: 1/23/2009 2:14:22 AM > DNS Servers: 68.28.114.91, 68.28.122.93 > WINS Server: 192.168.13.31 > > Actually, the gateway doesn't look strange at all. I think that the problem is that with a IP address of 68.25.157.115 and a mask of 255.255.255.255, there is still no way to talk to the gateway. route is expecting that when you apply the mask to the ip address and also apply the mask to the gateway address that you'll get a common network. If the subnet mask were instead 255.255.255.0 then it would be able to get to the gateway. So windows must have some type of special rule it's using to allow it to talk to the gateway, or just blindly assuming it can talk to the gateway. You could manually add a route. You might need to change the network mask first. -- Dave Hylands Shuswap, BC, Canada http://www.DaveHylands.com/ |
From: rketcham <Ric...@gm...> - 2009-01-23 19:11:05
|
Great! That worked. On the newer buildroot, I did: ifconfig eth0 netmask 255.255.255.0 route add default gw 68.25.157.1 eth0 On the older buildroot, I had to use this: ifconfig eth0 netmask 255.255.255.0 ip route add default via 68.25.157.1 On the newer buildroot I was able to edit /etc/udhcpc.d/50default by changing: [ -n "$subnet" ] && NETMASK="netmask $subnet" to [ -n "$subnet" ] && NETMASK="netmask 255.255.255.0" By doing it this way, udhcpc is forced to used 255.255.255.0 as the netmask and subsequently gets the correct gateway IP. Is there a way to do this in the older buildroots? Like 1508? The only file I have been able to find is /etc/init.d/S40network. Thanks! Rich Dave Hylands wrote: > > Hi Rich, > >> I think you're right; udhcpc is somehow not getting the gateway IP. I >> read >> up on what the udhcpc error I received when starting udhcpc: >> >> root@gumstix-custom-verdex:~$ udhcpc >> udhcpc (v1.2.1) started >> Sending discover... >> Sending select for 68.25.157.115... >> Lease of 68.25.157.115 obtained, lease time 14400 >> route: SIOC[ADD|DEL]RT: Network is unreachable >> adding dns 68.28.114.91 >> adding dns 68.28.122.93 >> >> From: http://www.daemon-systems.org/man/route.8.html route >> >> Network is unreachable >> An attempt to add a route failed because the gateway listed >> was >> not on a directly-connected network. The next-hop gateway >> must >> be given. >> >> I might be wrong, but I'm guessing that the gateway IP must be looking >> kind >> of strange so route just dumps it. Although, when I connected with my >> windows machine I had the following IPs in my configuration: >> >> IP Address: 68.25.157.115 >> Subnet Mask: 255.255.255.255 >> Default Gateway: 68.25.157.1 >> DHCP Server: 192.168.13.31 >> Lease Obtained: 1/22/2009 10:14:22 PM >> Lease Expires: 1/23/2009 2:14:22 AM >> DNS Servers: 68.28.114.91, 68.28.122.93 >> WINS Server: 192.168.13.31 >> >> Actually, the gateway doesn't look strange at all. > > I think that the problem is that with a IP address of 68.25.157.115 > and a mask of 255.255.255.255, there is still no way to talk to the > gateway. route is expecting that when you apply the mask to the ip > address and also apply the mask to the gateway address that you'll get > a common network. > > If the subnet mask were instead 255.255.255.0 then it would be able to > get to the gateway. So windows must have some type of special rule > it's using to allow it to talk to the gateway, or just blindly > assuming it can talk to the gateway. > > You could manually add a route. You might need to change the network mask > first. > > -- > Dave Hylands > Shuswap, BC, Canada > http://www.DaveHylands.com/ > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://www.nabble.com/Help-with-ethernet-settings-tp21593619p21630883.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: rketcham <Ric...@gm...> - 2009-01-23 20:13:34
|
Nevermind, I found it in /usr/share/udhcpc/default.script I edited the script to the following: #!/bin/sh # udhcpc script edited by Tim Riker <Tim@Rikers.org> [ -z "$1" ] && echo "Error: should be called from udhcpc" && exit 1 RESOLV_CONF="/etc/resolv.conf" [ -n "$broadcast" ] && BROADCAST="broadcast $broadcast" [ -n "$subnet" ] #[ -n "$subnet" ] && NETMASK="netmask $subnet" if echo $subnet | grep 255.255.255.255 > /dev/null then NETMASK="netmask 255.255.255.0" else NETMASK="netmask $subnet" fi case "$1" in deconfig) ip route flush dev $interface ip addr flush dev $interface ip link set $interface down ip link set $interface up ;; renew|bound) #ip link set $interface up #ip addr add dev $interface local $ip/$mask $BROADCAST /sbin/ifconfig $interface $ip $BROADCAST $NETMASK if [ -n "$router" ] ; then for i in $router ; do ip route add default via $i dev $interface done fi echo -n > $RESOLV_CONF [ -n "$domain" ] && echo domain $domain >> $RESOLV_CONF for i in $dns ; do echo nameserver $i >> $RESOLV_CONF done [ -x /etc/init.d/S50bonjour ] && /etc/init.d/S50bonjour restart ;; esac exit 0 -- View this message in context: http://www.nabble.com/Help-with-ethernet-settings-tp21593619p21631852.html Sent from the Gumstix mailing list archive at Nabble.com. |