Re: SSH Access Issue

2017-03-26 Thread Philippe LeCavalier
On Sun, Mar 26, 2017 at 6:04 PM Joshua Schaeffer wrote: > > On 03/26/2017 08:30 AM, Cindy-Sue Causey wrote: > > > In the case I'm thinking, it's about manually adding multiple lines to > a file that I'm not completely remembering just now. Gut is saying > it's /etc/network/interfaces. Mine's almo

Re: SSH Access Issue

2017-03-26 Thread Joshua Schaeffer
On 03/26/2017 08:30 AM, Cindy-Sue Causey wrote: In the case I'm thinking, it's about manually adding multiple lines to a file that I'm not completely remembering just now. Gut is saying it's /etc/network/interfaces. Mine's almost empty so I don't have an example to confirm that. Typically use

Re: SSH Access Issue

2017-03-26 Thread David Christensen
On 03/26/2017 05:21 AM, Philippe LeCavalier wrote: Turns out the box had a second default gateway by mistake, mine of course. I guess I forgot I manually added the default gateway when the box was in my lab. As it turns out the clue was irrelevant but talking things out here did somehow lead my t

Re: SSH Access Issue

2017-03-26 Thread Cindy-Sue Causey
On 3/26/17, Cindy-Sue Causey wrote: > On 3/26/17, Philippe LeCavalier wrote: >> On Sat, Mar 25, 2017, 17:52 wrote: >> >>> On Sat, Mar 25, 2017 at 06:56:03PM +, Philippe LeCavalier wrote: >>> >>> > Nevermind. I changed the forward to another box and can't get to it >>> either >>> > so it has

Re: SSH Access Issue

2017-03-26 Thread Cindy-Sue Causey
On 3/26/17, Philippe LeCavalier wrote: > On Sat, Mar 25, 2017, 17:52 wrote: > >> On Sat, Mar 25, 2017 at 06:56:03PM +, Philippe LeCavalier wrote: >> >> > 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

Re: SSH Access Issue

2017-03-26 Thread Philippe LeCavalier
On Sat, Mar 25, 2017, 17:52 wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Sat, Mar 25, 2017 at 06:56:03PM +, Philippe LeCavalier wrote: > > [...] > > > Nevermind. I changed the forward to another box and can't get to it > either > > so it has to be something in the firewall

Re: SSH Access Issue

2017-03-25 Thread tomas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, Mar 25, 2017 at 06:56:03PM +, Philippe LeCavalier wrote: [...] > 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

Re: SSH Access Issue

2017-03-25 Thread Philippe LeCavalier
On Sat, Mar 25, 2017 at 2:49 PM Philippe LeCavalier wrote: > On Sat, Mar 25, 2017 at 2:08 PM Nate Bargmann 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 debi

Re: SSH Access Issue

2017-03-25 Thread Philippe LeCavalier
On Sat, Mar 25, 2017 at 2:08 PM Nate Bargmann 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

Re: SSH Access Issue

2017-03-25 Thread David Christensen
On 03/25/2017 10:35 AM, Philippe LeCavalier wrote: I've recently installed a new server for a client, using Deb 8.5 net install. 2017-03-25 11:05:42 dpchrist@jesse ~ $ cat /etc/debian_version 8.7 Your Debian is stale. Please 'apt-get update' and 'apt-get upgrade'. Linux localhost(masked f

Re: SSH Access Issue

2017-03-25 Thread Nate Bargmann
* 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 se