On Sat, Mar 25, 2017 at 2:49 PM Philippe LeCavalier <supp...@plecavalier.com> wrote:
> On Sat, Mar 25, 2017 at 2:08 PM Nate Bargmann <n...@n0nb.us> wrote: > > * On 2017 25 Mar 12:36 -0500, Philippe LeCavalier wrote: > > > One obvious aspect is firewalling. Rest assured I have opened TCP 22 and > > ofrwarded to the correct host(the debian box). I can access all the other > > forwarded services I've configured without issues but not SSH on the Deb > > box. I can see the connection go through the firewall in the live feed > but > > the box doesn't answer. > > Is there a firewall running on the server that is blocking port 22? > > > sshd_config is stock and daemon is running yet I get nothing in the logs. > > Not even attempts with DEBUG enabled. > > Usually if there is a firewall running on the box, entries will be found > in syslog, but your logs are quiet. > > A default sshd_config has ListenAddress set to 0.0.0.0, if it were set > to anything other than the network IP address, that would cause an issue > > It's 0.0.0.0 > > > Otherwise, I'd make sure the router is actually forwarding port 22 to > the right box. > > As I mentioned, I can see the firewall forwarding the connection to the > server. > > > I've found some ISPs block port 22 to their customers. In that case, a > port above 1024 can be used and the router can then forward that > connection to the server on port 22. > > I changed it to 2222 and still get the same issue. As with 22, after I > change the port to 2222 I can successfully ssh to the box from within the > LAN. > > > - Nate > > -- > > "The optimist proclaims that we live in the best of all > possible worlds. The pessimist fears this is true." > > Ham radio, Linux, bikes, and more: http://www.n0nb.us > > -- > Regards, > Phil > Nevermind. I changed the forward to another box and can't get to it either so it has to be something in the firewall capturing the connection despite it showing a clean passthru. Thank you for your help guys! Sorry for the false alarm. -- Regards, Phil
