On Mon, Aug 11, 2008 at 01:56:14PM +0100, saqmaster wrote:
| Paul de Weerd wrote:
| # ifconfig -A
| lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33208
| groups: lo
| inet 127.0.0.1 netmask 0xff000000
| inet6 ::1 prefixlen 128
| inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
| vic0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
| lladdr 00:0c:29:57:23:b6
| groups: egress
| media: Ethernet autoselect
| status: active
| inet 217.169.13.143 netmask 0xffffff80 broadcast 217.169.13.255
| inet6 2001:8b0:13:1::1 prefixlen 64
And here's the gist of your problem. Your vic0 interface doesn't have
a link-local address.
That's very interesting - did you somehow configure this yourself ?
Generally speaking, when an interface is up and your kernel supports
IPv6, the interface gets a link-local address (see lo0 and gif0 for
examples, they're the fe80::/64 addresses).
| enc0: flags=0<> mtu 1536
| gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280
| groups: gif
| physical address inet 217.169.13.143 --> 81.187.81.6
| inet6 fe80::20c:29ff:fe57:23b6%gif0 -> prefixlen 64 scopeid 0x4
| inet6 2001:8b0:13:1::1 -> 2001:8b0::1 prefixlen 128
|
|
| And /etc/sysctl.conf (stripped);
|
| net.inet6.ip6.forwarding=1
| net.inet6.ip6.accept_rtadv=0
This is good.
|
| On the client, sysctrl.conf:-
|
| net.inet6.ip6.forwarding=0
| net.inet6.ip6.accept_rtadv=1
This is good, too (assuming you made a typo in the filename there ;)
| Just noticed, on the router in /var/log/daemon:-
|
| Aug 11 12:45:37 sontaran rtadvd[14832]: <getent> open: No such file or
directory
| Aug 11 12:45:37 sontaran rtadvd[14832]: <getconfig> vic0 isn't defined
| in the configuration file or the configuration file doesn't exist.
| Treat it as default
That's OK, doesn't matter, since you're interface is configured with
an IPv6 address it'll "just work (tm)".
| .. when starting 'rtadvd -D vic0' - it was doing this before I renamed
| /etc/rtadvd.conf (I did try specifiying -c /etc/rtadvd.conf before
| too, to no avail).
|
|
| Further info: no pf, no local firewalls on any machines, various
| physical and virtual machines on various network segments - nothing
| else is configured to listen for RA and nothing else is configured as
| a 'ra server(?)'..
You'll now have to figure out how you managed to remove the link-local
address from vic0 or why it didn't get one in the first place. Since
vic0 is a VMware virtual interface, it stands to reason that you're
trying all of this on virtual hardware. Maybe try using other types of
interfaces in VMware or play with this on 'real' hardware first.
Hope that helps, happy v6'ing ;)
Cheers,
Paul 'WEiRD' de Weerd
--
>++++++++[<++++++++++>-]<+++++++.>+++[<------>-]<.>+++[<+
+++++++++++>-]<.>++[<------------>-]<+.--------------.[-]
http://www.weirdnet.nl/
