Groups | Search | Server Info | Login | Register
Groups > alt.sys.pdp10 > #9830
| From | jayjwa <jayjwa@atr2.ath.cx.invalid> |
|---|---|
| Newsgroups | alt.sys.pdp10 |
| Subject | Re: Try again: IP between Pi <--> klh10 TOPS-20 |
| Date | 2025-12-30 12:54 -0500 |
| Organization | Atr2 RG 2025 |
| Message-ID | <87ms2zluse.fsf@atr2.ath.cx> (permalink) |
| References | <10iv302$1dl2h$1@dont-email.me> |
David Todd <HDTodd@gmail.com> writes:
> With the patch from github PDP-10/klh10 pull #77 installed, the tap
> you ask for in the klt20.ini file is the tap you get. With that patch
> installed:
>
> 1. On a fresh boot of the Pi, with just devices lo, eth0, and wlan0
> defined, booting the DEC20 results in a system in which the Pi and
> DEC20 can communicate with each other over IP, but IP connectivity
> to the outside local network is broken for both systems.
> 2. On a fresh boot of the Pi, if br0 and tap0 are set up (below),
> booting the DEC20 results in a system in which there is no IP
> connectivity to/from either system.
Are you forwarding IP traffic out to the internet? This has to be done
from the Linux host. I do it with iptables. What does Wireshark/tcpdump
say about it?
Which is your external interface to the outside world? eth0? wlan0?
> I'm using ip to manage the network to stay within the NetManager
> environment that Debian seems to have moved to. My local network is
> 192.168.1.0/24; my host Pi is .88 (eth0) and .89 (wlan0); I intend for
> the DEC20 to be .62 (specified in the klt20.ini file), so I designated
> .62 for the bridge device, br0.
eth0 is my external interface, it has a global ip4. wlan0 is an AP under
br0. Nothing under the bridge has an IP. The bridge br0 has an internal
ip4 and the global ip6. I have no separate router - Linux *is* the
router. It forwards ip4 and ip6. There's some sysctl parameters to do
this. They have "forward" in the name. sysctl -A | grep forward I don't
know if NetworkManager does this for you. Any traffic Linux gets from a
guest has to be passed along if you want to reach the greater internet.
> I think I should be specifying:
>
> - in klt20.ini, the DEC20 IP address is 192.168.1.62
No IP address in klt20.ini at all. Maybe there's multiple ways to do
this but I don't set one. I only make sure it's not in use in another
place on the network and it's in the LAN subnet.
devdef ni0 564 ni20 dedic=true ifmeth=tap ifc=tap10 decnet=true
> - the bridge, br0 in Linux, should have IP address 192.168.1.62
> - the tap, tap0 in Linux, should have br0 as its master but no IP
> address (but dpni20 seems to assign one).
No IP addresses on taps.
ip -c addr show tap10
16: tap10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UP group default qlen 1000
link/ether 22:47:39:cb:f5:ba brd ff:ff:ff:ff:ff:ff
inet6 fe80::2047:39ff:fecb:f5ba/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
> I think part of the problem may be the changes in the networking
> environment and tools as Linux has evolved. For example, I'm
> suspicious of the ifconfig system command executed from dpni20:
>
> [dpni20: osn_pfinit_tuntap, line 1993: execute 'ifconfig tap0
> 192.168.1.88 pointopoint 192.168.1.62 up']
It should not doing that. No pointopoint. That will disconnect you.
> ip link set ${bridge_name} type bridge stp_state 1
> # If you're going to run DECnet, set the bridge lladdr here
> ip link set ${bridge_name} up
> ip -4 addr add ${bridge_address} broadcast + dev ${bridge_name}
>
> # Add the tap and bring it up under the bridge
> printf "\\n${BLUE}Set up tap$1 ${NC}\\n"
> ip tuntap add dev tap$1 mode tap
> ip link set dev tap$1 master ${bridge_name}
> ip link set tap$1 up
That should be all you need.
> #? do we need to set routing for the bridge?
> #ip r add via 192.168.1.1 proto static src ${bridge_address} default
> dev ${bridge_name}
Adding the address should get you the route.
ip -c route show dev br0
192.168.20.0/24 proto kernel scope link src 192.168.20.1
> 5: tap0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel
> master br0 state UP group default qlen 1000
> link/ether ae:93:5c:49:86:c9 brd ff:ff:ff:ff:ff:ff
> inet 192.168.1.88 peer 192.168.1.62/24 brd 192.168.1.255 scope
No IPs on taps.
> global tap0
> valid_lft forever preferred_lft forever
> inet6 fe80::ac93:5cff:fe49:86c9/64 scope link proto kernel_ll
> valid_lft forever preferred_lft forever
> + ip route show
> default via 192.168.1.1 dev eth0 proto dhcp src 192.168.1.88 metric 100
> default via 192.168.1.1 dev wlan0 proto dhcp src 192.168.1.89 metric 600
Two default routes? That doesn't look right.
ip -c route show
default via 69.201.64.1 dev eth0 proto dhcp src 69.201.64.96 metric 1002
69.201.64.0/19 dev eth0 proto dhcp scope link src 69.201.64.96 metric 1002
127.0.0.0/8 dev lo scope link
192.168.20.0/24 dev br0 proto kernel scope link src 192.168.20.1
> 192.168.1.0/24 dev br0 proto kernel scope link src 192.168.1.62
> 192.168.1.0/24 dev tap0 proto kernel scope link src 192.168.1.88
> 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.88 metric 100
> 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.89
> metric 600
If eth0 is going out to the world, what is wlan0 doing? Or is that
backwards?
> + ip link show dev br0
> 4: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
> UP mode DEFAULT group default qlen 1000
> link/ether ae:93:5c:49:86:c9 brd ff:ff:ff:ff:ff:ff
> + ip tuntap show
> tap0: tap persist
Seems fine.
> The DEC20 "info inter" shows that it thinks the network is up and that
> it has the .62 address. But the Pi and the DEC20 can't communicate,
> and IP connections to/from the local network to the Pi don't work,
> either.
❰jayjwa❙~❱✔≻ uname
Linux
❰jayjwa❙~❱✔≻ hostname -s
atr2
❰jayjwa❙~❱✔≻ ping -c 2 amatsu
PING amatsu (192.168.20.8) 56(84) bytes of data.
64 bytes from amatsu (192.168.20.8): icmp_seq=1 ttl=255 time=0.349 ms
64 bytes from amatsu (192.168.20.8): icmp_seq=2 ttl=255 time=0.557 ms
--- amatsu ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1044ms
rtt min/avg/max/mdev = 0.349/0.453/0.557/0.104 ms
❰jayjwa❙~❱✔≻ telnet amatsu
Trying 192.168.20.8...
Connected to amatsu.
Escape character is '^]'.
AMATSU KLH, PANDA TOPS-20 Monitor 7.1(21733)-4
This system is for the use of authorized users only. Usage of
this system may be monitored and recorded by system personnel.
Anyone using this system expressly consents to such monitoring
and is advised that if such monitoring reveals possible
evidence of criminal activity, system personnel may provide the
evidence from such monitoring to law enforcement officials.
@login (USER) jayjwa (PASSWORD)
Job 12 on TTY44 atr2.lan(TCP) 30-Dec-2025 12:35:30
Last interactive login 29-Dec-2025 22:10:12
Last non-interactive login 15-Sep-2025 18:14:08
End of LOGIN.CMD.10
@info interNET
Network atr2net host name is amatsu.lan
Network interface type is IPNI, Internet address is 192.168.20.8
Network interface is up, output is enabled
Network service is enabled
Last network interface up transition: 28-Dec-2025 17:25:00
@finger @mim.softjar.se
RSX-11M-PLUS system MIM. Tue Dec 30 18:36:22 2025. Up: 17 days, 2:11.
Luser Real name Term Idle Logged in From
BILLQUIST Johnny Billquist TT10: 1:39 23 Dec 11:17 50-73-179-7-pennsylv
SETALA Saku Setala TT11: 3d 25 Dec 02:58 sdfeu
BILLQUIST Johnny Billquist TT12: 20:33 25 Dec 14:45 50-73-179-7-pennsylv
@
Note TOPS-20's resolver has to call out to global DNS and whiff first
before it consults its local host tables. This is opposite of what
happens almost everywhere else. The stall might be 30-60 seconds. If the
hostname is in global DNS this is not problem. Either wait, or point
TOPS-20 at your own resolver that has your local LAN hosts listed. I
just wait. AFAIK, TOPS-20 does not like bare IP addresses - you have to
fill out your hosts table (TOPS20:<system>hosts.txt) if the host is not
in global DNS. Such is the case if I use my internal LAN name for the
Linux host (but not its global hostname):
@finger root@atr2.lan
::: ::::::. :::. ... ::: .,:: .:
;;; ;;;`;;;;, `;;; ;; ;;; `;;;, .,;;
[[[ [[[ [[[[[. '[[[[' [[[ '[[,,[['
$' $ $ "Y $ Y$
o88oo,.__888 888 Y8888 .d888 oP"``"Yo,
""""YUMMMMMM MMM YM "YmmMMMM"",m" "Mm,
unknown@amatsu request at Tue Dec 30 12:37 PM (EST)
++++++
Username: root In real life:
This user last read mail Mon Dec 29 10:10 AM (EST)
++++++
"Those who say something is impossible should not
interrupt those who are doing it."
@
--
PGP Key ID: 781C A3E2 C6ED 70A6 B356 7AF5 B510 542E D460 5CAE
"The Internet should always be the Wild West!"
Back to alt.sys.pdp10 | Previous | Next — Previous in thread | Next in thread | Find similar
Try again: IP between Pi <--> klh10 TOPS-20 David Todd <HDTodd@gmail.com> - 2025-12-29 18:31 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-30 12:54 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 Rich Alderson <news@alderson.users.panix.com> - 2025-12-30 20:43 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-31 12:50 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 David Todd <HDTodd@gmail.com> - 2026-01-01 09:59 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 jayjwa <jayjwa@atr2.ath.cx.invalid> - 2026-01-01 11:08 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 David Todd <HDTodd@gmail.com> - 2026-01-01 11:27 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 jayjwa <jayjwa@atr2.ath.cx.invalid> - 2026-01-02 13:04 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 David Todd <hdtodd@gmail.com> - 2026-01-02 17:36 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-03 05:37 +0000
Re: Try again: IP between Pi <--> klh10 TOPS-20 David Todd <HDTodd@gmail.com> - 2026-01-03 07:09 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 David Todd <hdtodd@gmail.com> - 2026-01-03 08:40 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 jayjwa <jayjwa@atr2.ath.cx.invalid> - 2026-01-03 11:33 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 David Todd <HDTodd@gmail.com> - 2026-01-03 06:59 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 David Todd <hdtodd@gmail.com> - 2026-01-04 09:07 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 David Todd <hdtodd@gmail.com> - 2026-01-04 09:20 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 Johnny Billquist <bqt@softjar.se> - 2026-01-04 16:26 +0100
Re: Try again: IP between Pi <--> klh10 TOPS-20 David Todd <hdtodd@gmail.com> - 2026-01-04 10:57 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-05 06:38 +0000
Re: Try again: IP between Pi <--> klh10 TOPS-20 David Todd <hdtodd@gmail.com> - 2026-01-02 07:46 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 jayjwa <jayjwa@atr2.ath.cx.invalid> - 2026-01-02 12:54 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 David Todd <hdtodd@gmail.com> - 2026-01-02 17:05 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 Rich Alderson <news@alderson.users.panix.com> - 2026-01-02 20:32 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 David Todd <HDTodd@gmail.com> - 2026-01-02 22:21 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 David Todd <hdtodd@gmail.com> - 2026-01-02 17:47 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 jayjwa <jayjwa@atr2.ath.cx.invalid> - 2026-01-03 12:15 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 David Todd <hdtodd@gmail.com> - 2026-01-03 16:57 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 David Todd <hdtodd@gmail.com> - 2026-01-03 17:00 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 jayjwa <jayjwa@atr2.ath.cx.invalid> - 2026-01-04 11:21 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 David Todd <HDTodd@gmail.com> - 2026-01-05 17:52 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 David Todd <HDTodd@gmail.com> - 2026-01-05 18:13 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 jayjwa <jayjwa@atr2.ath.cx.invalid> - 2026-01-06 12:53 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 David Todd <HDTodd@gmail.com> - 2026-01-06 18:12 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 David Todd <HDTodd@gmail.com> - 2026-01-06 18:15 -0500
MM vs. MS/MX [was Re: Try again: IP between Pi <--> klh10 TOPS-20] Rich Alderson <news@alderson.users.panix.com> - 2026-01-07 18:28 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 David Todd <hdtodd@gmail.com> - 2026-01-03 17:07 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 jayjwa <jayjwa@atr2.ath.cx.invalid> - 2026-01-04 11:28 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 David Todd <hdtodd@gmail.com> - 2026-01-04 13:52 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 David Todd <hdtodd@gmail.com> - 2026-01-03 18:12 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 scott@slp53.sl.home (Scott Lurndal) - 2026-01-04 00:00 +0000
Re: Try again: IP between Pi <--> klh10 TOPS-20 David Todd <hdtodd@gmail.com> - 2026-01-04 08:48 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 scott@slp53.sl.home (Scott Lurndal) - 2026-01-04 16:00 +0000
Re: Try again: IP between Pi <--> klh10 TOPS-20 David Todd <hdtodd@gmail.com> - 2026-01-04 14:02 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 jayjwa <jayjwa@atr2.ath.cx.invalid> - 2026-01-04 11:56 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 David Todd <hdtodd@gmail.com> - 2026-01-04 14:21 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 jayjwa <jayjwa@atr2.ath.cx.invalid> - 2026-01-04 16:16 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 David Todd <hdtodd@gmail.com> - 2026-01-04 16:58 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 David Todd <hdtodd@gmail.com> - 2026-01-04 14:28 -0500
Re: Try again: IP between Pi <--> klh10 TOPS-20 scott@slp53.sl.home (Scott Lurndal) - 2026-01-05 15:33 +0000
Re: Try again: IP between Pi <--> klh10 TOPS-20 Andy Valencia <vandys@vsta.org> - 2026-01-05 15:45 -0800
Re: Try again: IP between Pi <--> klh10 TOPS-20 David Todd <hdtodd@gmail.com> - 2026-01-04 08:59 -0500
csiph-web