Groups | Search | Server Info | Login | Register


Groups > alt.sys.pdp10 > #9761

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

Path csiph.com!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail
From David Todd <HDTodd@gmail.com>
Newsgroups alt.sys.pdp10
Subject Re: ?TCPIP TOPS-20 <--> Raspberry Pi or Mac OSX
Date Sat, 25 Oct 2025 18:53:20 -0400
Organization A noiseless patient Spider
Lines 164
Message-ID <597cce07-dc9b-4f7b-b39c-3bd6d97049e7@gmail.com> (permalink)
References <10dfvld$2k7ba$1@dont-email.me> <87frb7g9po.fsf@atr2.ath.cx>
MIME-Version 1.0
Content-Type text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding 7bit
Injection-Date Sat, 25 Oct 2025 22:53:24 +0000 (UTC)
Injection-Info dont-email.me; posting-host="7aa08e96a52d966fe643370c8d3e38ee"; logging-data="3858592"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18RNcLWYZI4LHwOumrLJcxV"
User-Agent Mozilla Thunderbird
Cancel-Lock sha1:XemRRf9ocXQJaod+AKpcqMAeuhQ=
In-Reply-To <87frb7g9po.fsf@atr2.ath.cx>
Content-Language en-US
Xref csiph.com alt.sys.pdp10:9761

Show key headers only | View raw


