makes sense. you need to configure the fileserver to listen on the network by specifying bootargs on the fs like: local!/dev/sdXX/fscache -a tcp!*!564
you can verify this with the netstat command on the fs console looking for 9fs service in Listen state. or use "tcp" instead of "tls" on the netbooting client's bootargs. tls is handled by a helper service that terminates the tls connection and relays the paintext to its fileserver. if that fileserver is not listening for network connections that it will fail like this. it is probably a good idea to put fs= and auth= attributes in your ndb ipnet entry, so you do not need to specify this information in plan9.ini and dhcpd will supply this information to the client. -- cinap ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tda6e61e03ce222c0-Mfb338473b81d385622c100d7 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
