[opensuse] Trying to access IPv6 web page on firefox - revisited
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Back on 2011⁽*⁾ we found that to access my printer web page on firefox, I had to type the link: http:///[FE80::21E:BFF:FE08:4CCB%eth0] But now this doesn't work at all, firefox says "The address isn’t valid". Then what is the correct syntax to reach that address? No, I can not configure an address such as "fc00::3" as I wish, IPv6 is not configurable at all on the printer. I also try to reach "fc00::14" and it doesn't work either. Ping works: cer@Telcontar:~> ping6 fc00::14 PING fc00::14(fc00::14) 56 data bytes 64 bytes from fc00::14: icmp_seq=1 ttl=64 time=0.036 ms 64 bytes from fc00::14: icmp_seq=2 ttl=64 time=0.044 ms ^C cer@Telcontar:~> ping6 "fe80::21e:bff:fe08:4ccb%eth0" PING fe80::21e:bff:fe08:4ccb%eth0(fe80::21e:bff:fe08:4ccb) 56 data bytes 64 bytes from fe80::21e:bff:fe08:4ccb: icmp_seq=1 ttl=64 time=0.709 ms 64 bytes from fe80::21e:bff:fe08:4ccb: icmp_seq=2 ttl=64 time=0.327 ms (1) https://lists.opensuse.org/opensuse/2011-01/msg00165.html - -- Cheers Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlpWKNwACgkQtTMYHG2NR9VvWwCggleXwT3G/wJ/LytajKKwlOsr V8sAniUQTNnav/R29Xm0jRIDslY9UGo3 =8GSE -----END PGP SIGNATURE-----
On Wed, Jan 10, 2018 at 5:53 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
Back on 2011⁽*⁾ we found that to access my printer web page on firefox, I had to type the link:
Apart from the obvious one slash too many - it works (as in - it at least attempts to connect to) if you remove zone indication, at least here on FF ESR 52 on Windows. https://support.mozilla.org/en-US/questions/1111992 Could be workaround of you only have single interface. Probably will not work reliably with multiple interfaces (without explicit route entry for destination). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/10/2018 09:53 AM, Carlos E. R. wrote:
Back on 2011⁽*⁾ we found that to access my printer web page on firefox, I had to type the link:
http:///[FE80::21E:BFF:FE08:4CCB%eth0]
But now this doesn't work at all, firefox says "The address isn’t valid". Then what is the correct syntax to reach that address?
No, I can not configure an address such as "fc00::3" as I wish, IPv6 is not configurable at all on the printer.
I also try to reach "fc00::14" and it doesn't work either.
Firefox does not like link-local IPv6 addresses. I came across the same thing. You have to use global or unique local addresses. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-ID: <alpine.LSU.2.21.1801111335321.21751@Telcontar.valinor> On Wednesday, 2018-01-10 at 10:19 -0500, James Knott wrote:
On 01/10/2018 09:53 AM, Carlos E. R. wrote:
Back on 2011⁽*⁾ we found that to access my printer web page on firefox, I had to type the link:
http:///[FE80::21E:BFF:FE08:4CCB%eth0]
But now this doesn't work at all, firefox says "The address isn’t valid". Then what is the correct syntax to reach that address?
No, I can not configure an address such as "fc00::3" as I wish, IPv6 is not configurable at all on the printer.
I also try to reach "fc00::14" and it doesn't work either.
Firefox does not like link-local IPv6 addresses. I came across the same thing. You have to use global or unique local addresses.
The address can not be changed. IPv6 can not be configured at all in that printer. This works, it is my desktop computer: <http://[fc00::14]/> The issue is that the exact address <http:///[FE80::21E:BFF:FE08:4CCB%eth0]> did work back in 2011. Firefox has changed. It does not matter if I remove the extra slash or the "eth0" part. In fact, when I remove the "%eth0" the link is erased and replaced with "about:blank". Back on 2011 we tried several concoctions here in this mail list and we found that the address had to be surrounded by square brackets because the colons are used already to separate the port number, and eth0 had to be added because those addresses are not routed so the system doesn't know what network interface to use. The link that Andrei suggested doesn't give any more light, except that it doesn't work. - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlpXWh8ACgkQtTMYHG2NR9UlIgCfYPWqOMTYoDrPunS6SUm5gIEu qpIAmgIiPNLd640GsNHujrUrh2qLVWvk =j5eC -----END PGP SIGNATURE-----
On 01/11/2018 07:35 AM, Carlos E. R. wrote:
Content-ID: <alpine.LSU.2.21.1801111335321.21751@Telcontar.valinor>
On Wednesday, 2018-01-10 at 10:19 -0500, James Knott wrote:
On 01/10/2018 09:53 AM, Carlos E. R. wrote:
Back on 2011⁽*⁾ we found that to access my printer web page on firefox, I had to type the link:
http:///[FE80::21E:BFF:FE08:4CCB%eth0]
But now this doesn't work at all, firefox says "The address isn’t valid". Then what is the correct syntax to reach that address?
No, I can not configure an address such as "fc00::3" as I wish, IPv6 is not configurable at all on the printer.
I also try to reach "fc00::14" and it doesn't work either.
Firefox does not like link-local IPv6 addresses. I came across the same thing. You have to use global or unique local addresses.
The address can not be changed. IPv6 can not be configured at all in that printer.
Addresses are normally assigned with SLAAC or DHCPv6. If it has a link local address, either of those should work.
This works, it is my desktop computer: <http://[fc00::14]/>
The issue is that the exact address <http:///[FE80::21E:BFF:FE08:4CCB%eth0]> did work back in 2011. Firefox has changed. It does not matter if I remove the extra slash or the "eth0" part. In fact, when I remove the "%eth0" the link is erased and replaced with "about:blank".
Back on 2011 we tried several concoctions here in this mail list and we found that the address had to be surrounded by square brackets because the colons are used already to separate the port number, and eth0 had to be added because those addresses are not routed so the system doesn't know what network interface to use.
The link that Andrei suggested doesn't give any more light, except that it doesn't work.
I also was able to do it years ago, but no longer can. This is something that changed. I believe similar happens with other browsers. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, Jan 11, 2018 at 4:48 PM, James Knott <james.knott@rogers.com> wrote:
On 01/11/2018 07:35 AM, Carlos E. R. wrote:
The link that Andrei suggested doesn't give any more light, except that it doesn't work.
I also was able to do it years ago, but no longer can. This is something that changed.
The link I suggested contains link to bug report that explains what changed. I would not call it "no more light", but YMMV. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-01-11 15:16, Andrei Borzenkov wrote:
On Thu, Jan 11, 2018 at 4:48 PM, James Knott <james.knott@rogers.com> wrote:
On 01/11/2018 07:35 AM, Carlos E. R. wrote:
The link that Andrei suggested doesn't give any more light, except that it doesn't work.
I also was able to do it years ago, but no longer can. This is something that changed.
The link I suggested contains link to bug report that explains what changed. I would not call it "no more light", but YMMV.
Ah, I didn't go that far. I now did, and I only understand that they are still discussing after six years how they should do it :-( The intentionally disabled the code that implemented this feature for some security problem, about disclosing internal URI information? Something I don't understand. As someone points out, FF asks google about the address at some point before failing on it. I also tried <http:///[FE80::21E:BFF:FE08:4CCB%250]>, if I understood the proposal correctly. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 2018-01-11 14:48, James Knott wrote:
On 01/11/2018 07:35 AM, Carlos E. R. wrote:
The address can not be changed. IPv6 can not be configured at all in that printer.
Addresses are normally assigned with SLAAC or DHCPv6. If it has a link local address, either of those should work.
That's the only address it has, or at least the only one it says it has. Automatic IPv6 address giving doesn't work, at least till Telefónica gives us IPv6 external addresses somehow. On that bugzilla Andrei linked, someone said about another use case: a router that was misconfigured and would not respond on the supposed address, thus trying the hardware fixed address instead, the LL.
This works, it is my desktop computer: <http://[fc00::14]/>
The issue is that the exact address <http:///[FE80::21E:BFF:FE08:4CCB%eth0]> did work back in 2011. Firefox has changed. It does not matter if I remove the extra slash or the "eth0" part. In fact, when I remove the "%eth0" the link is erased and replaced with "about:blank".
Back on 2011 we tried several concoctions here in this mail list and we found that the address had to be surrounded by square brackets because the colons are used already to separate the port number, and eth0 had to be added because those addresses are not routed so the system doesn't know what network interface to use.
The link that Andrei suggested doesn't give any more light, except that it doesn't work.
I also was able to do it years ago, but no longer can. This is something that changed. I believe similar happens with other browsers.
Links, lynx and w3m fail. Seamonkey goes to google. First hit is a post of mine asking about this back on 2011, LOL. "Web" says: unable to display this website". The URL can’t be shown" It may be temporarily unavailable or moved to a new address. You may wish to verify that your internet connection is working correctly." Konqeror says: The requested operation could not be completed Improperly Formatted URL Details of the Request: URL: http:/[FE80::21E:BFF:FE08:4CCB%25eth0] Protocol: http Date and Time: Thursday, January 11, 2018 18:37 Additional Information: http:///[FE80::21E:BFF:FE08:4CCB%eth0] Chrome also does a google search. It finds this conversation as the first hit. Absurd. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 01/11/2018 12:42 PM, Carlos E. R. wrote:
Addresses are normally assigned with SLAAC or DHCPv6. If it has a link
local address, either of those should work. That's the only address it has, or at least the only one it says it has. Automatic IPv6 address giving doesn't work, at least till Telefónica gives us IPv6 external addresses somehow.
Any router capable of supporting IPv6 can provide addresses. You could even set up pfSense in a virtual machine. Also, I believe the ISC DHCP server provided by OpenSUSE supports IPv6. If you want to experiment with IPv6, you really want to use proper addresses. Link local address certainly have their purposes, such as router addresses, etc., but you don't want to work with them if you don't have to.
On that bugzilla Andrei linked, someone said about another use case: a router that was misconfigured and would not respond on the supposed address, thus trying the hardware fixed address instead, the LL.
Routers normally use link local addresses for routing. Of course, management can be done using either. Regardless, this is a browser issue, not OpenSUSE. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-01-11 18:55, James Knott wrote:
On 01/11/2018 12:42 PM, Carlos E. R. wrote:
Addresses are normally assigned with SLAAC or DHCPv6. If it has a link
local address, either of those should work. That's the only address it has, or at least the only one it says it has. Automatic IPv6 address giving doesn't work, at least till Telefónica gives us IPv6 external addresses somehow.
Any router capable of supporting IPv6 can provide addresses.
Well, it doesn't. I switched one machine here to automatic configuration - it is apparently impossible in YaST to have IPv4 manual configuration and IPv6 automatic configuration. Well, it got and IPv4 address, but not an IPv6: Isengard:~ # ifconfig eth0 Link encap:Ethernet HWaddr 4C:CC:6A:61:50:A1 inet addr:192.168.1.134 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::4ecc:6aff:fe61:50a1/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:49550 errors:0 dropped:0 overruns:0 frame:0 TX packets:153739 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:5044374 (4.8 Mb) TX bytes:213100692 (203.2 Mb) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:13923 errors:0 dropped:0 overruns:0 frame:0 TX packets:13923 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:204824646 (195.3 Mb) TX bytes:204824646 (195.3 Mb) Isengard:~ # I also tried: Isengard:~ # dhclient6 -v Internet Systems Consortium DHCP Client 4.3.3 Copyright 2004-2015 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ /sbin/dhclient-script: unable to pre-init requested interface wlan0 /sbin/dhclient-script: unable to pre-init requested interface eth0 /sbin/dhclient-script: unable to pre-init requested interfaces -- see log messages If you think you have received this message due to a bug rather than a configuration issue please read the section on submitting bugs on either our web page at www.isc.org or in the README file before submitting a bug. These pages explain the proper process and the information we find helpful for debugging.. exiting. Isengard:~ # Ah, it conflicts with wicked. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 01/11/2018 01:29 PM, Carlos E. R. wrote:
On 2018-01-11 18:55, James Knott wrote:
On 01/11/2018 12:42 PM, Carlos E. R. wrote:
Addresses are normally assigned with SLAAC or DHCPv6. If it has a link
local address, either of those should work. That's the only address it has, or at least the only one it says it has. Automatic IPv6 address giving doesn't work, at least till Telefónica gives us IPv6 external addresses somehow. Any router capable of supporting IPv6 can provide addresses. Well, it doesn't.
It doesn't have a DHCPv6 server? Can't be configured for SLAAC?
I switched one machine here to automatic configuration - it is apparently impossible in YaST to have IPv4 manual configuration and IPv6 automatic configuration. Well, it got and IPv4 address, but not an IPv6:
Isengard:~ # ifconfig eth0 Link encap:Ethernet HWaddr 4C:CC:6A:61:50:A1 inet addr:192.168.1.134 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::4ecc:6aff:fe61:50a1/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:49550 errors:0 dropped:0 overruns:0 frame:0 TX packets:153739 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:5044374 (4.8 Mb) TX bytes:213100692 (203.2 Mb)
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:13923 errors:0 dropped:0 overruns:0 frame:0 TX packets:13923 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:204824646 (195.3 Mb) TX bytes:204824646 (195.3 Mb)
There is nothing here to say whether it's a manual or some sort of automatic configuration. The fe80 link local shows IPv6 is supported, as does the ::1 loopback address. There is nothing magic here. In this regard, IPv6 is no different than IPv4, other than SLAAC can be used in addition to DHCP or manual configuration. If your router supports providing an IPv6 address via SLAAC or DHCPv6, that printer should have an IPv6 address. If you use either method, then other devices should also get IPv6 addresses. One thing to consider. Windows has something called HomeGroup networking, which requires IPv6 and uses the link local addresses. I assume the printer can work with it. If so, how is the configuration done?
Isengard:~ #
I also tried:
Isengard:~ # dhclient6 -v Internet Systems Consortium DHCP Client 4.3.3 Copyright 2004-2015 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/
/sbin/dhclient-script: unable to pre-init requested interface wlan0 /sbin/dhclient-script: unable to pre-init requested interface eth0 /sbin/dhclient-script: unable to pre-init requested interfaces -- see log messages
If you think you have received this message due to a bug rather than a configuration issue please read the section on submitting bugs on either our web page at www.isc.org or in the README file before submitting a bug. These pages explain the proper process and the information we find helpful for debugging..
exiting. Isengard:~ #
Ah, it conflicts with wicked.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-01-11 20:01, James Knott wrote:
On 01/11/2018 01:29 PM, Carlos E. R. wrote:
On 2018-01-11 18:55, James Knott wrote:
On 01/11/2018 12:42 PM, Carlos E. R. wrote:
Addresses are normally assigned with SLAAC or DHCPv6. If it has a link
local address, either of those should work. That's the only address it has, or at least the only one it says it has. Automatic IPv6 address giving doesn't work, at least till Telefónica gives us IPv6 external addresses somehow. Any router capable of supporting IPv6 can provide addresses. Well, it doesn't.
It doesn't have a DHCPv6 server? Can't be configured for SLAAC?
It only works if it gets an IP on the external port from the provider, and it doesn't. This is the configuration: <http://susepaste.org/56779419> If I change that, I may not notice the day the ISP starts providing IPv6.
I switched one machine here to automatic configuration - it is apparently impossible in YaST to have IPv4 manual configuration and IPv6 automatic configuration. Well, it got and IPv4 address, but not an IPv6:
Isengard:~ # ifconfig eth0 Link encap:Ethernet HWaddr 4C:CC:6A:61:50:A1 inet addr:192.168.1.134 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::4ecc:6aff:fe61:50a1/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:49550 errors:0 dropped:0 overruns:0 frame:0 TX packets:153739 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:5044374 (4.8 Mb) TX bytes:213100692 (203.2 Mb)
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:13923 errors:0 dropped:0 overruns:0 frame:0 TX packets:13923 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:204824646 (195.3 Mb) TX bytes:204824646 (195.3 Mb)
There is nothing here to say whether it's a manual or some sort of automatic configuration. The fe80 link local shows IPv6 is supported, as does the ::1 loopback address.
It is an openSUSE Leap 42.2 machine, configured with YaST to use automatic configuration, so it is using wicked, using whatever method SUSE uses, I don't know which. And the above is what it gets. So either the router is not giving IPv6 addresses (what for, if it can not route them to Internet), or Leap Linux is not getting it.
There is nothing magic here. In this regard, IPv6 is no different than IPv4, other than SLAAC can be used in addition to DHCP or manual configuration. If your router supports providing an IPv6 address via SLAAC or DHCPv6, that printer should have an IPv6 address. If you use either method, then other devices should also get IPv6 addresses.
One thing to consider. Windows has something called HomeGroup networking, which requires IPv6 and uses the link local addresses. I assume the printer can work with it. If so, how is the configuration done?
I've never used that printer with Windows, so I don't know. If I had to use it in Windows I would use IPv4, the same as I use in Linux. The printer configuration page offers IPv4 configuration, but not IPv6. For IPv6 it simply displays the LL address. See: <http://susepaste.org/75790671> <http://susepaste.org/39127759> It is pointless to try configure the router, the printer will only use that fixed IPv6 configuration. On the computers I can manually define an IPv6 fixed address, that's easy. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
12.01.2018 02:21, Carlos E. R. пишет:
On 2018-01-11 20:01, James Knott wrote:
On 01/11/2018 01:29 PM, Carlos E. R. wrote:
On 2018-01-11 18:55, James Knott wrote:
On 01/11/2018 12:42 PM, Carlos E. R. wrote:
Addresses are normally assigned with SLAAC or DHCPv6. If it has a link > local address, either of those should work. That's the only address it has, or at least the only one it says it has. Automatic IPv6 address giving doesn't work, at least till Telefónica gives us IPv6 external addresses somehow. Any router capable of supporting IPv6 can provide addresses. Well, it doesn't.
It doesn't have a DHCPv6 server? Can't be configured for SLAAC?
It only works if it gets an IP on the external port from the provider, and it doesn't.
This is the configuration: <http://susepaste.org/56779419>
You can try enable ULA or add static prefix just to see whether other hosts will pick it up for IPv6 auto-configuration.
If I change that, I may not notice the day the ISP starts providing IPv6.
IPv6 host can have multiple valid addresses with different prefixes. The real problem is that as soon as router starts advertising valid IPv6 prefix it also may start advertising itself as default gateway and this may cause problems. I do not see on this screenshot if it is possible to disable default route advertisement or where is it configured.
I switched one machine here to automatic configuration - it is apparently impossible in YaST to have IPv4 manual configuration and IPv6 automatic configuration. Well, it got and IPv4 address, but not an IPv6:
Isengard:~ # ifconfig eth0 Link encap:Ethernet HWaddr 4C:CC:6A:61:50:A1 inet addr:192.168.1.134 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::4ecc:6aff:fe61:50a1/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:49550 errors:0 dropped:0 overruns:0 frame:0 TX packets:153739 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:5044374 (4.8 Mb) TX bytes:213100692 (203.2 Mb)
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:13923 errors:0 dropped:0 overruns:0 frame:0 TX packets:13923 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:204824646 (195.3 Mb) TX bytes:204824646 (195.3 Mb)
There is nothing here to say whether it's a manual or some sort of automatic configuration. The fe80 link local shows IPv6 is supported, as does the ::1 loopback address.
It is an openSUSE Leap 42.2 machine, configured with YaST to use automatic configuration, so it is using wicked, using whatever method SUSE uses, I don't know which. And the above is what it gets.
So either the router is not giving IPv6 addresses (what for, if it can not route them to Internet), or Leap Linux is not getting it.
More likely router has nothing to advertise.
There is nothing magic here. In this regard, IPv6 is no different than IPv4, other than SLAAC can be used in addition to DHCP or manual configuration. If your router supports providing an IPv6 address via SLAAC or DHCPv6, that printer should have an IPv6 address. If you use either method, then other devices should also get IPv6 addresses.
One thing to consider. Windows has something called HomeGroup networking, which requires IPv6 and uses the link local addresses. I assume the printer can work with it. If so, how is the configuration done?
I've never used that printer with Windows, so I don't know. If I had to use it in Windows I would use IPv4, the same as I use in Linux.
The printer configuration page offers IPv4 configuration, but not IPv6. For IPv6 it simply displays the LL address. See:
<http://susepaste.org/75790671> <http://susepaste.org/39127759>
It is pointless to try configure the router, the printer will only use that fixed IPv6 configuration.
IPv6 hosts are supposed to implement SLAAC, so unless documentation for your printer tells different, I do not see why "it is pointless to configure router". That printer does not support manually defined IPv6 address does not mean it won't do SLAAC when available.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2018-01-12 at 06:46 +0300, Andrei Borzenkov wrote:
12.01.2018 02:21, Carlos E. R. пишет:
This is the configuration: <http://susepaste.org/56779419>
You can try enable ULA or add static prefix just to see whether other hosts will pick it up for IPv6 auto-configuration.
I have no idea what to set on my router page to do that. I configured the wlan interface of my little home server to automatic configuration on IPv6 only (dhcp6). I also wrote in the router: LAN IPv6 Link-Local Address Configuration ( ) EUI-64 (*) User Setting Interface Identifier: [0:0:0:1] (see photo of router at susepaste) But I get nothing on that wlan0 when restarted. I gather I must fill this field: Static LAN IPv6 Address Configuration Interface Address (prefix length is required): [______] I wrote there "fc00::/64", applied, and restarted network on machine. Still, no go: wlan0 Link encap:Ethernet HWaddr A0:D3:7A:82:B3:4C inet6 addr: fe80::a2d3:7aff:fe82:b34c/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:615 errors:0 dropped:0 overruns:0 frame:0 TX packets:85 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:50765 (49.5 Kb) TX bytes:20160 (19.6 Kb) <0.6> 2018-01-12T22:19:04.807116+01:00 Isengard kernel - - - [98419.957660] r8169 0000:03:00.0 eth0: link down <0.6> 2018-01-12T22:19:04.807143+01:00 Isengard kernel - - - [98419.957728] r8169 0000:03:00.0 eth0: link down <0.6> 2018-01-12T22:19:04.807146+01:00 Isengard kernel - - - [98419.957812] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready <0.6> 2018-01-12T22:19:04.811107+01:00 Isengard kernel - - - [98419.960846] iwlwifi 0000:01:00.0: L1 Disabled - LTR Enabled <0.6> 2018-01-12T22:19:04.811139+01:00 Isengard kernel - - - [98419.961105] iwlwifi 0000:01:00.0: L1 Disabled - LTR Enabled <0.6> 2018-01-12T22:19:04.927096+01:00 Isengard kernel - - - [98420.079026] iwlwifi 0000:01:00.0: L1 Disabled - LTR Enabled <0.6> 2018-01-12T22:19:04.931104+01:00 Isengard kernel - - - [98420.079299] iwlwifi 0000:01:00.0: L1 Disabled - LTR Enabled <0.6> 2018-01-12T22:19:04.943081+01:00 Isengard kernel - - - [98420.093248] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready <0.6> 2018-01-12T22:19:07.139117+01:00 Isengard kernel - - - [98422.289336] r8169 0000:03:00.0 eth0: link up <0.6> 2018-01-12T22:19:07.139151+01:00 Isengard kernel - - - [98422.289352] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready <3.6> 2018-01-12T22:19:08.228153+01:00 Isengard avahi-daemon 1138 - - Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.16. <3.6> 2018-01-12T22:19:08.228872+01:00 Isengard avahi-daemon 1138 - - New relevant interface eth0.IPv4 for mDNS. <3.6> 2018-01-12T22:19:08.229417+01:00 Isengard avahi-daemon 1138 - - Registering new address record for 192.168.1.16 on eth0.IPv4. <3.6> 2018-01-12T22:19:08.371382+01:00 Isengard wpa_supplicant 9985 - - ioctl[SIOCSIWFREQ]: Device or resource busy <0.6> 2018-01-12T22:19:08.375486+01:00 Isengard kernel - - - [98423.523611] wlan0: authenticate with 70:8b:cd:59:88:3c <0.6> 2018-01-12T22:19:08.375521+01:00 Isengard kernel - - - [98423.526658] wlan0: send auth to 70:8b:cd:59:88:3c (try 1/3) <0.6> 2018-01-12T22:19:08.379167+01:00 Isengard kernel - - - [98423.528561] wlan0: authenticated <0.6> 2018-01-12T22:19:08.379202+01:00 Isengard kernel - - - [98423.531470] wlan0: associate with 70:8b:cd:59:88:3c (try 1/3) <0.6> 2018-01-12T22:19:08.383085+01:00 Isengard kernel - - - [98423.535257] wlan0: RX AssocResp from 70:8b:cd:59:88:3c (capab=0x411 status=0 aid=2) <0.6> 2018-01-12T22:19:08.387088+01:00 Isengard kernel - - - [98423.536853] wlan0: associated <0.6> 2018-01-12T22:19:08.387111+01:00 Isengard kernel - - - [98423.536932] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready <3.5> 2018-01-12T22:19:08.389506+01:00 Isengard wickedd-dhcp6 1283 - - wlan0: Request to acquire DHCPv6 lease with UUID 0da6575a-5890-0d00-0f05-000030000000 in mode auto <3.6> 2018-01-12T22:19:08.603621+01:00 Isengard avahi-daemon 1138 - - Joining mDNS multicast group on interface eth0.IPv6 with address fe80::4ecc:6aff:fe61:50a1. <3.6> 2018-01-12T22:19:08.604275+01:00 Isengard avahi-daemon 1138 - - New relevant interface eth0.IPv6 for mDNS. <3.6> 2018-01-12T22:19:08.604803+01:00 Isengard avahi-daemon 1138 - - Registering new address record for fe80::4ecc:6aff:fe61:50a1 on eth0.*. <3.6> 2018-01-12T22:19:09.967505+01:00 Isengard avahi-daemon 1138 - - Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::a2d3:7aff:fe82:b34c. <3.6> 2018-01-12T22:19:09.973088+01:00 Isengard avahi-daemon 1138 - - New relevant interface wlan0.IPv6 for mDNS. <3.6> 2018-01-12T22:19:09.973753+01:00 Isengard avahi-daemon 1138 - - Registering new address record for fe80::a2d3:7aff:fe82:b34c on wlan0.*. <0.4> 2018-01-12T22:19:16.627091+01:00 Isengard kernel - - - [98431.778457] IPv4: martian source 192.168.1.255 from 192.168.1.16, on dev wlan0 <0.4> 2018-01-12T22:19:16.627120+01:00 Isengard kernel - - - [98431.778468] ll header: 00000000: ff ff ff ff ff ff 4c cc 6a 61 50 a1 08 00 ......L.jaP... <3.6> 2018-01-12T22:19:34.734983+01:00 Isengard wicked 20327 - - lo up <3.6> 2018-01-12T22:19:34.736025+01:00 Isengard wicked 20327 - - eth0 up <3.6> 2018-01-12T22:19:34.736518+01:00 Isengard wicked 20327 - - wlan0 setup-in-progress <3.6> 2018-01-12T22:19:34.736981+01:00 Isengard systemd 1 - - Started wicked managed network interfaces. <0.4> 2018-01-12T22:20:00.943152+01:00 Isengard kernel - - - [98476.096549] IPv4: martian source 192.168.1.255 from 192.168.1.16, on dev wlan0 <0.4> 2018-01-12T22:20:00.943182+01:00 Isengard kernel - - - [98476.096559] ll header: 00000000: ff ff ff ff ff ff 4c cc 6a 61 50 a1 08 00 ......L.jaP... <10.6> 2018-01-12T22:20:01.530573+01:00 Isengard cron 20821 - - pam_unix(crond:session): session opened for user root by (uid=0) <3.6> 2018-01-12T22:20:01.556075+01:00 Isengard systemd 1 - - Started Session 557 of user root. <0.4> 2018-01-12T22:20:02.787088+01:00 Isengard kernel - - - [98477.941910] IPv4: martian source 192.168.1.255 from 192.168.1.16, on dev wlan0 <0.4> 2018-01-12T22:20:02.787119+01:00 Isengard kernel - - - [98477.941920] ll header: 00000000: ff ff ff ff ff ff 4c cc 6a 61 50 a1 08 00 ......L.jaP... <0.4> 2018-01-12T22:20:02.787121+01:00 Isengard kernel - - - [98477.943238] IPv4: martian source 192.168.1.255 from 192.168.1.16, on dev wlan0 <0.4> 2018-01-12T22:20:02.787123+01:00 Isengard kernel - - - [98477.943271] ll header: 00000000: ff ff ff ff ff ff 4c cc 6a 61 50 a1 08 00 ......L.jaP... <10.6> 2018-01-12T22:20:03.795605+01:00 Isengard CRON 20821 - - pam_unix(crond:session): session closed for user root <0.4> 2018-01-12T22:20:04.939090+01:00 Isengard kernel - - - [98480.093727] IPv4: martian source 192.168.1.255 from 192.168.1.16, on dev wlan0 <0.4> 2018-01-12T22:20:04.939119+01:00 Isengard kernel - - - [98480.093736] ll header: 00000000: ff ff ff ff ff ff 4c cc 6a 61 50 a1 08 00 ......L.jaP... Notice the martians on wlan on IPv4, despite being configured for IPv6 only. And it doesn't get an IPv6 address.
If I change that, I may not notice the day the ISP starts providing IPv6.
IPv6 host can have multiple valid addresses with different prefixes.
Yes...
The real problem is that as soon as router starts advertising valid IPv6 prefix it also may start advertising itself as default gateway and this may cause problems. I do not see on this screenshot if it is possible to disable default route advertisement or where is it configured.
I don't remember seeing that option, no. ...
SLAAC or DHCPv6, that printer should have an IPv6 address. If you use either method, then other devices should also get IPv6 addresses.
One thing to consider. Windows has something called HomeGroup networking, which requires IPv6 and uses the link local addresses. I assume the printer can work with it. If so, how is the configuration done?
I've never used that printer with Windows, so I don't know. If I had to use it in Windows I would use IPv4, the same as I use in Linux.
The printer configuration page offers IPv4 configuration, but not IPv6. For IPv6 it simply displays the LL address. See:
<http://susepaste.org/75790671> <http://susepaste.org/39127759>
It is pointless to try configure the router, the printer will only use that fixed IPv6 configuration.
IPv6 hosts are supposed to implement SLAAC, so unless documentation for your printer tells different, I do not see why "it is pointless to configure router". That printer does not support manually defined IPv6 address does not mean it won't do SLAAC when available.
Ah. Well... :-? I don't know. - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlpZKaEACgkQtTMYHG2NR9VZuACgjXZPRouQLUGf9kGBwCx7cs+c QaAAnA6aJnXXHjdCRJIGnVQOa95K/FLh =ShUQ -----END PGP SIGNATURE-----
On 01/12/2018 04:33 PM, Carlos E. R. wrote:
I configured the wlan interface of my little home server to automatic configuration on IPv6 only (dhcp6). I also wrote in the router:
LAN IPv6 Link-Local Address Configuration ( ) EUI-64 (*) User Setting Interface Identifier: [0:0:0:1]
(see photo of router at susepaste)
But I get nothing on that wlan0 when restarted. I gather I must fill this field:
Static LAN IPv6 Address Configuration Interface Address (prefix length is required): [______]
I wrote there "fc00::/64", applied, and restarted network on machine. Still, no go:
As I said before, you need some method of providing those automatic addresses. The usual way is with SLAAC, though DHCPv6 can also be used. You need one or the other. What would you do on IPv4? You'd set up DHCP. With IPv6, you use SLAAC or perhaps DHCPv6. https://en.wikipedia.org/wiki/IPv6#Stateless_address_autoconfiguration_.28SL... I don't know what you're using for a router, but I use pfSense and it works well. I used to use OpenSUSE as a firewall/router and it also worked well, when I had a 6in4 tunnel. With IPv6, routers use something called router advertisements to announce the network prefix, default route, DHCP, etc.. If you don't have RAs, nothing will happen. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-01-12 22:43, James Knott wrote:
On 01/12/2018 04:33 PM, Carlos E. R. wrote:
I configured the wlan interface of my little home server to automatic configuration on IPv6 only (dhcp6). I also wrote in the router:
LAN IPv6 Link-Local Address Configuration ( ) EUI-64 (*) User Setting Interface Identifier: [0:0:0:1]
(see photo of router at susepaste)
But I get nothing on that wlan0 when restarted. I gather I must fill this field:
Static LAN IPv6 Address Configuration Interface Address (prefix length is required): [______]
I wrote there "fc00::/64", applied, and restarted network on machine. Still, no go:
As I said before, you need some method of providing those automatic addresses. The usual way is with SLAAC, though DHCPv6 can also be used. You need one or the other. What would you do on IPv4? You'd set up DHCP. With IPv6, you use SLAAC or perhaps DHCPv6. https://en.wikipedia.org/wiki/IPv6#Stateless_address_autoconfiguration_.28SL...
I'm trying to do it with the router as is. I have no idea what the router does.
I don't know what you're using for a router, but I use pfSense and it works well. I used to use OpenSUSE as a firewall/router and it also worked well, when I had a 6in4 tunnel.
It is a commercial router installed by my ISP and can not be changed. Comtrend VG-8050
With IPv6, routers use something called router advertisements to announce the network prefix, default route, DHCP, etc.. If you don't have RAs, nothing will happen.
I have what I posted on the photo: <http://susepaste.org/56779419> And no, I don't know what it all means or does. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
With IPv6, routers use something called router advertisements to announce the network prefix, default route, DHCP, etc.. If you don't have RAs, nothing will happen. I have what I posted on the photo: <http://susepaste.org/56779419>
And no, I don't know what it all means or does. Well, I see DHCPv6 and RADVD settings there and they appear to show normal operation. Stateless DHCPv6 means it is not used to provide addresses, but can provide addresses for servers, such as DNS. RADVD is enabled. I don't know why the preference is low, though. Based on what I see there, it should be providing IPv6 addresses, assuming the ISP does. I see it also can provide Unique Local Addresses (ULA). This is
On 01/12/2018 05:07 PM, Carlos E. R. wrote: the IPv6 equivalent of IPv4 RFC 1918 addresses. You could enable that to provide usable IPv6 addresses, though they won't connect to the Internet. With ULA, you choose a prefix starting with fc00 and add another 40 bits. The idea is to use some random means to generate those 40 bits. I see it can also automagically pick a random prefix. So, enable ULA prefix Advertisement and select either random or static, to create your ULA prefix. Once that's all done, your devices should have an IPv6 address. Incidentally, one thing I don't see, which is available with pfSense, is the means to have multiple networks. I have a /56 prefix from my ISP, which gives me 256 /64 prefixes, to assign to various networks. This would imply you only get a single /64. The same applies with my ISP, if I used their router. With the modem in bridge mode, I get the /56. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
13.01.2018 00:33, Carlos E. R. пишет:
On Friday, 2018-01-12 at 06:46 +0300, Andrei Borzenkov wrote:
12.01.2018 02:21, Carlos E. R. пишет:
This is the configuration: <http://susepaste.org/56779419>
You can try enable ULA or add static prefix just to see whether other hosts will pick it up for IPv6 auto-configuration.
I have no idea what to set on my router page to do that.
It has checkbox "Enable ULA Prefix Advertisement" ... and it has table with column heading "Static Prefix" and "Add" button ... and you are sitting before this box and can experiment.
I configured the wlan interface of my little home server to automatic configuration on IPv6 only (dhcp6). I also wrote in the router:
LAN IPv6 Link-Local Address Configuration ( ) EUI-64 (*) User Setting Interface Identifier: [0:0:0:1]
That looks like router own interface IPv6 address.
(see photo of router at susepaste)
But I get nothing on that wlan0 when restarted. I gather I must fill this field:
Static LAN IPv6 Address Configuration Interface Address (prefix length is required): [______]
Which again looks like router own interface IPv6 address.
I wrote there "fc00::/64", applied, and restarted network on machine. Still, no go:
... You did not change anything related to client configuration, why you expect any change on client?
On 01/11/2018 06:21 PM, Carlos E. R. wrote:
The printer configuration page offers IPv4 configuration, but not IPv6. For IPv6 it simply displays the LL address. See:
<http://susepaste.org/75790671> <http://susepaste.org/39127759>
It is pointless to try configure the router, the printer will only use that fixed IPv6 configuration. On the computers I can manually define an IPv6 fixed address, that's easy.
I guess you'll have to use IPv4, until Firefox fixes the browser. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
On 2018-01-11 20:01, James Knott wrote:
On 01/11/2018 01:29 PM, Carlos E. R. wrote:
On 2018-01-11 18:55, James Knott wrote:
On 01/11/2018 12:42 PM, Carlos E. R. wrote:
Addresses are normally assigned with SLAAC or DHCPv6. If it has a link > local address, either of those should work. That's the only address it has, or at least the only one it says it has. Automatic IPv6 address giving doesn't work, at least till Telefónica gives us IPv6 external addresses somehow. Any router capable of supporting IPv6 can provide addresses. Well, it doesn't.
It doesn't have a DHCPv6 server? Can't be configured for SLAAC?
It only works if it gets an IP on the external port from the provider, and it doesn't.
This is the configuration: <http://susepaste.org/56779419>
If I change that, I may not notice the day the ISP starts providing IPv6.
I would suggest you set up your radvd on a local machine and let it issue an address, but _only_ for your printer - for radvd.conf: clients { FE80::21E:BFF:FE08:4CCB; } If your provider should ever decide to begin using IPv6, your printer might have problems, but then you'll know anyway. -- Per Jessen, Zürich (3.9°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/12/2018 08:28 AM, Per Jessen wrote:
If your provider should ever decide to begin using IPv6, your printer might have problems, but then you'll know anyway.
Why would the printer have problems? I don't expect a printer to be communicating off the local network in a home environment. So, default route is not an issue. Also, when the ISP provides IPv6, then this fix will no longer be required. BTW, he can also get IPv6 via 6in4 tunnel from he.net. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 01/12/2018 08:28 AM, Per Jessen wrote:
If your provider should ever decide to begin using IPv6, your printer might have problems, but then you'll know anyway.
Why would the printer have problems? I don't expect a printer to be communicating off the local network in a home environment. So, default route is not an issue.
I hadn't thought it through, I was just wondering about what might happen with two radvds running. You're right, he doesn't need the default route, so that could be switched off in the local radvd: prefix 2001:db8::/64 { AdvOnLink on; AdvAutonomous on; AdvRouterAddr off; };
Also, when the ISP provides IPv6, then this fix will no longer be required.
Of course, but Carlos was worried about not finding out if/when his ISP starts to offer IPv6.
BTW, he can also get IPv6 via 6in4 tunnel from he.net.
According to wikipedia in Europe only in 8 countries. It doesn't say if Spain is included, but it seems odd - why would they limit it to specific countries?? -- Per Jessen, Zürich (4.1°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/12/2018 09:00 AM, Per Jessen wrote:
BTW, he can also get IPv6 via 6in4 tunnel from he.net. According to wikipedia in Europe only in 8 countries. It doesn't say if Spain is included, but it seems odd - why would they limit it to specific countries??
I had not heard that. Here's what I found on Wikipedia: "Hurricane Electric offers an IPv6 tunnel broker service,[3] providing free connectivity to the IPv6 Internet via 6-in-4 IPv6 transition mechanisms. The company also provides an IPv6 certification program to further education and compliance in IPv6 technology.[4][5] According to Hurricane Electric's statistics, as of January 19, 2015, the company provided 80,487 tunnels spanning 169 countries[6] via the IPv6 tunnel broker and 10,383 individuals have reached the highest level of the IPv6 certification." https://en.wikipedia.org/wiki/Hurricane_Electric However, their server list shows only 8 countries, but that doesn't mean they can't be used from elsewhere. https://www.tunnelbroker.net/status.php And this shows over 1000 tunnel users in Spain. https://tunnelbroker.net/usage/tunnels_by_country.php So, perhaps he could use the tunnel servers in France or Portugal. Incidentally, the tunnel broker I used to use had tunnel servers in other parts of the world and I could connect through them, but I normally used the one in Montreal. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 01/12/2018 09:00 AM, Per Jessen wrote:
BTW, he can also get IPv6 via 6in4 tunnel from he.net. According to wikipedia in Europe only in 8 countries. It doesn't say if Spain is included, but it seems odd - why would they limit it to specific countries??
I had not heard that. Here's what I found on Wikipedia:
"Hurricane Electric offers an IPv6 tunnel broker service,[3] providing free connectivity to the IPv6 Internet via 6-in-4 IPv6 transition mechanisms. The company also provides an IPv6 certification program to further education and compliance in IPv6 technology.[4][5] According to Hurricane Electric's statistics, as of January 19, 2015, the company provided 80,487 tunnels spanning 169 countries[6] via the IPv6 tunnel broker and 10,383 individuals have reached the highest level of the IPv6 certification." https://en.wikipedia.org/wiki/Hurricane_Electric
However, their server list shows only 8 countries, but that doesn't mean they can't be used from elsewhere. https://www.tunnelbroker.net/status.php
Right. I think the authors of the wikipedia articles may have misunderstood: https://en.wikipedia.org/wiki/List_of_IPv6_tunnel_brokers https://de.wikipedia.org/wiki/Liste_von_IPv6-Tunnelbrokern For Hurricane Electric: "Locations: Canada, Europe (9 Countries), Hong Kong, Japan, Singapore, United States (11 States), South Africa" Seems a little silly to list 8 POPs when it doesn't matter much. I thought I also had my first tunnel with HE, but it was someone called Dolphins (now iWay) - in October 2006. -- Per Jessen, Zürich (4.0°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Andrei Borzenkov -
Carlos E. R. -
James Knott -
Per Jessen