Hi, I'm the upstream maintainer of radvd and noticed this bug report.
I believe in the first case the reporter made a typo, instead of /proc/sys/net/ipv6/neigh/eth0/hop_limit he should have been looking at /proc/sys/net/ipv6/conf/eth0/hop_limit.
The problem is due to how early radvd drops root privileges and as an extension, how it cannot reconfigure the interface at SIGHUP signal if it has already dropped the privileges.
I've only documented the problem for now unless someone else steps up and provides concrete patches to really address this issue.
See: http://lists.litech.org/pipermail/radvd-devel-l/2007-October/000281.html -- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
