networking/internet always fails for me

Removing the -R (Record Route) solves the issue

What is this option for? Can we remove it?

Hey!

Could you please attach output of:

ifconfig

route -n

also try to ping 10.1.1.1 from the wireless interface, assuming it's wlan0:

ping -I wlan0 10.1.1.1 (note uppercase i)

cyphermox mentioned something about Oneiric not setting the route's metrics correctly, I ran the command on Natty and it works correctly, sending stuff through my wireless interface (the only one connected at the time), so my guess is it may have to do with the routing thing, but this info will help debug things.

Thanks!

ara@sushirider:~/.cache/checkbox$ ping -I wlan1 10.1.1.1
PING 10.1.1.1 (10.1.1.1) from 10.1.13.0 wlan1: 56(84) bytes of data.
64 bytes from 10.1.1.1: icmp_req=1 ttl=64 time=4.73 ms
64 bytes from 10.1.1.1: icmp_req=2 ttl=64 time=1.05 ms

It works, as it does not have the -R

ra@sushirider:~/.cache/checkbox$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.1.1.1 0.0.0.0 UG 0 0 0 wlan1
10.1.0.0 0.0.0.0 255.255.0.0 U 0 0 0 wlan1
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 wlan1

ara@sushirider:~/.cache/checkbox$ ifconfig
eth0 Link encap:Ethernet HWaddr f0:de:f1:5c:69:b9
          UP BROADCAST MULTICAST MTU:1500 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:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
          Interrupt:20 Memory:d1600000-d1620000

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:8970 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8970 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1503564 (1.5 MB) TX bytes:1503564 (1.5 MB)

wlan1 Link encap:Ethernet HWaddr 00:24:d7:c5:fc:58
          inet addr:10.1.13.0 Bcast:10.1.255.255 Mask:255.255.0.0
          inet6 addr: fe80::224:d7ff:fec5:fc58/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:996939 errors:0 dropped:0 overruns:0 frame:0
          TX packets:306452 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:358419433 (358.4 MB) TX bytes:60288436 (60.2 MB)

the -R option includes routing info (and a request for that) in each packet. When you use it output looks like this:

ping -R 10.153.108.1
PING 10.153.108.1 (10.153.108.1) 56(124) bytes of data.
64 bytes from 10.153.108.1: icmp_req=1 ttl=64 time=0.977 ms
RR: 10.153.108.180
 10.153.108.1
 10.153.108.1
 10.153.108.180

64 bytes from 10.153.108.1: icmp_req=2 ttl=64 time=0.926 ms (same route)

I'm not sure that we use that information for anything, so it might be possible to remove it. I'd like to know:

- Whether we indeed ignore it, by looking at internet_test's code (if we're not parsing ping's output, then we don't need this.
- I'd still love to see output for route and ifconfig, to make sure there's nothing weird there, it seems strange that -R would outright not work and make ping fail.