• Updated 2023-07-12: Hello, Guest! Welcome back, and be sure to check out this follow-up post about our outage a week or so ago.

MacIPgw VM 3.0 | TCP/IP over LocalTalk gateway

mactjaap

Well-known member
Thanks for the Kudos! I really like to hear it worked for you!
 
I think my prediction has come true with in month.  
On the 2th of april 2017 MacTjaap said: 
"I think there is a world market for about five MacIPgw VM’s." 

 
More good news today. With the help of two Linux guru’s if found a fix for the Ethernet errors on the MacIPpi. The Orange Pi hardware solution for macipgw. With this fix it can work 24x7 in your network. The price? Starting at $6,99 for a simple Orange Pi Zero 256 MB. 
Read all about it on:
https://forum.armbian.com/index.php?/topic/3236-appletalkagain
 

DrJosh9000

Member
First off, I'm pretty happy this project even exists, thank you for your efforts!

I'm trying to use MacIPgw-VM-3.0.ova in VirtualBox 5.1.22. I attached a regular Apple USB Ethernet Adapter (en8) to the VM (with an AsantéTalk + Mac Plus on the other end) before firing it up. (I'm expecting to power cycle the AsantéTalk after atalkd is up due to the EtherTalk V1/V2 problem.)

But when I log in, or run nbplkup I get:

nbp_lookup: Cannot assign requested address

I'm guessing something about the network isn't working, causing netatalk to not come up. `systemctl status netatalk` agrees. I can't start it - `systemctl start netatalk` wants a password for the user "ubuntu" (??) and `sudo systemctl start netatalk` doesn't work because "macipgw is not in the sudoers file". Also it generates this error: "sudo: unable to resolve host macipgw-vm: Connection refused", but that shouldn't matter...Ok Ubuntu, block this: reboot, single-user mode, `usermod -a -G sudo macipgw`, exit.

Now I can try `sudo journalctl -xe`, which is informative: netatalk quits because atalkd thinks there are zero interfaces.

ifconfig says the adapter is enp0s3. `sudo vi /etc/netatalk/atalkd.conf` -> append enp0s3 the end -> `sudo systemctl start netatalk`.

Success! Hopefully my story might glean some improvements to a future version MacIPgw-VM.

Screen Shot 2017-05-30 at 11.44.53 am.png

 

mactjaap

Well-known member
[SIZE=10.5pt]@DrJosh9000[/SIZE]

Thanks for the credits! It is always nice if people see you do a lot of work for a small audience! And of course…. I try to get the solution better and better. Then it is very nice to see it really is used!.

About your problem.

Not sure what it is. I can’t reproduce it. Maybe VirtualBox on a Mac is a little bit different? Or maybe you have a different network setup?

I post mine:

Naamloos2.jpg

 If you want to debug, please login as root:

See the "man" page about this, http://www.macip.net/

[SIZE=10pt]• [/SIZE][SIZE=10pt] sshd started at boot. You can login with ssh. User macipgw can login with ssh. Password is also macipgw. If you like to be root login as root or do a sudo su and enter the macipgw user password: macipgw[/SIZE]

Sometimes netatalk is a pain.  A restart of netatalk can help:

/etc/init.d/netatalk restart
Your solution is also possible, but I’m not sure if it is a good idea to put it permanent in the setup.

Could be that if you have a different setup in VirtualBox you get problems with this config,

 

DrJosh9000

Member
When reading macip.net the first time, I didn't notice root login over SSH was allowed. (Although I admin various other systems where that is the case.)

Now that I'm looking at it again, I'm finding the whole page a bit difficult to navigate. Would you be open to some suggestions for making the macip.net site easier to use?

 

markyb86

Well-known member
I'm performing a bit of necromancy in here, but a question on this,

does this work with ethernet equipped macs or strictly localtalk bridged macs?

Thanks!

 

cheesestraws

Well-known member
localtalk bridged macs
If a LocalTalk bridge is doing its job properly, a bridged mac should look identical to an EtherTalk mac.  That said, though, most Ethernet-equipped macs can run IP the "normal" way, rather than MacIP, so I'm guessing that's why it's not mentioned.

 

markyb86

Well-known member
gotcha. I think I'm going to play around with this and see if I can get some of those features running on my SE with a Farallon EtherMacSE.

I've used it over ethernet in the past just fine for FTP and Telnet, but a pre-built solution for WRP at least is pretty cool.

 

