IPv6 Bug ::1 notation do not work
-
Hi @jknott
Not it is not a loopback address.
The address is a /64 like this
fc00:####:####:####:0:0:0:1/64 This will work, but if you write it like this, fc00:####:####:####::1/64 it will not work .Regards
Henning -
@hsv It is working here (22.05-RC):
-
Do you use :: anywhere else in the address? It can only be used once.
BTW, there's not much point in hiding Unique Local Addresses. You're not protecting anything.
-
-
@jknott
No only as in my example. -
@jknott
I using this version:
Version 2.6.0-RELEASE (amd64)
built on Mon Jan 31 19:57:53 UTC 2022
FreeBSD 12.3-STABLEIf the next version works it's fin, but this version do not.
But your example is a subnet and not an ip number.
What I describe is the IPv6 number your are using under the interface.
Regards
Henning -
Well it works elsewhere and there are 2 examples of it above. By hiding that address, it makes it harder to see what the issue is. As with RFC1918 IPv4 addresses, there is absolutely no point in hiding ULA, as they can't be reached from the public Internet. If you are paranoid or wear a tinfoil hat, just change some of the digits, without changing the overall structure.
-
@hsv said in IPv6 Bug ::1 notation do not work:
I using this version:
Version 2.6.0-RELEASE (amd64)I'm running that too, which is the latest. What is the next version you're referring to?
-
22.05-rc I thought was the next version.
What is the first 64bit as long they are the same in a /64 is not crucial. I can change the notation from full to :: 1, where it stops working and change it back again, and it works. So I have reproduced the error.
Regarding your opinions about other persons, should you keep them to yourself. -
I just changed fd48:1a37:2160:4:4262:31ff:fe12:b66d to fd48:1a37:2160:4:4262::1 and it works.
Here's what ifconfig shows: inet6 fd48:1a37:2160:4:4262::1 prefixlen 64. So, you have some other issue that we can't see.
-
@hsv I noticed problems with IPv6 too, but for me these are not general but individual to an interface. For example, because mine is virtual and I deleted a "faulty" interface, added a new one and problem was gone (new MAC address etc.). So maybe try this four your installation too, if you can.
