problem getting ethernet attached to BSD2.11

[bmeyer29]

Hi all! First of all, I'm really impressed with the quality and attention to detail on my new PiDP-11. Thanks, Oscar!

I'm new to simh, and have trouble getting simh to link to an ethernet port in the BSD2.11 image. 

The error when starting simh is:

ETH devices:

 eth0   udp:sourceport:remotehost:remoteport (Integrated UDP bridge support)

Eth: Pcap capable device not found.  You may need to run as root

../bootscripts/2_211bsd.script-35> att xu0 eth0

File open error

MAC=08:00:2B:AE:B6:46

Seeing references to pcap elsewhere, I loaded the lib with:

sudo apt-get install libpcap-dev, then rebooted the host. No difference in result

I've seen in other posts that one workaround is to add an external USB to Ethernet adapter. I had one on hand so I've added it, and changed the connection in the bootscript from "att xu0 eth0 to eth1.

when started simh with ... /pidp11.sh 2 (for BSD2.11 image)

the error changed to:

ETH devices:

 eth0   udp:sourceport:remotehost:remoteport (Integrated UDP bridge support)

../bootscripts/2_211bsd.script-35> att xu0 eth1

File open error

MAC=08:00:2B:AE:B6:46

I've also seen comments about making the interface promiscuous, but don't know how to do that.

Any help would be greatly appreciated!

Details:

RPi3 runing latest version of Stretch. Have Wifi dongle attached and able to ssh through it.

generic USB to Ethernet attached.

from sim> sh ver

PDP-11 simulator V4.0-0 Current REALCONS build May 16 2018

...

Simulator Compiled a C arch: ARM (Release Build) on May 16 2018

...

OS:Linux Blinken 4.14.71-v7+ #1145

from sim> sh dev

...

XU address=17774510-1774517, vector=120, BR5, MAC=08:00:2B:AE:B6:46 type=DELUA, throttle=disabled

--------- 

from the host rpi3:

 dmesg | grep eth1

[    5.163660] r8152 1-1.4:1.0 eth1: v1.09.9

[    7.326256] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready

[    7.793265] r8152 1-1.4:1.0 eth1: carrier on

[    7.793321] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready

-----------

