@MacJunky
Great that it works!!!!
I already thought that it would be your internal LAN routing. You now are the world wide, official, first, (much appreciated) user of MacIPgw (besides myself....)
You are right about the hassle. But that is not strange for network issues. Specially AppleTalk/TCP IP issues...
You idea of starting up everything fresh is good. Also with FastPath or IPNetrouter you can have this kind of issues. I have two FathPath's and a machine with IPNetrouter...so I can know!
My advice is to start up your MacIPgw first. Then boot your LocalTalk only Mac if connected with a LocalTalk only bridge. If you have a software LocalTalk bridge fire up that Mac first and finally the LocalTalk only Mac. You will see that it works.
@NJRoadfan
It would be great if you could do some more testing this weekend. I didn't had any feedback on this besides you and MacJunky. It would be great to know what I can improve. About your network issues. The VM machine is not capable of handling the routing to the 172.16.2.0/24 network by itself. This is done on the FreeBSD box. The 172.16.2.0/24 network can be reached by it's tun0 device. The tun0 device simulates a network layer device and it operates with layer 3 packets such as IP packets.
These are the routing tables.
As you can see the FreeBSD box with internal LAN address 192.168.62.10 know where to find the default gateway ( my internet router) and the 172.16.2.0/24 network. That is why you have to tell your default router that the route to the 172.16.2.0/24 can be found on the IP address of your MacIPgw.
About MacIPgw ( http://www.macip.net)
I'm working on a version 2.1 where I will fix some minor details like:
- Stopping the logfiles and cron from flooding the disk
- More free disk space
- gw.macip.net and mac.macip.net are now resolved by DNS
- Installed nmap for testing
- Some more old services are starting up, besides telnetd and ftpd also tftpd, finger, daytime are started. Nice for testing old MacTCP applications.
- Fixed typo in start up script which gave the impression that there was an 8 to much in macipgw dns resolver.
For 2.2 I'm thinking of more applications on the MacIPgw box, like lynx, mutt, etc. Maybe also make a kind of NAT solution to handle with the problem of adding a static route on your default router....
My goal is to have a MacIP gateway which is not to difficult to run and without any costs. If you have two Mac's, one with a network card and LocalTalk bridge control panel and one with LocalTalk only it already is enough. If you have one Mac with a hardware LocalTalk bridge only it also works.
So.... all readers of the forum are invited to test!!! I'm more then happy to help with your setup and to answer your questions.
Great that it works!!!!
I already thought that it would be your internal LAN routing. You now are the world wide, official, first, (much appreciated) user of MacIPgw (besides myself....)
You are right about the hassle. But that is not strange for network issues. Specially AppleTalk/TCP IP issues...
You idea of starting up everything fresh is good. Also with FastPath or IPNetrouter you can have this kind of issues. I have two FathPath's and a machine with IPNetrouter...so I can know!
My advice is to start up your MacIPgw first. Then boot your LocalTalk only Mac if connected with a LocalTalk only bridge. If you have a software LocalTalk bridge fire up that Mac first and finally the LocalTalk only Mac. You will see that it works.
@NJRoadfan
It would be great if you could do some more testing this weekend. I didn't had any feedback on this besides you and MacJunky. It would be great to know what I can improve. About your network issues. The VM machine is not capable of handling the routing to the 172.16.2.0/24 network by itself. This is done on the FreeBSD box. The 172.16.2.0/24 network can be reached by it's tun0 device. The tun0 device simulates a network layer device and it operates with layer 3 packets such as IP packets.
These are the routing tables.
Code:
Routing tables
Internet:
Destination Gateway Flags Refs Use Netif Expire
default 192.168.62.1 UGS 0 0 em0
localhost link#3 UH 0 16481 lo0
172.16.2.0 link#4 UH 0 0 tun0 =>
172.16.2.0 172.16.2.1 US 0 980 tun0
172.16.2.1 link#4 UHS 0 0 lo0
192.168.62.0 link#1 U 0 2805 em0
192.168.62.10 link#1 UHS 0 0 lo0About MacIPgw ( http://www.macip.net)
I'm working on a version 2.1 where I will fix some minor details like:
- Stopping the logfiles and cron from flooding the disk
- More free disk space
- gw.macip.net and mac.macip.net are now resolved by DNS
- Installed nmap for testing
- Some more old services are starting up, besides telnetd and ftpd also tftpd, finger, daytime are started. Nice for testing old MacTCP applications.
- Fixed typo in start up script which gave the impression that there was an 8 to much in macipgw dns resolver.
For 2.2 I'm thinking of more applications on the MacIPgw box, like lynx, mutt, etc. Maybe also make a kind of NAT solution to handle with the problem of adding a static route on your default router....
My goal is to have a MacIP gateway which is not to difficult to run and without any costs. If you have two Mac's, one with a network card and LocalTalk bridge control panel and one with LocalTalk only it already is enough. If you have one Mac with a hardware LocalTalk bridge only it also works.
So.... all readers of the forum are invited to test!!! I'm more then happy to help with your setup and to answer your questions.