Subject: Re: [netatalk-admins] Routing between LocalTalk and EtherTalk
From: Hannu Krosing (hannu@trust.ee)
Date: Tue Jul 14 1998 - 07:15:34 EDT
Patrik Schindler wrote:
>
> At 18:04 Uhr +0300 13.07.1998, Hannu Krosing wrote:
>
> >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:
Did you actually try it ?
> - 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.
or perhaps the _wrong_ net range ;)
IMHO net range is what appletalk uses for deciding where to find a net
with certain number.
> - 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.
They overlap on purpose - so leela can know that going through eth0 it
can get to nets 125 and 130 as well
> - The net range for leela's eth1 and tycho's eth0 overlap, they aren't unique.
again on purpose, but the _nets_ are unique and looking from tycho, they
are within the net range of eth0
> 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
they are ,just net _ranges_ are'nt
> - for one "cable" the attached networking devices MUST have an unique address in the network number(s) declared for this "cable".
ditto
> 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.
what are the _actual_ (versus _configured_) nets and net ranges seeded
by the AIR router ?
Hannu
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:32:55 EST