ifconfig

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet 192.168.1.139  netmask 255.255.255.0  broadcast 192.168.1.255

        inet6 fe80::bbd0:3001:f497:dd30  prefixlen 64  scopeid 0x20<link>

        ether b8:27:eb:17:66:09  txqueuelen 1000  (Ethernet)

        RX packets 15938  bytes 1012822 (989.0 KiB)

        RX errors 0  dropped 15  overruns 0  frame 0

        TX packets 3915  bytes 448871 (438.3 KiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet 192.168.1.117  netmask 255.255.255.0  broadcast 192.168.1.255

        inet6 fe80::76c2:22f6:1f2f:c6e7  prefixlen 64  scopeid 0x20<link>

        ether 70:88:6b:82:78:ff  txqueuelen 1000  (Ethernet)

        RX packets 14305  bytes 1130966 (1.0 MiB)

        RX errors 0  dropped 15  overruns 0  frame 0

        TX packets 136  bytes 8915 (8.7 KiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536

        inet 127.0.0.1  netmask 255.0.0.0

        inet6 ::1  prefixlen 128  scopeid 0x10<host>

        loop  txqueuelen 1000  (Local Loopback)

        RX packets 7805249  bytes 750282140 (715.5 MiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 7805249  bytes 750282140 (715.5 MiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet 192.168.1.188  netmask 255.255.255.0  broadcast 192.168.1.255

        inet6 fe80::f0ba:c878:7c9a:248d  prefixlen 64  scopeid 0x20<link>

        ether b8:27:eb:42:33:5c  txqueuelen 1000  (Ethernet)

        RX packets 4717  bytes 548507 (535.6 KiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 367  bytes 29043 (28.3 KiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[Henk Gooijen]

I never used an ethernet port, but I have read many times about issues getting an ethernet port working in SimH.
Did your SimH PDP-11 build include the Pcap library?  That's all I can remember as being very important.
And what I also remember is that a WiFi dongle is even more tricky to get working in  SimH ...
For more on this issue, check out the SimH maillist.

[Craig Ruff]

> On Nov 10, 2018, at 11:47 AM, bmeyer29 <bmeyer...@gmail.com> wrote:
>
> Hi all! First of all, I'm really impressed with the quality and attention to detail on my new PiDP-11. Thanks, Oscar!
>
> I'm new to simh, and have trouble getting simh to link to an ethernet port in the BSD2.11 image.

I've used the Ethernet with simh and 2.11 successfully on my Mac in the past, but after some upgrades of macOS it isn't currently behaving. While there are no errors from simh on startup, the simulated 2.11 system isn't able to contact any other host on my network.

[bmeyer29]

Update Nov 12, 2018 (Happy Veteran's Day!):

Thanks to those who have responded already! Here is some additional info:

1) My original post was about using the image referenced on Oscar's page, located at https://github.com/PiDP/pidp11. I'm not certain if libpcap was in place when it was compiled, but it does show up in the src files downloaded from that site, so my assumption is that yes, it was there at compile time. 

Please let me know if that is incorrect.

2) There are references to a technique for adding a second ethernet port (eth1) and bridging a tap device to the first (eth0) to allow both the host and the sim pidp-11 to access the net. This is described in: https://github.com/simh/simh/blob/master/0readme_ethernet.txt

However, the closest script example in there was for Ubuntu 10.04, so some changes were required to make it work on raspbian stretch. I can provide if anyone is interested. After running it, there are two new devices displayed by ifconfig: br0 and tap0, as expected. However, simh doesn't recognize tap devices when type "sh tap", although it does recognize eth devices with "sh eth". So it won't allow a connection to an xu device. One other thing I had to change in the script in 0readme_ethernet.txt. It says to attach to an xq device rather than an xu device, but of course simh doesn't like xq for a unibus pdp-11/70. 

3) Ok, so by the end of the weekend, I was getting cross-eyed looking at rpi text screens, and decided to switch over to the nice windows-based setup with a pretty interactive graphics display by http://www.retrocmp.com/projects/blinkenbone/simulated-panels/243-blinkenbone-panelsim-pdp11-70 . Very pretty and nicely done! I have the latest winpcap installed, but get similar message that it can't find a pcap device and that I may need to run as root. ARRRGH!!

I'm open to any other suggestions or other places to look for assistance. It's unlikely I'm the only one trying to make a link between this great project and the network. My first thought was to look for a forum relative to simh, but thought there would be lots of energy to get this going here with the PiDP-11. 

Many thanks, Bob

[Tomas Prybil]

On Mon, Nov 12, 2018 at 09:19:07AM -0800, bmeyer29 wrote:
> Update Nov 12, 2018 (Happy Veteran's Day!):
>
> Thanks to those who have responded already! Here is some additional info:
>
> 1) My original post was about using the image referenced on Oscar's page,
> located at https://github.com/PiDP/pidp11. I'm not certain if libpcap was
> in place when it was compiled, but it does show up in the src files
> downloaded from that site, so my assumption is that yes, it was there at
> compile time.

Bob, (and Oscar)
If You browse the history of this group you will find another couple of
mentions regarding the ethernet behaviour of the PiDP distribution of SIMH.
I made a cludge and recompiled with success, but I'm sure that could be done
in a more propoer way.
Anyway I think it would be nice if someone could make a proper recompile and
ask Oscar to include this in forthcoming updates.

BR
/t

> --
> 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 on the web visit https://groups.google.com/d/msgid/pidp-11/12e6a5cb-6821-4ef1-b3d0-92b5b0f12ec2%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[bmeyer29]

@BR

Thanks for your quick reply! Tell me about your kludge, please. I'm willing to create a new sim and document it for others if found useful.

-bmeyer29

[bmeyer29]

Update Nov 16, 2018

I now see multiple eth, including nat and vde devices in simh, thanks to post from Mark Matlock in another thread here, dated Oct 21. He provided a pdp-11 compile script, which included those additional devices. I'm still stuck in knowing how to connect the xu interface to nat or vde. The examples in 0readme_ethernet.txt seem straightforward, but I'm unable to verify the connection is complete. I must be missing something simple. Any help greatly appreciated!

details:

sim> sh xu

XU      address=17774510-17774517, vector=120, BR5, MAC=08:00:2B:AE:B6:46

        type=DELUA, throttle=disabled

        attached to eth0

sim> sh eth

ETH devices:

eth0   eth0                                 (No description available)

eth1   wlan0                                (No description available)

eth2   eth1                                 (No description available)

eth3   tap:tapN                             (Integrated Tun/Tap support)

eth4   vde:device{:switch-port-number}      (Integrated VDE support)

eth5   nat:{optional-nat-parameters}        (Integrated NAT (SLiRP) support)

eth6   udp:sourceport:remotehost:remoteport (Integrated UDP bridge support)

Many thanks!

On Saturday, November 10, 2018 at 12:47:18 PM UTC-6, bmeyer29 wrote:

[Ian Schofield]

Dear All,

 This can be a bit involved. Firstly, I haven't managed to get a valid connection via wlan0. This is a known issue with Linux in that the wlan interface is not quite what is seems. But, the standard Raspian config allows eth0 to be used without resorting to tun/tap/nat etc. This requires a build modification which is configured in the directory of the link below. To rebuild pidp11_realcons, use the make.sh command. However, one side effect is that to attach to the local eth0, the simh executable (pdp11_realcons) must be run as root. I have not determined the reason for this. In contrast, should you wish to use the pidp1170_blinkenlightd module, I have rebuilt this to reference gpiomem such that this does not require root creds. I have attached a build containing the scripts and executables (ummm) that will run BSD. It expects the BSD disk images to be in directory named '2' in the same directory as the scripts. You can use Oscars's original image but the one I use is from http://www.ak6dn.com/PDP-11/2.11BSD/?C=D;O=D. Put the image 2.11BSD_rq.dsk in this directory as well. This version of BSD is configured for networking but you will need to set it up. Finally, the pidp1170_blinkenlightd build uses gpiomem as above and contains an appalling kludge to reduce the flashing led issue. (See thread on this). Finally finally, this pdp11_realcons is built with and references SDL2 used by the VT11 susbsystem. You may need to install this (sudo apt-get install libsdl2-dev). 

 

Link:  (if you need it) https://drive.google.com/file/d/1C6O4rnYhuXYGFrmToJsUtt18zao_9Rgk/view?usp=sharing

Regards, Ian.

[Mark Matlock]

bmeyer29,

   I haven't had much time to work on the ethernet issues (pesky day job keeps me hopping), but I have some time off over Thanksgiving

and would love to get stuff working. I do have a Simh RSX11M+ V4.6 system with Johnny Billquists TCP/IP and DECnet working perfectly

on a VMware Ubuntu running under MAC OSX. Also, I have had Raspberry PI Simh version of the same working in the past. I thought

the big issue was the lack of vde or other ethernet bridge capabilities being included in Simh with REALCONS, but there are additional

issues of some sort. The Simh command below Sim>show eth was new to me and I thank you for that tip as it provides a good bit of

additional info on the status of the connections.

Ian,

   Earlier this morning you posted some new make files and a large amount of new info that I have yet to experiment with. I have run Simh

from root and do get the attach to work without resorting to vde or tap etc. However when I am getting an initialization failure from DECnet

when I set the circuit on.

   If I understand your message in the post from earlier today you do have ethernet connectivity with BSD 2.11 Unix now?

Thanks!

Mark

[bmeyer29]

Mark and Ian:

Many thanks for your assistance! I think the PiDP-11 sim from Mark gets me to the point where I has several ethernet options, described in the github.com/simh/simh/0readme_ethernet.txt, including tun/tap, vde, and nat. Of those three, nat appears to be described as able to do tcp/ip across the internet, but not decnet. Since I don't have any other DEC equipment, it seems NAT is my best choice. I think I have a handle on setting up a nat connection to the DEC xu device

The following two lines are excerpts from the whole bootscript listed below

att xu nat:gateway=192.168.1.1,dns=192.168.1.1,network=192.168.1.44,tcp=2323:192.168.1.44:23

What I'm missing is how to connect this NAT device back to xu so that an external telnet from the host RPi3 or elsewhere on my LAN, makes a connection to the ethernet drivers inside the PiDP11. If i start the sim, the type ^D to get into multi-user mode with the network "enabled", I don't see anything in device tables, routing tables, net status, that says there is a connection between the xu device with NAT, and tools such as ftp, telnet, and so on. Also, when I run Kermit, I get a core dump message. Any guidance on this phase of the installation? Many thanks! -bmeyer29

Details of simh pidp-11 config file:

detach all

reset all

; bsd211 install part afer opening 1144.sim

set cpu 11/70 4096K fpp

set throttle 2M

show cpu hist=100

set tm enabled

attach tm0 ../bootscripts/2/211bsd.tap

set tti 7b

set tto 7b

; to work with kermit

;set tti 8b

;set tto 8b

;set cons telnet=23

; set one DZ11 8 line async mux

set dz enabled

set dz lines=8

set dz 8b

;set dz vector=310

;attach 8 DZ11 lines to telnet 4000..4007

;attach -am dz 4000; -am for modem control

attach dz 4000

;

; following added by rdm 2018/11/09 for usb to serial port

;attach dz -V line=0,NoModem,connect=/dev/ttyUSB0;19200-8n1

sho dz

; network on UBUNTU

set xu enabled

set xu type=delua

sh xu eth

;sh xu tap

;att xu0 eth0

; attach changed to vde rdm 20181111

;att xu vde:/tmp/switch1

;att xu tap:tap0

att xu nat:gateway=192.168.1.1,dns=192.168.1.1,network=192.168.1.44,tcp=2323:192.168.1.44:23

;att xu0 eth5

sh xu mac

sh xu

; rp0 muss ein rm02/3 sein!

set rl0 rl02

att rl0 ../bootscripts/2/tmp.rl02

; RX02 floppy drive

set rx disabled

set ry enabled

attach ry0 ../bootscripts/2/tmp.rx02

att rp0 ../bootscripts/2/211bsd.rm02

; mount second disk, get formated with bad sectors

;att ../bootscripts/2/rp1 root1.rm02

; be sure to create bad block table on last track, if file new!

; 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

; real VT100 locks on 24 newlines?

echo

echo

echo

echo

echo

echo

echo

echo

echo

echo

boot rp0

echo on the "Disk?" prompt, enter "xp(0,0)unix"

-------------------------------

[Mark Matlock]

BMeyer29,

    The one thing that I did not see in your Simh configuration file (see Fig #5) was any reference to a

CSR address for the delua, For BSD to access the delua Simh would need to make the device available

at an I/O address. There could be other issues as well such as the Vector

which I think is the problem I have below.

    Below (Fig #1) is the output of a show xu on my PiDP-11. One thing that bothers me is that I don't seem to

be able  to set a vector for xu. I have seen a vector get set in DELQA emulations in Simh. The vector is important

because when a ethernet packet arrives or a send completes an interrupt should occur and the vector

points to the part of the OS that handles the interrupt.

   I am running RSX!1M+ and the NCP SET LIN UNA-0 ALL completes fine as well as the

NCP SET CIR UNA-0 STA ON but then in a bit I get an initialization error on the UNA-0 Circuit.

Also, RSX does see some activity on the counters for UNA-0 (See FIG #2) Also, in RSX

both NCP and CONfigure does show that RSX sees the DELUA and has the CSR and Vector

but if Simh does not have a vector associated with the DELUA that would be a problem I think.

I had been getting Circuit Initialization failures, but now I don't see that however the other

DECnet nodes just aren't seen. DECnet up which does not require anything except MAC addresses for

ethernet transport. The MAC address does seem to be set fine and does propagate out from

the tap0 device to the br0 device. (see FIG #3) 

   So to summarize if Simh does not simulate a vector interrupt from 120 then this is about what one

might expect. Things get configured via the CSR but RSX never sees a response from the DELUA.

   In your BSD I didn't see a CSR or a Vector so that is a problem to be investigated. Also, you

should be able to telnet into BSD via Simh on port 4000 if you comment

sim>attach dz 4000

   The Simh telnet connection to RSX does work fine for me. (see Fig #4)

   I feel that we are very close but of course close only counts in hand grenades and thermonuclear

devices.

Best,

Mark

FIG #1

sim> sho xu
XU      address=17774510-17774517, no vector, BR5, MAC=AA:00:04:00:0C:78
        type=DELUA, throttle=disabled
        attached to tap:tap0

sim> sh eth
ETH devices:
 eth0   eth0                                 (No description available)
 eth1   wlan0                                (No description available)

 eth2   tap0                                 (No description available)
 eth3   br0                                  (No description available)
 eth4   tap:tapN                             (Integrated Tun/Tap support)
 eth5   vde:device{:switch-port-number}      (Integrated VDE support)
 eth6   nat:{optional-nat-parameters}        (Integrated NAT (SLiRP) support)
 eth7   udp:sourceport:remotehost:remoteport (Integrated UDP bridge support)
Open ETH Devices:
 XU     tap:tap0 (No description available)
Ethernet Device:
  Name:                    tap0
  Reflections:             0
  Self Loopbacks Sent:     2
  Self Loopbacks Rcvd:     0
  Packets Sent:            93
  Packets Received:        382204
  Asynch Interrupts:       Disabled
  Read Queue: Count:       200
  Read Queue: High:        200
  Read Queue: Loss:        2402
  Peak Write Queue Size:   1

Fig #2

RSX>ncp sho lin una-0 char

Line characteristics as of 1-JAN-2017 21:49:28

Line = UNA-0

   Controller = Normal
   Counter timer = Off
   Protocol = ETHERNET
   Controller CSR = 174510, Vector = 120
   Priority = 5

>ncp sho cir una-0 cha

Circuit characteristics as of 1-JAN-2017 22:07:55

Circuit = UNA-0

   Service = Enabled
   Level one cost = 3
   Level two cost = 3
   Maximum routers = 5, Router priority = 64
   Hello timer = 15, Counter timer = Off
   Owner = XPT
   Type = ETHERNET

>ncp sho cir una-0 cou

Circuit counters as of 1-JAN-2017 22:02:42

Circuit = UNA-0

      50522  Seconds since last zeroed
          0  Terminating packets received
          0  Originating packets sent
          0  Corruption loss
          0  Transit packets received
          0  Transit packets sent
          0  Transit congestion loss
          0  Circuit down
          0  Initialization failure
          0  Adjacency down
          0  Peak adjacencies
          0  Bytes received
        392  Bytes sent
          0  Data blocks received
         14  Data blocks sent
          0  User buffer unavailable

RSX>con dis cont att
SYS
                PDP-11/70, EIS,UNIBUS_Map,D-Space,SWR,Cache,FPP,
                Clock=KW11-L, $TKPS=60., $TTPRM=000002, Cache_control=000001
WEA
                Csr=174510, Vector=000120, Pri=000005, Urm=000001
YLA
                Csr=177560, Vector=000060, Pri=000005, Urm=000001
YLB
                Csr=176510, Vector=000310, Pri=000005, Urm=000001
YLC
                Csr=176520, Vector=000320, Pri=000005, Urm=000001
YLD
                Csr=176530, Vector=000330, Pri=000005, Urm=000001
YVA
                Csr=160440, Vector=000340, Pri=000005, Urm=000001
DUA
                Csr=172150, Vector=000154, Pri=000005, Urm=000001
MUA
                Csr=174500, Vector=000260, Pri=000005, Urm=000001
DYA
                Csr=177170, Vector=000264, Pri=000005, Urm=000001
DDA
                Csr=176500, Vector=000300, Pri=000004, Urm=000001
LHA
                Csr=177776, Vector=000000, Pri=000005, Urm=000001

Fig #3

Linux $ ifconfig
br0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 1500
        inet 192.168.0.189  netmask 255.255.255.0  broadcast 192.168.0.255
        ether aa:00:04:00:0c:78  txqueuelen 1000  (Ethernet)
        RX packets 662308  bytes 72276112 (68.9 MiB)
        RX errors 0  dropped 37  overruns 0  frame 0
        TX packets 24556  bytes 6195501 (5.9 MiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 1500
        inet 169.254.42.164  netmask 255.255.0.0  broadcast 169.254.255.255
        inet6 fe80::5fd8:3d29:aef3:33c8  prefixlen 64  scopeid 0x20<link>
        ether b8:27:eb:29:3d:0d  txqueuelen 1000  (Ethernet)
        RX packets 666594  bytes 81999870 (78.2 MiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 25602  bytes 6527410 (6.2 MiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>

        loop  txqueuelen 1  (Local Loopback)
        RX packets 7075666  bytes 700965487 (668.4 MiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 7075666  bytes 700965487 (668.4 MiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

tap0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 1500
        inet 169.254.30.254  netmask 255.255.0.0  broadcast 169.254.255.255
        inet6 fe80::f9bd:300e:1bde:edb9  prefixlen 64  scopeid 0x20<link>
        ether 06:e1:07:ee:91:01  txqueuelen 1000  (Ethernet)
        RX packets 97  bytes 5820 (5.6 KiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 657199  bytes 81187483 (77.4 MiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet 192.168.0.55  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fe80::4b47:f914:57fe:59b3  prefixlen 64  scopeid 0x20<link>
        ether b8:27:eb:7c:68:58  txqueuelen 1000  (Ethernet)
        RX packets 195133  bytes 48904631 (46.6 MiB)
        RX errors 0  dropped 3  overruns 0  frame 0
        TX packets 223  bytes 37207 (36.3 KiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Fig #4

Linux $ telnet 192.168.0.55 10001
Trying 192.168.0.55...
Connected to 192.168.0.55.
Escape character is '^]'.

Connected to the PDP-11 simulator VH device, line 0

>hello

Account or name: matlock
Password:

RSX-11M-PLUS V4.6   BL87    [1,54] System    PIDP11
1-JAN-2017 22:23   Logged on Terminal TT4:  as MGM2

On Saturday, November 17, 2018 at 11:05:00 PM UTC-6, bmeyer29 wrote:

Mark and Ian:

Many thanks for your assistance! I think the PiDP-11 sim from Mark gets me to the point where I has several ethernet options, described in the github.com/simh/simh/0readme_ethernet.txt, including tun/tap, vde, and nat. Of those three, nat appears to be described as able to do tcp/ip across the internet, but not decnet. Since I don't have any other DEC equipment, it seems NAT is my best choice. I think I have a handle on setting up a nat connection to the DEC xu device

The following two lines are excerpts from the whole bootscript listed below

att xu nat:gateway=192.168.1.1,dns=192.168.1.1,network=192.168.1.44,tcp=2323:192.168.1.44:23

What I'm missing is how to connect this NAT device back to xu so that an external telnet from the host RPi3 or elsewhere on my LAN, makes a connection to the ethernet drivers inside the PiDP11. If i start the sim, the type ^D to get into multi-user mode with the network "enabled", I don't see anything in device tables, routing tables, net status, that says there is a connection between the xu device with NAT, and tools such as ftp, telnet, and so on. Also, when I run Kermit, I get a core dump message. Any guidance on this phase of the installation? Many thanks! -bmeyer29

Fig #5

Details of simh pidp-11 config file:

[Mark Matlock]

All,

    I just re-read my previous post and realized that I did not explain what happens when I try to set a

vector for xu in Simh.

Best,

Mark

Setting CSR address, no problem

sim> set xu address=17774510

sim>

sim> sh xu

XU      address=17774510-17774517, no vector, BR5, MAC=AA:00:04:00:0C:78
        type=DELUA, throttle=disabled
        attached to tap:tap0

Trying to set Vector

sim> set xu vector=120
Non-existent parameter

Also, it does not show up as a valid command. I vaguely recall that some devices don't

have switch jumpers for vector and are configure by software through the CSR.

Anyone have any ideas on this?

sim> help set xu

XU device SET commands:

set XU ADDRESS=val             
set XU AUTOCONFIGURE           
set XU MAC=xx:xx:xx:xx:xx:xx    MAC address
set XU STATS                    Display or reset statistics
set XU TYPE={DEUNA|DELUA}       Display the controller type
set XU THROTTLE=DISABLED|TIME=n{;BURST=n{;DELAY=n}}
                                Display transmit throttle configuration
set XU ENABLE                   Enables device XU
set XU DISABLE                  Disables device XU
set XU DEBUG                    Enables debugging for device XU
set XU NODEBUG                  Disables debugging for device XU
set XU DEBUG=TRACE;WARN;REG;PACKET;DATA;ETH
                                Enables specific debugging for device XU
set XU NODEBUG=TRACE;WARN;REG;PACKET;DATA;ETH
                                Disables specific debugging for device XU

*XU device DEBUG settings:
    TRACE       trace routine calls
    WARN        warnings
    REG         read/write registers
    PACKET      packet headers
    DATA        packet data
    ETH         ethernet device

[Johnny Billquist]

Matt - that is exactly as it is supposed to be. The ethernet controllers do not have dip switches to set the vector so there is no corresponding command in simh. These controllers set up the vector in software.

Johnny

Mark Matlock <ma...@matlockfamily.com> skrev: (18 november 2018 16:15:32 CET)

--
Skickat från min Android-enhet med K-9 Mail. Ursäkta min fåordighet.

[Mark Matlock]

Johnny,

   Thanks for refreshing my somewhat dusty, rusty and a little musty memory.

    I fired up VMware on my iMac and launched the Simh (July, 2018 vintage) where I keep a copy

on my PDP-11/83 disk images for RSX11M+ V4.6 with DECnet and your TCP/IP. The CPU in

my Simh configuration is a 11/93 so I don't have to type the time in and being Qbus it uses a DELQA

emulation for ethernet and when DECnet came up it properly configured the Vector as seen in Simh

before.

   I'm just not sure why the UNA-0 DELUA is not configuring the Vector on the PiDP-11. I did a new

NETGEN yesterday that seemed to eliminate the Initialization failure when I started the CIRcuit UNA-0

and I do see some sent Bytes in the UNA-0 counters but no received bytes.

   On a separate note, I did not know the Simh SHOW ETH until BMeyer29 mentioned it. From it I notice

on the iMac that:

BPF Filter: (((ether dst AB:00:00:01:00:00) or (ether dst CF:00:00:00:00:00) or (ether dst AB:00:00:03:00:00) or (ether dst FF:FF:FF:FF:FF:FF) or (ether dst AA:00:04:00:05:78)))

  which includes the DECnet address AA:00:04:XX:XX:XX and I was wondering the others must be LAT,

down line load requests and a couple other things from the DECnet side of things?

  This also explains to me your comment a week or so ago that Promiscuous ethernet is not needed for DECnet.

Best,

Mark

Before booting RSX:

sim-imac.ini-50> sho xq
XQ    address=17774440-17774457, no vector, BR5, MAC=AA:00:04:00:05:78
    type=DELQA, polling=disabled, sanity=OFF
    throttle=time=5;burst=4;delay=10, DEQNALock=OFF, leds=(ON,ON,ON)
    attached to eth0
sim-imac.ini-51> sho eth

ETH devices:
 eth0    eth0                                 (No description available)

 eth1    tap:tapN                             (Integrated Tun/Tap support)
 eth2    vde:device{:switch-port-number}      (Integrated VDE support)
 eth3    nat:{optional-nat-parameters}        (Integrated NAT (SLiRP) support)
 eth4    udp:sourceport:remotehost:remoteport (Integrated UDP bridge support)
libpcap version 1.5.3
Open ETH Devices:
 XQ     eth0 (No description available)
Ethernet Device:
  Name:                    eth0

  Reflections:             0
  Self Loopbacks Sent:     2
  Self Loopbacks Rcvd:     0

  Host NIC Address:        00:0C:29:DB:08:31
  Packets Sent:            2
  Asynch Interrupts:       Disabled
  Read Queue: Count:       0
  Read Queue: High:        0
  Read Queue: Loss:        0
  Peak Write Queue Size:   0
  BPF Filter: (((ether dst AA:00:04:00:05:78)))

After booting RSX, loading DECnet and TCP/IP:

Simulation stopped, PC: 025340 (BR 25306)
sim> sho xq
XQ    address=17774440-17774457, vector=120, BR5, MAC=AA:00:04:00:05:78
    type=DELQA, polling=disabled, sanity=OFF
    throttle=time=5;burst=4;delay=10, DEQNALock=OFF, leds=(ON,ON,ON)
    attached to eth0

sim> sho eth

ETH devices:
 eth0    eth0                                 (No description available)

 eth1    tap:tapN                             (Integrated Tun/Tap support)
 eth2    vde:device{:switch-port-number}      (Integrated VDE support)
 eth3    nat:{optional-nat-parameters}        (Integrated NAT (SLiRP) support)
 eth4    udp:sourceport:remotehost:remoteport (Integrated UDP bridge support)
libpcap version 1.5.3
Open ETH Devices:
 XQ     eth0 (No description available)
Ethernet Device:
  Name:                    eth0

  Reflections:             0
  Self Loopbacks Sent:     2
  Self Loopbacks Rcvd:     0

  Host NIC Address:        00:0C:29:DB:08:31
  Packets Sent:            691
  Packets Received:        9062
  Asynch Interrupts:       Enabled
  Interrupt Latency:       0 uSec
  Read Queue: Count:       7
  Read Queue: High:        60
  Read Queue: Loss:        0
  Peak Write Queue Size:   2
  BPF Filter: (((ether dst AB:00:00:01:00:00) or (ether dst CF:00:00:00:00:00) or (ether dst AB:00:00:03:00:00) or (ether dst FF:FF:FF:FF:FF:FF) or (ether dst AA:00:04:00:05:78)))

On Sunday, November 18, 2018 at 9:20:24 AM UTC-6, Johnny Billquist wrote:

Matt - that is exactly as it is supposed to be. The ethernet controllers do not have dip switches to set the vector so there is no corresponding command in simh. These controllers set up the vector in software.

Johnny

Mark Matlock <ma...@matlockfamily.com> skrev: (18 november 2018 16:15:32 CET)

sim> sh xu

[Johnny Billquist]

Matt, the ethernet do have a vector (every device that generates
interrupts have to have one), but it's not set on DIP-switches on the
board (an thus, no simh command either).

The it works is that you have to set the CSR. The software then programs
whatever vector it wants by writing it to the CSR registers, and after
that you do have a vector.

If simh can show anything, it will be showing whatever have been
programmed by the software.

In RSX, the vector that will be used is still set by the software.
Either in the SYSGEN, if you use the XE device driver, or when you do
the NETGEN, if you have DECnet. And this vector can of course be changed
by a command, either through CON with the XE driver, or through CFE if
you have DECnet.

As for the various addresses, it's a bit more complicated, but then
again, actually not.

(((ether dst AB:00:00:01:00:00) or (ether dst
CF:00:00:00:00:00) or (ether dst AB:00:00:03:00:00) or (ether dst
FF:FF:FF:FF:FF:FF) or (ether dst AA:00:04:00:05:78)))

CF:00:00:00:00:00 is the loopback assist multicast address.

AB:00:00:01:00:00 is the DNA (MOP) Dump/Load assistance address.
AB:00:00:03:00:00 is the DNA routing layer routers multicast address.

FF:FF:FF:FF:FF:FF is the generic multicast (broadcast) address.

Other you might sometime see:
AB:00:00:02:00:00 is the DNA remote console (MOP)
AB:00:00:04:00:00 is the DNA routing layer end-node multicast address.
AB:00:03:00:00:00 is local area transport (LAT) multicast.


And of course, AA:00:04:00:xx:xx is your own address.

So, not neccesarily, but sometimes, related to other protocols than
DECnet proper.

But you need to remember that, apart from when you need some
multicasting, other protocols, such as MOP or LAT, use your same
ethernet address. Any ethernet controller only have one address.
Multicast addresses you can listen to many of.

Promiscuous mode is something you need if you want to receive packets
meant for some other explicit node than your own. So, you need that if
you are sharing the interface between two systems, since the ethernet
controller itself only have one address (as mentioned).

Johnny

> XQ    address=17774440-17774457, *vector=120*, BR5, MAC=AA:00:04:00:05:78

> Mark Matlock <ma...@matlockfamily.com <javascript:>> skrev: (18

> november 2018 16:15:32 CET)
>
> sim> sh xu
> XU      address=17774510-17774517, no vector, BR5,
> MAC=AA:00:04:00:0C:78
>         type=DELUA, throttle=disabled
>         attached to tap:tap0
>

> --
> 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 on the web visit

> https://groups.google.com/d/msgid/pidp-11/8f1e0e98-7fb0-4a92-b17d-4470cc9cf87f%40googlegroups.com
> <https://groups.google.com/d/msgid/pidp-11/8f1e0e98-7fb0-4a92-b17d-4470cc9cf87f%40googlegroups.com?utm_medium=email&utm_source=footer>.

> For more options, visit https://groups.google.com/d/optout.

--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: b...@softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol

[bmeyer29]

Update Nov 19:

Thanks to those that are trying to help with ethernet using BSD2.11!

My problem with no vector assigned to xu is resolved. I had unplugged the

USB/Serial adapter, which caused a conflict, which caused the

vector for xu to be undefined. Plugged it back in, and xu now has

a vector at 120.

Also set the eth0 port on the rpi3 to be a static address of

192.168.1.44, which is what is used as the BSD2.11 address inside

this configuration. It is easier to edit things in raspbian stretch, than

to edit things with vi in the BSD2.11 world!

My current sequence:

After reboot of rpi3, shutdown sim with ^E and then sim>exit, 

run s3.sh (listed below) to get bridge between tap0 and eth0 established

pi@Blinken:~ $ sudo ./s3.sh

then restart simh with 2 option, which is BSD 2.11 unix

pi@Blinken:~ $ cd /opt/pidp11/bin

pi@Blinken:/opt/pidp11/bin $ sudo ./pidp11.sh 2

At the : prompt, hit enter to start the boot into single user,

Then edit /etc/interfaces file to change line

hostname=dpd1144.internal to

hostname=192.168.1.44

because previous attempts got an error in a following ifconfig de0 ... statement.

Now back at the # prompt,  type ^D to get into multiuser mode.

There is an error generated in this process in /etc/netstart, when the

route command attempts to add to the route table. Netstart script tries to

use $HOSTNAME, but it is blank at this point This needs to

be fixed still. 

ifconfig de0 to see device stats, need to edit ? to get proper data into route tables. 

$HOSTNAME is blank, so above doesn't work.

# ./netstart

Assuming NETWORKING system ...

start rout commands

add host 192.168.1.44: gateway 127.0.0.1

add net default: gateway 192.168.1.1

# ifconfig de0

de0: flags=63<UP,BROADCAST,NOTRAILERS,RUNNING>

        inet 192.168.1.44 netmask ffffff00 broadcast 192.168.1.255

So, I feel like I am getting close! Mainly wanted to put this out today so

others wouldn't waste time trying to help figure out why there was

no vector assigned to my xu device. See details below. Now, any ideas on what tools

are available in BSD2.11 to see if there is network traffic coming in?

Thanks again for your interest and help!

bmeyer29

simh details:

from sh dev

...

XU      address=17774510-17774517, vector=120, BR5, MAC=08:00:2B:AE:B6:46

        type=DELUA, throttle=disabled

...

from sh eth

ETH devices:

eth0   eth0                                 (No description available)

eth1   wlan0                                (No description available)

eth2   tap0                                 (No description available)

eth3   br0                                  (No description available)

eth4   tap:tapN                             (Integrated Tun/Tap support)

eth5   vde:device{:switch-port-number}      (Integrated VDE support)

eth6   nat:{optional-nat-parameters}        (Integrated NAT (SLiRP) support)

eth7   udp:sourceport:remotehost:remoteport (Integrated UDP bridge support)

Open ETH Devices:

XU     tap:tap0 (No description available)

Ethernet Device:

  Name:                    tap0

  Reflections:             0

  Self Loopbacks Sent:     2

  Self Loopbacks Rcvd:     0

  Packets Sent:            47

  Packets Received:        313

  Asynch Interrupts:       Disabled

  Read Queue: Count:       18

  Read Queue: High:        18

  Read Queue: Loss:        0

  Peak Write Queue Size:   1

s3.sh

pi@Blinken:~ $ cat s3.sh

#!/bin/sh

#script to bridge network for simh on rpi for PiDPsimulator

#

HOSTIP=`/sbin/ifconfig eth0 | grep "inet " | gawk -- '{ print $2 }'`

echo $HOSTIP

HOSTNETMASK=`/sbin/ifconfig eth0 | grep "inet " | gawk -- '{ print $4 }' `

echo $HOSTNETMASK

HOSTBCASTADDR=`/sbin/ifconfig eth0 | grep "inet " | gawk -- '{ print $6 }'`

echo $HOSTBCASTADDR

#HOSTDEFAULTGATEWAY=`/sbin/route -n | grep ^0.0.0.0 | gawk -- '{ print $2 }'`

HOSTDEFAULTGATEWAY='192.168.1.1'

echo $HOSTDEFAULTGATEWAY

#

/usr/bin/tunctl -t tap0 # [-u someuser]

/sbin/ifconfig tap0 up

#

# Now convert eth0 to a bridge and bridge it with the TAP interface

/sbin/brctl addbr br0

/sbin/brctl addif br0 eth0

/sbin/brctl setfd br0 0

/sbin/ifconfig eth0 0.0.0.0

/sbin/ifconfig br0 $HOSTIP netmask $HOSTNETMASK broadcast $HOSTBCASTADDR up

# set the default route to the br0 interface

/sbin/route add -net 0.0.0.0/0 gw $HOSTDEFAULTGATEWAY

# bridge in the tap device

/sbin/brctl addif br0 tap0

/sbin/ifconfig tap0 0.0.0.0

# set br0 to desired ...44 ip address

/sbin/ifconfig br0 192.168.1.44

pi@Blinken:~ $

[Sytse van Slooten]

Hi,

I think the issue you had with the hostname= line is because you should also define that same name in your /etc/hosts (and make it resolve to 127.0.0.1, probably). This is how I run my systems, at least, and everything seems to be happy with it. Obviously when the script runs the resolver can’t reach dns yet, but several things need to have the hostname working already.

to see if there’s traffic coming in, easiest is just pinging - both from the pdp11 side to the pi, as the other way, I would say. And you could use netstat (-i, or -s) to look at the counters. There’s no tcpdump yet ;-)

and as to editing: I’ve taken to ed. There is vi in 2.11bsd, but the way it works is too different from what I’m used to, so ed is easier - it’s not like I’m doing major edits on the pdp side anyway.

Cheers

Sytse

To unsubscribe from this group and stop receiving emails from it, send an email to pidp-11+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pidp-11/9b22771d-cf6b-4c98-a2e2-c8ddcd91e826%40googlegroups.com.

[bmeyer29]

Sytse, thanks for your suggestions!.  I'll take a look at ed, as well!

The hosts file looks like this:

# cat /etc/hosts

127.0.0.1       localhost.intern localhost

192.168.1.44    pdp1144.intern pdp1144

I'm very weak on unix networking, so not sure how it should be edited to get it to work. Please advise.

I can ping my router from the bsd just fine with 40ms time. When i ping from the host rpi3 to ....44, i get a fast .1ms time.

Info from netstat on raspbian host and bsd:

# netstat -rn

Routing tables

Destination      Gateway            Flags     Refs     Use  Interface

127.0.0.1        127.0.0.1          UH          0        0  lo0

192.168.1.44     127.0.0.1          UH          0        0  lo0

default          192.168.1.1        UG          0       26  de0

192.168.1        192.168.1.44       U           0        0  de0

... and from raspbian host on rpi3

pi@Blinken:~ $ netstat -rn

Kernel IP routing table

Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface

0.0.0.0         192.168.1.1     0.0.0.0         UG        0 0          0 br0

0.0.0.0         192.168.1.1     0.0.0.0         UG        0 0          0 wlan0

169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0 tap0

192.168.1.0     0.0.0.0         255.255.255.0   U         0 0          0 br0

192.168.1.0     0.0.0.0         255.255.255.0   U         0 0          0 wlan0

netstat -s on the bsd system gives 3 tcp packets sent and 0 tcp packets received.

I've been tricked numerous times into thinking I was close to getting this to work. :) My plan was to get to work with the eth0/tap0 bridge, and then to move

to the vde approach described in github.com/simh/simh/0readme_ethernet.txt. My understanding is vde will be able to get beyond the host and allow communication across my LAN. Do you have that working on your pdp-11 simh?

Again, many thanks!

bmeyer29

[Sytse van Slooten]

I’ll speculate a bit (I’m running bsd on my fpga, not on the rpi, so it’s all a bit different… but it should be the same on the pdp side).

Firstly, the .1 response to the ping shows that you are getting the response from the rpi itself, not from the pdp. I think you should not set an ip address on the br interface? or at least it should be a different one - such that the ip stack on the rpi will not respond.

my /etc/hosts looks like this:

# cat /etc/hosts

127.0.0.1       de0.sytse.net localhost.arpa localhost

and the bit from netstart:

hostname=de0.sytse.net

netmask=255.255.255.0

broadcast=10.1.0.255

default=10.1.0.1

hostname $hostname                                      >/dev/console 2>&1

hostid $hostname                                        >/dev/console 2>&1

if [ $INET = YES ]; then

        ifconfig lo0 inet localhost up -trailers        >/dev/console 2>&1

        ifconfig de0 inet 10.1.0.4 netmask 255.255.255.0 broadcast $broadcast up -trailers

        route add $hostname localhost 0         >/dev/console 2>&1

        route add default $default 1            >/dev/console 2>&1

fi

To view this discussion on the web visit https://groups.google.com/d/msgid/pidp-11/cafe506d-1440-4b96-803f-0043e0ac7bfc%40googlegroups.com.

[bmeyer29]

I'm back trying to get TCP/IP working on BSD2.11. Decided to try approach described by Ian a few posts back, and have made a little more progress. This approach doesn't use TUN or VDE or NAT, and uses the BSD image from ak6dn.com. I can now ping from bsd2.11 to the outside world: ping google.com and get about 50ms times. Also can ping from PC to PiDP-11 at 192.168.1.44 and get about 30ms times. Running "netstat -s" shows BSD2.11 is sending and receiving packets.

However, I can't telnet to or from BSD2.11. For instance putty to 192.168.1.44, telnet port 23 from my local PC gives me "Network error, Connection refused".  I think I still don't have my interface configured right. My PC is connected to the RPi3 via wifi and I can login to Raspbian via putty/SSH to 192.179.1.137 just fine. The builtin ethernet port in Raspbian is now static at 192.168.1.70. Inside BSD2.11, the de0 port is still 192.168.1.44, to be different that the .70 defined in Raspbian Stretch. (Previously, I had Raspbian and BSD2.11 both identifying the hardwired port as 192.168.1.44.) However, when I run a nmap scan (from my PC) on 192.168.1.44, I don't see a port 23 (for telnet as defined in /etc/inetd.conf and /etc/services), but 22 for SSH and several other ports which are enabled in Raspbian.

I'm still confused about how to get the traffic for the hardwired ethernet port past the RPi3/Raspbian world and to/from the simulated PiDP-11/BSD2.11 world. 

Any additional advice is greatly appreciated!

-bmeyer29

[bmeyer29]

[bmeyer29]

Sorry for the double entry earlier today! Want to update my last post to correct report about seeing the RPi3 ports when running a nmap scan. I'm showing ports 21,23,25 and 113 almost immediately and a few others such as 1 and 514 after a few minutes when I scan the 192.168.1.44 address (eth0 attached to xu) as defined in PiDP-11/BSD2.11. Getting closer! Still can't connect with telnet  using putty from PC to 192.168.1.44 (port 23). What am I missing?

-bmeyer29 

[Chris Smith]

This is no guarantee, just a thread to investigate.

Look up "ip forwarding". This is a setting that controls the forwarding of packets inside Linux. For security reasons it is commonly set off these days, but for hosted OSes such as containers, it needs to be on. Running inside the Pi may be akin to having a container.

I'm not clear on why you can still ping from PC but not connect, but that might be because one is ICMP and the other is TCP.

To view this discussion on the web visit https://groups.google.com/d/msgid/pidp-11/7ef5744d-294b-4c12-8091-24f25a11716c%40googlegroups.com.

[Craig Ruff]

On Dec 9, 2018, at 5:15 PM, bmeyer29 <bmeyer...@gmail.com> wrote:

My PC is connected to the RPi3 via wifi 

Have you tried directly connecting the PC to the RPi3 with a cable?

[bmeyer29]

Yea! Got Telnet to work through xu/eth0/de0 interface from another RPi3 (Raspbian Stretch) to my PiDP-11! As you already know, most of my issues have been due to my shallow understanding of how things work in BSD2.11. Many thanks to all who have given examples and suggestions. 1) It took me far too long to understand that promiscuous mode meant that I had to trick the host into thinking the hardwired ethernet port (eth0) had an IP address (in my case I'm using 192.168.1.70) different that what the simulated PiDP-11 was going to use (I'm using 192.168.1.44). My momma always warned me about being promiscuous!

2) who knew you can't have a # comment on the end of a line in /etc/network/interfaces!?! Well, now I do... until I forget and get tripped up by that sometime in the near future.

There were many other things prior to these two things, so I am in the process of starting from scratch on a fresh RPi3+ and document the steps that ended up getting me to where telnet works through this interface. It is late Monday night here in mid-America, so I will post the steps for other folks like me in the next day or so. Also, the last poster asked if I was able to get connected with a serial cable. I haven't tried with this version of realcons and bsd2.11 image, but did get it to work just fine earlier with the original realcons and disk image from Oscar. See my post in "Show us your builds" thread. I have an HP "palmtop" from the mid '90s attached and logged in.

Again, many thanks for for the advice and suggestions from all!

-bmeyer29

[Leonardo Cardoso]

Hi bmeyer29,

I'm also interested in this, but I must admit I'm a bit lost reading through all the posts to come up with a clear procedure. Do you plan on making your document available as a HOWTO of sorts?

Thanks for the hard work

Leo

[bmeyer29]

Leo:

Thanks for your inquiry! This morning I was wondering if I was the only one that was having trouble with this (or cared about getting ethernet working with BSD2.11). I'm about 90% done with documenting the steps, and now need to put it in readable form. 

Oscar's (and friend's) efforts have been considerable, so my doc will start assuming you've followed his steps and have the simulator running with all the various OS available by setting the switches on the front, or by running /opt/pidp11/bin/pidp11.sh 2 to get BSD2.11 going. Are you at the point where you can get BSD running OK (without ethernet)?

-bmeyer29 

[bmeyer29]

Hi all:

Attached is a first pass of the steps to create a BSD-with-ethernet version of the PiDP-11 OS. It borrows very heavily from Ian's post in this thread, but attempts to be more of a cookbook style for people with limited experience with unix and DEC hardware. (Like me). Please post comments, corrections, improvements in this thread, so those following along at home are kept abreast of the latest info. I'll try to do updates as quickly as I can. Many thanks to all that helped me along the way!

-bmeyer29

[Leonardo Cardoso]

Yes, I'm in BSD2.11 and exploring around! :)

[Leonardo Cardoso]

Hey Bmeyer,

First of all happy new year! 

The howto is really well explained and I did go through it without any problems. The only point that caused me problems is the ethernet port, that was not labeled "eth0" as expected in my raspberry pi... A quick change in the boot script and everything went fine.

Now I'm looking for a http server to install in it. :)

Any clues?

BR

[Bob Meyer]

Leo, I’m glad my notes were useful. 

I haven’t looked at this yet, but perhaps if you described in detail what you want to do, others in the group can give some pointers. 

To view this discussion on the web visit https://groups.google.com/d/msgid/pidp-11/d16b6502-97af-4dd0-9724-c2a2a9c98b19%40googlegroups.com.

[Sunnyboy010101]

Also to Bmeyer,

Your notes are excellent. I followed along from page 6/9 and mostly from page 7/9 "Here are what my files are like...". I've done some network configuration in the past, even doing things considered "impossible" on Solaris zones some years ago...

What I did do was edit the three files (/etc/hosts, /etc/resolv.conf and /etc/netstart) using your files as a guideline (my subnet is 10.1.1.x so different IPs). I also did the edits from single-user mode as that's before the network tries (and fails) to start initially.

One note: editing files using VI from single-user mode is not recommended. That version of vi is really rudimentary - no movement except with enter and spacebar. Fortunately I got the files edited anyway, and the reboot was clean.

Of course, I had not internet access. That's because the new versions of the 211bsd ini file uses ETH0, which is the wired ethernet connection. I was reluctant to use that simply because I'm over 60 and the network switch is behind a desk, on the floor and I really hate getting down on my knees these days!!! :-D

However, once it booted I could see by "ifconfig de0" that the static IP was good (unused by anything else on the sub-net) and *should* work.

So I bowed (literally) to the inevitable, got out a network cable and plugged one end into the switch and the other into my rPi3B+. As soon as the link light came on, I had INTERNET access from my BSD2.11 OS running on the RPi.

Again, a very nice job all around.

Now if only I could get it running on WLAN0 somehow. I really dislike wired internet these days.

I have some wifi dongles from my RPi 2 days (they were needed to get wifi) but what I remember most about them is they were not fun to configure and acted somewhat flakey even once running properly... (something about powering down to save power).

Cheers,

-R

To view this discussion on the web visit https://groups.google.com/d/msgid/pidp-11/EF9D62D7-73F9-4CD4-AC23-887DA6BEC9DE%40gmail.com.

For more options, visit https://groups.google.com/d/optout.

Virus-free. www.avast.com

[Leonardo Cardoso]

You're definitely right. I'll do the in another thread to not disturb the focus of this one.

Thank you once again.

--Leo

[Mark Lawler]

All,

First of all, great instructions from this thread that then ended up in the PiDP-11 Manual v0.2.odt.  It took a little jumping around, but I was able to configure the Raspberry Pi 4, SIMH, and 2.11BSD to work over WiFi (without jumping on Ethernet first).  Have already enjoyed FTP-ing files from my Windows desktop over to the PiDP-11/70 over this WiFi enabled connection. I do have one question though:

I was able to edit /etc/hosts file as mentioned in the documentation, but my host file had this additional entry in it that wasn't covered in the documentation. Is there an IP address I should have set this to?

xxx.xxx.xxx.xxx rpi.home.lan rpi

I made an EWAG and set it to the IP address of the Raspberry Pi itself, but that doesn't sound right at all as BSD on a real PDP-11 would have been something completely different...  Is there a correct value to go here or should I delete this line as it isn't ever referenced in the instructions?  That value that was originally in there was +4 of the default router.home.lan router entry in the hosts file before I edited it, but that seemed arbitrary vs based on anything real...

Best,

-Mark

[Randy Merkel]

I had the same problem with rpi; first by removing it from /etc/hosts and getting a "unable to get hostname to rpi" error, then adding it back with an arbitrary address. 

What is "rpi" and what should it's address be?

Thanks,

- Randy

[Ville Laitinen]

Hi, check /etc/netstart for the network setup.

rpi (on the image i'm running anyway) is used for the default gateway. 

br,

-Ville

--

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/5aa71665-69a8-43b8-8384-2f1493caa8fan%40googlegroups.com.