MrAvaronald wrote on 2024-08-14, 12:14:

I've used this command in Raspberry Pi OS to start pppd: […]
Show full quote

I've used this command in Raspberry Pi OS to start pppd:

Copy code to clipboard

1pppd ttyUSB0 57600 local lock passive proxyarp defaultroute noauth persist mtu 576 192.168.0.161:192.168.0.162

.

Bit of a skim of it, and a look at man pppd, and that "defaultroute" I wonder about:

man pppd wrote:

defaultroute
Add a default route to the system routing tables, using the peer as the gateway, when IPCP negotiation is successfully completed. This entry is removed when the PPP connection is broken. This option is privileged
if the nodefaultroute option has been specified.

Try changing it to nodefaultroute..... (or removing it)

progman.exe wrote on 2024-08-15, 01:28:

Bit of a skim of it, and a look at man pppd, and that "defaultroute" I wonder about:

man pppd wrote:

defaultroute
Add a default route to the system routing tables, using the peer as the gateway, when IPCP negotiation is successfully completed. This entry is removed when the PPP connection is broken. This option is privileged
if the nodefaultroute option has been specified.

Try changing it to nodefaultroute..... (or removing it)

I tried it and unfortunately removing defaultroute or changing it to nodefaultroute didn't do anything. Still can't access anything beyond Raspberry.

In and of themselves each command won't do much, but they will all be needed. The commands set up the network interface, tell the computer to allow packets to be passed between network interfaces, and then set up the Linux firewall to do network address translation.

Personally I would not use NAT, I'd use actual routing, but doing that does mean adding a static route on your home's main network router. That is a step that has different details for every router, so in a way using NAT is easier. The ancient PC also gets isolated somewhat from the rest of the network with a NAT set up.

Whilst I use ppp for my broadband, I've not used it like how you are trying to use it. That ppp0 on the Pi having no IP, according to screen shot in the article on Medium, baffles me a bit, but I think I can run with it. Maybe an IP is only assigned once a PPP link is established?

Just to rule out the basics:
- The Pi can ping 127.0.0.1
- the Pi can ping its own 192.168.x.y IP on wlan0.
- The Pi can ping the wifi Access Point
- the Pi can ping the internet
- the Pi can be pinged from other computers on your LAN
If any of those fail, fix it, because they are signs there is something fundamentally set up wrong.

There are things too that can get in the way. I do not run NetworkManager on any of my machines, on Slackware, Debian and derivatives, I use their traditional network config: text files somewhere in /etc. Maybe NetworkManager is running on your Pi and hindering you trying to tell the machine what to do? A mate's Ubuntu machine was doing that when I tried to fix his wifi: I disabled networkmanager and configured the network with /etc/network/interfaces to get it working reliably.

But one other thing might be to do with the network ranges. The PPP stuff is using 192.168.0.x , and if your home LAN is already using that range, it might be a problem. You could try changing 192.168.0.161:192.168.0.162 to 192.168.10.161:192.168.10.162 . A corresponding edit (at least) in mtcp.cfg would be needed on the DOS machine, too.

One other thing, can your 386's serial ports do the speeds you are trying for? In the article the guy is using a 286 and serial speeds of 115200. I really doubt that is possible, based on how our 486 when I was a kid could only do 19200. 9600 bps I think is historically a stable speed for serial stuff. Might be worth making sure your serial settings are well within the specs of the hardware.