Path: csiph.com!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail From: David Todd Newsgroups: alt.sys.pdp10 Subject: Re: ?TCPIP TOPS-20 <--> Raspberry Pi or Mac OSX Date: Thu, 30 Oct 2025 09:04:32 -0400 Organization: A noiseless patient Spider Lines: 61 Message-ID: <0eedd284-76eb-4c71-9718-d26f14f43e9e@gmail.com> References: <10dfvld$2k7ba$1@dont-email.me> <87frb7g9po.fsf@atr2.ath.cx> <3b30b25f-63d6-49ca-9158-1d885b69c50f@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Thu, 30 Oct 2025 13:04:33 +0000 (UTC) Injection-Info: dont-email.me; posting-host="fe04038684e27296c1ff9ec0c06524a2"; logging-data="3884101"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+Gi7h/uDG7eZC2kHnxSUKq" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:Ps8D5Arvr3wAIs2ZGKUeCv0iu/M= In-Reply-To: Content-Language: en-US Xref: csiph.com alt.sys.pdp10:9772 Scott, thanks for the suggestions below. I'll check with brctl as I work through the process again today and document that. I'll also try your method for setting up the bridge. But I run klh10 as root, anyway, for other reasons, so I'm not so concerned about device ownership. On 10/29/25 1:24 PM, Scott Lurndal wrote: > David Todd writes: >> On 10/26/25 2:51 PM, jayjwa wrote: >> >> >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. >> >> I think I know why this is... >> >> >> Jayjwa, >> >> Thanks for your detailed reply. I was able to execute most of your >> script, and it seemed to work fine, except that I don't have the >> script for "make_set_tuntap". Could you reply with that? >> >> I assumed that it set up the indicated set of taps, so I enabled my >> tap0 (I'll only have the one, plus the tap1 needed when klh10 starts >> up its network interface). >> >> When I started tap1, as klh10 was loading the NI, I checked with >> ifconfig and tap1 had the ip address of wan0! I deleted its >> address, and subsequently tap0 entirely, but I'm still getting >> the behavior that ftp to the Pi fails and telnet into the dec20 fails. >> Again, the ftp from the pi to the dec20 ends up getting connected >> to the pi. >> >> And somewhere along the line, I broke the routing for the Pi, so it can't >> get to the outside world. :-) Fine after reboot of the Pi. >> >> So I'll start from scratch again tomorrow. >> >> Meanwhile, here's the ifconfig after all my tinkering. It *looks* like >> the configuration you suggested I should be seeing, but something's >> clearly still wrong. I'll check iroute2 tomorrow. > > What is the output from > > # brctl show > > > The sequence I use to create a tap device is: > > # tunctl -p -u USERNAME -t xxxnic0 > # brctl addbr xxxbr0 > # brctl addif xxxbr0 xxxnic0 > # ifconfig xxxnic0 up > # ifconfig xxxbr0 172.25.13.1/24 up > # ethtool -K xxxbr0 tx off > > Substitute your username for "USERNAME"; this will > ensure the tap device is owned by and accessible to > your user (so you don't have to run simh as root). > >