|
Route problems?
![[ie]](/s/countries/ie.gif) Shadow Hawkins on Friday, 25 May 2007 00:38:55
I seem to be having a problem setting up a static tunnel. If I tcpdump the receiving end I can see my pings come in but nothing comes back. I suspect its going somewhere it shouldn't be due to the slightly weird network setup.
sixxs Link encap:IPv6-in-IPv4
inet6 addr: 2001:4830:1600:84::2/64 Scope:Global
inet6 addr: fe80::d065:34e2/128 Scope:Link
UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:380 dropped:0 overruns:0 carrier:380
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
conor@atlantis [~]# /sbin/ip -6 route
2001:4830:1600:84::/64 via :: dev sixxs metric 256 expires 2132897sec mtu 1280 advmss 1220 hoplimit 64
::/1 via 2001:4830:1600:84::1 dev sixxs metric 1024 expires 2133130sec mtu 1280 advmss 1220 hoplimit 64
fe80::/64 dev eth0 metric 256 expires 86596sec mtu 1500 advmss 1220 hoplimit 64
fe80::/64 dev eth1 metric 256 expires 86596sec mtu 1500 advmss 1220 hoplimit 64
fe80::/64 via :: dev sixxs metric 256 expires 2132897sec mtu 1280 advmss 1220 hoplimit 64
ff00::/8 dev eth0 metric 256 expires 86596sec mtu 1500 advmss 1220 hoplimit 1
ff00::/8 dev eth1 metric 256 expires 86596sec mtu 1500 advmss 1220 hoplimit 1
ff00::/8 dev sixxs metric 256 expires 2132897sec mtu 1280 advmss 1220 hoplimit 1
default via 2001:4830:1600:84::1 dev sixxs metric 1024 expires 2132897sec mtu 1280 advmss 1220 hoplimit 64
Route problems?
No bits sent or received on the tunnel interface.
Start reading "Reporting Problems" on the contact page this will help you narrow down the problem. Don't forget to check your firewall, tunnel endpoints etc etc, see the list.
Route problems?
![[nl]](/s/countries/nl.gif) Shadow Hawkins on Friday, 25 May 2007 12:47:34
I just notice traffix on the sit1 interface without a problem:
sit1 Link encap:IPv6-in-IPv4
inet6 addr: 2001:960:2:595::2/64 Scope:Global
inet6 addr: fe80::54f4:849b/64 Scope:Link
inet6 addr: fe80::c0a8:9001/64 Scope:Link
inet6 addr: fe80::c0a8:9101/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MTU:1480 Metric:1
RX packets:370032 errors:0 dropped:0 overruns:0 frame:0
TX packets:407950 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:28890725 (27.5 MiB) TX bytes:263673284 (251.4 MiB)
To the best of my knowledge it will have packet and octet counters but not much else. No hardware counters like error, collisions, .... (Not like the pseudo interface which have none of these at all.)
Route problems?
Shadow Hawkins on Friday, 25 May 2007 18:00:23
I've been digging about and it seems there is something with my version and/or iptable rules that is affecting it. If I restart iptables, I am able to get a connection via IPv6 but after a few minutes of being idle I loose my IPv6 connectivity.
I've been looking through the FAQ and there is a mention of it happening but when it is also a NAT end point which this server is not.
Is there anywhere specific I should be looking in the iptables -L output to see if IPv6 is being blocked/filtered somewhere
Route problems?
Most, if not all, Linux kernels are build with the "Connection Tracking" option activated. When that is present it can cause the effect of dropping connections after a timeout occurs.
Route problems?
Shadow Hawkins on Monday, 28 May 2007 18:25:22
I've added the gateways IPv4 address to my firewall's whitelist and my tunnel seems to be staying up without an issue now. Of course only time will tell now.
|
![[ch]](/s/countries/ch.gif)
on Friday, 25 May 2007 09:02:25
Posting is only allowed when you are