On Sun, Jul 20, 2014 at 11:54 PM, E.S. Rosenberg
wrote:
> I think we need to reset here for a minute...
>
> Is your goal to connect to a machine with a IP on a private range where
> there exists a gateway machine or router with a (known) public IP?
> In that case the solution is very simple: port-
Hi Erez,
On Mon, Jul 21, 2014 at 4:18 AM, Erez D wrote:
>
> it is not even a dynamic ip, it is a private ip behind a dynamic one
>
Then, what Eliyahu wrote should serve you a perfect solution.
Also, there's not much advantage in the point of hiding behind the
"security by obscurity" method (i
On 22 July 2014 00:52, Guy Gold wrote:
> Hi Erez,
>
> On Mon, Jul 21, 2014 at 4:18 AM, Erez D wrote:
>
>>
>> it is not even a dynamic ip, it is a private ip behind a dynamic one
>>
>
> Then, what Eliyahu wrote should serve you a perfect solution.
>
> Also, there's not much advantage in the poin
Any decent port scanner (nmap for instance) will find the SSH service
regardless of the port its' on, while the likelihood of a firewall blocking
access to random non-standard ports is very high.
I use fail2ban to prevent brute forcing and generally also try to have some
form of port knocking (kno
Whatever.
I'm speaking from personal experience that I didn't find this necessary.
On 22 July 2014 08:21, E.S. Rosenberg wrote:
> Any decent port scanner (nmap for instance) will find the SSH service
> regardless of the port its' on, while the likelihood of a firewall blocking
> access to ran
