I know I can use nailed ports with telnet, but I want to use ssh. How
can I control my user logins by port#. I could have Linux "listen" on
ports other than 22 and have users "ssh host port#", but can I nail a D3
port# to an ssh port#?

Thanks,

Bruce Ackman

Lewis Supply Company

PS I'm also interested in the SATA vs SCSI thread. I'm planning on
buying a nifty little device from Adaptec, holds 4 SATA or SCSI drives
in a hot-swappable 3 enclosure and supports various RAID levels. But
what should I go with, SATA or SCSI?

Bruce,

I have a one site with an Adaptec 4 port SATA controller + Adaptec 4
drive hot-swap enclosure package, and many other sites with 3Ware
controllers and various drive enclosures, including one all 3Ware
solution. I recommended the Adaptec because it was slightly less
expensive than the 3ware, but now regret it. I like the 3Ware software
way better; the Adaptec interface is pretty confusing and the
performance is not great.

/Scott Ballinger
Pareto Corporation
Edmonds WA USA
206 713 6006

you can start up an ssh server on any TCP port you wish with the -p
command line argument (ex: sshd -p 22331). To achieve the 'nailed
telnet' effect you could put the D3 command line in the shell's login
script file (.bash_login if you use the bash). Specify the port number
you want on the D3 command line that you put in that script to 'nail'
the user to that port.

Can SSH be controlled with the xinetd in the same manner as telnet ?
May be able to model after the nailed telnet example that RD use ?

"Tedd Scofield" wrote
and hardcode the d3 port number based on that userid; the alternative
would be to have a single linux userid that every d3 user invokes, whose
..bash_login script laboriously converts the 'tty' number back to sshd port
number and thence to assigned D3 port number, using native linux cmds.

I think Ross' suggestion is the place to start. Look at the auto-xinet
process in dm,bp, that sets up nailed telnet sessions automatically. I
think it creates an executable script for each port in /usr/bin/d3net,
and also a bunch of d3nnnnn entries in /etc/xinetd.d. Maybe you could
tweak them to use sshd instead of telnet?

/Scott Ballinger
Pareto Corporation
Edmonds WA USA
206 713 6006

This might be worth taking a look-see. We use Pathfinders D3USER on all
our D3/Linux client's systems. It works and the price is right!

http://www.pfinders.com/d3user.html
http://www.pfinders.com/pricing.html

Dave Weaver, Weaver Consulting


Lewis Supply Company wrote:

Lewis Supply Company wrote:
I'd be curious to know how you made out with this issue.

Thanks, Art