Closed ghost closed 10 years ago
radvd listens to a netlink socket. This socket is one method the kernel can communicate hardware changes to user space. radvd listens specifically for link up and link down state changes so it can start and stop sending router advertisements accordingly.
This seems like radvd is getting messages about the interface entering and leaving promiscuous mode and, just to be safe, is reinitializing the interface.
radvd 1.10 is some fairly course handling of the netlink messages. I think when it gets a netlink message that may be of intrerest, radvd just reinitializes every interface by rereading the config file. radvd-2.0, if I can ever manage to finish it, will be smarter about that. If you'd like, you can try the radvd-2 branch in github and let me know how it behaves..it may be better than 1.10.
On Mon, Apr 7, 2014 at 9:20 AM, NiTruS notifications@github.com wrote:
i keep getting these error messages when running radvd 1.10.0 on my dd-wrt router.. [image: image]https://cloud.githubusercontent.com/assets/3003530/2631926/2563de54-be5f-11e3-908a-dadf8dfe68b6.jpg
can u tell me why? radvd is still working fine..
— Reply to this email directly or view it on GitHubhttps://github.com/reubenhwk/radvd/issues/26 .
i keep getting these error messages when running radvd 1.10.0 on my dd-wrt router..
can u tell me why? radvd is still working fine..