|
RADVD problem
![[nl]](/s/countries/nl.gif) Shadow Hawkins on Wednesday, 12 January 2011 17:39:29
Hi,
I'm not sure if this is the best forum to ask this.
I configured a tunnel as described on Synology. After fixing the tun-module loading this works fine, the tunnel is up and running.
Radvd however advertises the routers link-local address as default gateway, which is unreachable from the network.
radvd.conf looks like
interface eth0
{
AdvSendAdvert on;
AdvLinkMTU 1280;
MaxRtrAdvInterval 300;
prefix 2001:1af8:fe7f:a::/64
{
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr on;
};
};
The routers eth0 is configured as:
eth0 Link encap:Ethernet HWaddr 00:11:32:07:16:3D
inet addr:192.168.1.21 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: 2001:1af8:fe7f:a::1/64 Scope:Global
inet6 addr: fe80::211:32ff:fe07:163d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5803 errors:0 dropped:0 overruns:0 frame:0
TX packets:3606 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:532
RX bytes:499888 (488.1 KiB) TX bytes:402229 (392.8 KiB)
Interrupt:11
At the client side I get:
# ifconfig eth1
eth1 Link encap:Ethernet HWaddr 00:17:31:f4:25:64
inet addr:192.168.1.52 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: 2001:1af8:fe7f:a:217:31ff:fef4:2564/64 Scope:Global
inet6 addr: fe80::217:31ff:fef4:2564/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1739 errors:0 dropped:0 overruns:0 frame:0
TX packets:1561 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:523865 (523.8 KB) TX bytes:221440 (221.4 KB)
Interrupt:46
# ip -6 route
2001:1af8:fe7f:a::/64 dev eth1 proto kernel metric 256 expires 86357sec mtu 1280 advmss 1220 hoplimit 0
fe80::/64 dev eth1 proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 0
default via fe80::211:32ff:fe07:163d dev eth1 proto kernel metric 1024 expires 852sec mtu 1280 advmss 1220 hoplimit 64
Thanks in Advance
Hans
RADVD problem
AdvLinkMTU 1280;
You should not use this option as the local link MTU is 1500 (Ethernet). The upstream tunnel is indeed 1280, but PathMTU discovery (ICMP packet too big) will take care of that.
As for the other options, do you know what they do and if so why did you have turn those on?
Radvd however advertises the routers link-local address as default gateway, which is unreachable from the network.
There is nothing wrong with that, that is simply how it works ;)
$ ping6 -I eth1 fe80::211:32ff:fe07:163d
should work like a charm, thus if you have forwarding enabled on that host (which you have, otherwise radvd doesn't run) and your firewall rules are correctly set up, it should work just fine.
RADVD problem
Shadow Hawkins on Wednesday, 12 January 2011 17:53:16
Thanks, I did not know about ping6 -I.
ping6 fe80::211:32ff:fe07:163d returns 'invalid argument', that is why i suspected that to be the problem.
For the routing problem see my other post.
Hans
RADVD problem
Shadow Hawkins on Wednesday, 12 January 2011 17:48:54
Hi,
I found a solution.
The default gateway is automatically set to the local end of the tunnel. The problem is solved by manually setting the default route to the remote end of the tunnel.
Best regards,
Hans de Ridder
PS, The forum complained about an error in my previous post. My first reply mystically disappeared. If it decides to publish it anyhow this may a duplicate anwer.
Hans
|
![[ch]](/s/countries/ch.gif)
on Wednesday, 12 January 2011 17:44:48
Posting is only allowed when you are