can't ssh from host to remote

kitepilot at kitepilot.com kitepilot at kitepilot.com
Fri Jul 18 15:46:22 MST 2014


> is there a way turn NAT off in the second router?
Most likely yes, but not always.
ET 

> :-)~MIKE~(-: 
> 
> 
> On Fri, Jul 18, 2014 at 2:49 PM, Michael Havens <bmike1 at gmail.com> wrote: 
> 
>> you are correct. that is what I've done and what is going on. I don't have
>> a switch.... only the other router. I'm mad at myself..... I had a switch
>> but got rid of it before I moved to FL. 
>>
>> :-)~MIKE~(-: 
>>
>>
>> On Fri, Jul 18, 2014 at 2:37 PM, Gilbert T. Gutierrez, Jr. <
>> mailing-lists at phoenixinternet.net> wrote: 
>>
>>> What I think you are doing is using NAT between your 2 networks. Below is
>>> my approximation of your system patched together from your comments...
>>> 1. You have the router that is connected to your ISP. It is performing
>>> NAT and handing out a private network to anything on its LAN and WIFI
>>> interfaces.
>>> 2. You have a second router that has its Internet/WAN interface connected
>>> to one of the LAN interfaces on the first router. It is also performing NAT
>>> and handing out a second private network on its LAN and WIFI interfaces. 
>>>
>>> You WOULD be able to connect via SSH from a device connected to the
>>> router listed in point 2 to a device connected to the router listed in
>>> point 1. You WOULD NOT be able to connect from the device connected to the
>>> router listed in point 2 FROM a device connected to the router listed in
>>> point 1 due to NAT. 
>>>
>>> There are ways to get beyond this and only have one network utilizing 2
>>> SOHO routers. I would always recommend for anyone who has limited network
>>> experience to only use one router and use a combination of switches and
>>> access points to extend wired LANs and provide better WIFI coverage. If the
>>> setup is how I described, you may have other issues due to DOUBLE NAT that
>>> you just have not recognized yet. 
>>>
>>> Gilbert 
>>>
>>>
>>> On 7/18/2014 12:30 PM, Michael Havens wrote: 
>>>
>>>> telnet localhost 22 from the server received no answer from the client
>>>> telnet 192.168.1.101 22 from the client received no answer from the
>>>> server 
>>>>
>>>> I'll get back to you about the research project
>>>>  (and as a private message) 
>>>>
>>>> :-)~MIKE~(-: 
>>>>
>>>>
>>> ---------------------------------------------------
>>> PLUG-discuss mailing list - PLUG-discuss at lists.phxlinux.org
>>> To subscribe, unsubscribe, or to change your mail settings:
>>> http://lists.phxlinux.org/mailman/listinfo/plug-discuss 
>>>
>> 
>>


More information about the PLUG-discuss mailing list