Search results

After rebuilding atalkd with the split-horizon patch reverted I'm sorry to say that the disconnects continue. It didn't seem to change much of anything.

After an entire morning spent chasing kernel panics on the Pi Zero W I was finally able to install this new kernel. It seems to work as advertised! The recipe for tashrouter invocation now works with macvtap and is behaving as well as my attempt yesterday with Raspbian. Currently building a...

npblkup @LocalTalk2ZoneA - returns nothing. The Apple 2 is connected to the Tashtalk hat (Pi Zero). I had been having build problems with the latest netatalk (with fixed horizon behavior), but finally found a workaround. Tomorrow I'll try running with that code. More information: I can no...

Well, that gets things a bit further. getzones shows: root@dockstar:/etc/netatalk# getzones EtherTalk Network LToUDP Network TashTalk Network The Apple 2 finds the dockstar server on the EtherTalk Network and can list files on mounted directories. However, the connection is dropped after...

I restarted the tashrouter, then stopped netatalk, modified atalkd.conf as you suggested and restarted it. The ethertalk network is now showing up as 55, but the debug message remains the same - showing DEBUG: router adding network range 256-256 to zone LocalTalk2ZoneA (now default zone for...

A light just went on... My netatalk server definitely has the 'split horizon' mod, since that was the only way I could get it to cooperate with most of the little bridge boxes. I know there have been a bunch of changes to the netatalk code base as of late, but I was hoping to avoid having to...

The netatalk server 'dockstar' uses this setup: eth0 -router -phase 2 -net 1-255 -addr 1.163 -zone "LocalTalk2ZoneA" I edited the taprouter.py to use network 2, 3 and 4-6. No improvement. I cannot see anything on the Tashtalk network from the server. getzones shows only my zone - I don't...

More information: A lookup from the AFP server does not seem to find the tashtalk router. $ ./nbplkup dockstar:ProDOS16 Image 1.163:3 dockstar:Apple //e Boot 1.163:3 dockstar:AFPServer...

I apologize if I haven't been clear - long day of head banging! I am indeed using a single Apple IIe w/ workstation card connected through a pair of dongles to the DIN port of the tashtalk hat. There is an AFP server on the ethernet side of things. The logon program cannot find the server...

So I've tried a direct connect using a crossover 8-pin cable and a pair of PhoneNet dongles. Same results with either: I can see four zones: LtoUDP Network Tashtalk Network Ethernet Network LocalTalk2ZoneA The last of these is my netatalk server running on a dedicated system. When I try to...

Before I let the smoke out of something, is it safe to directly connect the tasktalk hat to an Apple //gs serial port - or do I need the localtalk transformers + phone wire in between?

I reflashed the SD card with the current 32-bit Raspbian and started working through the recipe. There appears to be a step missing. I have created the /etc/network/interfaces.d/br0 file per instructions, disabled dhcpcd using systemctl and rebooted. Now I have no networking. None of the...

I'm throwing in the towel for now. The writeup I'm trying to follow assumes Raspbian with systemd and I'm running Void Linux. For example, there is no /etc/network/interfaces.d directory in which to create the br0 specification. Clearly this effort will need to wait until the Void Linux folks...

From what I've read here, the issue is centered around the Wifi access point behavior during frame translation. I have a GL.inet router, which is Linux based and hopefully won't exhibit this problem. I'm using Tashtalk with a Pi Zero W and I'm not sure whether it supports a USB<-->ethernet...

Thanks - off I go! Thanks!

That's terrific news. I assume this update would be to a beta or testing release, correct? Where do they publish those?

I'll give that long set of directions a shot. Couple of questions: Can 'wlan0' be substituted for 'eth0' in order to use Wifi? With dhcpcd disabled, how does the RPi get assigned an IP address?

Well, that would explain it... In reading the preceeding pages of this topic I get the impression that the more common tun/tap utilities can also do the trick, but if the recipe is there I must have missed it. Can this work, or do I need to pickup a 64-bit RPi?

]$ modprobe macvtap modprobe: FATAL: Module macvtap not found in directory /lib/modules/6.1.69_1 Blast. Once again, the xbps-query tool finds nothing. How exactly does one get it to accept a wildcard?