I neglected to add that tcp17020 is the tls trampoline that redirects to 564.
So I suspect my tls handshake but don't know how to debug it. Paul On Wed, Apr 9, 2025, 4:29 p.m. ron minnich <[email protected]> wrote: > But is it only listening on 564? > local!/dev/sdE5/fs -m 7549 -A -a tcp!*!564 > > no 17020 there? > > On Wed, Apr 9, 2025 at 3:36 PM Paul Lalonde <[email protected]> > wrote: > >> Ok, I keep re-learning the hardest lesson: tail doesn't tail a live file >> but cat does. >> Anyhow, I seem to have narrowed my problem down to the tls trampoline on >> tcp17020. >> Which, if I'm understanding correctly, means that I've got broken >> authentication? >> >> To summarize: Trying to network boot my terminal. I get my plan9.ini and >> kernel successfully from my server. >> I'd like the terminal to mount the file system from the server. >> When prompted for bootargs, when I provide "tls" I get the error message >> "/bin/tlsclient: dial tcp!192.168.0.2!17020: connection refused". >> My server runs the file system with options: local!/dev/sdE5/fs -m 7549 >> -A -a tcp!*!564 >> I think that means it will listen on *any* local interface, right? >> Or do I need something different to get it to listen on ether1 instead of >> ether0's tcp setup? >> >> Thanks, >> Paul >> >> On Tue, Apr 8, 2025 at 3:04 PM Paul Lalonde <[email protected]> >> wrote: >> >>> I've tried that one as well, also to the same no-contact. >>> So ipxe sees my host, at 192.169.0.2, but my Plan9 system doesn't. When >>> everything was plugged into the same subnet (ie, not using 2 interfaces on >>> my host) I mounted files fine from there. >>> I'm guessing I have a problem lower down in my stack. I'll delve deeper. >>> >>> Paul >>> >>> On Tue, Apr 8, 2025, 3:01 p.m. <[email protected]> wrote: >>> >>>> Quoth Paul Lalonde <[email protected]>: >>>> > Ok, on to my next problem: Though I can get dhcpd and tftpd to serve >>>> > happily from /net.alt, apparently I can't get aux/listen to do so. >>>> > >>>> > When my terminal tries to dial tcp!192.168.1.2!17020 I get a >>>> connection >>>> > refused. This is the same IP that's serving dhcp and tftp. >>>> > How do I get aux/listen to pay attention there? It's listening >>>> correctly >>>> > on my other interface, where drawterm connects quite happily. >>>> > >>>> > Any suggestions? >>>> > >>>> >>>> aux/listen doesn't have a '-x' option but it does have a final arg that >>>> lets >>>> you pass the protocol and netstack. >>>> >>>> aux/listen ... /net.alt/tcp >>>> >>>> should work. >>>> >>> *9fans <https://9fans.topicbox.com/latest>* / 9fans / see discussions > <https://9fans.topicbox.com/groups/9fans> + participants > <https://9fans.topicbox.com/groups/9fans/members> + delivery options > <https://9fans.topicbox.com/groups/9fans/subscription> Permalink > <https://9fans.topicbox.com/groups/9fans/Tb7d0bba710659dc0-M10157ad538948263a6e0aa31> > ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tb7d0bba710659dc0-M42ed63229831b6f4156a90fd Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
