Hey guys, i have a problem and i thought maybe you can help me.

>>55996808
Oh yeah, and a port scan of my global ip shows me that port 22 is visible to the outside

Change the port number so that all the chinese haxorz can't get to you.

>>55996986

I already tried that. I forwarded port 9999 and 18400 to 22, but still the same message.

>>55996808
>i cannot disable the firewall of my router, but pinging my global ip works, so i don't think the firewall is blocking the ssh connection
Wow, you are dumb.

You really shouldn't be doing this with the level of knowledge you haev.

Is ssh listening on only network lol

>>55996808
No you didn't do everything right

For one you're running fucking Putty

OK. Try to SSH from your windows "computer" directly to the local IP address of your Raspberry Pi. Not your internet IP address. If it doesn't work, that means you have to check the firewall config on the Pi, as well as the SSH settings.

>>55997041
Only local network*

>>55997015


I know that ping and ssh are different protocols and have nothing to do with each other. My thought process was: if they dont block ping, they maybe also don't block ssh.


Also: Saying someone is dumb without reasoning why.


Enlighten me

Telnet from the outside to port 22. It will give you some idea if the connection fails or the authentication fails. You should also be able to see the connection in the logs on your pi.

>>55996808
Try port scanning it from one of those online nmap services.

>>55997078
An ICMP echo request 'ping' is used for network troubleshooting. An SSH connection on port 22 is used for remotely connecting and controlling computers.

Your thought process kind of sucked on that one. It's acceptable from a security standpoint for a firewall to answer ping requests. It's useful for a tech to troubleshoot basic networking faults. It's absolutely unacceptable to ship a default firewall config with fucking SSH wide open.

>>55997041

I did not know that this was a possibility, will check in a minute

>>55997057

Thanks for the advice, but i explained in the OP that i already did that, and that i can establish a connection from my local network.

>>55997101

Will try


>>55997102

I did run a port scan and it showed the port, so port forwarding seems to work

>>55997057
>can't read op
>>55997078
>can't read sticky

>>51971506
>/g/ is NOT your personal tech support team or personal consumer review site.
There's even threads for retarded questions like these.

it says the connection is refused, not 'no response' or w/e which it would if dropped. It's receiving the connection on the pi and refusing it.

what you really need to do is put the pi on a dmz and make an airtight firewall on the device itself with iptables, but since that ups the complexity by 100 times just open your home lan on the most dangerous port and use challenge-response authentication with a short password, and don't log anything