On Tue, 2015-05-19 at 16:29 +0200, Oscar Knorn wrote: > Package: linux-image-3.2.0-4-amd64 > Version: 3.2.60-1+deb7u3 This is outdated; the lastest for wheezy is 3.2.68-1+deb7u1. But I don't see any fixes that seem related to this bug. > Arch: amd64 Linux > Desc: 3.2 for 64-bit PCs > > When using 'route -n' or 'ip route show' a certain /24 Route is > displayed, but does not have effect on the routing decision of the > kernel. > After removing the bogus route and setting it once again, everything > works as expected. How often does this happen? > Other packages in conjunction: > net-tools_1.60-24.2_amd64 > iproute_20120521-3+b3_amd64 > vlan_1.9-3_amd64 > libc6_2.13-38+deb7u4_amd64 > > Here is a transcript: > ------------------------------%<----------------------------------------- > toaster:~# ping 192.168.18.1 > PING 192.168.18.1 (192.168.18.1) 56(84) bytes of data. > ^C > --- 192.168.18.1 ping statistics --- > 3 packets transmitted, 0 received, 100% packet loss, time 2006ms > > toaster:~# ping 192.168.18.2 > PING 192.168.18.2 (192.168.18.2) 56(84) bytes of data. > ^C > --- 192.168.18.2 ping statistics --- > 2 packets transmitted, 0 received, 100% packet loss, time 1006ms > > toaster:~# route -n > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use > Iface > 0.0.0.0 192.124.246.50 0.0.0.0 UG 0 0 0 > vlan10 > 192.124.246.0 0.0.0.0 255.255.255.0 U 0 0 0 > vlan10 > 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 > vlan13 > 192.168.11.0 0.0.0.0 255.255.255.0 U 0 0 0 > vlan12 > 192.168.18.0 192.124.246.48 255.255.255.0 UG 0 0 0 > vlan10 > 192.168.71.0 0.0.0.0 255.255.255.0 U 0 0 0 > vlan11 > toaster:~# ip route show > default via 192.124.246.50 dev vlan10 > 192.124.246.0/24 dev vlan10 proto kernel scope link src > 192.124.246.66 > 192.168.1.0/24 dev vlan13 proto kernel scope link src 192.168.1.11 > 192.168.11.0/24 dev vlan12 proto kernel scope link src 192.168.11.201 > 192.168.18.0/24 via 192.124.246.48 dev vlan10 > 192.168.71.0/24 dev vlan11 proto kernel scope link src 192.168.71.201 > toaster:~# traceroute 192.168.18.1 > traceroute to 192.168.18.1 (192.168.18.1), 30 hops max, 60 byte packets > 1 win1.asfh-berlin.de (192.124.246.50) 0.319 ms 0.309 ms 0.302 ms > 2 * * * > 3 * * * > 4 * * * > 5 * * * > 6 * * * > 7 *^C > toaster:~# traceroute 192.168.18.2 > traceroute to 192.168.18.2 (192.168.18.2), 30 hops max, 60 byte packets > 1 gw.asfh-berlin.de (192.124.246.48) 0.146 ms * * > 2 10.8.0.2 (10.8.0.2) 23.625 ms 23.562 ms 23.561 ms Seems like this one is correctly routed, then? Only 192.168.18.1 is special. Were there any changes in routing to 192.168.18.1 or to 192.168.18.0/24, or was the route shown above present since boot? [...] > I suggest that the issue may be reproduced. I doubt it! This is quite weird. Ben. > I am using Debian GNU/Linux 7, kernel 3.2.60-1+deb7u3 > and libc6 2.13-38+deb7u4. > > -- Ben Hutchings Reality is just a crutch for people who can't handle science fiction.
Attachment:
signature.asc
Description: This is a digitally signed message part