[radvd-devel-l] radvd stuck on linux 2.6.31+
Steven J Newbury
steve at snewbury.org.uk
Mon Sep 28 09:00:43 EDT 2009
On Mon, 2009-09-28 at 13:21 +0100, Steven J Newbury wrote:
> On Mon, 2009-09-28 at 15:01 +0300, Pekka Savola wrote:
> > There are a couple of odd messages here:
> >
> > On Mon, 28 Sep 2009, Steven J Newbury wrote:
> > > eater ~ # radvd -C /etc/radvd.conf -u radvd -d 5 -m stderr
> > > [Sep 28 12:23:04] radvd: version 1.5 started
> > > [Sep 28 12:23:04] radvd: interface wlan0 did not exist, ignoring the interface
> > ...
> > > [Sep 28 12:23:04] radvd: no linklocal address configured for wlan0
> > > [Sep 28 12:23:04] radvd: interface definition for wlan0 is ok
> > ...
> > > [Sep 28 12:23:04] radvd: interface eth0 did not exist, ignoring the interface
> >
> > First, it's complaining that wlan0 does not exist. What does it look
> > like with '/sbin/ifconfig wlan0'? The flags should should be UP,
> > BROADCAST, RUNNING, MULTICAST unless something changed, and a
> > link-local address should exist. One speculation wrt changing is that
> > the ioctl interface and RUNNING flag definition could have changed,
> > causing userspace-kernel mismatch.
> >
> > I'm also wondering why it's reporting about other interfaces here. Do
> > you also have them configured on radvd.conf and omitted this for
> > brevity or is radvd picking them up from somewhere else?
> wlan1 is my link to the Internet facing router, for the purposes of
> trying to fix this, wlan0 is not currently in use, neither is eth0 nor
> the tun0 device. I have them configured "IgnoreIfMissing" in
> radvd.conf.
>
> I've now removed all other devices from the config and switched back to
> my old kernel. Strangely I'm seeing very few RA broadcasts on my client
> machine, and my kernel hasn't picked up the advertised network
> configuration. I'm somewhat at a loss now. I'm going to try updating
> the kernel on the client, but this was all working fine just yesterday!
>
> More to come no doubt...
After rebooting my client laptop, it just started working with solicited
RAs. I don't know why that stopped working?!? I'm switching back to
the new kernel now, and I'll see if I get any broadcasts, since it's the
lack of radvdump received broadcasts which led me to think it an issue
server-side...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://lists.litech.org/pipermail/radvd-devel-l/attachments/20090928/4f75b263/attachment.pgp>
More information about the radvd-devel-l
mailing list