I'm a french student trying desperately to grant access to a raspberry pi using ssh. I'm using :
raspberry : raspberry B+ with raspbian
laptop : ubuntu 18.04
router : livebox 3 (France)
My goal : I want to set up my raspberry pi and my router to enable the use of SSH from a remote network on the internet. I'm perfectly able to access my raspberry via ssh on my local network using both IPv4 and IPv6 address and the command :
sudo ssh pi@192.168.1.30
I tried a lot of different things and found a bunch of tuto all over the internet including on Stack Overflow websites or on YouTube.
I set up my router from an internet browser. The public address of my router is using IPv6 however IPv4 seems required and is enabled on the local network. The following video (in French, sorry) perfectly describe the web pages hosted by the router and how to set it and I followed the instruction without sucess : Youtube video presenting my router set up page
I really struggle with this issue. I created a fixed IP address for the raspberry on the local network, and created a NAT rule with following settings :
When I try to start a ssh connection from the internet, knowing the IP address of my router, I get this :
onyr@kenzae:~$ sudo ssh -p 50050 pi@2a******************* # I use IPv6, and also tried IPv4 without success
[sudo] password for onyr:
ssh: connect to host 2a********************* port 50050:Connection refused
I obviously not forgot to set up the port I use as external port, here 50050 as open in the IPv6 firewall. I absolutely don't know what to search for next... Pls help.
Post info : Thanks to a helpful user (@Bra1n), I probed the port I want to open, using GRC ShieldsUp!. Here is what I get :
GRC Port Authority Report created on UTC: 2019-04-24 at 09:24:57
Results from probe of port: 50050
1 Ports Tested
1 Ports Open
0 Ports Closed
0 Ports Stealth
THE PORT tested was found to be: OPEN.
TruStealth: FAILED - NOT all tested ports were STEALTH, - NO unsolicited packets were received, - NO Ping reply (ICMP Echo) was received
Apparently, the port I wanted is open, which sounds good. Another idea is to use UFW, here is what I get :
pi@phaeryos:~ $ sudo ufw status verbose
Status: inactive
pi@phaeryos:~ $ sudo ufw enable
Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
Firewall is active and enabled on system startup
pi@phaeryos:~ $ sudo ufw status verbose
Status: active
Logging: on (low)
Default: deny (incoming), allow (outgoing), disabled (routed)
New profiles: skip
To Action From
-- ------ ----
22/tcp ALLOW IN Anywhere
22/tcp (v6) ALLOW IN Anywhere (v6)