Date: Fri, 18 Mar 2011 21:35:16 +0500 From: "Eugene M. Zheganin" <eugene@zhegan.in> To: freebsd-net@freebsd.org Subject: Re: ipv6, stateful config and non-default prefixlen Message-ID: <4D8389C4.8050408@zhegan.in> In-Reply-To: <20110318115748.708aee22@shibato.opal.com> References: <4D8370AB.1070000@zhegan.in> <20110318115748.708aee22@shibato.opal.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi.
On 18.03.2011 20:57, J.R. Oldroyd wrote:
> You don't say what prefix length rtadvd is sending or that you're seeing
> in the wireshark log.
>
> Do you have prefixlen#120 in your rtadvd.conf?
Yup.
rtadvd.conf from router:
default:
:raflags#192:
vlan1:\
:addr="fd00::0300":prefixlen#120:raflags#192:
vlan15:\
:addr="fd00::0700":prefixlen#120:raflags#192:
Output from my desktop FreeBSD (nfe0 is in the network that router is
connected with vlan15):
%ps ax | grep dhc
25642 ?? Is 0:00,01 dhclient: nfe0 [priv] (dhclient)
25660 ?? Is 0:00,01 dhclient: nfe0 (dhclient)
25672 ?? Is 0:00,01 /usr/local/sbin/dhclient -6 nfe0
%ifconfig nfe0
nfe0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric
0 mtu 1500
options=82008<VLAN_MTU,WOL_MAGIC,LINKSTATE>
ether 00:1d:7d:92:45:84
inet6 fe80::21d:7dff:fe92:4584%nfe0 prefixlen 64 scopeid 0x3
inet 192.168.7.246 netmask 0xffffff00 broadcast 192.168.7.255
inet6 fd00::7d2 prefixlen 64
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
%ndp -p
fd00::/64 if=nfe0
flags=LO vltime=infinity, pltime=infinity, expire=Never, ref=1
No advertising router
fd00::700/120 if=nfe0
flags=LAO vltime=2592000, pltime=604800, expire=29d23h55m11s, ref=0
advertised by
fe80::204:23ff:febc:840c%nfe0 (reachable)
fe80::%nfe0/64 if=nfe0
flags=LAO vltime=infinity, pltime=infinity, expire=Never, ref=0
No advertising router
fe80::%lo0/64 if=lo0
flags=LAO vltime=infinity, pltime=infinity, expire=Never, ref=0
No advertising router
So it's shown here that no router advertises fd00::/64.
Furthermore, I can assure you that this address isn't the result of
misconfiguration - it is provided by the dhclient.
Eugene.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D8389C4.8050408>