On 12/14/2012 12:21 PM, Csillag Tamas wrote:
> For a friend of mine it was a "dadfailed" address on the interface which
> prevented the it from working.
> (And google revealed this bugreport before we found that.)
hm, i'm afraid i don't know enough to say whether the issue was
DADfailed or not.
> Can you still reproduce this? (more than a year old bugreport)
Hm, i had to rebuild the machine that was seeing this due to a disk
failure since i reported it last. The rebuild happened around 2012-05-17.
Looking at the logs in the new machine, it appears only once in the
logs, and has not shown up since the initial installation and successful
configuration:
2012-05-17_08:27 radvd: IPv6 forwarding setting is: 0, should be 1
2012-05-17_08:27 radvd: IPv6 forwarding seems to be disabled, but
continuing anyway.
2012-05-17_08:27 radvd: IPv6 forwarding setting is: 0, should be 1
2012-05-17_08:27 radvd: sendmsg: Invalid argument
2012-05-17_08:32 radvd: version 1.6 started
2012-05-17_08:40 radvd: version 1.6 started
And now that the configuration is correct, it doesn't happen any more.
I hope that helps with the diagnosis! sorry to not have a better
understanding of the underlying issues.
--dkg
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
