SixXS::Sunset 2017-06-06

IPv6 Tunnel Problem - Debian
[de] Carmen Sandiego on Thursday, 22 April 2004 13:23:00
Hello, I have a problem, my internal IPv6 works fine but when i want go out to the Internet i got "no route to host". Where is the fault? I suggest the Router or Hearbeat Software with wrong Time. My system: Debian 3.0 Woody/Sid (pinning) 100 Mbits Ipv4+Ipv6 its behind a router, i think a NAT router. Ifconfig says: sixxs Link encap:IPv6-in-IPv4 inet6 addr: 2001:6f8:900:1f9::2/64 Scope:Global inet6 addr: fe80::c0a8:4/64 Scope:Link UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:1316 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:163136 (159.3 KiB) and the Time (synced with ntpdate ntp0.fau.de): 22 Apr 12:10:58 ntpdate[17889]: step time server 131.188.3.220 offset -3.799100 sec (wrong timezone?!) Any suggestions? BTW I live in Germany Timezone is set to CEST
IPv6 Tunnel Problem - Debian
[de] Carmen Sandiego on Thursday, 22 April 2004 13:05:59
My ping6 result: server:~/heartbeat/client# ping6 2001:6f8:900:1f9::1 PING 2001:6f8:900:1f9::1(2001:6f8:900:1f9::1) from 2001:6f8:900:1f9::2 : 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:900:1f9::1 ping statistics --- 3 packets transmitted, 0 received, +3 errors, 100% loss, time 2001ms i pinged my pop ipv6, its still not working, and here the ping for ipv4: server:~/heartbeat/client# ping 212.224.0.188 PING 212.224.0.188 (212.224.0.188) from 192.168.0.4 : 56(84) bytes of data. 64 bytes from 212.224.0.188: icmp_seq=1 ttl=58 time=39.3 ms 64 bytes from 212.224.0.188: icmp_seq=2 ttl=58 time=27.2 ms 64 bytes from 212.224.0.188: icmp_seq=3 ttl=58 time=25.7 ms --- 212.224.0.188 ping statistics --- 3 packets transmitted, 3 received, 0% loss, time 2001ms rtt min/avg/max/mdev = 25.723/30.787/39.349/6.090 ms
IPv6 Tunnel Problem - Debian
[de] Carmen Sandiego on Thursday, 22 April 2004 13:21:22
sorry for double post
IPv6 Tunnel Problem - Debian
[ch] Jeroen Massar SixXS Staff on Thursday, 22 April 2004 13:23:32
Tripple post ;) Anyhow... check your routing tables as the error is returned from ::1 (localhost).
IPv6 Tunnel Problem - Debian
[de] Carmen Sandiego on Thursday, 22 April 2004 13:32:14
my routing table: Kernel IPv6 routing table Destination Next Hop Flags Metric Ref Use Iface ::1/128 :: U 0 4 0 lo 2001:6f8:900:1f9::2/128 :: U 0 50 0 lo 2001:6f8:900:1f9::/64 :: U 256 18 0 sixxs 2000::/3 2001:6f8:900:1f9::1 UG 1024 1342 0 sixxs fe80::c0a8:4/128 :: U 0 0 0 lo fe80::280:5fff:fe06:a1ab/128 :: U 0 0 0 lo fe80::/64 :: U 256 0 0 eth0 fe80::/64 :: U 256 0 0 sixxs ff00::/8 :: U 256 0 0 eth0 ff00::/8 :: U 256 0 0 sixxs ::/0 :: UD 256 0 0 eth0 ::/0 2001:6f8:900:1f9::1 UG 1024 0 0 sixxs what is wrong? btw i use Kernel 2.6.5
IPv6 Tunnel Problem - Debian
[ch] Jeroen Massar SixXS Staff on Thursday, 22 April 2004 13:43:11
Wow neat 2 default routes one going into oblivion and also with a lower metric... Though the 2000::/3 should precede it and be used. Fix those, check your firewalling rules and then start tcpdumping to figure out what is going wrong.
IPv6 Tunnel Problem - Debian
[de] Carmen Sandiego on Thursday, 22 April 2004 14:03:58
Sorry i dont know how to "modify" the routing tables, can you give me the commands to delete all needless routes and add the routes that i need. When i run tcpdump i always get the TCP Packages from my ssh connection (a lot) because im connecting from outside to this box. DMZ is enabled for this box :O

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker