Weird Problem with routing to LAN
Shadow Hawkins on Monday, 04 April 2005 10:58:43
Hello, i have a weird problem on my LAN.
I have set up routing for my LAN and it worked some weeks ago...but suddenly something must be broken.
Here my routing table:
2001:6f8:900:4bd::/64 via :: dev sit1 proto kernel metric 256 mtu 1280 advmss 1220
2001:6f8:1378::/64 dev bond0 metric 1024 mtu 1500 advmss 1440
fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1220
fe80::/64 dev eth1 proto kernel metric 256 mtu 1500 advmss 1220
fe80::/64 dev eth2 proto kernel metric 256 mtu 1500 advmss 1220
fe80::/64 dev bond0 proto kernel metric 256 mtu 1500 advmss 1440
fe80::/64 via :: dev sit1 proto kernel metric 256 mtu 1280 advmss 1220
ff00::/8 dev eth0 proto kernel metric 256 mtu 1500 advmss 1220
ff00::/8 dev eth1 proto kernel metric 256 mtu 1500 advmss 1220
ff00::/8 dev eth2 proto kernel metric 256 mtu 1500 advmss 1220
ff00::/8 dev bond0 proto kernel metric 256 mtu 1500 advmss 1440
ff00::/8 dev sit1 proto kernel metric 256 mtu 1280 advmss 1220
default via 2001:6f8:900:4bd::1 dev sit1 metric 1024 mtu 1280 advmss 1220
sit1 ...well its not a sit device...its just named so..i put it so in aiccu.conf..for compatibility for my ip6tables script.
sit1 Link encap:IPv6-in-IPv4 [84.153.237.190-inet6->212.224.0.188]
inet6 addr: 2001:6f8:900:4bd::2/64 Scope:Global
inet6 addr: 2001:6f8:1378::1/128 Scope:Global
inet6 addr: fe80::5499:edbe/128 Scope:Link
UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1
RX packets:763 errors:0 dropped:0 overruns:0 frame:0
TX packets:789 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:646953 (631.7 Kb) TX bytes:124388 (121.4 Kb)
bond0 also channel bonding...
bond0 Link encap:Ethernet HWaddr 00:00:CB:62:90:7D
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: 2001:6f8:1378::2/128 Scope:Global
inet6 addr: fe80::200:cbff:fe62:907d/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:93847 errors:0 dropped:0 overruns:0 frame:0
TX packets:109474 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6891215 (6.5 Mb) TX bytes:57995157 (55.3 Mb)
Ok well the weird thing is that i can ping for example cluster-node3
PING 2001:6f8:1378::4(2001:6f8:1378::4) from 2001:6f8:1378::1 : 56 data bytes
64 bytes from 2001:6f8:1378::4: icmp_seq=1 ttl=64 time=0.467 ms
64 bytes from 2001:6f8:1378::4: icmp_seq=2 ttl=64 time=0.235 ms
64 bytes from 2001:6f8:1378::4: icmp_seq=3 ttl=64 time=0.225 ms
--- 2001:6f8:1378::4 ping statistics ---
3 packets transmitted, 3 received, 0% loss, time 2002ms
rtt min/avg/max/mdev = 0.225/0.309/0.467/0.111 ms
But if i ping my network interface also bond0
PING 2001:6f8:1378::2(2001:6f8:1378::2) from 2001:6f8:1378::1 : 56 data bytes
From ::1 icmp_seq=1 Destination unreachable: Address unreachable
From ::1 icmp_seq=2 Destination unreachable: Address unreachable
From ::1 icmp_seq=3 Destination unreachable: Address unreachable
--- 2001:6f8:1378::2 ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% loss, time 3009ms
Ok, the weird thing is...that if i dump with tcpdump the following is to appear:
10:51:18.823682 ipv6.tuxwave.net > ff02::1:ff00:2: icmp6: neighbor sol: who has ipv6-gw.tuxwave.net
10:51:18.823853 ipv6.tuxwave.net > ff02::1:ff00:2: icmp6: neighbor sol: who has ipv6-gw.tuxwave.net
also if i listen with tcpdump on bond0 the interface does also receive it but does not answer to the neighbor solication messages....so i dont know why that happens. It worked also some weeks ago...
Forwarding is enabled and the result is not in any way different when turned off all iptables and ip6tables rules and setting policy to accept.
I searched on the net and there were no very useful search results.
The problem is...
10:55:05.152388 cluster-node3.tuxwave.net > ipv6.tuxwave.net: icmp6: neighbor adv: tgt is cluster-node3.tuxwave.net
10:55:05.152442 ipv6.tuxwave.net > cluster-node3.tuxwave.net: icmp6: echo request
10:55:05.152470 cluster-node3.tuxwave.net > ipv6.tuxwave.net: icmp6: neighbor adv: tgt is cluster-node3.tuxwave.net
10:55:05.152553 cluster-node3.tuxwave.net > ipv6.tuxwave.net: icmp6: echo reply
Why do i reach the other nodes in my linux-loadbalancing-cluster when i cant reach the nic also bond0 (are 2 nics but also bonded to one interface...both have same mac and ipv6 link adress set)...when i use for example the tiscali router found on traceroute6.org then i cant ping the nodes on my network...only the 2001:6f8:1378::1 and the usual ipv6 endpoint address is reachable. But not anything of my lan is reachable from outside.
Does someone know why?
Thanks
Sebastian Kricner
Weird Problem with routing to LAN
Shadow Hawkins on Monday, 04 April 2005 11:02:58
Ah and to mention:
2.4.22 - Kernel version
Hearbeat - Tunnel type...automatically reconfigured per shell script after ipv4 change
Weird Problem with routing to LAN
Shadow Hawkins on Monday, 04 April 2005 11:21:44
For some hints...theres a dump of the usual route utility...(not iproute2)
route --inet6
Kernel IPv6 routing table
Destination Next Hop Flags Metric Ref Use Iface
::1/128 :: U 0 7 0 lo
2001:6f8:900:4bd::/128 :: U 0 0 0 lo
2001:6f8:900:4bd::2/128 :: U 0 75 0 lo
2001:6f8:900:4bd::/64 :: UA 256 78 1 sit1
2001:6f8:1378::1/128 :: U 0 1143 0 lo
2001:6f8:1378::/64 :: U 1024 0 0 bond0
fe80::5499:edbe/128 :: U 0 0 0 lo
fe80::200:cbff:fe62:907d/128 :: U 0 0 0 lo
fe80::200:cbff:fe62:e16a/128 :: U 0 0 0 lo
fe80::/64 :: UA 256 0 0 eth0
fe80::/64 :: UA 256 0 0 eth1
fe80::/64 :: UA 256 0 0 eth2
fe80::/64 :: UA 256 0 0 bond0
fe80::/64 :: UA 256 0 0 sit1
ff00::/8 :: UA 256 0 0 eth0
ff00::/8 :: UA 256 0 0 eth1
ff00::/8 :: UA 256 0 0 eth2
ff00::/8 :: UA 256 0 0 bond0
ff00::/8 :: UA 256 0 0 sit1
::/0 2001:6f8:900:4bd::1 UG 1024 120 0 sit1
Weird Problem with routing to LAN
Shadow Hawkins on Monday, 04 April 2005 13:52:42
OK,
you can safely delete this thread if needed.
I solved it, the error was sure in the wrong prefix length,
also used now ip route .../48 dev ....
and ifconfig [device].../64...
Now it works again.
Regards
Sebastian
Posting is only allowed when you are logged in. |