No IPv6 DNS

Tymanthius · April 26, 2012, 08:37:48 AM

Quote from: broquea on April 26, 2012, 08:34:50 AM
No, use the ROUTED /64, not the tunnel's /64. These will be different, and that difference will be in BOLD

2001:470:1f0e:1034::1 is HE's side of the tunnel and shouldn't be configured locally.

That may be my problem. I was following someone's guide, and it seemed wierd, but I wasn't sure enough to change it. I'll go edit some things & report back.

Tymanthius · April 26, 2012, 08:55:27 AM

Ok, now I look like this:

Quote
eth0 Link encap:Ethernet HWaddr 10:78:d2:d7:b8:16
inet addr:72.219.26.49 Bcast:72.219.27.255 Mask:255.255.254.0
inet6 addr: 2001:470:1f0f:1034::1/64 Scope:Global
inet6 addr: fe80::1278:d2ff:fed7:b816/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6020 errors:0 dropped:0 overruns:0 frame:0
TX packets:1872 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1093831 (1.0 MB) TX bytes:251012 (251.0 KB)
Interrupt:32 Base address:0x2000

eth1 Link encap:Ethernet HWaddr 10:78:d2:f3:2c:52
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: 2001:470:1f0f:1034::3/64 Scope:Global
inet6 addr: fe80::1278:d2ff:fef3:2c52/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2325 errors:0 dropped:0 overruns:0 frame:0
TX packets:2263 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:343562 (343.5 KB) TX bytes:763219 (763.2 KB)
Interrupt:34 Base address:0x6000

he-ipv6 Link encap:IPv6-in-IPv4
inet6 addr: 2001:470:1f0f:1034::2/64 Scope:Global
inet6 addr: fe80::48db:1a31/128 Scope:Link
UP POINTOPOINT RUNNING NOARP MTU:1480 Metric:1
RX packets:200 errors:0 dropped:0 overruns:0 frame:0
TX packets:206 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:20608 (20.6 KB) TX bytes:19552 (19.5 KB)

But not much change. If I ping ipv6.google.com from a client it resolves to 2001:4860:4002:801::1013, but no replies come back. Pings fine from the server.

I from the client I only get ping responses from my ::3 address.

This is my win 7 client:

Quote
Wireless LAN adapter Wireless Network Connection 2:

Connection-specific DNS Suffix . : tymanthius.net
IPv6 Address. . . . . . . . . . . : 2001:470:1f0f:1034:acc3:3578:a207:2312
Temporary IPv6 Address. . . . . . : 2001:470:1f0f:1034:2c52:9c0e:6cc2:30b0
Link-local IPv6 Address . . . . . : fe80::acc3:3578:a207:2312%14
IPv4 Address. . . . . . . . . . . : 192.168.1.121
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::1278:d2ff:fef3:2c52%14
192.168.1.1

That default gateway listing looks suspicious to me. Shouldn't it be the global address of the eth1 above? (eth0 is my external facing nic, eth1 is internal facing).

broquea · April 26, 2012, 09:00:45 AM

If you are using RADVD, then your clients' default gateway will be the link-local address of the advertising router's LAN facing interface. When I trace to 2001:470:1f0f:1034:acc3:3578:a207:2312 I get a route-loop between your Linux machine acting as router and the tunnel-server, which means you've got some sort of bad/wedged/stuck route or something on the Linux machine. You might want to check your routing table on the Linux machine. If you aren't using RADVD and instead have statically/manually configured Windows with an IPv6 address, then you should also be manually setting the default route to point to the IP configured on the LAN facing interface.

Tymanthius · April 26, 2012, 09:08:00 AM

Quote from: broquea on April 26, 2012, 09:00:45 AM
If you are using RADVD, then your clients' default gateway will be the link-local address of the advertising router's LAN facing interface. When I trace to 2001:470:1f0f:1034:acc3:3578:a207:2312 I get a route-loop between your Linux machine acting as router and the tunnel-server, which means you've got some sort of bad/wedged/stuck route or something on the Linux machine. You might want to check your routing table on the Linux machine. If you aren't using RADVD and instead have statically/manually configured Windows with an IPv6 address, then you should also be manually setting the default route to point to the IP configured on the LAN facing interface.

