Groups | Search | Server Info | Login | Register


Groups > alt.sys.pdp10 > #9776

Re: ?TCPIP TOPS-20 <--> Raspberry Pi or Mac OSX

From David Todd <HDTodd@gmail.com>
Newsgroups alt.sys.pdp10
Subject Re: ?TCPIP TOPS-20 <--> Raspberry Pi or Mac OSX
Date 2025-11-01 14:05 -0400
Organization A noiseless patient Spider
Message-ID <68b1ef8e-482a-4260-a7c7-0b0cce5df3ee@gmail.com> (permalink)
References <10dfvld$2k7ba$1@dont-email.me> <87frb7g9po.fsf@atr2.ath.cx> <3b30b25f-63d6-49ca-9158-1d885b69c50f@gmail.com> <U4sMQ.286425$pQe6.88687@fx40.iad> <87ms58barw.fsf@atr2.ath.cx>

Show all headers | View raw


Jayjwa, Scott, Lawrence,

Short version: TCPIP Pi <--> klh10 DEC20 works.

Long version:

I reset and then reinitialized my Pi networking so
that it matched what a newly-installed OS would look
like.  I created a new DEC20 virtual machine from
scratch but used my old RP07 virtual disk drive.
I did nothing to set up bridges or taps:  I just
booted the DEC20 and the IP connection between
the two now works:

     o  I reset my Pi network so that only lo, eth0,
        and wlan0 devices are defined.  eth0 and
        wlan0 have the .78 and .79 addresses as
        assigned by the DHCP server.
     o  I cloned the github repository for klh10,
        executed the autoconf, rebuilt the virtual
        machine, and created a new directory for
        its installation.  There were no source
        code changes from my prior compilation,
        but I wanted a clean install.
     o  I copied my prior klh10 .ini file and my
        prior RP07 (Panda) virtual drive into the
        new directory.  I stripped the devdef for
        the NI to what I think is the bare minimum:
        devdef ni0 564 ni20 ipaddr=192.168.1.60 ifc=tap0 ifmeth=tap
     o  On DEC20 boot, the NI initializes using
        "tap0" (!). I have no tap0 defined on the
        Pi side, and I don't assign any parameters
        to it during DEC20 boot.  An "ip -c address"
        (below) shows its instantiation on the
        Pi after the DEC20 boot.
     o  I can ftp from the DEC20 to the Pi, and
        I can telnet and ftp from the Pi to the
        DEC20, but it takes quite a delay to
        actually initiate the connection and get
        the prompt from the other host.
     o  I cannot access either the Pi or the DEC20
        from other systems on my net, nor can I
        access any of those systems from the DEC20
        or Pi. That's not ideal, but I can live with it.

I've done a trial run-through of installing on a
brand new Pi-5 with a fresh installation of
Raspberry Pi (Debian) Trixie but using my old
RP07 (Panda) disk drive, and the Pi-DEC20
IP connection between them works, too.

To document this, I'll do a clean, fresh install
of klh10 and panda from the github repositories
onto that new Raspberrry Pi / Trixie system,
set up IP on MRC's RP07 rather than my own,
and document it  carefully just to make sure it
works.  I'll post that here and on the klh10 site
when I've finished.

While I'm happy to have the connection working again,
I'm frustrated that I don't know specifically what
fixed it and so don't know what caused it.  And I
spent the better part of two weeks, and wasted your
time, getting it to work.  My apologies for that,
but also my deep appreciation for helping me try to
work through it.

Thanks!

David


On Pi, before DEC20 boot:

hdtodd@Pi-0:~ $ ip -c address
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 
group default qlen 1000
     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
     inet 127.0.0.1/8 scope host lo
        valid_lft forever preferred_lft forever
     inet6 ::1/128 scope host noprefixroute
        valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP 
group default qlen 1000
     link/ether dc:a6:32:1a:83:91 brd ff:ff:ff:ff:ff:ff
     inet 192.168.1.78/24 brd 192.168.1.255 scope global dynamic 
noprefixroute eth0
        valid_lft 63176sec preferred_lft 63176sec
     inet6 fe80::5df1:6190:3ab6:a5bd/64 scope link noprefixroute
        valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel 
state UP group default qlen 1000
     link/ether dc:a6:32:1a:83:92 brd ff:ff:ff:ff:ff:ff
     inet 192.168.1.79/24 brd 192.168.1.255 scope global dynamic 
noprefixroute wlan0
        valid_lft 63181sec preferred_lft 63181sec
     inet6 fe80::27a8:e9fe:8b2f:4f55/64 scope link noprefixroute
        valid_lft forever preferred_lft forever

No networking commands given on the Pi, but
after the DEC20 boot:

hdtodd@Pi-0:~ $ ip -c address
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 
group default qlen 1000
     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
     inet 127.0.0.1/8 scope host lo
        valid_lft forever preferred_lft forever
     inet6 ::1/128 scope host noprefixroute
        valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP 
group default qlen 1000
     link/ether dc:a6:32:1a:83:91 brd ff:ff:ff:ff:ff:ff
     inet 192.168.1.78/24 brd 192.168.1.255 scope global dynamic 
noprefixroute eth0
        valid_lft 63111sec preferred_lft 63111sec
     inet6 fe80::5df1:6190:3ab6:a5bd/64 scope link noprefixroute
        valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel 
state UP group default qlen 1000
     link/ether dc:a6:32:1a:83:92 brd ff:ff:ff:ff:ff:ff
     inet 192.168.1.79/24 brd 192.168.1.255 scope global dynamic 
