Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
Location: Somewhere inside 9.9 million sq. km. Canada
Distribution: Slackware 14.1, 14.2
The standard port for ssh is 22. I don't see that in your listing.
Have a look at /etc/ssh/ssh_config. In that file the port can be defined. You do not have to use port 22, if you are not using port 22, you need to forward what ever port you are using, and make it match in the ssh config file.
As far as port forwarding in your router, have you got a rule set for your linux server pointing to the linux systems IP address? Is the linux IP address static?
As far as I know, for ipv6, :::* indicates all fields of 0's, repeated.
What ":::*" means in that context is "any address + any port". The initial "::" means the address. So "tcp 0 0 :::22 :::* LISTEN 3422/sshd" means listening on any address in IPv6 on port 22, and accept from any address in IPv6 from any port.
By default, a listen on "::" also listens on 0.0.0.0, so both IPv4 and IPv6 can be listened for on one socket, which is convenient for simple programs that are going to block in an accept() call. This can be seen by an attempt by ssh when doing port forwarding to listen to both "::" and 0.0.0.0 and getting a bind failure for the 0.0.0.0 because the port is busy with "::" on the same port. You can turn this behavior off with "echo 1 > /proc/sys/net/ipv6/bindv6only", in which case for a program to listen on both IPv6 and IPv4, it has to bind separate sockets to each, and do the appropriate blocking I/O on both sockets to wait for incoming connections on either.
Since I do see a listen on port 22, it's another issue. Your solution mentioned a gateway setting. If that was wrong, it should break a lot more than just ssh, relative to the internet. As for the IPv6 modules, I don't see how that would impact things if ssh was successfully bound to port 22 and listening (as your on-LAN connections worked with).
BTW, I recommend using a different port than 22, at least at the router side facing the internet. There are lots of crackpots scanning for weak passwords via ssh. Even if all your passwords are strong, this still makes for lots of noisy messages in logs, discouraging you from looking for legitimate breakins. Pick a different port not well known for any common service and use that for your ssh service facing the internet.