[radvd-devel-l] radvd on dynamically created interfaces

Nathan Lutchansky radvd-devel-l@litech.org
Mon, 8 Apr 2002 11:03:16 -0400 (EDT)

Hash: SHA1

On 8 Apr 2002, Morten Heiberg Rasmussen wrote:

> I am setting up a Linux box with some ISDN cards used for dialin. When I
> dial in control is passed to one of several waiting IPv6 capable pppd
> processes (I'm using the Bieringer pppd patch).
> This creates the interfaces ppp0, ppp1, ...
> On these interfaces the peer will send solicitations in order to be
> autoconfigured with a global address from my prefix.
> The problem is that I seem to be unable to start radvd because the
> interfaces in the radvd.conf file are not present at radvd startup time
> (I did a "chkconfig radvd on").

Hmmm...  radvd isn't really set up to handle interfaces that disappear 

Proposed solution:

- - New configuration directive that allows interfaces to be marked 
"optional", meaning that if they are not present on radvd startup, they 
will be ignored.

- - Errors from sendmsg() that indicate that an interface has been disabled 
cause radvd to discontinue advertising to that interface.

These changes will allow you to list all your ppp interfaces in 
radvd.conf, and radvd will only advertise to interfaces that are up.  
Whenever a new ppp session begins, you will need to SIGHUP radvd (probably 
from /etc/ppp/if-up or whatever) to tell it to rescan the interfaces.

Would this work for you?  -Nathan

- -- 
| Nathan Lutchansky | lutchann@litech.org |  Lithium Technologies  |
|  I dread success.  To have succeeded is to have finished one's   |
|  business on earth...  I like a state of continual becoming,     |
|  with a goal in front and not behind. - George Bernard Shaw      |
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: pgpenvelope 2.10.2 - http://pgpenvelope.sourceforge.net/