Subject: Re: [netatalk-admins] Routing between LocalTalk and EtherTalk
From: Patrik Schindler (poc@pocnet.net)
Date: Tue Jul 14 1998 - 13:37:49 EDT
At 14:15 Uhr +0300 14.07.1998, Hannu Krosing wrote:
>Did you actually try it ?
No, I think of it as lost time. It won't work. For sure. Read on ;-)
>> - 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 ;)
Why?
>IMHO net range is what appletalk uses for deciding where to find a net
>with certain number.
No. AppleTalk is different from other known protocols. AppleTalk won't use the range parameter to pick one number for a net. Instead, a net consists of more numbers, the net range. AppleTalk nodes choose an unique number from within this range, which lie within the defined range.
To explain some statements further, AppleTalk knows two two kinds of network numbering
- Nonextended numbering (no range but single, unique number for the net and only one assigned zone), found on ARCnet and EtherTalk Phase 1 Networks. Phase 1 networks use the Ethernet II frame which is the same as used with IP. One can have a maximum of 254 nodes on such a network and must choose the net number between 1 65279. A valid zone name consists of up to 32 chars including spaces.
"All AppleTalk routers connected to a network must use the same number for that network, and no other network can use that number." [1]
- Extended Numbering (an unique network numbering range and up to 255 zones assigned per network), found on TokenTalk and EtherTalk Phase 2 networks. Phase 2 networks use the 802.2 Type 1 packet frame, also known as SNAP frame. A net range allows range times 253 nodes in it's net. A one-numer-range is acceptable (net=2-2).
"All AppleTalk routers connected to that network must use the same range for that network, and no other network can use that range or any number contained within it." [2]
>> - 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
But this breaks with the unique-numbering-law. I think I get the point you want to tell, you try to adapt IP numbering with the different classes and netmask parameters to AppleTalk.
You need to take care of "splitting" a class C net into smaller pieces in IP. With AppleTalk, you do not need this, AppleTalk's Routing Table Maintenance Protocol keeps all routers informed about all network numbers and how to reach them in an internet network, this is a bit like RIP in the IP world.
That's why the Internet speaks IP, no RIP and no AppleTalk, all routers were busy with broadcasting their configuration out ;-)
>> - 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
Jup, but you'll have to see the whole range, not only single numbers. As of your point of view, this is okay, but if you see the whole range, it's invalid.
>they are ,just net _ranges_ are'nt
Eh? Right, they are ranges, the net is configured as range and NOT as a bunch of cluttered numbers.
>what are the _actual_ (versus _configured_) nets and net ranges seeded
>by the AIR router ?
121-130 +----------+ 131-140 +------+
----------+ nwserver +---------------+ p475 |
+-----+----+ +--+---+
| |
141-150 | 151 | LocalTalk
| |
Okay, the config is a little bit different. I kept unique ranges on ethernet and an unique number on LocalTalk. It works.
I hope, I could state the whole routing problematic a bit clearer.
As far as I can see I've no configuration errors. Perhaps it may help the coders around, changing the line ordering in atalkd.conf from tycho, I get errors like this:
Jun 22 13:35:40 tycho atalkd[97]: rtmp_request for ltalk0
Jun 22 13:35:40 tycho atalkd[97]: rtmp_packet gateway 100.2 up
Jun 22 13:35:41 tycho atalkd[97]: rtmp_request for ltalk0
Jun 22 13:35:45 tycho atalkd[97]: rtmp_config net mismatch 100 != 0
just after trying to configure ltalk0.
I must configure ltalk0 before eth0, than it works without errors. Of course, networks of eth0 and ltalk0 are different.
[1] Netware for Macintosh 3.12 Installation and Maintenance Manual, Page 17
[2] Netware for Macintosh 3.12 Installation and Maintenance Manual, Page 18
:wq! PoC
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:32:55 EST