Even with a single interface, you should be able to seed.  I don't  
   know precisely how netatalk works, but for systems like the Apple  
   Network Server and Mac OS X Server, this is legal.

my patches to netatalk allow the seeding of a single interface. they
just use a different option (-router) so that people using -seed with
a single interface don't suddenly get different behaviour.

   The network number and node number are always subject to change upon  
   reboot.  Normally, sytems cache addresses and use these as hints on  
   reboot.  Seeding (of network numbers) is orthogonal to the reuse of  
   addresses.

netatalk does that as well. for my next patchset, i've added bits so
that you can multihome. it's currently called -dontroute right now as
you can't run such devices in router mode. if i have time, i'll change
the logic so that single interface routing works with multihoming as
well as supporting virtual appletalk routing domains. in addition, i
had to change stuff so that you can specify the actual appletalk
address to use for any particular service.

unfortunately, netatalk still sends nbp info for all devices that it
knows about. my simple attempt to bind nbp entries to devices seems to
have failed, but i'll try to come up with something so that it doesn't
do that.

-a

Reply via email to