[GRLUG] ssh timed out

Joseph Workman joseph.workman at gmail.com
Thu Aug 4 16:13:39 EDT 2011


Is SSH listening on the internal address ?

On Thu, Aug 4, 2011 at 4:06 PM, Michael Mol <mikemol at gmail.com> wrote:

> You can identify a TCP connection by as a
> sourceip:sourceport/destip:destport set. You can only have one
> connection with a particular combination of source and destination IPs
> and ports. You can have an effectively infinite number of connections
> to the same destination port at a destination IP. (roughly four
> billion times sixty-five thousand, but you'll hit resource limits on
> the server machine long before you approach that kind of theoretical
> number)
>
> Typically, multiple connections are allowed by changing the source
> port for each connection. I can have twenty concurrent SSH connections
> to the same destination box, and the only problem I'll have is keeping
> track of all my SSH clients.
>
> On Thu, Aug 4, 2011 at 4:00 PM, Eric Beversluis
> <ebever at researchintegration.org> wrote:
> > Hypothesis: I need to use NX to get from my windows machine to my linux
> > machine (dead screen) to use ssh on the latter. Since the server I'm
> > trying to access from inside the office is also the LAN router, does
> > that "occupy" port 22 so I can't then ssh from the linux box to the
> > server/router? Whereas, when I'm ssh-ing to that server from the outside
> > I'm not tying up its port 22? But, on the other hand, I'm now using port
> > 22 twice on the linux box when I use NX to get to the linux box and then
> > use ssh from the linux box to an outside box?
> >
> > On Thu, 2011-08-04 at 14:33 -0400, Joseph Workman wrote:
> >> Is SSH listening on that IP
> >>
> >> On Aug 4, 2011 2:23 PM, "Michael Mol" <mikemol at gmail.com> wrote:
> >> > On Thu, Aug 4, 2011 at 2:20 PM, Eric Beversluis
> >> > <ebever at researchintegration.org> wrote:
> >> >> The box has a public IP to the 2Wire modem and the outside and it's
> >> >> NATting the LAN. So when I'm trying to ssh in locally I've got a
> >> private
> >> >> address on the LAN and trying to reach the box at its private
> >> address.
> >> >> Both the (public) URL and the private address work with a browser.
> >> I can
> >> >> ping the box on its private IP address.
> >> >
> >> > Can you access the box at its public IP from the internal network?
> >> >
> >> > Is it possible the box has firewall rules which drop packets to port
> >> > 22 from the internal network?
> >> >
> >> > --
> >> > :wq
> >> >
> >> > --
> >> > This message has been scanned for viruses and
> >> > dangerous content by MailScanner, and is
> >> > believed to be clean.
> >> >
> >> > _______________________________________________
> >> > grlug mailing list
> >> > grlug at grlug.org
> >> > http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug
> >>
> >>
> >> --
> >> This message has been scanned for viruses and
> >> dangerous content by MailScanner, and is
> >> believed to be clean.
> >> _______________________________________________
> >> grlug mailing list
> >> grlug at grlug.org
> >> http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug
> >
> >
> >
> > --
> > This message has been scanned for viruses and
> > dangerous content by MailScanner, and is
> > believed to be clean.
> >
> > _______________________________________________
> > grlug mailing list
> > grlug at grlug.org
> > http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug
> >
>
>
>
> --
> :wq
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> _______________________________________________
> grlug mailing list
> grlug at grlug.org
> http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug
>



-- 
Joseph Workman
C.616.734.1411

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shinobu.grlug.org/pipermail/grlug/attachments/20110804/d09c5547/attachment.html>


More information about the grlug mailing list