Search results

Rambling/rubber-duck-debugging ahead, again. I have AURP on the brain. I've tried to get through the spec before and was only met with an overwhelming sense that I'd rather be doing anything else, but lately the gears have started to turn a little. It's not hard to imagine how I'd rig up a...

So, for the moment, anyway, I have inserted AppleTalkPort into the class hierarchy between Port and EtherTalkPort/LocalTalkPort. Only change that should be required to your router configuration is to change from tashrouter.port.localtalk.tashtalk import TashTalkPort to from...

Rambling/rubber-duck-debugging ahead. The more I learn about AppleTalk networking, the harder it becomes to resolve with the current design of TashRouter. Am currently in the process of removing NullModemPort because even though it does work, it works using RTMP and ZIP, which shouldn't be...

I've been working to try to make TashRouter's behavior more correct in a number of places in order to better support Ports that are not strictly AppleTalk networks (half-routers and such) and to lay the groundwork for fixing things like this issue that's been outstanding for two years now. I...

This (the first half) is the part that looks odd to me - LocalTalk activity but no corresponding activity on the UART output. I'm assuming that the dense part of the first half is the ImageWriter firing out a bunch of ENQs to make sure its chosen address is not in use, but not sure about the...

Just to ensure all the bases are covered - did the non-working phone cord have four conductors? (PhoneNet uses the second pair, which many phone cords omit.)

8 channels should be plenty. The signals you want to attach to are all on the PIC (U2 on the USB-TashTalk board): .--------. Supply -|01 \/ 08|- Ground LocalTalk <-> RA5 -|02 07|- RA0 --> UART Out Driver Enable <-- RA4 -|03 06|- RA1 <-- UART In...

Correct on both counts. TashTalk (the PIC firmware, that is) does no filtering of what it sees on the LocalTalk bus - every frame it sees, whether it's a control frame (RTS, CTS, ENQ, ACK) or a data frame, no matter who it's addressed to, is relayed over the UART output. Frames that TashTalk...

It could be, if someone who's more of an electrical engineer than I am decided to lay out a board (and an enclosure)... I'd take a stab at it myself, but the thing is that mains current is involved... I don't feel super comfortable dealing with that, both from the perspective of my own skills...

I just pushed a change to the repo that adds a brand new type of port, a NullModemPort. Previously I had ignored the "half router" use case that Inside AppleTalk detailed, but this port implements exactly that. For example, running this router on a Windows machine: router = Router('router'...

Excellent, glad to hear it!

It defaults to 0.0.0.0, but you can change the interface address for LtoudpPort by passing the intf_address argument to it, comme ça: router = Router('router', ports=( LtoudpPort(seed_network=1, seed_zone_name=b'LToUDP Network', intf_address='1.2.3.4'), MacvtapPort(macvtap_name='macvtap0'...

Okay, this is what I did, it's been pushed to github - @fergycool, can you give this a try? Besides the erroneous behavior of the AT ImageWriter and friends, are there any consequences of them being short form? TashRouter's Name Information Service broadcasts short-form DDP datagrams, and...

Hmm. So this is caused by LkupRouter routing a datagram that it's pretending it didn't originate, which means it'll have a hop count of 1, which means it can't be short-form... but it tries to make it short form and fails. I could solve this one of two ways: One, I could force the generated...

Okay, so I've pushed an update to the github with two changes: One, the 'lookup router' that was in name_information5.zip that should make the AppleTalk ImageWriter II work properly. This behavior is disabled by default, though - to enable it, add route_lkup_replies=True to the arguments to...

Trying to clear some of the many rocks out of my head and work a little on TashRouter again... Thanks for this, I've merged it in. I also made a change to support BSD taps, which have a slightly different interface to Linux TUN/TAP and broke that into two classes (LinuxTapPort and BsdTapPort)...

Hmmm. Will have to keep an eye out for one to come up for sale...

Interesting! I'd love to add that to the device list - there are some special questions that can be asked of mice, like which of the three possible protocol handlers they support. I'll message you about it shortly (been crazy busy lately...)

I haven't! I did get my hands on a JL Cooper Media Control Station at one point and RE its protocol, but it sounds like the two are quite different animals... the Media Control Station has a mode that sends proprietary ADB commands, but mostly it seems you program it to send keystrokes or mouse...

So one of the creators of the original ADB I/O has resurfaced and is selling five of them on ebay... bit rich for my blood at $280 starting bid, though. https://www.ebay.com/itm/198289571175 It's made me wonder, though, what ever happened to the board designs folks were working on? I'd be...