On the one hand, that stands in specific defiance of Inside AppleTalk... on the other, it sort of makes sense, as the start index in GetZoneList and GetLocalZones is 1-relative and GetMyZone is supposed to follow the same format. "Do as I do, not as I say"? Any case, I removed that check and pushed the change to the repo. Thanks for testing it.
Sorry, spoke to soon. Let me test that again.
Alright-- I pulled the latest tashrouter from GitHub and applied these patches:
Interesting. I'm using the same tun/tap setup and seeing no issues at all with Macs on the LT side. Everything shows up as expected on both sides of the router. The only difference is that I use the tashrouter to seed both ethernet and localtalk.
Ah, I think we're talking past each other. Chooser was not the issue. It was the Appletalk control panel. The machine is a 32 MB SE/30 running System 7.5.5. There are a number of things installed, but nothing network related.
Yup, here's my config without seed:
import logging
import time
import tashrouter.netlog
from tashrouter.port.ethertalk.tap import TapPort
from tashrouter.port.localtalk.ltoudp import LtoudpPort
from tashrouter.port.localtalk.tashtalk import TashTalkPort
from tashrouter.router.router import Router
logging.basicConfig(level=logging.DEBUG, format='%(asctime)s %(levelname)s: %(message)s')
#tashrouter.netlog.set_log_str_func(logging.debug) # comment this line for speed and reduced spam
router = Router('router', ports=(
LtoudpPort(seed_network=999, seed_zone_name=b'JUPAK'),
# TashTalkPort(serial_port='/dev/ttyAMA0', seed_network=988, seed_zone_name=b'JUPAKL TashTalk'),
TapPort(tap_name='tap2', hw_addr=b'\xDE\xAD\xBE\xEF\xCA\xFE'),
))
print('router away!')
router.start()
try:
while True: time.sleep(1)
except KeyboardInterrupt:
router.stop()
TapPort(tap_name='tap2', hw_addr=b'\xDE\xAD\xBE\xEF\xCA\xFE', seed_network_min=990, seed_network_max=998, seed_zone_names=[b'JUPAK']),Shoot. Okay, I'm working on something that will hopefully make everyone happy, please stand by...
broadcast method to Port and updated everything that sends broadcast datagrams to use it - this will allow LocalTalk broadcasts to use the short header and EtherTalk broadcasts to use network number zero.A bit tight on time this AM, but SE/30 and IIe are behaving themselves. I'll do some further testing with ethertalk clients this evening. Thanks for the update!
Thank you for the quick turnaround! This now works with all my regular LT and LToUDP machines, with both configurations (ie. both with and without tashrouter serving as a seed router).
I think there are some electrical issues with a direct connection due to the way the tashtalk hat localtalk interface is designed.
Interesting! In this particular case it seems like a direct connection actually worked *better* since I could at least see and browse other zones, but I need to actually properly test now
This is correct - to the best of my knowledge, the TashTalk 2 Hat that I sell requires the use of a LocalTalk or PhoneNet dongle. It connects the Rx and Tx lines together, which isn't a problem when they go into the same transformer, but this is not what the Mac expects when speaking LocalTalk over its ports.
Is this still happening with the latest code?
