On 09/08/2016 03:06 PM, Anton Aylward wrote:
On 09/08/2016 02:41 PM, jdd wrote:
and to follow the questions, using IPV6 is not an option, not really in the wild.
Yes, no maybe.
First, there's encapsulation.
I'll leave it to James Knott to cover that.
I used a 6in4 tunnel, which used IPv4 to carry the IPv6 traffic to/from a "tunnel broker", who'd then connect to the Internet via IPv6. I had a /56 prefix, which provided 2^72 addresses. However, my ISP started offering IPv6 a few months ago, so I no longer use the tunnel.
Secondly, there is no reason you can't use ipv6 between hosts behind a IPV4 NAT'ing firewall.
I certainly did that, in addition to my IPv6 tunnel, as well with my ISP provided IPv6. Most of the traffic on my home network is IPv6.
Finally, SSH and SSHD can be forces to use ipv4 ONLY, ipv6 ONLY, or, as the man page makes clear, it can listen on multiple addresses, multiple ports at each address, and IPv4 addresses simultaneous with IPV6 addresses.
Of course the client SSH can be directed to any address, any port and told to use either IPV4 or IPV6. See the man page for that too.
And yes you can encode that in the config file on a per host basis.
So, the end result is you can have the best of both worlds on your internal network, for example, only allowing inbound ipv4 SSH because of your NAT'ing router and reluctant ISP, but ipv6 internally.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org