On 10/24/25 7:29 PM, jayjwa wrote:
> If you want the script (it's pretty Slackware-specific) let me
> know.

First, thank you very much for replying so quickly and with details.  I 
kept thinking that the tap<n+1> issue was something I was doing wrong 
rather than a design feature.

Second, my apologies.  Despite having spent several days looking for 
solutions, I did not see your posting on the github klh10 site.  I don't 
know that I'd have resolved the problem, but I'd have known that what I 
was seeing wasn't unique.

Finally, yes, I think it would help for me to see your script if you're 
willing to share it.

I tried to follow your guidance using the nmcli tools in the Debian 
Trixie environment but I'm still unable to connect.  As you can see 
below, attempting to get to Panda dec20 instance (hosted on "pi-0"), 
gets me to the Pi port, not the dec20 port.  I'm assuming that I haven't 
gotten the bridge set up correctly, so maybe a slackware example will help.

When I get this working correctly for the Pi (again), I'll document it 
in detail for others -- I know others running on Pi's have had the same 
problem and been unable to solve it.


My setup:
    "Pi-0" is the host Pi.  Wifi port is 192.168.1.79, "pi-0w".
    EN port is not assigned an IP.
    Pi-0 doesn't support telnet service but does support FTP
    with a vsFTPd installation.

    "dec20" is the Panda virtual machine.  Its
    IP port is 192.168.1.60, assigned as a dedicated
    port in the devdef.

What I find trying to access Pi from itself:

     $ telnet pi-0w
     Trying 192.168.1.79...
     telnet: Unable to connect to remote host: Connection refused
     Name (pi-0:hdtodd):

     $ ftp pi-0w
     Connected to Pi-0w.
     220 (vsFTPd 3.0.5)
     Name (pi-0w:hdtodd):

which shows that Pi-0's telnet fails as expected but ftp works.

Telnet in from Panda host (Pi-0) to dec20 gets:
     $ telnet dec20
     Trying 192.168.1.60...
     telnet: Unable to connect to remote host: Connection refused

     Run FTPSER.EXE on the dec20 and try to
     FTP from Panda host to dec20 gets
     $ ftp dec20
     Connected to dec20.
     220 (vsFTPd 3.0.5)
     Name (dec20:hdtodd):

THIS IS THE PI-0 HOST RESPONDING!  NOT SURPRISING THAT TELNET
DIDN'T WORK AS APPARENTLY 192.168.1.60 ACTUALLY
GOES TO 192.168.1.79.

FTP from dec20 to its host, Pi-0, gets:
     @ftp pi-0
     ?Couldn't connect to Pi-0 - Retransmission timeout
     @

     Telnet from dec20 to itself gets:
     @telnet dec20
      Trying... Open

      KLH20-2.0h Panda Distribution, PANDA TOPS-20 Monitor 7.1(21733)-4
     HDT's KL10/TOPS20

So telnet on the dec20 is working.

The networking configuration on Pi-0 *looks* correct.  br0
has the IP address of the dec20 virtual machine, and its
MAC address is the same as eth0.

$ ifconfig
br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
         inet 192.168.1.60  netmask 255.255.255.0  broadcast 192.168.1.255
         inet6 fe80::9d97:6b3a:1220:cba4  prefixlen 64  scopeid 0x20<link>
         ether dc:a6:32:1a:83:91  txqueuelen 1000  (Ethernet)
         RX packets 1876  bytes 972360 (949.5 KiB)
         RX errors 0  dropped 7  overruns 0  frame 0
         TX packets 645  bytes 51851 (50.6 KiB)
         TX errors 0  dropped 69 overruns 0  carrier 0  collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
         ether dc:a6:32:1a:83:91  txqueuelen 1000  (Ethernet)
         RX packets 2215  bytes 1063939 (1.0 MiB)
         RX errors 0  dropped 48  overruns 0  frame 0
         TX packets 886  bytes 64425 (62.9 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 68  bytes 7471 (7.2 KiB)
         RX errors 0  dropped 0  overruns 0  frame 0
         TX packets 68  bytes 7471 (7.2 KiB)
         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

tap0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
         inet 192.168.1.79  netmask 255.255.255.0  broadcast 192.168.1.255
         inet6 fe80::38ff:5eff:fedc:20f7  prefixlen 64  scopeid 0x20<link>
         ether 3a:ff:5e:dc:20:f7  txqueuelen 1000  (Ethernet)
         RX packets 46  bytes 5113 (4.9 KiB)
         RX errors 0  dropped 17  overruns 0  frame 0
         TX packets 101  bytes 8164 (7.9 KiB)
         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
         inet 192.168.1.79  netmask 255.255.255.0  broadcast 192.168.1.255
         inet6 fe80::27a8:e9fe:8b2f:4f55  prefixlen 64  scopeid 0x20<link>
         ether dc:a6:32:1a:83:92  txqueuelen 1000  (Ethernet)
         RX packets 848  bytes 119049 (116.2 KiB)
         RX errors 0  dropped 0  overruns 0  frame 0
         TX packets 80  bytes 15323 (14.9 KiB)
         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

The klt20.ini definition for the NI has tap0 and the right IP address:

     devdef ni0 564 ni20 ipaddr=192.168.1.60 dedic=true ifc=tap0 ifmeth=tap

When booting, dec20 seems to have set up the network:
     [KNILDR: Loading microcode version 1(172) into Ethernet channel 0]

     [dpni20: ifc "tap0" => ether f2:b:a4:fd:40:a8]
     [dpni20:   VHOST 192.168.1.60]
     [dpni20: Enabled net.ipv4.conf.tap0.arp_accept]

And in operation, it seems to think it's working:
     @info internet
      Network Todds.Comcast.net host name is DEC20
      Network interface type is IPNI, Internet address is 192.168.1.60
      Network interface is up, output is enabled
      Network service is enabled
      Last network interface up transition: 25-Oct-2025 17:27:09

The resolv.config file probably isn't the issue for what I'm seeing,
but it looks correct, too:
     $cat resolv.config
     ; Default (safety belt) nameservers.  These are contacted when we
     ; are completely unable to figure out who ask a particular query.
     DSERVE	192.168.1.1
     DSERVE	8.8.8.8
     ;
     ; Locally loaded zones and search paths.
     ;
     ; Remote searches.
     RSEARCH		.		;Try for fully specified name first
     RSEARCH 	todds.comcast.net
     ;
     ; Privileged user(s) who can send resolver control messages
     WHOPR		OPERATOR	;System Jobs

Back to alt.sys.pdp10 | Previous | NextPrevious in thread | Next 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