lisa2

Well-known member
As was said, it does not matter if the cabling is LocalTalk or EtherTalk.  But note that MacIP is only supported up to System 8.6, System 9 users can not connect using MacIP. Your SE will not support System 9 anyway, so for this case it is moot.

 

mactjaap

Well-known member
My main goal with MacIP “products” like the MacIPgw VM and the MacIPpi are to make it possible for LocalTalk only machines like the Macintosh 512, Macintosh   ED, Macintosh Plus, Portable, PowerBook 100, etc. to connect to the Internet. However some of the features can be interesting for other machines as well. Like a shared Volume to exchange files or the WRP. 

Currently I’m working on a new version for Orange Pi and ... new... for Raspberry Pi. This will include latest version of the WRP and lots of easy file sharing. So you can exchange easily between a MacBook and a Mac 512k. Or between Macs and PC or Linux box. And yes... still available macipgw out of the box. Your own “FastPath” (poor mans edition) to connect to the internet without any hassle or Linux knowledge. 

 

markyb86

Well-known member
Thanks for your work on this!

I have used stunnel and  WRP in the past to bring some modern internet to my iMac G3 and a OS/2 box. I don't have the host machine set up anymore but I already have a virtualbox host up, so this is great.

 

markyb86

Well-known member
Works fine over ethernet. Took a bit of fiddling though. At first, the AppleShare folders showed up just fine, but none of the web routing worked. However, changing the IP address to something on my local network range, and pointing it to my actual router, let me use the VM as a proxy without issue.

Now I just need to get JPEGview on the mac so I can actually see what WRP is feeding me :)

Thanks again!

 

mactjaap

Well-known member
The 172.16.2.0/24 network is only accessible if your Mac is connected via MacIP. If you try to access the “normal” Ethernet IP adres of the MacIPgw you need to use the address given by your home router. That’s in short what you found out yourself. :)

 

NZ_KGB

Member
Thanks for this, it's awesome! I tried getting Vicomsoft Internet Gateway working on a G3 with no luck before I found this.

Se/30 -> phonenet/localtalk -> Power Mac G3 (system 9.2 with localtalk bridge) -> macipgw vm

Can now easily share files between my Windows PC and the SE/30 by mounting the macipgw apple share folder on windows PC.

Telnet is working well

Lots more to try ;)  

 

mactjaap

Well-known member
Thanks! Always nice to know that I made someone happy. 

Main goal of the MacIPgw stuff (www.macip.net)  is to get a hassle free way of connecting your old LocalTalk only machines to the Internet. But in later versions file sharing became also important, which is also a nice feature!

Currently working on version 5.0 for the MacIPpi. This can run on a Raspberry PI. File sharing for all platforms; old school Macintosh, MacOS X, Windows, Linux...you name it. And a new version of the Web Rendering Proxy.

 

dochilli

Well-known member
And perhaps printing to a modern network printer with a laserjet 8 printer driver? Tried to get this to work with the A2Server but had no success. Would be a nice feature.

 

mactjaap

Well-known member
I must be honnest... never tried it.....

is it possible to make a generic solution? Which will work with any laserprinter?

 

dochilli

Well-known member
Here is a description' how it could work.


I used this for setting up a printer in A2Server, but I had no success. Other users said, that it worked for them. I had a lpr on my raspberry that could print to my modern Brother MFC, but my SE/30 did not see the printer. May be that I had to use laserprinter 8.6. driver

 

NJRoadfan

Well-known member
netatalk's PAP printing should work "out of the box" with the LaserWriter 8 driver. The bigger issue is compiling netatalk on recent Linux distros as it requires patches for using more recent OpenSSL libraries and patches to compile against anything newer then CUPS 1.5 if you want printing. Both have been solved and newer versions of CUPS have the added benefit of supporting driverless printing to AirPrint compatible printers.

I have been working on getting netatalk's printing working with something older then the LaserWriter 8 driver. I finally got it working with the LaserWriter 7 driver if you are running an older Mac that can't run LaserWriter 8 for some reason (usually RAM), and the Apple IIgs LaserWriter driver. Support for LaserWriter 6.0 and older isn't happening due to the extensive work to capture and handle the LaserPrep header those drivers require pre-loaded in the printer (7.0 and newer embed it into print jobs automatically). You can run the LaserWriter 7 driver on System 2.0/Finder 4.1 if you really need to!

 
Top