-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-ID: <alpine.LSU.2.21.1908080027080.748@Telcontar.valinor> On Wednesday, 2019-08-07 at 16:44 -0400, James Knott wrote:
On 2019-08-07 04:16 PM, Carlos E. R. wrote:
It asks for IPv4 Label, address and netmask. What is label? Ah. Help explains it. Still, no IPv6 support in Yast :-(
In all the years I've been running IPv6, I've never had to manually configure an IPv6 address. It normally happens automagically.
And I have never had it happen automatically, because no provider provides IPv6 here. As far as we know, it is going to be IPv4 for ever. Those histories about IPv4 running out and having to implement IPv6 now yes or yes, were all lies {sarcastic}. I don't know if I'll ever see IPv6 before I go gaga. Maybe if the Chinese implement 5G here we might see something. I'm not the only one wondering about it: <https://www.adslzone.net/2017/02/16/no-estamos-utilizando-ya-todos-espana-ipv6-pleno-2017/> *Why aren't we all already using IPv6 in Spain in full 2017?* ... In Europe we find countries with an average of 12%, with Spain being one of the countries in the European Union where there is the least adoption with 0.11%. ... The main problem is that Spanish operators do not have IPv6 routing enabled. Movistar has adapted its network to IPv6 and with addresses assigned to all customers, but these addresses are not routable over the Internet as routing and RA/DHCPv6 are deactivated, so until they activate it, the rest of the operators will not move a chip. <https://www.adslzone.net/2018/05/22/reduce-velocidad-adopcion-ipv6/> *IPv6 Adoption Slowed: What's Happening?* IPv6 was officially released to the world in 2012, and since then its adoption has been accelerating. However, so far in 2018 its adoption has stagnated, which is atypical considering the rapid adoption it has had so far. ... There is little interest in implementing it However, these measures do not appear to be sufficient to encourage adoption that does not seem to follow patterns, making it difficult to understand the deployment or predict what its adoption will be in the coming years. In addition, a user often looks at coverage, price and speed when contracting the Internet rather than whether or not he or she has IPv6. <https://www.redeszone.net/2019/05/04/adopcion-ipv6-nativa/> *Adoption of native IPv6 worldwide is around 25%, in Spain only 2.1% of connections.* Written by Sergio De Luz 4 May, 2019 at 13:00 The IPv6 protocol continues to expand around the world at a good pace, but it is not yet too widespread, which is a problem since all IPv4 addresses are exhausted. Currently what some operators are doing is trying to delay as much as possible the adoption of IPv6 in their networks, mitigating the problem of lack of public IPv4 addresses by using techniques such as CG-NAT to save a significant number of public IP addresses, while they continue to grow in number of customers. Do you want to know how is the adoption of IPv6 worldwide, in Spain and surrounding countries? ... While, worldwide, the use of IPv6 measured by Google is around 25%, in Spain we have a serious problem and that is that only 2.1% of Internet connections that use Google services use this network protocol natively. Currently the main operators are already deploying this protocol to their customers, but they do not usually do so natively, but make use of techniques such as DS-Lite, to provide connectivity with IPv4 networks since we are currently in a transition period.
With pfSense, you could configure it to use SLAAC or DHCPv6 to assign addresses.
Well, the router is ISP provided and I can not change it, so there is nothing of that. And no point in setting it up, as there is no IPv6 to internet. (as a matter of fact, the router supports IPv6. But as it sees no outside IPv6, it does not handle them internally either) I can only set up IPv6 internally, with no route to internet, to play internally. That's what I'm trying on that computer, and YaST doen't seem to allow it. Funny, because years ago I did set it up in this computer: 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 00:21:85:16:2d:0b brd ff:ff:ff:ff:ff:ff inet 192.168.1.14/24 brd 192.168.1.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fc00::14/64 scope global valid_lft forever preferred_lft forever inet6 fe80::221:85ff:fe16:2d0b/64 scope link valid_lft forever preferred_lft forever YaST: Network Card Setup ┌General──Address──Hardware───────────────────────────────────────┐ │ Device Type Configuration Name │ │ Ethernet▒▒▒▒▒▒▒▒▒▒▒▒↓ eth0▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ │ │( ) No Link and IP Setup (Bonding Slaves) [ ] Use iBFT Values │ │( ) Dynamic Address DHCP▒▒▒▒▒▒▒▒▒▒↓ DHCP both version 4 and 6▒↓│ │(x) Statically Assigned IP Address │ │IP Address Subnet Mask Hostname │ │192.168.1.14▒▒▒▒▒▒ /24▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ ←contar.valinor▒ │ │┌Additional Addresses───────────────────────────────────────────┐│ ││ ┌───────────────────────────────────────────────────────┐ ││ ││ │IPv4 Address Label│IP Address │Netmask │ ││ ││ │ │fC00:0:0:0::14│/64 │ ││ ││ │ │ ││ ││ │ │ ││ ││ │ │ ││ ││ │ │ ││ ││ │ │ ││ ││ │ │ ││ ││ │ │ ││ Maybe it works. I'll try to just write an fc00::16 address there, even if it says IPv4 only. [...] Slow... takes minutes to think it out. Well, it took: 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 4c:cc:6a:61:50:a1 brd ff:ff:ff:ff:ff:ff inet 192.168.1.16/24 brd 192.168.1.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fc00::16/64 scope global valid_lft forever preferred_lft forever inet6 fe80::4ecc:6aff:fe61:50a1/64 scope link valid_lft forever preferred_lft forever I have /64. You commented to use /7. I have no preference either way. Should I? Still, it doesn't work by name after updating my name server: Telcontar:~ # host Isengard Isengard.valinor has address 192.168.1.16 Isengard.valinor has IPv6 address fc00::16 Telcontar:~ # host Telcontar Telcontar.valinor has address 192.168.1.14 Telcontar.valinor has IPv6 address fc00::14 Telcontar.valinor mail is handled by 10 Telcontar.valinor. Telcontar:~ # ping Isengard PING Isengard.valinor (192.168.1.16) 56(84) bytes of data. 64 bytes from Isengard.valinor (192.168.1.16): icmp_seq=1 ttl=64 time=0.309 ms 64 bytes from Isengard.valinor (192.168.1.16): icmp_seq=2 ttl=64 time=0.352 ms ^C - --- Isengard.valinor ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1000ms rtt min/avg/max/mdev = 0.309/0.330/0.352/0.028 ms Telcontar:~ # ping -6 Isengard connect: Invalid argument Telcontar:~ # ping -6 fc00::16 PING fc00::16(fc00::16) 56 data bytes 64 bytes from fc00::16: icmp_seq=1 ttl=64 time=0.643 ms 64 bytes from fc00::16: icmp_seq=2 ttl=64 time=0.344 ms ^C - --- fc00::16 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1030ms rtt min/avg/max/mdev = 0.344/0.493/0.643/0.151 ms Telcontar:~ # I can not ping using IPv6 by name. I can by IP. Same thing with ssh. cer@Telcontar:~> ssh -X cer@Isengard.valinor Last login: Wed Aug 7 21:33:42 2019 from 192.168.1.14 Have a lot of fun... cer@Isengard:~> logout Connection to isengard.valinor closed. cer@Telcontar:~> ssh -6 -X cer@Isengard.valinor ssh: connect to host isengard.valinor port 22: Invalid argument cer@Telcontar:~> ssh -6 -X cer@fc00::16 The authenticity of host 'fc00::16 (fc00::16)' can't be established. ECDSA key fingerprint is SHA256:ILybaOsrdw95ufuc4st0K1V6QyLT8ZWwBCJQVZfzwNk. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'fc00::16' (ECDSA) to the list of known hosts. Last login: Thu Aug 8 00:22:42 2019 from 192.168.1.14 Have a lot of fun... cer@Isengard:~> Baffled... - -- Cheers, Carlos E. R. (from openSUSE 15.0 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXUtQ7xwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVeysAnRh7PhB5SqpP73tgc+vo w+qOeWpyAJ0YMeM4uyO4Bio6E1U4xLytpctgWA== =E4hH -----END PGP SIGNATURE-----