GlobalTalk - Global AppleTalk network for MARCHintosh 2024 (and beyond!)

[Mk.558]

Normally on a DDP/IP gateway you have the LocalTalk side as say, 192.168.1.x, while the Ethernet side is 192.168.0.x, and the gateway does what a gateway does.

IPNetRouter and Vicom Internet Gateway require the two networks to be in different subnets. Apparently, Apple IP Gateway ... doesn't do that? Flipping through the manual again, I see no mention that it even says to do that. I will fiddle with it more in the next few days, but I'm not sure if it's actually a gateway. Definitions for this stuff is usually murky from what I can tell, with different textbook definitions in different places.

If it needs AIR or something to serve DDP/IP to a LocalTalk port, that's not really a gateway? From what I can tell it's basically just a DDP/IP server, and doesn't work like the others where it "takes control" so to speak of a serial port. It doesn't get assigned LocalTalk Printer Port or LocalTalk Modem Port.

WWW not working I think is a problem with Mosaic. Mosaic 2.0.1 was my default 68k browser for a little while but haven't used it in years and now it doesn't resolve HTTP traffic on any machine I have. Other browsers work fine.

Edit: It works with LocalTalk Bridge and an AppleTalk bridge, but not by itself.

 

[atariorbit]

I don't really follow, but I try and clarify my statements around where you put the AIR IP addresses to use....

The AIR system is a gateway between LocalTalk (physical cable plugged into printer/serial port of the Mac running AIR) and Ethertalk/MacIP - the Macintosh also has an ethernet adapter in it an can send/recieve ethernet frames to and from it's default route, which is a FW that also has a default route to the gateway device that provides Internet service for me.

I was simply saying- if you want to have two distinct subnets on Ethernet - what device is routing between them and knows how to move the packets around the right way?

I was saying this to back my claim that you should not use two subnets- but put the AIR IP address just on the same subnet as the Macintosh running AIR and it just works without needing any special routing at the TCP/IP level.


Regarding HTTP, as I said, nothing will work save things like http://frogfind.com, and IMHO HTTP browing on a 68k device is just not that interesting.... THere are other much more interesting protocols to use.

 

[Mk.558]

I think I figured it out. Apple IP Gateway is a software gateway that seeds EtherTalk networks with MacIP packets. As it cannot route to a LocalTalk or any other port, you need a bridge between the LocalTalk machines and the normal Ethernet network. The bridge then allows EtherTalk packets through and fro, enabling the MacIP server function to work. Without the bridge (or router, in the case of Apple Internet Router or Farallon Liaison) then the Apple IP Gateway doesn't work to serve MacIP to LocalTalk machines.

Since normally machines with Ethernet don't need MacIP over Ethernet, it's safe to say that a bridge / router is required for use with AIG.

 

[Mu0n]

I tried spinning up QEMU in windows 11 again in preparation for this year's marchintosh but couldn't get to see the other zones at all.
things I did:
-reinstall openvpn
-bridge my regular LAN to TapQemu1
-open udp port 387 to an unclaimed LAN IP
-use that same unclaimed IP in MacTCP in system 7

it doesn't complain when it loads my apple router def file, but it doesn't see anyone else other than me.

thoughts? ideas?

meanwhile, everything loaded up with 0 issue with my hardware Mac SE/30 and I was able to exchange files with others yesterday.

Tried allowing the qemu app itself, then wholesale the firewall for a few minutes, no change unfortunately.