Subject: Re: [netatalk-admins] Routing between LocalTalk and EtherTalk: news
From: Patrik Schindler (poc@pocnet.net)
Date: Thu Jul 16 1998 - 13:26:17 EDT
Me again, ;-)
I've changed the configuration for a one-number range:
[tycho]
ltalk0 -seed -phase 1 -net 10 -addr 10.1 -zone "Local"
eth0 -seed -phase 2 -net 11 -addr 11.1 -zone "Ether"
eth1 -seed -phase 2 -net 12 -addr 12.1 -zone "Ether"
[leela]
eth0 -seed -phase 2 -net 11 -addr 11.2 -zone "Ether"
eth1 -seed -phase 2 -net 13 -addr 13.1 -zone "Ether"
>Type 3 (remote?) routes only appear for EtherTalk but NOT for LocalTalk in leela. I think, tycho won't broadcast its ltalk0-route (net 125) with RTMP.
Okay, the route to 10 is now showing up in leela's /proc/net/atalk_route -> no ranges allowed in the entire net? Why? Is netatalk not 100% Phase-2 compliant?
But aecho-requests won't even now come back from LocalTalk devices to anything in the net except tycho.
More interesting facts:
- A Mac within net 12 can see devices on localtalk (but cannot send any data to them). Because this net is directly connected?
- A Mac in net 10 cannot see anything but devices in net 10 (and an running AFPServer on tycho).
- A Mac in net 12 cannot see any devices in net 13.
- A Mac in net 13 cannot see any devices in net 12.
I remember someone complaining about the last 2 facts in this list a while ago.
It seems that routing further than 1 hop simply doesn't work.
Something else, I missed to state clear: Aechoing the local LocalTalk interface address from anywhere succeeds.
Any tips?
:wq! PoC
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:32:56 EST