9front - general discussion about 9front
 help / color / mirror / Atom feed
* [9front] tsl boot, tsl error
@ 2021-01-14 10:16 Daniel Morandini
  2021-01-14 11:47 ` cinap_lenrek
  0 siblings, 1 reply; 3+ messages in thread
From: Daniel Morandini @ 2021-01-14 10:16 UTC (permalink / raw)
  To: 9front

Hi folks,
I’m attempting to tls boot my thinkpad but I’m stuck on a “tls error” (see below).

I suspect there is something wrong with my secstored/factotum setup. I can rcpu,
but if I attempt to srvtsl the fileserver I get a tsl error on mount.

I was wondering if any of you had a little bit of time for helping me :)

Cheers,
dan

Plan 9
126 holes free
0x0001b000 0x00090000 479232
0x00661000 0x0ffff000 261742592
262221824 bytes free
pcirouting: ignoring south bridge PCI.0.31.0 8086/1E56
cpu0: 2494MHz GenuineIntel P6 (AX 000306A9 CX 77BAE3FF DX BFEBFBFF)
LAPIC: fee00000 0xe002d000
ec: cmd 66, data 62
ELCR: 0000
cpu0: lapic clock at 100MHz
cpu1: 2494MHz GenuineIntel P6 (AX 000306A9 CX 77BAE3FF DX BFEBFBFF)
cpu2: 2494MHz GenuineIntel P6 (AX 000306A9 CX 77BAE3FF DX BFEBFBFF)
cpu3: 2494MHz GenuineIntel P6 (AX 000306A9 CX 77BAE3FF DX BFEBFBFF)
#l0: iwl: 54Mbps port 0xF0C00000 irq 255 ea 843a4bd682ac
#S/sdE: ahci: sata-II with 1 ports
#A0: hda mem f1510000 irq 255
#A0: codec #0, vendor 10ec0269, rev 00100203
#A0: codec #3, vendor 80862806, rev 00100000
usbehci: 0x8086 0x1e2d: port f151a000 size 1024 irq 255
usbehci: 0x8086 0x1e26: port f1519000 size 1024 irq 255
usbxhci: 0x8086 0x1e31: port f1500000 size 65536 irq 255
3326M memory: 256M kernel data, 3069M user, 3694M swap
#l0: firmware: iwn-6005, rev 12a80601, build 0, size [2] 25c50+14000 + [2] 20868+14000 + 0
sdE0: LLBA 500,118,192 sectors
  TOSHIBA THNSNF256GMCS FSLAN102 738S125GT38S125GTVEY [newdrive]

/dev/sdE0: TOSHIBA THNSNF256GMCS
/dev/sdE0/9fat	 dos
/dev/sdE0/data	
/dev/sdE0/fscache	 cwfs64x
/dev/sdE0/fsworm	
/dev/sdE0/nvram
/dev/sdE0/other	
/dev/sdE0/plan9
bootargs is (tcp, tls, il, local!device)[local!/dev/sdE0/fscache] !rc
% factotum
% aux/wpa -n\b\b-\b\b\b\b\b\b\b\b\bcat /net/ether0/ifstats
essid: 
bssid: ffffffffffff
node: 1414590eb4a1 1411 100         12 VodafoneMosca
node: 6214590eb4a2 1401 90          12 Vodafone-WiFi
node: 6214590eb4a4 1411 90          12 Vodafone-Guest
% \b\b\baux/wpa -p -s VodafoneMosca /net/ether0

!Adding key: essid=VodafoneMosca proto=wpapsk
password: 
!
% ip/ipconfig
% cat /net/e\bndb
ip=192.168.1.12 ipmask=255.255.255.0 ipgw=192.168.1.1
	sys=thinkterm
	dom=thinkterm.station
	dns=192.168.1.1
% echo $auth

% echo $fs

bootargs is (tcp, tls, il, local!device)[local!/dev/sdE0/fscache] tls
ipconfig: recvra6: no router advs after 3 sols on /net/ether0
fs address is? 192.168.1.11
auth address is? [192.168.1.11] 
secstore password: 
secstore

!Adding key: dom=Pardac proto=dp9ik
user[glenda]: 
password: 
!
mount: mount /root: tls error
mount -c #s/boot /root: mount 504: mount

/dev/sdE0: TOSHIBA THNSNF256GMCS
/dev/sdE0/9fat	 dos
/dev/sdE0/data	
/dev/sdE0/fscache	 cwfs64x
/dev/sdE0/fsworm	
/dev/sdE0/nvram
/dev/sdE0/other	
/dev/sdE0/plan9
bootargs is (tcp, tls, il, local!device)[local!/dev/sdE0/fscache] 
current fs is "main"
11 uids read, 6 groups used
63-bit cwfs as of Wed Jan 13 16:10:19 2021
	last boot Thu Jan 14 10:49:32 2021

init: starting /bin/rc
nusb/serial: getdev: '/dev/usb/ep9.0/data' device or object already in use


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [9front] tsl boot, tsl error
  2021-01-14 10:16 [9front] tsl boot, tsl error Daniel Morandini
@ 2021-01-14 11:47 ` cinap_lenrek
  2021-01-14 15:13   ` Daniel Morandini
  0 siblings, 1 reply; 3+ messages in thread
From: cinap_lenrek @ 2021-01-14 11:47 UTC (permalink / raw)
  To: 9front

the t9fs service basically just establishes a tls tunnel,
authenticated using your dp9ik key, and then proxies to
the 9fs service on the fileserver.

here, take a look:

term% cat /rc/bin/service/tcp17020
#!/bin/rc
exec tlssrv -A /bin/aux/trampoline 'net!$fs!9fs'

so this implies that your fileserver is also listed in
ndb with a fs= attribute in the ipnet or the cpu server
ip entry.

and, that the fileserver is listening on the 9fs
(tcp port 564).

you can test if your fs is listening by dialing
the 'net!$fs!9fs' dialstring. (note here, $fs is
*NOT* a environment variable, it is a ndb attribute
that ndb/cs will search for (relative to the machines
ip address) and substitute it by the value).

--
cinap

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [9front] tsl boot, tsl error
  2021-01-14 11:47 ` cinap_lenrek
