minivmac's LToUDP implementation has some bugs. Through testing with tashtalkd and TashRouter indicates its a problem with minivmac itself. The emulator's ability to transmit data onto the network seems to be speed limited, roughly to the speed of a modem. This is very noticeable if you ever try...
The PowerBook still isn't seeing all zones, but a complete shutdown of both TashRouter and atalkd and then restart should clear that up. Its completely normal for routers to develop stale zone tables when you are starting up and shutting down routers one at a time.
Most Mac emulators patch the ROM to an extent. Its one reason why the machine is fairly easy to emulate! It wasn't until efforts like MAME or QEMU that there was any attempt to emulate the machine with actual hardware.
Motorola had a different approach to Intel in that the newer generation CPUs weren't 100% compatible with software written for the earlier generation. Apple got away with this by not supporting older OS versions on newer hardware. The Amiga worked around it by having loadable CPU libraries in...
I think I know what might be going on. Change the MAC address used by TashRouter for the tap interface, it should not match the one NetBSD assigned the interface on creation. For A2SERVER, I just use a completely bogus address (AA:BB:CC: DD:11:22) since its a virtual interface anyway.
ie...
This is an invalid configuration. Both atalkd and TashRouter both need the same zone list configured on tap0. The atalkd line should be as follows in this case:
tap0 -seed -phase 2 -net 3 -addr 3.33 -zone "Danger Zone" -zone "EtherTalk Network"
Anyway, one more thing to try. TashRouter had a...
Keep in mind that the Zorro bus was being developed by pretty much ONE person, Dave Haynie. No surprise it took a few revisions of the Buster chip to get stuff working. Reading the war stories can be funny at times. Things like "EISA got this nice feature, might as well add it to Zorro while...
There should be RTMP traffic on vioif0, at a minimum it should be broadcasting two tuples for networks 2 and 3 that atalkd is setup for. TashRouter appears to be working correctly, its routing table has all three networks.
One last test, shut down TashRouter and restart atalkd. See if you are...
Things seem to be communicating. Don't know what is causing the zone error, unless TashRouter isn't replying to the requests from atalkd for a zone list. On your Ethernet network, run Wireshark with the "atalk" filter. You should see the RTMP packets every 10 seconds, and expanding them should...
Odd, but it may be a regression from fixes on Linux to prevent NBPReplies coming from the loopback. Can you setup atalkd as follows:
See if Macs on your main network trigger NBPReplys.
TashRouter is now working over AppleTalk, the AARP lookup/reply shows that. LToUDP traffic shouldn't be going over the tap interface at all. On Linux, TashRouter's LToUDP always seems to correctly select the main NIC and send out packets in my setup.
I do have the problem with Minivmac on...
Here is a sample output from one of my test VMs with A2SERVER. I manually started TashRouter (6502.183) and then atalkd (6502.16).
21:20:22.418742 aarp probe 6502.183 tell 6502.183 <-- TashRouter AARP Probe
21:20:22.622576 aarp probe 6502.183 tell 6502.183
21:20:22.823363 aarp probe 6502.183...
atalkd is emitting the right packets. When you fire up TashRouter, does anything pop up? You should see a burst of AARP probes from TashRouter at a minimum, then eventually periodic RTMP packets roughly every 10 seconds. You will see them from both atalkd's address (3.17) and TashRouter's address.
Something isn't working still. Maybe TashRouter still needs tweaking to work with a tap interface on NetBSD. If everything was working properly, atalkd should have sent a ZIP GetNetInfo packet over the tap interface, and TashRouter would have responded with the setup information. Running...
Set TashRouter's seed_network_max=3. The seed configuration between the two routers has to match (network range 3-3, zone name "EtherTalk Network"). Also, you likely have to create the tap interface as root and run TashRouter as root. This was the case under Linux.
Optionally, you can setup...
Save yourself the hassle and use atalkd to route between your host network interface and the tap interface. Yes, that involves an extra hop over a virtual bridge, but it will save your sanity of VM routing. In A2SERVER, I have tashrouter linked to atalkd using a tap interface called tash0. In...
There was a bit of a cottage industry of emulating the Mac on both the Amiga and Atari ST. Compared to the Mac, they were pretty cheap to buy, plus they had higher resolution graphics vs. an actual Mac Plus! The Amiga could do 640x400 interlaced black and white graphics, while the ST with a...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.