noprefixroute wlan0
        valid_lft 63116sec preferred_lft 63116sec
     inet6 fe80::27a8:e9fe:8b2f:4f55/64 scope link noprefixroute
        valid_lft forever preferred_lft forever
11: tap0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel 
state UNKNOWN group default qlen 1000
     link/ether 36:3c:0f:d1:c1:84 brd ff:ff:ff:ff:ff:ff
     inet 192.168.1.78 peer 192.168.1.60/24 brd 192.168.1.255 scope 
global tap0
        valid_lft forever preferred_lft forever
     inet6 fe80::343c:fff:fed1:c184/64 scope link proto kernel_ll
        valid_lft forever preferred_lft forever

Back to alt.sys.pdp10 | Previous | NextPrevious in thread | Find similar


Thread

?TCPIP TOPS-20 <--> Raspberry Pi or Mac OSX David Todd <HDTodd@gmail.com> - 2025-10-24 09:40 -0400
  Re: ?TCPIP TOPS-20 <--> Raspberry Pi or Mac OSX jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-10-24 19:29 -0400
    Re: ?TCPIP TOPS-20 <--> Raspberry Pi or Mac OSX David Todd <HDTodd@gmail.com> - 2025-10-25 18:53 -0400
      Re: ?TCPIP TOPS-20 <--> Raspberry Pi or Mac OSX Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-10-26 03:50 +0000
        Re: ?TCPIP TOPS-20 <--> Raspberry Pi or Mac OSX David Todd <HDTodd@gmail.com> - 2025-10-26 07:10 -0400
          Re: ?TCPIP TOPS-20 <--> Raspberry Pi or Mac OSX Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-10-26 21:16 +0000
            Re: ?TCPIP TOPS-20 <--> Raspberry Pi or Mac OSX David Todd <HDTodd@gmail.com> - 2025-10-27 15:18 -0400
      Re: ?TCPIP TOPS-20 <--> Raspberry Pi or Mac OSX jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-10-26 14:51 -0400
    Re: ?TCPIP TOPS-20 <--> Raspberry Pi or Mac OSX David Todd <HDTodd@gmail.com> - 2025-10-28 18:13 -0400
      Re: ?TCPIP TOPS-20 <--> Raspberry Pi or Mac OSX jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-10-29 13:14 -0400
        Re: ?TCPIP TOPS-20 <--> Raspberry Pi or Mac OSX Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-10-29 23:51 +0000
        Re: ?TCPIP TOPS-20 <--> Raspberry Pi or Mac OSX David Todd <HDTodd@gmail.com> - 2025-10-30 08:59 -0400
          Re: ?TCPIP TOPS-20 <--> Raspberry Pi or Mac OSX jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-10-30 13:51 -0400
      Re: ?TCPIP TOPS-20 <--> Raspberry Pi or Mac OSX scott@slp53.sl.home (Scott Lurndal) - 2025-10-29 17:24 +0000
        Re: ?TCPIP TOPS-20 <--> Raspberry Pi or Mac OSX David Todd <HDTodd@gmail.com> - 2025-10-30 09:04 -0400
        Re: ?TCPIP TOPS-20 <--> Raspberry Pi or Mac OSX jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-10-30 12:43 -0400
          Re: ?TCPIP TOPS-20 <--> Raspberry Pi or Mac OSX scott@slp53.sl.home (Scott Lurndal) - 2025-10-30 17:36 +0000
            Re: ?TCPIP TOPS-20 <--> Raspberry Pi or Mac OSX David Todd <HDTodd@gmail.com> - 2025-11-07 13:30 -0500
              Re: ?TCPIP TOPS-20 <--> Raspberry Pi or Mac OSX scott@slp53.sl.home (Scott Lurndal) - 2025-11-07 21:48 +0000
              Re: ?TCPIP TOPS-20 <--> Raspberry Pi or Mac OSX jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-11-07 17:21 -0500
                Re: ?TCPIP TOPS-20 <--> Raspberry Pi or Mac OSX David Todd <HDTodd@gmail.com> - 2025-11-08 05:55 -0500
                Re: ?TCPIP TOPS-20 <--> Raspberry Pi or Mac OSX Lars Brinkhoff <lars.spam@nocrew.org> - 2025-11-08 17:16 +0000
                Re: ?TCPIP TOPS-20 <--> Raspberry Pi or Mac OSX David Todd <HDTodd@gmail.com> - 2025-11-08 15:33 -0500
                Re: ?TCPIP TOPS-20 <--> Raspberry Pi or Mac OSX jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-11-09 17:45 -0500
                Re: ?TCPIP TOPS-20 <--> Raspberry Pi or Mac OSX Rich Alderson <news@alderson.users.panix.com> - 2025-11-08 20:42 -0500
                Re: ?TCPIP TOPS-20 <--> Raspberry Pi or Mac OSX jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-11-08 14:57 -0500
                Re: ?TCPIP TOPS-20 <--> Raspberry Pi or Mac OSX David Todd <HDTodd@gmail.com> - 2025-11-08 15:37 -0500
                Re: ?TCPIP TOPS-20 <--> Raspberry Pi or Mac OSX Rich Alderson <news@alderson.users.panix.com> - 2025-11-08 20:47 -0500
                Re: ?TCPIP TOPS-20 <--> Raspberry Pi or Mac OSX jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-11-09 17:58 -0500
                Re: ?TCPIP TOPS-20 <--> Raspberry Pi or Mac OSX Rich Alderson <news@alderson.users.panix.com> - 2025-11-09 21:00 -0500
          Re: ?TCPIP TOPS-20 <--> Raspberry Pi or Mac OSX David Todd <HDTodd@gmail.com> - 2025-11-01 14:05 -0400

csiph-web