Tunnel not staying up
Shadow Hawkins on Thursday, 13 November 2008 07:34:22
Hello,
System: Debian etch (2.6.18-6-k7)
I'm having troubles with my tunnel. I can get it up and ping works... for 5-10 minutes ok. Then it suddently breaks down and i have to restart the tunnel. I think this is because of iptables firewall. I tried -proto 41 NOTRACK, but it just broke it for good. Any ideas for me?
Tunnel not staying up
Shadow Hawkins on Thursday, 13 November 2008 07:35:21
Couple more things..
I do not have NAT
Should i open these: https://www.sixxs.net/faq/connectivity/?faq=firewalled ??
Tunnel not staying up
Jeroen Massar on Thursday, 13 November 2008 07:36:18
Start by going through the "Reporting Problems" list on the contact page, that list is a general way of trying to figure out what possibly could go wrong.
Tunnel not staying up
Shadow Hawkins on Thursday, 13 November 2008 08:31:22
Thanks, but not helping.. :(
PoP Name fihel01
IPv6 Prefix 2001:14b8:100:201::1/64
PoP IPv6 2001:14b8:100:201::1
Your IPv6 2001:14b8:100:201::2
Tunnel not staying up
Shadow Hawkins on Thursday, 13 November 2008 08:33:31
Tag [/code] is not closed
Tunnel not staying up
Jeroen Massar on Thursday, 13 November 2008 09:41:59 default via fe80::20b:45ff:fe4c:8c01 dev eth1 proto kernel metric 1024 expires 1704sec mtu 1500 advmss 1220 hoplimit 64 default via 2001:14b8:100:201::1 dev sixxs metric 1024 expires 21192477sec mtu 1280 advmss 1220 hoplimit 4294967295
Two default routes? It seems that you have another device on eth1 that thinks it is a router. Check for router advertisements on that link. (Turning on IPv6 Forwarding on linux generally disables the acceptance of those RA's though).
Metrics are the same, thus default route will alternate between the two default routes.
As for those firewall rules, if you are having issues, always clear your firewall or do proper LOG for packets you DROP or REJECT.
Tunnel not staying up
Shadow Hawkins on Thursday, 13 November 2008 09:53:34
Thanks! Let's see if it works..
Tunnel not staying up
Shadow Hawkins on Tuesday, 18 November 2008 19:10:10
Ok. i'm bringin this up since nothing works.
I'm getting these in log file:
Nov 18 20:08:22 antares kernel: INPUT packet died: IN=eth1 OUT= MAC=00:06:4f:17:fc:60:00:0b:45:4c:8c:01:08:00 SRC=84.73.229.1 DST=84.20.147.248 LEN=64 TOS=0x00 PREC=0x00 TTL=38 ID=19367 DF PROTO=TCP SPT=4010 DPT=135 WINDOW=53760 RES=0x00 SYN URGP=0
Nov 18 20:08:25 antares kernel: INPUT packet died: IN=eth1 OUT= MAC=00:06:4f:17:fc:60:00:0b:45:4c:8c:01:08:00 SRC=84.73.229.1 DST=84.20.147.248 LEN=64 TOS=0x00 PREC=0x00 TTL=38 ID=20185 DF PROTO=TCP SPT=4010 DPT=135 WINDOW=53760 RES=0x00 SYN URGP=0
DST is my ipv4
I'm going to lose this tunnel soon if nothing works :( please?
Tunnel not staying up
Jeroen Massar on Tuesday, 18 November 2008 19:13:54
I would suggest google(INPUT packet died) which results in: this
aka fix your firewall. But as that is Samba (port 135) nothing related to SixXS.
Tunnel not staying up
Shadow Hawkins on Tuesday, 18 November 2008 19:15:26
I appreciate, thank you.
Tunnel not staying up
Shadow Hawkins on Tuesday, 18 November 2008 22:58:39
Isn't TCP/135 usually for RPC traffic?
Tunnel not staying up
Shadow Hawkins on Tuesday, 18 November 2008 23:03:38
The most simple suggestion is to remove IPv6 from eth0 for now. If your tunnel becomes stable you know there is another IPv6 device on your ethernet network that you need to fix.
If not it could be an firewall issue. Or a number of other things that we need to look at but Jeroen is right that you need to fix these alternative routes first before you do any other troubleshooting.
Tunnel not staying up
Carmen Sandiego on Tuesday, 24 February 2009 03:50:29
I'm having a similar problem...the route stays up for 20-30 minutes, then dies. If I ping an outside machine from the problem machine, only then can I ping in from the outside.
How does one disable the default fe80 addresses from eth0?
Tunnel not staying up
Carmen Sandiego on Tuesday, 24 February 2009 04:02:24
Disregard...was pointed to radvd as the solution to the problem.
Posting is only allowed when you are logged in. |