|
Debian IPv6 Setup (XEN Dom0)
![[de]](/s/countries/de.gif) Shadow Hawkins on Tuesday, 09 March 2010 22:07:50
HI there,
i'm trying to setup my static tunnel (T17783) on a Debian System for 4 days now and i'm a bit lost in searching for the problem.
From my understanding I setup everything correct and according to the FAQ entry.
This is my /etc/network/interfaces part:
# device: sixxs (6to4 tunnel interface)
auto sixxs
iface sixxs inet6 v4tunnel
address 2a01:198:200:254::2
netmask 64
endpoint 91.184.37.98
local 78.46.93.49
ttl 64
up ip link set mtu 1280 dev sixxs
up ip route add default via 2a01:198:200:254::1 dev sixxs
up ip -6 route flush dev eth0
down ip -6 route flush dev sixxs
This is the interface:
sixxs Link encap:IPv6-in-IPv4
inet6 addr: 2a01:198:200:254::2/64 Scope:Global
inet6 addr: fe80::4e2e:5d31/128 Scope:Link
UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:266 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:32984 (32.2 KiB)
This is the ipv6 routing table:
2a01:198:200:254::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220 hoplimit 4294967295
fe80::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220 hoplimit 4294967295
fe80::/64 dev vif1.0 metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev vif2.0 metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
default via 2a01:198:200:254::1 dev sixxs metric 1024 mtu 1280 advmss 1220 hoplimit 4294967295
These are the pings:
###### ipv4
dampfbad:~# ping 91.184.37.98
PING 91.184.37.98 (91.184.37.98) 56(84) bytes of data.
64 bytes from 91.184.37.98: icmp_seq=1 ttl=59 time=8.79 ms
64 bytes from 91.184.37.98: icmp_seq=2 ttl=59 time=8.24 ms
64 bytes from 91.184.37.98: icmp_seq=3 ttl=59 time=8.39 ms
64 bytes from 91.184.37.98: icmp_seq=4 ttl=59 time=9.24 ms
^C
--- 91.184.37.98 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3010ms
rtt min/avg/max/mdev = 8.244/8.671/9.246/0.394 ms
dampfbad:~# ping 78.46.93.49
PING 78.46.93.49 (78.46.93.49) 56(84) bytes of data.
64 bytes from 78.46.93.49: icmp_seq=1 ttl=64 time=0.040 ms
64 bytes from 78.46.93.49: icmp_seq=2 ttl=64 time=0.016 ms
64 bytes from 78.46.93.49: icmp_seq=3 ttl=64 time=0.022 ms
64 bytes from 78.46.93.49: icmp_seq=4 ttl=64 time=0.019 ms
64 bytes from 78.46.93.49: icmp_seq=5 ttl=64 time=0.020 ms
^C
--- 78.46.93.49 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3997ms
rtt min/avg/max/mdev = 0.016/0.023/0.040/0.009 ms
dampfbad:~#
###### ipv6
dampfbad:~# ping6 2a01:198:200:254::1
PING 2a01:198:200:254::1(2a01:198:200:254::1) 56 data bytes
^C
--- 2a01:198:200:254::1 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 9014ms
dampfbad:~# ping6 2a01:198:200:254::2
PING 2a01:198:200:254::2(2a01:198:200:254::2) 56 data bytes
64 bytes from 2a01:198:200:254::2: icmp_seq=1 ttl=64 time=0.024 ms
64 bytes from 2a01:198:200:254::2: icmp_seq=2 ttl=64 time=0.012 ms
64 bytes from 2a01:198:200:254::2: icmp_seq=3 ttl=64 time=0.029 ms
64 bytes from 2a01:198:200:254::2: icmp_seq=4 ttl=64 time=0.011 ms
64 bytes from 2a01:198:200:254::2: icmp_seq=5 ttl=64 time=0.019 ms
64 bytes from 2a01:198:200:254::2: icmp_seq=6 ttl=64 time=0.011 ms
64 bytes from 2a01:198:200:254::2: icmp_seq=7 ttl=64 time=0.015 ms
^C
--- 2a01:198:200:254::2 ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 5997ms
rtt min/avg/max/mdev = 0.011/0.017/0.029/0.007 ms
dampfbad:~#
I don't see where the problem is. I tried with aiccu and with a different approach of creating the interface with script:
#!/bin/sh
modprobe ipv6
# Create tunnel
ip tunnel add sixxs mode sit local 78.46.93.49 remote 91.184.37.98
# Bring tunnel up
ip link set sixxs up
# Set MTU
ip link set mtu 1280 dev sixxs
# Change TTL
ip tunnel change sixxs ttl 64
# Add 1. IP
ip -6 addr add 2a01:198:200:254::2/64 dev sixxs
# Default IPv6 Route
ip -6 ro add default via 2a01:198:200:254::1 dev sixxs
Maybe it is something 'special' about the routing inside XEN? Like I said, I want to create the tunnel inside the root system (dom0) of a XEN system.
Thanks for you input!
Best regards
Philipp
Debian IPv6 Setup (XEN Dom0)
Shadow Hawkins on Tuesday, 09 March 2010 22:09:47
Step2 should be to get autoconfiguration working properly from Dom0 (Host) to DomU (Guests).
But without the tunnel, no subnet for the the guests.
Best regards
Philipp
Debian IPv6 Setup (XEN Dom0)
# device: sixxs (6to4 tunnel interface)
6to4 is 2002::/16, what you have there is a plain old proto-41 tunnel.
up ip -6 route flush dev eth0 down ip -6 route flush dev sixxs
Why are you doing that? If an interface gets removed it gets deconfigured anyway, thus no need to do this.
Maybe it is something 'special' about the routing inside XEN? Like I said, I want to create the tunnel inside the root system (dom0) of a XEN system.
Or something is filtering protocol 41 or even on the IPv6 level. Check your own IPv4 (iptables) and IPv6 (ip6tables) firewalls, and also hope that between you and the PoP there are no firewalls enabled for this.
Tcpdump is also a good friend. For the rest see the contact page "Reporting Problems" list for details that you should list here if you want people to properly help you out.
As you seem to have been messing around a lot, you definitely need to provide those details as something ugly might have been left behind.
AICCU btw is something you don't want to use when you have a static tunnel and an ability to let the OS configure your tunnel.
Debian IPv6 Setup (XEN Dom0)
Shadow Hawkins on Friday, 12 March 2010 14:33:45
Hi Jeroen,
and to provide you the needed details with this reply.
uname -a
Linux dampfbad.5711.org 2.6.26-1-xen-amd64 #1 SMP Fri Mar 13 21:39:38 UTC 2009 x86_64 GNU/Linux
My IPv4 and IPv6 iptables are not filtering anything as their default action for INPUT, FORWARD and OUTPUT chains are ACCEPT (for testing purposes).
tcpdump (while running a ping6 to ipv6.google.com)
dampfbad:~# tcpdump -n 'proto 41'
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
14:17:00.087226 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2 > 2a00:1450:8001::6a: ICMP6, echo request, seq 1, length 64
14:17:01.088235 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2 > 2a00:1450:8001::6a: ICMP6, echo request, seq 2, length 64
14:17:02.088260 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2 > 2a00:1450:8001::6a: ICMP6, echo request, seq 3, length 64
...
tcpdump (while running a ping6 to the POP ipv6 endpoint)
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
14:19:11.307808 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2 > 2a01:198:200:254::1: ICMP6, echo request, seq 1, length 64
14:19:12.320251 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2 > 2a01:198:200:254::1: ICMP6, echo request, seq 2, length 64
14:19:13.320250 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2 > 2a01:198:200:254::1: ICMP6, echo request, seq 3, length 64
14:19:14.320223 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2 > 2a01:198:200:254::1: ICMP6, echo request, seq 4, length 64
...
ping to ipv4 endpoint
PING 91.184.37.98 (91.184.37.98) 56(84) bytes of data.
64 bytes from 91.184.37.98: icmp_seq=1 ttl=59 time=9.00 ms
64 bytes from 91.184.37.98: icmp_seq=3 ttl=59 time=8.37 ms
64 bytes from 91.184.37.98: icmp_seq=4 ttl=59 time=8.22 ms
64 bytes from 91.184.37.98: icmp_seq=5 ttl=59 time=8.23 ms
64 bytes from 91.184.37.98: icmp_seq=6 ttl=59 time=9.30 ms
64 bytes from 91.184.37.98: icmp_seq=7 ttl=59 time=8.17 ms
64 bytes from 91.184.37.98: icmp_seq=8 ttl=59 time=8.18 ms
^C
--- 91.184.37.98 ping statistics ---
8 packets transmitted, 7 received, 12% packet loss, time 7022ms
rtt min/avg/max/mdev = 8.170/8.499/9.308/0.430 ms
ping to local ipv6 IP
PING 2a01:198:200:254::2(2a01:198:200:254::2) 56 data bytes
64 bytes from 2a01:198:200:254::2: icmp_seq=1 ttl=64 time=0.031 ms
64 bytes from 2a01:198:200:254::2: icmp_seq=2 ttl=64 time=0.011 ms
64 bytes from 2a01:198:200:254::2: icmp_seq=3 ttl=64 time=0.022 ms
64 bytes from 2a01:198:200:254::2: icmp_seq=4 ttl=64 time=0.011 ms
^C
--- 2a01:198:200:254::2 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 0.011/0.018/0.031/0.009 ms
ping to local ipv4 IP
dampfbad:~# ping 78.46.93.49
PING 78.46.93.49 (78.46.93.49) 56(84) bytes of data.
64 bytes from 78.46.93.49: icmp_seq=1 ttl=64 time=0.027 ms
64 bytes from 78.46.93.49: icmp_seq=2 ttl=64 time=0.007 ms
64 bytes from 78.46.93.49: icmp_seq=3 ttl=64 time=0.011 ms
64 bytes from 78.46.93.49: icmp_seq=4 ttl=64 time=0.007 ms
^C
--- 78.46.93.49 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2997ms
rtt min/avg/max/mdev = 0.007/0.013/0.027/0.008 ms
dampfbad:~#
traceroute6 to ipv6 endpoint
traceroute to 2a01:198:200:254::1 (2a01:198:200:254::1), 30 hops max, 40 byte pa ckets
1 * * *
2 * * *
3 * * *
[...]
28 * * *
29 * * *
30 * * *
traceroute to ipv4 endpoint
traceroute to 91.184.37.98 (91.184.37.98), 30 hops max, 40 byte packets
1 static.33.93.46.78.clients.your-server.de (78.46.93.33) 0.810 ms 0.791 ms 0.932 ms
2 hos-tr3.juniper3.rz4.hetzner.de (213.239.244.129) 0.200 ms hos-tr2.juniper1.rz4.hetzner.de (213.239.244.65) 0.197 ms hos-tr1-juniper1.rz4.hetzner.de (213.239.244.1) 0.185 ms
3 hos-bb1.juniper2.ffm.hetzner.de (213.239.240.226) 3.450 ms 3.441 ms 3.428 ms
4 decix.r1.fra3.opencarrier.eu (80.81.192.24) 4.314 ms 5.040 ms 5.022 ms
5 oc-fra.speedpartner.de (194.54.95.218) 8.671 ms 8.383 ms 8.365 ms
6 dedus01.sixxs.net (91.184.37.98) 8.302 ms 8.266 ms 8.248 ms
interfaces
eth0 Link encap:Ethernet HWaddr 00:1d:92:39:33:f2
inet addr:78.46.93.49 Bcast:78.46.93.63 Mask:255.255.255.224
inet6 addr: fe80::21d:92ff:fe39:33f2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:399899 errors:0 dropped:0 overruns:0 frame:0
TX packets:396240 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:41563549 (39.6 MiB) TX bytes:66648845 (63.5 MiB)
Interrupt:19 Base address:0x2000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:48 errors:0 dropped:0 overruns:0 frame:0
TX packets:48 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5088 (4.9 KiB) TX bytes:5088 (4.9 KiB)
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
sixxs Link encap:IPv6-in-IPv4
inet6 addr: 2a01:198:200:254::2/64 Scope:Global
inet6 addr: fe80::4e2e:5d31/128 Scope:Link
UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:147 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:16788 (16.3 KiB)
vif1.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
inet addr:78.46.93.49 Bcast:78.255.255.255 Mask:255.255.255.255
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:170154 errors:0 dropped:0 overruns:0 frame:0
TX packets:210780 errors:0 dropped:5 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:28473575 (27.1 MiB) TX bytes:21332294 (20.3 MiB)
vif2.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
inet addr:78.46.93.49 Bcast:78.255.255.255 Mask:255.255.255.255
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:85808 errors:0 dropped:0 overruns:0 frame:0
TX packets:75370 errors:0 dropped:2 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:13204920 (12.5 MiB) TX bytes:8096635 (7.7 MiB)
routing-table (ipv6)
2a01:198:200:254::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220 hoplimit 4294967295
fe80::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220 hoplimit 4294967295
fe80::/64 dev vif1.0 metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev vif2.0 metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
default via 2a01:198:200:254::1 dev sixxs metric 1024 mtu 1280 advmss 1220 hoplimit 4294967295
routing-table (ipv4)
88.198.130.76 dev vif2.0 scope link src 78.46.93.49
88.198.130.74 dev vif1.0 scope link src 78.46.93.49
88.198.130.72/29 dev eth0 proto kernel scope link src 88.198.130.73
78.46.93.32/27 via 78.46.93.33 dev eth0
78.46.93.32/27 dev eth0 proto kernel scope link src 78.46.93.49
default via 78.46.93.33 dev eth0
PoP is according to PoP-Status Page up and running.
If there is anything else you need to know to help me. Just let me know.
Thanks for sharing your thoughts!
Best regards
Philipp
Debian IPv6 Setup (XEN Dom0)
tcpdump (while running a ping6 to ipv6.google.com)
Why bother trying to reach something so remote?
dampfbad:~# tcpdump -n 'proto 41'
You can tcpdump all you want, but with that query you won't see the responses from any of the hops on the internet between you and the PoP. Also, as you didn't specify an interface, you just have to hope it selects the right one.
Debian IPv6 Setup (XEN Dom0)
Shadow Hawkins on Tuesday, 16 March 2010 12:59:52
traceroute towards ipv6 PoP endpoint.
dampfbad:~# traceroute6 2a01:198:200:254::1
traceroute to 2a01:198:200:254::1 (2a01:198:200:254::1), 30 hops max, 40 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
^C
tcpdump -n -i sixxs (while running a traceroute6)
dampfbad:~# tcpdump -n -i sixxs
tcpdump: WARNING: sixxs: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on sixxs, link-type RAW (Raw IP), capture size 96 bytes
11:08:14.267937 IP6 2a01:198:200:254::2.47671 > 2a01:198:200:254::1.33434: UDP, length 40
11:08:14.267970 IP6 2a01:198:200:254::2.53566 > 2a01:198:200:254::1.33435: UDP, length 40
11:08:14.268010 IP6 2a01:198:200:254::2.41558 > 2a01:198:200:254::1.33436: UDP, length 40
11:08:14.268032 IP6 2a01:198:200:254::2.50043 > 2a01:198:200:254::1.33437: UDP, length 40
11:08:14.268059 IP6 2a01:198:200:254::2.39662 > 2a01:198:200:254::1.33438: UDP, length 40
11:08:14.268082 IP6 2a01:198:200:254::2.58543 > 2a01:198:200:254::1.33439: UDP, length 40
11:08:14.268105 IP6 2a01:198:200:254::2.56563 > 2a01:198:200:254::1.33440: UDP, length 40
11:08:14.268135 IP6 2a01:198:200:254::2.45627 > 2a01:198:200:254::1.33441: UDP, length 40
11:08:14.268159 IP6 2a01:198:200:254::2.50643 > 2a01:198:200:254::1.33442: UDP, length 40
11:08:14.268186 IP6 2a01:198:200:254::2.40596 > 2a01:198:200:254::1.33443: UDP, length 40
11:08:14.268211 IP6 2a01:198:200:254::2.57057 > 2a01:198:200:254::1.33444: UDP, length 40
11:08:14.268233 IP6 2a01:198:200:254::2.60541 > 2a01:198:200:254::1.33445: UDP, length 40
11:08:14.268265 IP6 2a01:198:200:254::2.42101 > 2a01:198:200:254::1.33446: UDP, length 40
11:08:14.268287 IP6 2a01:198:200:254::2.35116 > 2a01:198:200:254::1.33447: UDP, length 40
11:08:14.268310 IP6 2a01:198:200:254::2.45383 > 2a01:198:200:254::1.33448: UDP, length 40
11:08:14.268334 IP6 2a01:198:200:254::2.39573 > 2a01:198:200:254::1.33449: UDP, length 40
11:08:19.273066 IP6 2a01:198:200:254::2.57061 > 2a01:198:200:254::1.33450: UDP, length 40
11:08:19.273096 IP6 2a01:198:200:254::2.59092 > 2a01:198:200:254::1.33451: UDP, length 40
11:08:19.273119 IP6 2a01:198:200:254::2.38286 > 2a01:198:200:254::1.33452: UDP, length 40
11:08:19.273140 IP6 2a01:198:200:254::2.42041 > 2a01:198:200:254::1.33453: UDP, length 40
11:08:19.273162 IP6 2a01:198:200:254::2.55632 > 2a01:198:200:254::1.33454: UDP, length 40
11:08:19.273192 IP6 2a01:198:200:254::2.51312 > 2a01:198:200:254::1.33455: UDP, length 40
11:08:19.273214 IP6 2a01:198:200:254::2.46737 > 2a01:198:200:254::1.33456: UDP, length 40
11:08:19.273235 IP6 2a01:198:200:254::2.57512 > 2a01:198:200:254::1.33457: UDP, length 40
11:08:19.273256 IP6 2a01:198:200:254::2.38654 > 2a01:198:200:254::1.33458: UDP, length 40
11:08:19.273277 IP6 2a01:198:200:254::2.43148 > 2a01:198:200:254::1.33459: UDP, length 40
11:08:19.273299 IP6 2a01:198:200:254::2.56175 > 2a01:198:200:254::1.33460: UDP, length 40
11:08:19.273329 IP6 2a01:198:200:254::2.43765 > 2a01:198:200:254::1.33461: UDP, length 40
11:08:19.273350 IP6 2a01:198:200:254::2.56060 > 2a01:198:200:254::1.33462: UDP, length 40
11:08:19.273371 IP6 2a01:198:200:254::2.45346 > 2a01:198:200:254::1.33463: UDP, length 40
11:08:19.273393 IP6 2a01:198:200:254::2.48395 > 2a01:198:200:254::1.33464: UDP, length 40
11:08:19.273422 IP6 2a01:198:200:254::2.58682 > 2a01:198:200:254::1.33465: UDP, length 40
11:08:24.280979 IP6 2a01:198:200:254::2.56407 > 2a01:198:200:254::1.33466: UDP, length 40
11:08:24.281008 IP6 2a01:198:200:254::2.40146 > 2a01:198:200:254::1.33467: UDP, length 40
11:08:24.281030 IP6 2a01:198:200:254::2.46500 > 2a01:198:200:254::1.33468: UDP, length 40
11:08:24.281052 IP6 2a01:198:200:254::2.44787 > 2a01:198:200:254::1.33469: UDP, length 40
11:08:24.281074 IP6 2a01:198:200:254::2.42443 > 2a01:198:200:254::1.33470: UDP, length 40
11:08:24.281105 IP6 2a01:198:200:254::2.33812 > 2a01:198:200:254::1.33471: UDP, length 40
11:08:24.281127 IP6 2a01:198:200:254::2.45395 > 2a01:198:200:254::1.33472: UDP, length 40
11:08:24.281149 IP6 2a01:198:200:254::2.54674 > 2a01:198:200:254::1.33473: UDP, length 40
11:08:24.281171 IP6 2a01:198:200:254::2.41812 > 2a01:198:200:254::1.33474: UDP, length 40
11:08:24.281192 IP6 2a01:198:200:254::2.49936 > 2a01:198:200:254::1.33475: UDP, length 40
11:08:24.281222 IP6 2a01:198:200:254::2.47426 > 2a01:198:200:254::1.33476: UDP, length 40
11:08:24.281244 IP6 2a01:198:200:254::2.37390 > 2a01:198:200:254::1.33477: UDP, length 40
11:08:24.281266 IP6 2a01:198:200:254::2.36223 > 2a01:198:200:254::1.33478: UDP, length 40
11:08:24.281287 IP6 2a01:198:200:254::2.38501 > 2a01:198:200:254::1.33479: UDP, length 40
11:08:24.281309 IP6 2a01:198:200:254::2.56012 > 2a01:198:200:254::1.33480: UDP, length 40
11:08:24.281338 IP6 2a01:198:200:254::2.37568 > 2a01:198:200:254::1.33481: UDP, length 40
11:08:29.289015 IP6 2a01:198:200:254::2.48789 > 2a01:198:200:254::1.33482: UDP, length 40
11:08:29.289045 IP6 2a01:198:200:254::2.47191 > 2a01:198:200:254::1.33483: UDP, length 40
11:08:29.289067 IP6 2a01:198:200:254::2.50968 > 2a01:198:200:254::1.33484: UDP, length 40
11:08:29.289089 IP6 2a01:198:200:254::2.50714 > 2a01:198:200:254::1.33485: UDP, length 40
11:08:29.289110 IP6 2a01:198:200:254::2.33755 > 2a01:198:200:254::1.33486: UDP, length 40
11:08:29.289140 IP6 2a01:198:200:254::2.35335 > 2a01:198:200:254::1.33487: UDP, length 40
11:08:29.289161 IP6 2a01:198:200:254::2.49768 > 2a01:198:200:254::1.33488: UDP, length 40
11:08:29.289182 IP6 2a01:198:200:254::2.60382 > 2a01:198:200:254::1.33489: UDP, length 40
11:08:29.289203 IP6 2a01:198:200:254::2.52641 > 2a01:198:200:254::1.33490: UDP, length 40
11:08:29.289224 IP6 2a01:198:200:254::2.41843 > 2a01:198:200:254::1.33491: UDP, length 40
11:08:29.289245 IP6 2a01:198:200:254::2.54011 > 2a01:198:200:254::1.33492: UDP, length 40
11:08:29.289274 IP6 2a01:198:200:254::2.37972 > 2a01:198:200:254::1.33493: UDP, length 40
11:08:29.289295 IP6 2a01:198:200:254::2.35597 > 2a01:198:200:254::1.33494: UDP, length 40
11:08:29.289316 IP6 2a01:198:200:254::2.56989 > 2a01:198:200:254::1.33495: UDP, length 40
11:08:29.289337 IP6 2a01:198:200:254::2.59829 > 2a01:198:200:254::1.33496: UDP, length 40
11:08:29.289366 IP6 2a01:198:200:254::2.53534 > 2a01:198:200:254::1.33497: UDP, length 40
^C
64 packets captured
64 packets received by filter
0 packets dropped by kernel
dampfbad:~#
tcpdump -n -i eth0 (while running the same traceroute6) / eth0 is the physical ipv4 interface towards the internet
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
11:08:14.267945 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.47671 > 2a01:198:200:254::1.33434 : UDP, length 40
11:08:14.267973 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.53566 > 2a01:198:200:254::1.33435 : UDP, length 40
11:08:14.268012 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.41558 > 2a01:198:200:254::1.33436 : UDP, length 40
11:08:14.268034 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.50043 > 2a01:198:200:254::1.33437 : UDP, length 40
11:08:14.268061 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.39662 > 2a01:198:200:254::1.33438 : UDP, length 40
11:08:14.268084 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.58543 > 2a01:198:200:254::1.33439 : UDP, length 40
11:08:14.268107 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.56563 > 2a01:198:200:254::1.33440 : UDP, length 40
11:08:14.268137 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.45627 > 2a01:198:200:254::1.33441 : UDP, length 40
11:08:14.268161 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.50643 > 2a01:198:200:254::1.33442 : UDP, length 40
11:08:14.268188 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.40596 > 2a01:198:200:254::1.33443 : UDP, length 40
11:08:14.268213 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.57057 > 2a01:198:200:254::1.33444 : UDP, length 40
11:08:14.268236 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.60541 > 2a01:198:200:254::1.33445 : UDP, length 40
11:08:14.268267 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.42101 > 2a01:198:200:254::1.33446 : UDP, length 40
11:08:14.268289 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.35116 > 2a01:198:200:254::1.33447 : UDP, length 40
11:08:14.268312 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.45383 > 2a01:198:200:254::1.33448 : UDP, length 40
11:08:14.268336 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.39573 > 2a01:198:200:254::1.33449 : UDP, length 40
11:08:19.273074 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.57061 > 2a01:198:200:254::1.33450 : UDP, length 40
11:08:19.273099 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.59092 > 2a01:198:200:254::1.33451 : UDP, length 40
11:08:19.273121 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.38286 > 2a01:198:200:254::1.33452 : UDP, length 40
11:08:19.273143 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.42041 > 2a01:198:200:254::1.33453 : UDP, length 40
11:08:19.273164 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.55632 > 2a01:198:200:254::1.33454 : UDP, length 40
11:08:19.273194 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.51312 > 2a01:198:200:254::1.33455 : UDP, length 40
11:08:19.273216 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.46737 > 2a01:198:200:254::1.33456 : UDP, length 40
11:08:19.273237 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.57512 > 2a01:198:200:254::1.33457 : UDP, length 40
11:08:19.273258 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.38654 > 2a01:198:200:254::1.33458 : UDP, length 40
11:08:19.273279 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.43148 > 2a01:198:200:254::1.33459 : UDP, length 40
11:08:19.273307 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.56175 > 2a01:198:200:254::1.33460 : UDP, length 40
11:08:19.273330 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.43765 > 2a01:198:200:254::1.33461 : UDP, length 40
11:08:19.273352 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.56060 > 2a01:198:200:254::1.33462 : UDP, length 40
11:08:19.273373 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.45346 > 2a01:198:200:254::1.33463 : UDP, length 40
11:08:19.273395 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.48395 > 2a01:198:200:254::1.33464 : UDP, length 40
11:08:19.273424 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.58682 > 2a01:198:200:254::1.33465 : UDP, length 40
11:08:24.280986 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.56407 > 2a01:198:200:254::1.33466: UDP, length 40
11:08:24.281011 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.40146 > 2a01:198:200:254::1.33467: UDP, length 40
11:08:24.281033 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.46500 > 2a01:198:200:254::1.33468: UDP, length 40
11:08:24.281054 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.44787 > 2a01:198:200:254::1.33469: UDP, length 40
11:08:24.281076 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.42443 > 2a01:198:200:254::1.33470: UDP, length 40
11:08:24.281108 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.33812 > 2a01:198:200:254::1.33471: UDP, length 40
11:08:24.281129 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.45395 > 2a01:198:200:254::1.33472: UDP, length 40
11:08:24.281151 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.54674 > 2a01:198:200:254::1.33473: UDP, length 40
11:08:24.281173 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.41812 > 2a01:198:200:254::1.33474: UDP, length 40
11:08:24.281195 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.49936 > 2a01:198:200:254::1.33475: UDP, length 40
11:08:24.281224 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.47426 > 2a01:198:200:254::1.33476: UDP, length 40
11:08:24.281246 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.37390 > 2a01:198:200:254::1.33477: UDP, length 40
11:08:24.281268 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.36223 > 2a01:198:200:254::1.33478: UDP, length 40
11:08:24.281289 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.38501 > 2a01:198:200:254::1.33479: UDP, length 40
11:08:24.281311 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.56012 > 2a01:198:200:254::1.33480: UDP, length 40
11:08:24.281340 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.37568 > 2a01:198:200:254::1.33481: UDP, length 40
11:08:29.289023 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.48789 > 2a01:198:200:254::1.33482: UDP, length 40
11:08:29.289048 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.47191 > 2a01:198:200:254::1.33483: UDP, length 40
11:08:29.289070 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.50968 > 2a01:198:200:254::1.33484: UDP, length 40
11:08:29.289091 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.50714 > 2a01:198:200:254::1.33485: UDP, length 40
11:08:29.289112 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.33755 > 2a01:198:200:254::1.33486: UDP, length 40
11:08:29.289142 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.35335 > 2a01:198:200:254::1.33487: UDP, length 40
11:08:29.289163 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.49768 > 2a01:198:200:254::1.33488: UDP, length 40
11:08:29.289184 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.60382 > 2a01:198:200:254::1.33489: UDP, length 40
11:08:29.289205 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.52641 > 2a01:198:200:254::1.33490: UDP, length 40
11:08:29.289226 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.41843 > 2a01:198:200:254::1.33491: UDP, length 40
11:08:29.289248 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.54011 > 2a01:198:200:254::1.33492: UDP, length 40
11:08:29.289276 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.37972 > 2a01:198:200:254::1.33493: UDP, length 40
11:08:29.289297 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.35597 > 2a01:198:200:254::1.33494: UDP, length 40
11:08:29.289318 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.56989 > 2a01:198:200:254::1.33495: UDP, length 40
11:08:29.289339 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.59829 > 2a01:198:200:254::1.33496: UDP, length 40
11:08:29.289368 IP 78.46.93.49 > 91.184.37.98: IP6 2a01:198:200:254::2.53534 > 2a01:198:200:254::1.33497: UDP, length 40
^C
dampfbad:~#
from my understanding i'd say it leaves my system correctly but there is no reply. hmm.
Debian IPv6 Setup (XEN Dom0)
Shadow Hawkins on Tuesday, 16 March 2010 11:18:32
ieeks. sorry for bad formatting..
Debian IPv6 Setup (XEN Dom0)
dampfbad:~# traceroute6 2a01:198:200:254::1
What does the actual routing table look like?
dampfbad:~# tcpdump -n -i sixxs
That shows what your host is sending through the tunnel, not what it is actually transmitting to the PoP. Thus not very useful.
tcpdump -n -i eth0 (while running the same traceroute6) / eth0 is the physical ipv4 interface towards the internet
Did you add any filter statements? As you don't have any other traffic there, which is rather strange.
Maybe you have a firewall somewhere that is bothering (=filtering) you?
Debian IPv6 Setup (XEN Dom0)
Shadow Hawkins on Tuesday, 16 March 2010 14:45:15What does the actual routing table look like?
dampfbad:~# ip route
88.198.130.76 dev vif2.0 scope link src 78.46.93.49
88.198.130.74 dev vif1.0 scope link src 78.46.93.49
88.198.130.72/29 dev eth0 proto kernel scope link src 88.198.130.73
78.46.93.32/27 via 78.46.93.33 dev eth0
78.46.93.32/27 dev eth0 proto kernel scope link src 78.46.93.49
default via 78.46.93.33 dev eth0
dampfbad:~#
dampfbad:~# ip -6 route
2a01:198:200:254::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220 hoplimit 4294967295
fe80::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220 hoplimit 4294967295
fe80::/64 dev vif1.0 metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev vif2.0 metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
default via 2a01:198:200:254::1 dev sixxs metric 1024 mtu 1280 advmss 1220 hoplimit 4294967295
dampfbad:~#
Did you add any filter statements? As you don't have any other traffic there, which is rather strange.
Yes. I filtered out my own SSH traffic with "not host <my current ipv4 sourceip>", and the port 6667 (because there is an ircd running on a guest) which spammed a lot during the tcpdump. This should not affect our troubleshooting here.
Maybe you have a firewall somewhere that is bothering (=filtering) you?
At least not locally:
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
ACCEPT all -- eisbad.5711.org anywhere PHYSDEV match --physdev-in vif1.0
ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in vif1.0 udp spt:bootpc dpt:bootps
ACCEPT all -- grapevine.5711.org anywhere PHYSDEV match --physdev-in vif2.0
ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in vif2.0 udp spt:bootpc dpt:bootps
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
dampfbad:~#
dampfbad:~# ip6tables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
dampfbad:~#
The server is located in a datacenter of a webhoster (hetzner). It would highly surprise me if they filter the traffic for their dedicated servers..
Debian IPv6 Setup (XEN Dom0)
Shadow Hawkins on Wednesday, 17 March 2010 10:52:02
Very weird. Now it works out-of-nowhere...
dampfbad:~# ping6 ipv6.google.com
PING ipv6.google.com(2a00:1450:8001::68) 56 data bytes
64 bytes from 2a00:1450:8001::68: icmp_seq=1 ttl=56 time=27.4 ms
64 bytes from 2a00:1450:8001::68: icmp_seq=2 ttl=56 time=27.0 ms
64 bytes from 2a00:1450:8001::68: icmp_seq=3 ttl=56 time=26.9 ms
64 bytes from 2a00:1450:8001::68: icmp_seq=4 ttl=56 time=27.4 ms
64 bytes from 2a00:1450:8001::68: icmp_seq=5 ttl=56 time=27.1 ms
^C
--- ipv6.google.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4018ms
rtt min/avg/max/mdev = 26.922/27.200/27.445/0.255 ms
dampfbad:~#
I haven't done any changes during the last post and now.
|
![[ch]](/s/countries/ch.gif)
on Wednesday, 10 March 2010 17:57:26
Posting is only allowed when you are