@ 2021-01-14 15:13   ` Daniel Morandini
  0 siblings, 0 replies; 3+ messages in thread
From: Daniel Morandini @ 2021-01-14 15:13 UTC (permalink / raw)
  To: 9front

Hi cinap :D

> the t9fs service basically just establishes a tls tunnel,
> authenticated using your dp9ik key, and then proxies to
> the 9fs service on the fileserver.
> 
> here, take a look:
> 
> term% cat /rc/bin/service/tcp17020
> #!/bin/rc
> exec tlssrv -A /bin/aux/trampoline 'net!$fs!9fs'
Ahhhh got it!


> and, that the fileserver is listening on the 9fs
> (tcp port 564).
tcp  0    glenda     Listen       secstore   0          ::
tcp  1    none       Listen       rcpu       0          ::
tcp  2    glenda     Listen       ticket     0          ::
tcp  3    none       Listen       t9fs       0          ::
tcp  4    glenda     Established  rcpu       62315      192.168.1.12
tcp  5    glenda     Established  rcpu       38078      192.168.1.12
tcp  6    network    Closed       secstore   58979      192.168.1.6
tcp  7    glenda     Established  rcpu       58981      192.168.1.6
tcp  8    network    Closed       56203      ticket     filefucker.station
tcp  9    network    Closed       42207      ticket     filefucker.station
tcp  10   network    Closed       ticket     42207      filefucker.station
udp  0    network    Closed       0          0          ::
il   0    network    Closed       0          ticket     filefucker.station
icmp 0    network    Datagram     0          1          ::
icmpv6 0    glenda     Datagram     134        134        ff02::1

The server is *NOT* listening on 564, but

console=0 service=cpu sysname=filefucker nvram=#S/sdM0/nvram user=glenda authdom=Pardac nobootprompt=local!/dev/sdUdcc3b/fscache -a tcp!*!564

this is my cmdline.txt file. It theory I’m instructing cwfs to listen
on 564 right? (The fileserver is a raspberry pi4 with a SATA disk).

—--
As usual, telling the problem out loud made it clear :D

I am listening on the rcpu port because my server is instructed
to be a cpu server, hence starts listening and thats why I can rcpu
into it. I cannot use the file server directly though because
‘-a tcp!*!564’ is not interpreted correctly (spacing!)!

…I quoted that, I that just booted for the first time from the network.
It was just amazing 😂

Thank you sincerely,
I’m learning so much from the front like never before.
Have a nice day

dan

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2021-01-14 15:52 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-01-14 10:16 [9front] tsl boot, tsl error Daniel Morandini
2021-01-14 11:47 ` cinap_lenrek
2021-01-14 15:13   ` Daniel Morandini

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).