Pi to BSD 2.11 Networking

47 views
Skip to first unread message

Dwain Sims

unread,
Mar 10, 2026, 8:59:49 PM (4 days ago) Mar 10
to [PiDP-11]
Are there any tricks for getting Linux on the underlying Pi to talk to BSD once it is on the network.  Pi networking to the rest of the LAN is fine and working OK to the Internet as well.  This is on wired ethernet, Wireless is not connected.  The BSD system (pdp11) is talking fine to the local net and to the internet as well.  Its just the Pi to pdp11 connections that don't seem to work.  

When I try to telnet from the Pi to the pdp11 I get "No route to host."  Telnet connections from other systems on the net work fine.

Thanks!!

Dwain



Lawrence Fisher (RealTimeCat)

unread,
Mar 11, 2026, 9:59:11 AM (3 days ago) Mar 11
to [PiDP-11]
Dwain,

My experience with Linux Ethernet interfaces has always been that services (i.e. virtualized systems, or in your case, SIMH) cannot interact directly with the host Ethernet interface. On my KVM server I have implemented a dedicated NIC for my host network connection as well as a separate dedicated NIC for all of my virtual machines. 

If you want to be able to Telnet from your Pi host to your SIMH instance you may have to set up your wireless LAN as the primary NIC for your PI and leave the wired NIC unconfigured for your Linux instance.

All access to your PiDP-11 instance will then be via that wired port via your LAN, including connections from your Raspberry Pi Linux instance via your Wifi port.

Johnny Billquist

unread,
Mar 11, 2026, 11:22:40 AM (3 days ago) Mar 11
to pid...@googlegroups.com
The reason for the problems are that if you're using TUN/TAP (which
really is the easy way to do things), the host system will not see
outgoing packets from your simh instance. So they cannot directly
communicate with each other. Communication with any other system will
work just fine.

The solution of having the host system itself not use the wired port is
a really good suggestion. Then you avoid this problem completely.

Otherwise, you will need to start looking at how to create a bridge
device inside your host, to which both your host and your simh is the
connected, and that bridge in turn is connected to the rest of your
network. More complicated, but will also solve the problem.

Johnny
> --
> You received this message because you are subscribed to the Google
> Groups "[PiDP-11]" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to pidp-11+u...@googlegroups.com
> <mailto:pidp-11+u...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/
> pidp-11/31ca8d00-bf4d-4bb0-bfcf-a05395cd547an%40googlegroups.com
> <https://groups.google.com/d/msgid/pidp-11/31ca8d00-bf4d-4bb0-bfcf-
> a05395cd547an%40googlegroups.com?utm_medium=email&utm_source=footer>.

Adam Thornton

unread,
Mar 11, 2026, 11:24:38 AM (3 days ago) Mar 11
to ds...@bayleafnc.org, [PiDP-11]
Rather than using NAT, or dedicating a NIC, I prefer to create a bridge interface, add the ethernet to the bridge, and then create a bunch of TAP interfaces that I add to the bridge, one per guest with networking.

A tool to make this easy is at https://github.com/athornton/brnet-nmcli and I have an older version if you're not using NetworkManager.  But you probably are using it.

Adam

--
You received this message because you are subscribed to the Google Groups "[PiDP-11]" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pidp-11+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/pidp-11/e9e977b5-4663-4a3a-921b-c0b79cd3cda6n%40googlegroups.com.

Clem Cole

unread,
Mar 11, 2026, 4:09:41 PM (3 days ago) Mar 11
to Adam Thornton, ds...@bayleafnc.org, [PiDP-11]
Adam - You beat me to it.  I do something similar on my PiDP-11, but I never need some of your automation because that was pre-systemd-networkd.  I applied the commands as I went years ago, made sure there were persistent across reboots and never looked back 😉.  

As a reminder, this topic was discussed here a few times, but a year ago it was under the subject line: Networking BSD2.11+ installed on RPi4/5 with RPI OS Bookworm from GitHub

For the gory details, the URL https://groups.google.com/g/pidp-11/c/g_-U6TLFB7o will take you through.


FWIW: My Mac is set up similarly for OpenSIMH development, and I can talk to the PDP-10 under TOPS-20 or the PDP-11 under 2.11BSD (macos and the TUN/TAP driver is a little more difficult, but you can get it from the TunnelBrick VPN folks: https://tunnelblick.net/downloads.html)

Note, If there is any interest, I have a fairly current 2.11BSD (i.e. all but the last one or two updates from Steven - IIRC it has a number of the aforementioned fixes) that I made for Dave Plummer (the Dave's Garage guy) when we were working on his 11/83 running and while back).  Although I have been running it OpenSIMH (current) on the Mac as I have a lot more and much larger screens, and the system is so fast.  scp the system image (2.11BSD_xx.dsk)  file in /opt/pidp11/systems directory on your RPi and then make sure you have a boot.ini the older version of simh that Oscar supplies and needs these line to turn on his blinkenlights:
;connect to panel
set realcons host=localhost
set realcons panel=11/70
; We're running on a desktop PC with connection to localhost: max speed!
set realcons interval=1
set realcons connected
;set realcons debug
;show realcons

And you should be in business.  Send me email offline and I give you a pointer to the kit I put togther for Dave.
Clem

From this thread, I probably need to recreate my OS on the RPi2 that drives the PiDP-11 - since I created it [which was from Oscar's initial build].  But just runs and runs, although given the age of the SD card, I suspect I'm playing with fire (I had been thinking it was an RPi3, but I double-checked recently and was surprised to realize that.  But it just works, and on the PiDP-11, the boot.ini file is static and basically the original one that Oscar pushed out.

Reply all
Reply to author
Forward
0 new messages