Subject: Re: [netatalk-admins] Routing between LocalTalk and EtherTalk
From: Patrik Schindler (poc@pocnet.net)
Date: Mon Jul 13 1998 - 12:54:12 EDT
At 18:04 Uhr +0300 13.07.1998, Hannu Krosing wrote:
>AFAIK you should have only one seed router per network, so remove the
>-seed from either tycho:eth0 or leela:eth0. I'm not sure if it removes
>all your problems, but it's a start ;)
It doesn't work. I spent my leela an 100MBit card to connect my Mac a bit faster, but in the past without a seeding leela, the LocalTalk issue hasn't worked either.
So I don't think, it's a seeding-related problem.
In another net, there were two seeding-routers, too, and it worked. This net had one netware-server acting as seeder and an Apple Internet Router for connecting LocalTalk Devices running on a Mac.
Why two seeding routers? If I halt tycho and reboot leela for some reason, I cannot find devices on the net between leela and tycho, there's no seeder, this net is undefined. Netatalk shows the same behaviour as the AIR and I consider this okay. If I fire up tycho again after leela is running, I had some strange problems not seeing leela in the chooser. I first had to shut down atalk on leela, ifconfig down all netdevices and fire all up again. But I haven't yet analyzed this behaviour further. I'm happy if it runs, and it does. :-)
>Also (I am not very sure about it either ;), but I may be right),
>the net ranges should be inclusive, ie the following should work
>
>
> net:150 +-------+ net:140 +-------+ net:130
> ----------+ leela +---------------+ tycho +-----------
> eth1 +-------+ eth0 eth0 +---+---+ eth1
> |
> net:125 | ltalk0
> |
>
>[hostname: tycho]
>ltalk0 -seed -phase 1 -net 125 -addr 125.1 -zone "Local"
>eth0 -seed -phase 2 -net 140-150 -addr 140.1 -zone "Ether"
>eth1 -seed -phase 2 -net 130-130 -addr 130.1 -zone "Ether"
>
>[hostname: leela]
>eth0 -phase 2 -net 100-140 -addr 140.2 -zone "Ether"
>eth1 -seed -phase 2 -net 150-150 -addr 150.1 -zone "Ether"
>
>notice that 140-150 includes both nets 140 and 150, as doea 100-140
>for nets 125,130,and 140
No this could not work:
- The net ranges for eth0 from both tycho and leela are inconsistent but this is not important. leela's atalkd rewrites the config, 'cause tycho seeds (leela not) and tells leela the right net range.
- leela's eth0 and localtalk networks overlap, but this is not important, 'cause leela won't seed, tycho seeds the right range, which won't touch localtalk anyway.
- The net range for leela's eth1 and tycho's eth0 overlap, they aren't unique.
It's most important in networking business, whatever protocol(s) like IP, IPX, AppleTalk and such you are running, that
- in an internetwork, ALL network numbers MUST be unique in the whole internetwork and
- for one "cable" the attached networking devices MUST have an unique address in the network number(s) declared for this "cable".
Sorry, I don't know the technical right word for "cable", but I hope anyone knows what I mean, if one imagines a cheapernet. :-)
Anyway, running the same net with a Mac IIcx and AIR acting as replacement for tycho works fine! With the same net range and zone settings.
:wq! PoC
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:32:55 EST