Subject: Re: [netatalk-admins] Using Netatalk as a Router
From: bsmith@h-e.com
Date: Sun May 03 1998 - 00:54:28 EDT
Original message sent on Fri, May 1 1:09 AM by bandit@freeside.elte.hu (Andras
Kadinger) :
>> So, if I want afpd to seed a single cable with two zone names,
>> do I need two cards? Do I need one card?
>
>It is irrelevant, how many network interfaces You have. The only relevant
>point is, that You have to specify -seed for atalkd, to make it 'seed' the
>network with zone information.
.
.
>> Do you need a router?
>
>No. You should be able to do this even on a Linux machine without any
>network connectivity (atalkd must have a network interface to bind to,
>though), and define Zones.
.
.
>> What would afpd.conf look like?
>>
>> ed0 -seed -phase 2 -????? -zone "Foo" -zone "Bar"
>
>I think You meant atalkd.conf here. The man-page can be followed here, so
>Your example is correct (but no need for any extra options in place of the
>?-s). Like this:
>
>eth0 -seed -phase 2 -net 10 -addr 10.10 -zone "Appletree" -zone "Twilight"
Sorry to disagree, but in my experience atalkd does not work like this. I also
have a small network with no routers and no zones. I attempted to do exactly
what you describe, but I could not make it work. Every time atalkd started up
it over-wrote atalkd.conf and removed the "-zone" options, even though I had
included "-seed". To be specific, I changed atalkd.conf to look like this:
eth0 -seed -phase 2 -net 2 -addr 2.176 -zone "Engineering" -zone "Production"
Looks pretty much like the example above. But after restarting the Unix box,
the network still has no zones, and atalkd.conf now looks like this:
eth0 -seed -phase 2 -net 0-65534 -addr 2.176
I tried putting a different range for "-net", but every time it would revert to
"0-65534", and every time the "-zone" options disappeared. There is also a
comment in atalkd.conf that says "-seed only works if you have
multi-interfaces." From all this I conclude that you cannot use atalkd to
define zones when there is only one interface on your Unix machine and no other
router on your network.
The important detail here might be not having any other routers on the network.
If your network has other routers that show the same structure as atalkd.conf,
it might appear that atalkd is seeding when actually it is probing and finding
the structure defined by the other routers, and writing that to atalkd.conf. If
the other routers were not there, the zone list in atalkd.conf would disappear.
This might explain why it seems to work in some cases.
Bob
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:32:38 EST