|
IPv6-Traffic Fritzbox (fd00::) over tunnel
![[de]](/s/countries/de.gif) Shadow Hawkins on Sunday, 28 November 2010 23:11:58
Hi,
one of my friends has ipv6-enabled fritzbox.
Everything is working fine but dns-requests from firefox are slowed down :(
I get the resolver-config right:
nameserver fd00::21f:3fff:fef4:eec2
nameserver 192.168.2.1
search fritz.box
I can ping the fritzbox:
$ ping6 -n fd00::21f:3fff:fef4:eec2
PING fd00::21f:3fff:fef4:eec2(fd00::21f:3fff:fef4:eec2) 56 data bytes
64 bytes from fd00::21f:3fff:fef4:eec2: icmp_seq=1 ttl=64 time=2.90 ms
64 bytes from fd00::21f:3fff:fef4:eec2: icmp_seq=2 ttl=64 time=1.42 ms
64 bytes from fd00::21f:3fff:fef4:eec2: icmp_seq=3 ttl=64 time=2.65 ms
64 bytes from fd00::21f:3fff:fef4:eec2: icmp_seq=4 ttl=64 time=3.39 ms
64 bytes from fd00::21f:3fff:fef4:eec2: icmp_seq=5 ttl=64 time=1.24 ms
Even dig is working:
$ dig www.sixxs.net
; <<>> DiG 9.7.1-P2 <<>> www.sixxs.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5552
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;www.sixxs.net. IN A
;; ANSWER SECTION:
www.sixxs.net. 1992 IN CNAME nginx.sixxs.net.
nginx.sixxs.net. 300 IN A 94.75.219.73
nginx.sixxs.net. 300 IN A 213.197.30.67
nginx.sixxs.net. 300 IN A 213.204.193.2
;; Query time: 93 msec
;; SERVER: fd00::21f:3fff:fef4:eec2#53(fd00::21f:3fff:fef4:eec2)
;; WHEN: Sun Nov 28 23:04:56 2010
;; MSG SIZE rcvd: 99
But as soon as Firefox tries to resolve a hostname it is sent over the sixxs-tunnel:
2a01:198:200:865::2fd00::21f:3fff:fef4:eec2DNSStandard query AAAA www.google.com
As you can see the source address is my sixxs-endpoint.. Tcpdump with dig shows my local address:
2002:5845:8bbb:0:216:eaff:fe5f:5e28fd00::21f:3fff:fef4:eec2DNSStandard query AAAA www.google.com
My routing table:
$ ip -6 route
2002:5845:8bbb::/64 dev wlan0 proto kernel metric 256 expires 6910sec mtu 1280 advmss 1220 hoplimit 4294967295
2a01:198:200:865::/64 dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 4294967295
fe80::/64 dev wlan0 proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 4294967295
fe80::/64 dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 4294967295
default via fe80::21f:3fff:fef4:eec2 dev wlan0 proto kernel metric 1024 expires 1510sec mtu 1280 advmss 1220 hoplimit 255
default via 2a01:198:200:865::1 dev sixxs metric 1024 mtu 1280 advmss 1220 hoplimit 4294967295
Any guess what is wrong?
IPv6-Traffic Fritzbox (fd00::) over tunnel
Why are you bothering with mixing 6to4 with a SixXS tunnel? Terminate the tunnel on your Fritz!Box, get a subnet and use that.
You currently have two 'default' gateways and thus packets will randomly go to one or the other, and the PoPs really do not have an idea on what to do with packets inside fd00::/7 aka the ULA space.
IPv6-Traffic Fritzbox (fd00::) over tunnel
Shadow Hawkins on Monday, 29 November 2010 13:51:32
First: not my network. I was just a guest using my friends wlan.
Second: why does aiccu sets a route for a network which can't be handled by the pop?
IPv6-Traffic Fritzbox (fd00::) over tunnel
AICCU sets a default route, which is what every method (RA, DHCPv6 etc) set.
ULA though, cannot be routed by the PoPs per definition, as it is local and it does not belong on the Internet.
Also the SixXS PoPs only route the traffic that is sourced by address space assigned from the PoP, not any other packets, see the FAQ on transit.
|
![[ch]](/s/countries/ch.gif)
on Monday, 29 November 2010 11:57:20
Posting is only allowed when you are