Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
That explains the failure then, try doing 'ssh -6 -p 2345 ip6-localhost' or appending the line given previously as currently localhost will never resolve for ipv6 on that machine.
That explains the failure then, try doing 'ssh -6 -p 2345 ip6-localhost' or appending the line given previously as currently localhost will never resolve for ipv6 on that machine.
Both of those work but how does that help connect remotely using 2345?
It confirms it is working locally, so we can rule out any conflicts on that side.
Next suggestion, add a temporary rule in ip6tables that opens ALL traffic to the IP you are connecting from, so little more than a: -I INPUT 1 -s <yourip> -j ACCEPT
Well then I don't think the issue is ip6tables or sshd. It maybe another service on the server, but you don't happen to have a hardware firewall in front of the server do you? The only remaining ideas I have would be setting ip6tables to log and see if it reports anything hitting or using something like tcpdump or tethereal to actually scan the incoming traffic to see if it is hitting the server.
Fixed
Of course the answer is always obvious isn't it?
The remote server wasn't blocking the connection it was the local server stopping connections going out on port 2345. Duh! So all I had to do was add the remote servers ssh port to the "Allow outgoing IPv6 TCP ports" And in the hosts.allow file on remote server put the IPv6 addr in square brackets. Example:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.