I am using radvd, I will check the route tables.

<edit>

Here's the routing table. I just realized I don't really know how to read it. :((

Quote

Destination Next Hop Flag Met Ref Use If
2001:470:1f0f:1034::/64 :: Un 256 0 8179 he-ipv6
2001:470:1f0f:1034::/64 :: U 256 0 0 eth0
2001:470:1f0f:1034::/64 :: U 256 0 0 eth1
fe80::/64 :: U 256 0 0 eth1
fe80::/64 :: U 256 0 0 eth0
fe80::/64 :: Un 256 0 0 he-ipv6
fe80::/64 :: U 256 0 0 tap0
::/0 :: U 1024 0 0 he-ipv6
::/0 :: !n -1 1 8679 lo
::1/128 :: Un 0 2 29 lo
2001:470:1f0f:1034::/128 :: Un 0 1 0 lo
2001:470:1f0f:1034::/128 :: Un 0 1 0 lo
2001:470:1f0f:1034::/128 :: Un 0 1 0 lo
2001:470:1f0f:1034::1/128 :: Un 0 1 0 lo
2001:470:1f0f:1034::2/128 :: Un 0 1 32 lo
2001:470:1f0f:1034::3/128 :: Un 0 1 55 lo
fe80::/128 :: Un 0 1 0 lo
fe80::/128 :: Un 0 1 0 lo
fe80::/128 :: Un 0 1 0 lo
fe80::48db:1a31/128 :: Un 0 1 250 lo
fe80::1278:d2ff:fed7:b816/128 :: Un 0 1 0 lo
fe80::1278:d2ff:fef3:2c52/128 :: Un 0 1 33 lo
fe80::30bf:6eff:fe14:f35b/128 :: Un 0 1 0 lo
ff00::/8 :: U 256 0 0 eth1
ff00::/8 :: U 256 0 0 eth0
ff00::/8 :: U 256 0 0 he-ipv6
ff00::/8 :: U 256 0 0 tap0
::/0 :: !n -1 1 8679 lo

Tymanthius · April 30, 2012, 10:57:35 AM

Would love if someone could point me to a good site/book that would teach me about IPv6 routing tables.

I''ve been searching, but I seem to be missing a key point of understanding that will allow the rest to fall into place. :/

cholzhauer · April 30, 2012, 11:00:59 AM

There is nothing magical...it's the same thing as IPv4. The only thing you need to keep in mind is that ::/0 is the same as 0.0.0.0

In this case your default route is pointing to your HE interface

Tymanthius · April 30, 2012, 11:36:48 AM

Quote from: cholzhauer on April 30, 2012, 11:00:59 AM
There is nothing magical...it's the same thing as IPv4. The only thing you need to keep in mind is that ::/0 is the same as 0.0.0.0

In this case your default route is pointing to your HE interface

I know I sound like an idiot, but I just can't seem to make sense of the routing table. I've never really had to look at tables before, so I didn't realize my lack until now.

Which line in my table tells you my default route? I *think* I can figure out how to change it, IF I can figure out how to read the table.

broquea · April 30, 2012, 11:37:50 AM

This is the default route

Code Select

::/0 :: U 1024 0 0 he-ipv6

If this is the machine the tunnel terminates on, you don't want to change that.

Tymanthius · April 30, 2012, 11:49:55 AM

Quote from: broquea on April 30, 2012, 11:37:50 AM
This is the default route

Code Select Expand
::/0 :: U 1024 0 0 he-ipv6

If this is the machine the tunnel terminates on, you don't want to change that.

Ok. That is the machine that the tunnel terminates on. But according earlier someone did a tracert to my ipv6 address and it seemed to route to itself.

Any ideas on that? b/c if I'm reading this correctly my default route is set properly, at least for outbound connections, but I can't actually get out on IPv6 on any client machines.

News:

No IPv6 DNS