[NTLUG:Discuss] OpenSSH - Newbie Question
brian@pongonova.net
brian at pongonova.net
Wed Jul 5 15:17:51 CDT 2006
The other problem you'll discover is that the SSH client tries to
reverse-map its connections, and there is a significant delay when
connecting if it can't complete the reverse mapping.
I find it amusing that you consider DHCP "elegant and extensible." I
feel the same way about static addresses!
--Brian
On Wed, Jul 05, 2006 at 03:40:03PM -0500, Bobby Sanders wrote:
> On Wed, 2006-07-05 at 14:23 -0500, brian at pongonova.net wrote:
> > Why don't you just assign your internal machines non-routable IP
> > addresses?
>
> No real reason. (I'm only concerned with 2 or 3 Linux boxes and a couple
> of Windows machines that connect periodically.) It just seemed to be
> the most elegant and extensible way to go.
>
> BTW, I installed SAMBA for the windows machines (use this with the Linux
> machines, too. No problem in Samba with accessing the servers using
> their names. Wonder why ssh is so different.
>
> Thanks,
>
> Bobby
>
> > The you can either set up tinydns if you really want to
> > resolve the names, or just add them to your /etc/hosts file.
> >
> > --Bri
> >
> > On Wed, Jul 05, 2006 at 02:59:04PM -0500, Bobby Sanders wrote:
> > >
> > > On Wed, 2006-07-05 at 14:15 -0500, Bobby Sanders wrote:
> > > > I now believe that putting my router as a name server
> > > > in /etc/resolv.conf and allowing ssh access to all computers on the
> > > > local network managed by the router did the trick.
> > >
> > > Phooey! I was wrong.
> > >
> > > >From compt1
> > > $ ssh compt2
> > > ssh: compt2: Name or service not known
> > >
> > > $ ssh <compt2's IP>
> > > The authenticity of host '<compt2's IP> (1<compt2's IP>)' can't be
> > > established. ... Which, of course is just fine.
> > >
> > > Any ideas about what I'm doing wrong and/or not doing (right)? Surely
> > > it is possible to to do ssh compt1 from compt2 and be logged on to
> > > compt1. In fact, I do it at my ISP. Now if I could only figure out
> > > _how_ they do it, I would be moderately happy. :)
> > >
> > > Bobby
> > >
> > > > Bobby
> > > >
> > > > On Wed, 2006-07-05 13:55 -0500, Bobby Sanders wrote:
> > > > > I don't really know. :(
> > > > >
> > > > > Two computers, compt1 and compt2. On each machine these names is are
> > > > > aliases for for 127.0.0.1 in /etc/hosts.
> > > > >
> > > > > The computers are connected to a LinkSys router which connects to my
> > > > > cable modem and assigns dynamically assigns IPs to the computers when
> > > > > they connect to the router.
> > > > >
> > > > > In view of your comments on ssh using host resolver code to find the IP
> > > > > of a machine, I put the IP of my router as the 1st line
> > > > > in /etc/resolv.conf. Still no luck.
> > > > >
> > > > > Bobby
> > > > >
> > > > > On Wed, 2006-07-05 at 12:27 -0500, Wayne Walker wrote:
> > > > > > Are you using something like dyndns.org to handle these machine-name->
> > > > > > randomly-assigned-ips? ssh uses the system host resolver code to find
> > > > > > the IP for the machine to connect to.
> > > > > >
> > > > > > On Wed, Jul 05, 2006 at 12:04:18PM -0500, Bobby Sanders wrote:
> > > > > > > I'm making my 1st run at using OpenSSH. I have a router assigning IP
> > > > > > > addresses to the various machines. When I do:
> > > > > > >
> > > > > > > ssh <remote machine name>
> > > > > > >
> > > > > > > I get "ssh: <remote machine name>: Name or service not known"
> > > > > > >
> > > > > > > When I do:
> > > > > > >
> > > > > > > ssh <remote machine's current IP>
> > > > > > >
> > > > > > > the first time, I get the expected message to authenticate, etc.
> > > > > > >
> > > > > > > Can I use dynamically assigned IPs with OpenSSH and, if so, how.
> > > > > > >
> > > > > > > Thanks in advance.
> > > > > > >
> > > > > > > Bobby Sanders
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > http://ntlug.pmichaud.com/mailman/listinfo/discuss
> > > > > >
> > > > >
> > > > > _______________________________________________
> > > > > http://ntlug.pmichaud.com/mailman/listinfo/discuss
> > > > >
> > > > >
> > > >
> > > > _______________________________________________
> > > > http://ntlug.pmichaud.com/mailman/listinfo/discuss
> > > >
> > > >
> > >
> > > _______________________________________________
> > > http://ntlug.pmichaud.com/mailman/listinfo/discuss
> >
> > _______________________________________________
> > http://ntlug.pmichaud.com/mailman/listinfo/discuss
> >
> >
>
> _______________________________________________
> http://ntlug.pmichaud.com/mailman/listinfo/discuss
More information about the Discuss
mailing list