Re: [9front] Is there a way to extend telnet through rexport?

[Mack Wallace <mackbw@mapinternet.com>]

Thanks everyone.

Using con -l I was able to connect to a telnet service that was rexported from machine to another. I was able to do this as follows;

First: set up the connection to the host machine as a service
telnet -s service_name host

Second, if one needs to log into the host to keep the host from closing the session, echo the login to a file. In my case, the user name a password were both admin. Knowing that after a connection the host immediately asked for a username and then a password allowed me to do this “blind.” So I used the following twice:
echo admin >> /srv/service_name

To export that service file to another 9front machine, I had to bind that service to another file. In this case I set up an ‘exports’ directory under my home directory. In exports, I ’touched’ a file named for the host. This allowed me to then bind using:
bind /src/service_name /usr/user_name/exports/host_named_file

I was then able to export to the 9front server:
rexport -s exported_service_name /usr/user_name/exports 9front_server 

From the 9front server I was then able to
mount /srv/exported_service_name /n/exported_service_name (or whatever you want)

Then I was able to con -l /n/exported_service_name/host_named_file

This will work fine, as long as one doesn’t do something to make the host at the far end close the connection. For me, this means to never select “quit” (type q)  from a menu of choices that the host provides, but use the control-/ and q for the con program to close its connection without any of the other connections closing.

Hopefully those notes will be useful to someone someday.

For one of the machines I’m connecting to, I did compile u9fs and get it working. I haven’t done much file work with it, but it’s a start. I would love to use u9fs on another device, but the manufacturer has the system pretty locked down, with only telnet and tftp as means of getting files in and out. If only I could crack the root account. Oh well. 

Thanks for the help. 


> On Apr 5, 2021, at 10:14 PM, Lyndon Nerenberg (VE7TFX/VE6BBM) <lyndon@orthanc.ca> wrote:
> 
> Mack Wallace writes:
>> 
>> I have a number of different sites which each have numerous disparate =
>> systems that need to be administered - essentially by moving files =
>> around. I want to use Plan9/9front to consolidate these systems at each =
>> site and present them as a file structure on a server in the main =
>> office. So essentially each location has its own subdirectory, and each =
>> system as that site is represented by a subdirectory below that.
> 
> Depending on how 'disparate' those machines are, you might get
> surprisingly close to your goal by running u9fs on the target hosts.
> That, combined with a bit of ssh glue on the Plan9 side, will let
> you import arbitrary filesystem trees from remote UNIX-like hosts.
> It's not completely seamless, and you'll have to accept some very
> basic 'all or nothing' permissions -- the exported filesystems will
> have the permissions of the uid/gid running u9fs.  But you can get
> a surprising amount of work done with this model, despite the
> restrictions.
> 
> Several years ago I ran a setup like that to remotely monitor and
> administer about a half dozen sites scattered all over the place;
> it worked remarkably well, even if it wasn't the most blazingly
> fast for network I/O.  Since then the Plan9 ssh implementations
> have changed, so what I had before no longer works.  But, my lack
> of motivation to fix bitrot aside, there's no reason I (read 'you')
> couldn't build something like that today.
> 
> --lyndon
>