I don't know much about ssh, networking and so on, just enough to have got ssh working on ipv4 between various machines both on my LAN and remotely. Now I'm wanting to try and convert everything to ipv6, since my home ISP has switched to ipv6 by default and in theory it should be simpler overall, but info when googling is limited and outdated. I've had some success already but need more info. 1) I don't fully understand how ipv6 addresses get dished out. I can see, having now set up connections on three machines on my LAN, that one address seems to be the permanent one, chosen automatically for connections, although with one PC it initially chose a different address and settled on that other one later. After looking at info in <ip a> on two machines, the address that I suppose to be the 'main' or permanent one has different things appended. On my old laptop the main one has a /128 suffix followed by 'scope global dynamic'. On my new laptop it has a /64 suffix followed by 'scope global mngtmpaddr noprefixroute dynamic'. Does 'mngtmpaddr' imply it's only temporary? 2) The machine I administer remotely in another country is connected to an ISP that provides a dynamic IP, which has caused me headaches trying to find a method of automatically obtaining the new address each time it changes. If I change over to an ipv6 connection, will they still issue a dynamic address? (I don't know if the dynamic IP is a means to conserving limited ipv4 addresses or if it serves other purposes). 3) I can ssh within my LAN using the link-local address in the console, though I find it much faster and preferable to use a graphical interface and can't find how to make Dolphin accept this address in the 'Network Folder Wizard' dialog. It must need the interface specifying but no matter how I write out the string (%eth0, square brackets, quotes, backslash escapes, etc.) it doesn't accept it. 4) If I ssh to another machine on the LAN but using the afore-mentioned 'global' main address, does this go outside of my LAN, i.e. if I'm only using PAM authentication is there a risk of this being intercepted? Cheers, gumb -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-08-10 07:18 AM, gumb wrote:
I don't know much about ssh, networking and so on, just enough to have got ssh working on ipv4 between various machines both on my LAN and remotely. Now I'm wanting to try and convert everything to ipv6, since my home ISP has switched to ipv6 by default and in theory it should be simpler overall, but info when googling is limited and outdated. I've had some success already but need more info.
1) I don't fully understand how ipv6 addresses get dished out. I can see, having now set up connections on three machines on my LAN, that one address seems to be the permanent one, chosen automatically for connections, although with one PC it initially chose a different address and settled on that other one later. After looking at info in <ip a> on two machines, the address that I suppose to be the 'main' or permanent one has different things appended. On my old laptop the main one has a /128 suffix followed by 'scope global dynamic'. On my new laptop it has a /64 suffix followed by 'scope global mngtmpaddr noprefixroute dynamic'. Does 'mngtmpaddr' imply it's only temporary?
With IPv6, there are something called privacy addresses. These are based on a random number and you get a new one every day, with old ones falling off after a week. You should also have one permanent address, which can be based on the MAC address or a random number. This is the address you'd use when trying to connect to that computer. The privacy addresses are used for outgoing connections. There will also be a link local address, which starts with fe80. The link local address is typically used for things like router advertisements, default gateway and more, but generally you don't used them for connecting to a computer. A /64 means you're on a LAN, with the first 64 bits corresponding to the network prefix and the other 64 bits identifying the device on the LAN. A /128 is used identify a device and is used when connecting, but you can't connect directly to it. Traffic is actually routed to it, from another address. This is common on routers. If you have a point to point connection, you would have a /127 address.
2) The machine I administer remotely in another country is connected to an ISP that provides a dynamic IP, which has caused me headaches trying to find a method of automatically obtaining the new address each time it changes. If I change over to an ipv6 connection, will they still issue a dynamic address? (I don't know if the dynamic IP is a means to conserving limited ipv4 addresses or if it serves other purposes).
With IPv6, you'd normally have a consistent network prefix. This means you'd use the permanent address as your target, to configure DNS for etc. You would not use the privacy addresses for this.
3) I can ssh within my LAN using the link-local address in the console, though I find it much faster and preferable to use a graphical interface and can't find how to make Dolphin accept this address in the 'Network Folder Wizard' dialog. It must need the interface specifying but no matter how I write out the string (%eth0, square brackets, quotes, backslash escapes, etc.) it doesn't accept it.
That is not the intended purpose of a link local address as you also have to provide the interface ID to use it.
4) If I ssh to another machine on the LAN but using the afore-mentioned 'global' main address, does this go outside of my LAN, i.e. if I'm only using PAM authentication is there a risk of this being intercepted?
If it's on the LAN, it does not go through the router. This is exactly the same as with IPv4. When a device has a packet to send, it compares it's own address, the destination address and the prefix or subnet mask, to determine if the destination is on the local LAN. If it is, it uses neighbor solicitation on IPv6 or ARP on IPv4, to obtain the MAC address to send the packet to. If it determines the destination is elsewhere, it sends the packet to the router, using the routers's MAC address. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/08/2019 14:00, James Knott wrote:
With IPv6, there are something called privacy addresses. These are based on a random number and you get a new one every day, with old ones falling off after a week. You should also have one permanent address, which can be based on the MAC address or a random number. This is the address you'd use when trying to connect to that computer. The privacy addresses are used for outgoing connections. There will also be a link local address, which starts with fe80. The link local address is typically used for things like router advertisements, default gateway and more, but generally you don't used them for connecting to a computer.
A /64 means you're on a LAN, with the first 64 bits corresponding to the network prefix and the other 64 bits identifying the device on the LAN. A /128 is used identify a device and is used when connecting, but you can't connect directly to it. Traffic is actually routed to it, from another address. This is common on routers. If you have a point to point connection, you would have a /127 address.
<snip>
With IPv6, you'd normally have a consistent network prefix. This means you'd use the permanent address as your target, to configure DNS for etc. You would not use the privacy addresses for this.
<snip>
That is not the intended purpose of a link local address as you also have to provide the interface ID to use it.
<snip>
If it's on the LAN, it does not go through the router. This is exactly the same as with IPv4. When a device has a packet to send, it compares it's own address, the destination address and the prefix or subnet mask, to determine if the destination is on the local LAN. If it is, it uses neighbor solicitation on IPv6 or ARP on IPv4, to obtain the MAC address to send the packet to. If it determines the destination is elsewhere, it sends the packet to the router, using the routers's MAC address.
Thanks for the details. I'm a bit overloaded with too many things to deal with at once before I return abroad on Tuesday and set about trying to configure the remote machine. Sometime over the next couple of weeks I'll likely come back to demand more questions. In the meantime, this thread elsewhere seems to have uncorked a proverbial can of worms the size of a small city, and I have to switch off or I'll drown. Cheers, gumb -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
gumb wrote:
In the meantime, this thread elsewhere seems to have uncorked a proverbial can of worms the size of a small city, and I have to switch off or I'll drown.
Don't worry, it is largely irrelevant. -- Per Jessen, Zürich (18.8°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* gumb <gumb@linuxmail.org> [08-10-19 07:20]: [...]
2) The machine I administer remotely in another country is connected to an ISP that provides a dynamic IP, which has caused me headaches trying to find a method of automatically obtaining the new address each time it changes. If I change over to an ipv6 connection, will they still issue a dynamic address? (I don't know if the dynamic IP is a means to conserving limited ipv4 addresses or if it serves other purposes).
write a script for the remote box to email you when ip addr changes with new ip addr. I did this but didn't need to email the new ip addr as it was in the email header. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/08/2019 14:30, Patrick Shanahan wrote:
* gumb <gumb@linuxmail.org> [08-10-19 07:20]: [...]
2) The machine I administer remotely in another country is connected to an ISP that provides a dynamic IP, which has caused me headaches trying to find a method of automatically obtaining the new address each time it changes. If I change over to an ipv6 connection, will they still issue a dynamic address? (I don't know if the dynamic IP is a means to conserving limited ipv4 addresses or if it serves other purposes).
write a script for the remote box to email you when ip addr changes with new ip addr. I did this but didn't need to email the new ip addr as it was in the email header.
I asked about this before, but it ended with a debate between other users about which mailing application needs to be used and how it should be configured. It was all too much for me to understand and not as simple as I'd assumed. But yes, I can extract the address from emails sent by the user of that machine. Probably it would be easier, since Thunderbird is already used, to see if there's some add-on or script that will just send out mails on a regular basis, and I can look up the address in the header. gumb -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
gumb wrote:
On 10/08/2019 14:30, Patrick Shanahan wrote:
* gumb <gumb@linuxmail.org> [08-10-19 07:20]: [...]
2) The machine I administer remotely in another country is connected to an ISP that provides a dynamic IP, which has caused me headaches trying to find a method of automatically obtaining the new address each time it changes. If I change over to an ipv6 connection, will they still issue a dynamic address? (I don't know if the dynamic IP is a means to conserving limited ipv4 addresses or if it serves other purposes).
write a script for the remote box to email you when ip addr changes with new ip addr. I did this but didn't need to email the new ip addr as it was in the email header.
I asked about this before, but it ended with a debate between other users about which mailing application needs to be used and how it should be configured. It was all too much for me to understand and not as simple as I'd assumed.
Overall it really _is_ simple - use a dynamic DNS service. Or if you don't care about the name, maybe use an ssh tunnel, initiated from the other side. -- Per Jessen, Zürich (20.6°C) http://www.dns24.ch/ - dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-08-10 09:57 AM, Per Jessen wrote:
Or if you don't care about the name, maybe use an ssh tunnel, initiated from the other side.
https://en.wikipedia.org/wiki/The_Othersiders ;-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
gumb wrote:
2) The machine I administer remotely in another country is connected to an ISP that provides a dynamic IP, which has caused me headaches trying to find a method of automatically obtaining the new address each time it changes. If I change over to an ipv6 connection, will they still issue a dynamic address?
Most likely, yes. It might never change, but it'll still be a dynamic address :-) Automatically obtaining the external address shouldn't be difficult, but it depends on what you have running on that machine.
(I don't know if the dynamic IP is a means to conserving limited ipv4 addresses or if it serves other purposes).
Overall, it means nopt having to manage the pool of addresses. For IPv4, it is also due to the shortage of addresses. -- Per Jessen, Zürich (19.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 2019-08-10 08:48 AM, Per Jessen wrote:
gumb wrote:
2) The machine I administer remotely in another country is connected to an ISP that provides a dynamic IP, which has caused me headaches trying to find a method of automatically obtaining the new address each time it changes. If I change over to an ipv6 connection, will they still issue a dynamic address? Most likely, yes. It might never change, but it'll still be a dynamic address :-)
Automatically obtaining the external address shouldn't be difficult, but it depends on what you have running on that machine.
IPv6 uses something called "DUID" which is used to ensure you get the same prefix. That, combined with the consistent address (not privacy) means you can use DNS or even the hosts file, to provide the address for a connection. https://en.wikipedia.org/wiki/DHCPv6#DHCP_Unique_Identifier -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 2019-08-10 08:48 AM, Per Jessen wrote:
gumb wrote:
2) The machine I administer remotely in another country is connected to an ISP that provides a dynamic IP, which has caused me headaches trying to find a method of automatically obtaining the new address each time it changes. If I change over to an ipv6 connection, will they still issue a dynamic address? Most likely, yes. It might never change, but it'll still be a dynamic address :-)
Automatically obtaining the external address shouldn't be difficult, but it depends on what you have running on that machine.
IPv6 uses something called "DUID"
Oh yeah, I know. A pain in the behind that is :-) I wish I could use plain MAC's for the DHCP config file.
which is used to ensure you get the same prefix.
afaik, there is no guarantee, although a provider's ipv6 range is so huge that reuse will likely never happen. RIPE hands out /28 by default I think and the minimum is a /32. -- Per Jessen, Zürich (20.1°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-08-10 09:30 AM, Per Jessen wrote:
which is used to ensure you get the same prefix. afaik, there is no guarantee, although a provider's ipv6 range is so huge that reuse will likely never happen. RIPE hands out /28 by default I think and the minimum is a /32.
I have DHCP from my ISP on IPv4. The addresses change so seldom they're virtually static. The only thing that appears to cause a change is either the ISP makes significant changes in the network or I change hardware, resulting in a new lease. The host name, based on my router and modem MAC addresses never changes, unless I change hardware. So, on the rare occasion that it changes, I just update my DNS. I'd expect the same situation on IPv6. The address changes so seldom, it's not an issue. Now, if I was running a business, with customers coming to my web site, then it might be a different matter. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 2019-08-10 09:30 AM, Per Jessen wrote:
which is used to ensure you get the same prefix. afaik, there is no guarantee, although a provider's ipv6 range is so huge that reuse will likely never happen. RIPE hands out /28 by default I think and the minimum is a /32.
I have DHCP from my ISP on IPv4. The addresses change so seldom they're virtually static. The only thing that appears to cause a change is either the ISP makes significant changes in the network or I change hardware, resulting in a new lease.
Your provider probably has a sufficiently big range to permit that "virtually static" allocation. That's not always the case around here, even with the two-three bigger providers. Our dynamic DNS service is quite popular - http://www.dns24.ch. -- Per Jessen, Zürich (20.6°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-08-10 09:54 AM, Per Jessen wrote:
Your provider probably has a sufficiently big range to permit that "virtually static" allocation. That's not always the case around here, even with the two-three bigger providers. Our dynamic DNS service is quite popular - http://www.dns24.ch.
With DHCP, the address should not change, so long as it's renewed within the lease time. So, if your firewall/router is always up & connected, then the address shouldn't change. If it does, it's your ISP being nasty. Doing that will not save any addresses, as they still have to provide one. All it does is annoy customers. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 2019-08-10 09:54 AM, Per Jessen wrote:
Your provider probably has a sufficiently big range to permit that "virtually static" allocation. That's not always the case around here, even with the two-three bigger providers. Our dynamic DNS service is quite popular - http://www.dns24.ch.
With DHCP, the address should not change, so long as it's renewed within the lease time. So, if your firewall/router is always up & connected, then the address shouldn't change.
As usualy, it depends. One of my dynamic DNS customers has a host that had 8 different addresses in the last 30 days. Other hosts (he was some 20-odd) remained static for the last 30 days, but had 131 different addresses since 1 January. I don't know if a mobile connection is always 'on' ? -- Per Jessen, Zürich (20.8°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 10/08/2019 13.18, gumb wrote:
I don't know much about ssh, networking and so on, just enough to have got ssh working on ipv4 between various machines both on my LAN and remotely. Now I'm wanting to try and convert everything to ipv6, since my home ISP has switched to ipv6 by default and in theory it should be simpler overall, but info when googling is limited and outdated. I've had some success already but need more info.
1) I don't fully understand how ipv6 addresses get dished out. I can see, having now set up connections on three machines on my LAN, that one address seems to be the permanent one, chosen automatically for connections, although with one PC it initially chose a different address and settled on that other one later. After looking at info in <ip a> on two machines, the address that I suppose to be the 'main' or permanent one has different things appended. On my old laptop the main one has a /128 suffix followed by 'scope global dynamic'. On my new laptop it has a /64 suffix followed by 'scope global mngtmpaddr noprefixroute dynamic'. Does 'mngtmpaddr' imply it's only temporary?
So Say We All: I do not know :-p
2) The machine I administer remotely in another country is connected to an ISP that provides a dynamic IP, which has caused me headaches trying to find a method of automatically obtaining the new address each time it changes. If I change over to an ipv6 connection, will they still issue a dynamic address? (I don't know if the dynamic IP is a means to conserving limited ipv4 addresses or if it serves other purposes).
There is another problem: if you are on IPv6 only then AFAIK you can not connect to it, you need an IPv4. Or a tunnel provider or something. Hopefully your provider gives you both addresses. An easy way is having the other machine mail you, automatically or manually, but not using a webmail system. You use the command "mail", which can be used in a script, either on its own, or using postfix as an intermediary. I think trying to use Thunderbird for this is not a good idea. Basically, you have a cronjob that obtains the current external IP, compares it with the IP obtained the previous run, and if different, sends an email to you, then saves it on a file. You can also phone and ask him to read aloud that file to you. This IP can also be used to configure a server on Internet that offers free or paid Dynamic DNS hosting. Ie, a DNS server out there that stores that IP, and points some name you invent to it. Possibly his router supports directly some such service, and if you use this you don't need any scripting, the router will do it - as long as the router is not reset to factory defaults or replaced, so having the mail setup as a backup is probably a good idea.
3) I can ssh within my LAN using the link-local address in the console, though I find it much faster and preferable to use a graphical interface and can't find how to make Dolphin accept this address in the 'Network Folder Wizard' dialog. It must need the interface specifying but no matter how I write out the string (%eth0, square brackets, quotes, backslash escapes, etc.) it doesn't accept it.
No, the link local address (starts with fe80:) is basically useless. You can ping it by number: cer@Telcontar:~> ping -c 2 fe80::4ecc:6aff:fe61:50a1%eth0 PING fe80::4ecc:6aff:fe61:50a1%eth0(fe80::4ecc:6aff:fe61:50a1%eth0) 56 data bytes 64 bytes from fe80::4ecc:6aff:fe61:50a1%eth0: icmp_seq=1 ttl=64 time=0.343 ms 64 bytes from fe80::4ecc:6aff:fe61:50a1%eth0: icmp_seq=2 ttl=64 time=0.381 ms --- fe80::4ecc:6aff:fe61:50a1%eth0 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1024ms rtt min/avg/max/mdev = 0.343/0.362/0.381/0.019 ms cer@Telcontar:~> You can ssh to it by number: cer@Telcontar:~> ssh fe80::4ecc:6aff:fe61:50a1%eth0 The authenticity of host 'fe80::4ecc:6aff:fe61:50a1%eth0 (fe80::4ecc:6aff:fe61:50a1%eth0)' can't be established. ECDSA key fingerprint is SHA256:ILybaOsrdw95ufuc4st0K1V6QyLT8ZWwBCJQVZfzwNk. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'fe80::4ecc:6aff:fe61:50a1%eth0' (ECDSA) to the list of known hosts. Last login: Thu Aug 8 14:23:09 2019 from 192.168.1.14 Have a lot of fun... cer@Isengard:~> But you can not do it by name, because it needs the interface: cer@Isengard:~> grep fe80 /etc/hosts fe80::21e:bff:fe08:4ccb bilbo6 cer@Isengard:~> ping bilbo6 connect: Invalid argument cer@Isengard:~> ping bilbo6%eth0 ping: bilbo6%eth0: Name or service not known cer@Isengard:~> (It is the IPv6 address of my HP Laser Printer, and I can not configure it using IPv6) You can not browse to it on Firefox or Chrome because it has been intentionally disabled for security. This is a nice one: a format that is defined in the /official/ internet documentation can not be used because it has security issues. The bugzilla is old. If you google the "bilbo6" number above you find threads in this mail list about that: <http://opensuse.14.x6.nabble.com/Trying-to-access-IPv6-web-page-on-firefox-revisited-td5102258.html> <http://opensuse.14.x6.nabble.com/IPv6-in-Firefox-does-it-work-The-saga-continues-td4991712.html> The importance of having a browser access this particular type of IP is that it is the configuration address of small devices, and it does not change, can be printed on the device label. For example, to configure a router without resetting it, you need this access. If you are in this quandary, you need Firefox version 6! Some admins keeps a copy of it just for this usage. <https://support.mozilla.org/en-US/questions/1111992> <https://bugzilla.mozilla.org/show_bug.cgi?id=700999> -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-08-10 12:56 PM, Carlos E. R. wrote:
No, the link local address (starts with fe80:) is basically useless.
It is not useless. IPv6 wouldn't work without it. However, it is not intended for users. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 2019-08-10 12:56 PM, Carlos E. R. wrote:
No, the link local address (starts with fe80:) is basically useless.
It is not useless. IPv6 wouldn't work without it. However, it is not intended for users.
Three very pertinent sentences. I could not have summed that up any better. -- Per Jessen, Zürich (20.2°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/08/2019 20.06, James Knott wrote:
On 2019-08-10 12:56 PM, Carlos E. R. wrote:
No, the link local address (starts with fe80:) is basically useless.
It is not useless. IPv6 wouldn't work without it. However, it is not intended for users.
No, the last part at least is not true. My printer IPv6 part only responds on it. HP designed it to be used, till Firefox removed the support. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas))
Carlos E. R. wrote:
On 10/08/2019 20.06, James Knott wrote:
On 2019-08-10 12:56 PM, Carlos E. R. wrote:
No, the link local address (starts with fe80:) is basically useless.
It is not useless. IPv6 wouldn't work without it. However, it is not intended for users.
No, the last part at least is not true. My printer IPv6 part only responds on it. HP designed it to be used, till Firefox removed the support.
That devices respond on link-local addresses is no indication of what their intended use is. Appplications listening for clients usually don't care where they come from. I agree with James, 100%. -- Per Jessen, Zürich (21.8°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 11/08/2019 12.07, Per Jessen wrote:
Carlos E. R. wrote:
On 10/08/2019 20.06, James Knott wrote:
On 2019-08-10 12:56 PM, Carlos E. R. wrote:
No, the link local address (starts with fe80:) is basically useless.
It is not useless. IPv6 wouldn't work without it. However, it is not intended for users.
No, the last part at least is not true. My printer IPv6 part only responds on it. HP designed it to be used, till Firefox removed the support.
That devices respond on link-local addresses is no indication of what their intended use is. Appplications listening for clients usually don't care where they come from. I agree with James, 100%.
It does not respond on anything else on IPv6. It is either IPv4, or that lilnk-local addresses. On some IoT, the only available address for the initial configuration, is the link-local address. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Carlos E. R. wrote:
On 11/08/2019 12.07, Per Jessen wrote:
Carlos E. R. wrote:
On 10/08/2019 20.06, James Knott wrote:
On 2019-08-10 12:56 PM, Carlos E. R. wrote:
No, the link local address (starts with fe80:) is basically useless.
It is not useless. IPv6 wouldn't work without it. However, it is not intended for users.
No, the last part at least is not true. My printer IPv6 part only responds on it. HP designed it to be used, till Firefox removed the support.
That devices respond on link-local addresses is no indication of what their intended use is. Appplications listening for clients usually don't care where they come from. I agree with James, 100%.
It does not respond on anything else on IPv6. It is either IPv4, or that lilnk-local addresses.
Really? It does not respond on a normal IPv6 address? Okay, that is most unusual. It would mean it cannot be reached over a router.
On some IoT, the only available address for the initial configuration, is the link-local address.
That might make some sense, but as James said, not intended for users. The fact that LL is not routable really says it all. -- Per Jessen, Zürich (23.4°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 2019-08-11 06:34 AM, Per Jessen wrote:
Really? It does not respond on a normal IPv6 address? Okay, that is most unusual. It would mean it cannot be reached over a router.
On some IoT, the only available address for the initial configuration, is the link-local address. That might make some sense, but as James said, not intended for users. The fact that LL is not routable really says it all.
This might also be partly Microsoft's fault. They had their "HomeGroup" network that was intended for simple setup and used link local addresses. If that printer was built for that, then they wouldn't necessarily use other IPv6 addresses. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/08/2019 12.56, James Knott wrote:
On 2019-08-11 06:34 AM, Per Jessen wrote:
Really? It does not respond on a normal IPv6 address? Okay, that is most unusual. It would mean it cannot be reached over a router.
On some IoT, the only available address for the initial configuration, is the link-local address. That might make some sense, but as James said, not intended for users. The fact that LL is not routable really says it all.
This might also be partly Microsoft's fault. They had their "HomeGroup" network that was intended for simple setup and used link local addresses. If that printer was built for that, then they wouldn't necessarily use other IPv6 addresses.
It is impossible to write and configure an IPv6 on that printer. It is just possible it autoconfigures (DHCP6?) from the router, but mine doesn't. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-08-11 08:21 AM, Carlos E. R. wrote:
It is impossible to write and configure an IPv6 on that printer.
With IPv6, there's rarely a reason to configure an address. Between SLAAC and DHCPv6, addresses are automatically assigned. In all the years I've been using IPv6, I have never had any reason to configure an address, except when I was setting up pfSense to also provide Unique Local Addresses. IPv6 just works, but you need it to come from somewhere. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/08/2019 16.00, James Knott wrote:
On 2019-08-11 08:21 AM, Carlos E. R. wrote:
It is impossible to write and configure an IPv6 on that printer.
With IPv6, there's rarely a reason to configure an address. Between SLAAC and DHCPv6, addresses are automatically assigned. In all the years I've been using IPv6, I have never had any reason to configure an address, except when I was setting up pfSense to also provide Unique Local Addresses. IPv6 just works, but you need it to come from somewhere.
And how do you connect to anything in your lan, if you don't know its address? -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-08-11 01:34 PM, Carlos E. R. wrote:
And how do you connect to anything in your lan, if you don't know its address?
Carlos, why is it you seem to be so thick about this? You do not have, as far as I know, a working IPv6 network. You are trying to use link local addresses in a way they weren't intended to be used. Whether it worked in Firefox previously, but now doesn't is irrelevant. If you have a problem with the way Firefox now does things, take it up with them. It is not an issue with link local addresses! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/08/2019 19.55, James Knott wrote:
On 2019-08-11 01:34 PM, Carlos E. R. wrote:
And how do you connect to anything in your lan, if you don't know its address?
Carlos, why is it you seem to be so thick about this? You do not have, as far as I know, a working IPv6 network. You are trying to use link local addresses in a way they weren't intended to be used. Whether it worked in Firefox previously, but now doesn't is irrelevant. If you have a problem with the way Firefox now does things, take it up with them. It is not an issue with link local addresses!
You are missing the point. This is a theoretical question. You say I do not need them. To just plug an IPv6 device into the network (not necessarily mine) and it will be autoconfigured, it will get an address. Ok, what address will it get? How do I know that address? How do I connect to that new device without knowing its new IPv6 address? And about taking an issue with Firefox, you did not read the link I posted. Hundreds of people took and issue with them, there is bugzilla and I have nothing to with it. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-08-11 02:10 PM, Carlos E. R. wrote:
To just plug an IPv6 device into the network (not necessarily mine) and it will be autoconfigured, it will get an address. Ok, what address will it get? How do I know that address? How do I connect to that new device without knowing its new IPv6 address?
How do you know your IPv4 address when DHCP is used? Maybe you open a command prompt and type ip addr sh? You can even get fancy and use ip -6 addr sh, if you only want to see IPv6 addresses. I also mentioned, in another note, about the ip neighbor show command. It shows the addresses of other devices. How do you do that in IPv4? Why is IPv6 so special that you can't use the same or similar methods as IPv4? What does this have to do with your insistence on using link local addresses?
And about taking an issue with Firefox, you did not read the link I posted. Hundreds of people took and issue with them, there is bugzilla and I have nothing to with it.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/08/2019 20.19, James Knott wrote:
On 2019-08-11 02:10 PM, Carlos E. R. wrote:
To just plug an IPv6 device into the network (not necessarily mine) and it will be autoconfigured, it will get an address. Ok, what address will it get? How do I know that address? How do I connect to that new device without knowing its new IPv6 address?
How do you know your IPv4 address when DHCP is used? Maybe you open a command prompt and type ip addr sh? You can even get fancy and use ip -6 addr sh, if you only want to see IPv6 addresses.
As I said, I look into the documentation and they say the device comes factory set to 192.168.1.1 or 192.168.0.1. Some devices, like the chromecast, do the network configuration over bluetooth instead, off-band. New HP printers are configured on Windows probably with some specific broadcast and the printer responds to it. Tricks.
I also mentioned, in another note, about the ip neighbor show command. It shows the addresses of other devices.
News to me. Interesting. It does not say which is the new device. I can guess, though.
How do you do that in IPv4? Why is IPv6 so special that you can't use the same or similar methods as IPv4? What does this have to do with your insistence on using link local addresses?
As I said, IPv4 comes with a factory configuration of a fixed IP address. On ipv6, that is the link-local address.
And about taking an issue with Firefox, you did not read the link I posted. Hundreds of people took and issue with them, there is bugzilla and I have nothing to with it.
-- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Carlos E. R. wrote:
On 11/08/2019 19.55, James Knott wrote:
On 2019-08-11 01:34 PM, Carlos E. R. wrote:
And how do you connect to anything in your lan, if you don't know its address?
Carlos, why is it you seem to be so thick about this? You do not have, as far as I know, a working IPv6 network. You are trying to use link local addresses in a way they weren't intended to be used. Whether it worked in Firefox previously, but now doesn't is irrelevant. If you have a problem with the way Firefox now does things, take it up with them. It is not an issue with link local addresses!
You are missing the point.
This is a theoretical question.
You say I do not need them.
For the record, I agree with James. 100%. I think your issues stem from not having a properly operating ipv6 environment.
To just plug an IPv6 device into the network (not necessarily mine) and it will be autoconfigured, it will get an address. Ok, what address will it get? How do I know that address? How do I connect to that new device without knowing its new IPv6 address?
My solution - for something I need to connect to, I put it in the dhcpv6 config and add dynamic dns updates. In fact, every known device gets a dynamic dns update, visiting devices don't and are given a firewall restricted ipv6 range. In your case, I would get the LL address and replace 'fe80::' with the prefix you are using (fc00:what:ever:itis). -- Per Jessen, Zürich (18.4°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
On 2019-08-11 03:04 PM, Per Jessen wrote:
My solution - for something I need to connect to, I put it in the dhcpv6 config and add dynamic dns updates. In fact, every known device gets a dynamic dns update, visiting devices don't and are given a firewall restricted ipv6 range.
I use SLAAC and configure the DNS server with the consistent (usually MAC based) address. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/08/2019 21.21, James Knott wrote:
On 2019-08-11 03:04 PM, Per Jessen wrote:
My solution - for something I need to connect to, I put it in the dhcpv6 config and add dynamic dns updates. In fact, every known device gets a dynamic dns update, visiting devices don't and are given a firewall restricted ipv6 range.
I use SLAAC and configure the DNS server with the consistent (usually MAC based) address.
How do you configure the DNS if the prefix is changing every time the router reboots or the ISP sees fit? Just a theoretical cuestion, you know I don't have an actual prefix. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-08-11 04:19 PM, Carlos E. R. wrote:
How do you configure the DNS if the prefix is changing every time the router reboots or the ISP sees fit?
Just a theoretical cuestion, you know I don't have an actual prefix.
IPv6 uses something called a DUID, which ensures you get the same prefix. https://en.wikipedia.org/wiki/DHCPv6#DHCP_Unique_Identifier -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/08/2019 22.38, James Knott wrote:
On 2019-08-11 04:19 PM, Carlos E. R. wrote:
How do you configure the DNS if the prefix is changing every time the router reboots or the ISP sees fit?
Just a theoretical cuestion, you know I don't have an actual prefix.
IPv6 uses something called a DUID, which ensures you get the same prefix.
Do ISP provided routers support this? :-? Huh, maybe I understood badly or did not ask well. I mean the ISP prefix. Each machine gets an IP which is composed of the "external" prefix and a locally generated suffix. In my local DNS server I would have to write the whole IP and corresponding names, or use another IP number that is valid only locally. But the ISP can give me a different IP v6 prefix every time I boot the router. Spain, remember? They charge extra to fix the prefix, like for fixed IPv4 addresses. I have no personal direct confirmation of this, but it is what we expect to get. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-08-11 05:24 PM, Carlos E. R. wrote:
IPv6 uses something called a DUID, which ensures you get the same prefix.
https://en.wikipedia.org/wiki/DHCPv6#DHCP_Unique_Identifier Do ISP provided routers support this? :-?
I can't say for certain, but they should. pfSense certainly does.
Huh, maybe I understood badly or did not ask well.
I mean the ISP prefix. Each machine gets an IP which is composed of the "external" prefix and a locally generated suffix. In my local DNS server I would have to write the whole IP and corresponding names, or use another IP number that is valid only locally.
But the ISP can give me a different IP v6 prefix every time I boot the router. Spain, remember? They charge extra to fix the prefix, like for fixed IPv4 addresses. I have no personal direct confirmation of this, but it is what we expect to get.
The prefix is whatever is assigned to the local network. My ISP assigns me a /56 prefix, which I can then split into 256 /64s, if I wish. I'm currently using only 3. So, my main network has a "0" as part of it's prefix, my test LAN "3" and I use "ff" for my VPN. Because of the DUID I always get the same /56. Any ISP that charges for consistent prefixes (by consistent, I mean unlikely to change) is not one I would want to do business with. The IPv6 address space is so huge, there's no reason for anyone to charge for something like that. It's just plain greed. He.net won't do that to you. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-08-11 05:45 PM, James Knott wrote:
The prefix is whatever is assigned to the local network. My ISP assigns me a /56 prefix, which I can then split into 256 /64s, if I wish. I'm currently using only 3. So, my main network has a "0" as part of it's prefix, my test LAN "3" and I use "ff" for my VPN. Because of the DUID I always get the same /56.
One other thing. With pfSense, there's a setting that will cause pfSense to release the DUID on reboot. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/08/2019 23.45, James Knott wrote:
On 2019-08-11 05:24 PM, Carlos E. R. wrote:
IPv6 uses something called a DUID, which ensures you get the same prefix.
https://en.wikipedia.org/wiki/DHCPv6#DHCP_Unique_Identifier Do ISP provided routers support this? :-?
I can't say for certain, but they should. pfSense certainly does.
Huh, maybe I understood badly or did not ask well.
I mean the ISP prefix. Each machine gets an IP which is composed of the "external" prefix and a locally generated suffix. In my local DNS server I would have to write the whole IP and corresponding names, or use another IP number that is valid only locally.
But the ISP can give me a different IP v6 prefix every time I boot the router. Spain, remember? They charge extra to fix the prefix, like for fixed IPv4 addresses. I have no personal direct confirmation of this, but it is what we expect to get.
The prefix is whatever is assigned to the local network. My ISP assigns me a /56 prefix, which I can then split into 256 /64s, if I wish. I'm currently using only 3. So, my main network has a "0" as part of it's prefix, my test LAN "3" and I use "ff" for my VPN. Because of the DUID I always get the same /56.
Any ISP that charges for consistent prefixes (by consistent, I mean unlikely to change) is not one I would want to do business with. The IPv6 address space is so huge, there's no reason for anyone to charge for something like that. It's just plain greed. He.net won't do that to you.
I agree it makes no sense. Yes, it is plain greed. It makes business sense to them, though. Change ISP? I guess all will do the same - if one doesn't, then it is possible the rest will change. Long ago, here, they gave fixed address to everyone that got a connection. At some point, they changed to dynamic, and had the the cheek to charge for the /improvement/ (of being dynamic). Their commercial representatives where bewildered when talking to customers that were incensed by the change, they did not understand. At some point, they charged for "static IP". They want to keep charging for static IPv6 IPs; I'd bet the most I can bet on safe bets, ie, ten cents, that they will do it (I'm trying to paraphrase Asimov). Customer support query (Spanish): <https://comunidad.movistar.es/t5/Hogar-Fijo-Internet-TV/IPv6-est%C3%A1tica/td-p/3796824> (last April) The gist of the answers: - fixed IPv4: 25€/month. - No IPv6 for customers - They do not deny fixed IPv6 will have a cost. Thus, I understand my question is absurd to you, but you see, it will be a need here. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-08-11 06:03 PM, Carlos E. R. wrote:
Long ago, here, they gave fixed address to everyone that got a connection. At some point, they changed to dynamic, and had the the cheek to charge for the /improvement/ (of being dynamic). Their commercial representatives where bewildered when talking to customers that were incensed by the change, they did not understand.
Depending on how far back you go, at one time all addresses were static and DHCP wasn't available. That was the case with my first ISP, where I had to use SLIP, instead of PPP for my connection.
At some point, they charged for "static IP". They want to keep charging for static IPv6 IPs; I'd bet the most I can bet on safe bets, ie, ten cents, that they will do it (I'm trying to paraphrase Asimov).
Static also caused a bit more work for them. However, DHCP does not mean the address has to change. I have DHCP for IPv4 and the address is virtually static. The host name, based on modem and router MAC addresses, does not change, unless I change hardware. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 8/11/19 1:19 PM, Carlos E. R. wrote:
On 11/08/2019 21.21, James Knott wrote:
On 2019-08-11 03:04 PM, Per Jessen wrote:
My solution - for something I need to connect to, I put it in the dhcpv6 config and add dynamic dns updates. In fact, every known device gets a dynamic dns update, visiting devices don't and are given a firewall restricted ipv6 range. I use SLAAC and configure the DNS server with the consistent (usually MAC based) address.
How do you configure the DNS if the prefix is changing every time the router reboots or the ISP sees fit?
Just a theoretical cuestion, you know I don't have an actual prefix.
Carlos, in the situation you've outlined, you *don't* configure DNS. You simply rely on the DNS server provided by the DHCP server.... Where ever that happens to be ISP or locally administered. DNS is name resolution... You send a name and get back an IP address. Maybe IPv4 or IPv6, maybe both depending IP addressing scheme has NOTHING to do with DNS except as a cross reference. SOME DHCP clients send a DNS update, but this tends to only be effective on locally administered DNS servers; Almost never ISC BIND based ones and is usually on Windows AD Domain controller DNS servers. You CAN configure DNS updates on ISC BIND, but I don't. What you're thinking of as "link local address name resolution" actually relies on a multi-cast service known on Linux systems as Avahi and on everything else as Bonjour. Avahi/Bonjour listens for the multicast broadcasts (from a Avahi/Bonjour process) as interfaces come online, and using routines in glibc, present the information for name resolution to the rest of the system. On Linux systems, this behavior is configured via the file /etc/nsswitch. Browsers don't support or not support link local resolution... The system name resolution mechanisms have to be configured for it. OS X comes that way, install certain Apple products on a Windows system and you get the needed configs. Linux, you get to fiddle a bit. Just for fun, fire up Avahi on your system and watch the multicast range... For real fun, turn on pulse audio audio streaming and see what your network does. There is a reason most router discard multicast and why at one point in time they "invented" the mbone. Multicast can be a VERY not nice thing. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/08/2019 06.41, Bruce Ferrell wrote:
On 8/11/19 1:19 PM, Carlos E. R. wrote:
On 11/08/2019 21.21, James Knott wrote:
On 2019-08-11 03:04 PM, Per Jessen wrote:
My solution - for something I need to connect to, I put it in the dhcpv6 config and add dynamic dns updates. In fact, every known device gets a dynamic dns update, visiting devices don't and are given a firewall restricted ipv6 range. I use SLAAC and configure the DNS server with the consistent (usually MAC based) address.
How do you configure the DNS if the prefix is changing every time the router reboots or the ISP sees fit?
Just a theoretical cuestion, you know I don't have an actual prefix.
Carlos, in the situation you've outlined, you *don't* configure DNS.
You simply rely on the DNS server provided by the DHCP server.... Where ever that happens to be ISP or locally administered.
The DHCP is the router, obviously, and it does not provide local DNS service. It just ask the ISP for internet addresses like google.com.
DNS is name resolution... You send a name and get back an IP address. Maybe IPv4 or IPv6, maybe both depending
I know.
IP addressing scheme has NOTHING to do with DNS except as a cross reference.
SOME DHCP clients send a DNS update, but this tends to only be effective on locally administered DNS servers; Almost never ISC BIND based ones and is usually on Windows AD Domain controller DNS servers. You CAN configure DNS updates on ISC BIND, but I don't.
What you're thinking of as "link local address name resolution" actually relies on a multi-cast service known on Linux systems as Avahi and on everything else as Bonjour.
Avahi/Bonjour listens for the multicast broadcasts (from a Avahi/Bonjour process) as interfaces come online, and using routines in glibc, present the information for name resolution to the rest of the system. On Linux systems, this behavior is configured via the file /etc/nsswitch.
I have DNS created by me such that if I do: http://printer it works, on IPv4, because the local addresses are fixed. The issue is replicating the behaviour when IPv6 comes my way with dynamic prefixes. If/when it does, I'll have to concoct a script to do it.
Browsers don't support or not support link local resolution... The system name resolution mechanisms have to be configured for it.
How exactly? :-? The DNS has no problem giving "FE80::21E:BFF:FE08:4CCB" as an answer, but no GUI browser will accept any FE80:: address with the required interface name attached. The support has been intentionally removed, and there is a several year old bugzilla on that. What can be done on DNS to change this? :-? You must be talking of something different.
OS X comes that way, install certain Apple products on a Windows system and you get the needed configs. Linux, you get to fiddle a bit.
Just for fun, fire up Avahi on your system and watch the multicast range... For real fun, turn on pulse audio audio streaming and see what your network does.
Avahi service is running by default on most opensuse machines since years ago. Telcontar:~ # systemctl status avahi-daemon ● avahi-daemon.service - Avahi mDNS/DNS-SD Stack Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2019-08-08 12:39:39 CEST; 3 days ago Main PID: 1583 (avahi-daemon) Status: "Server startup complete. Host name is Telcontar.local. Local service cookie is 203941546." Tasks: 1 (limit: 4915) CGroup: /system.slice/avahi-daemon.service └─1583 avahi-daemon: running [Telcontar.local] Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable. Telcontar:~ #
There is a reason most router discard multicast and why at one point in time they "invented" the mbone. Multicast can be a VERY not nice thing.
-- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 8/12/19 12:37 AM, Carlos E. R. wrote:
On 12/08/2019 06.41, Bruce Ferrell wrote:
On 8/11/19 1:19 PM, Carlos E. R. wrote:
On 11/08/2019 21.21, James Knott wrote:
On 2019-08-11 03:04 PM, Per Jessen wrote:
My solution - for something I need to connect to, I put it in the dhcpv6 config and add dynamic dns updates. In fact, every known device gets a dynamic dns update, visiting devices don't and are given a firewall restricted ipv6 range. I use SLAAC and configure the DNS server with the consistent (usually MAC based) address.
How do you configure the DNS if the prefix is changing every time the router reboots or the ISP sees fit?
Just a theoretical cuestion, you know I don't have an actual prefix.
Carlos, in the situation you've outlined, you *don't* configure DNS.
You simply rely on the DNS server provided by the DHCP server.... Where ever that happens to be ISP or locally administered. The DHCP is the router, obviously, and it does not provide local DNS service. It just ask the ISP for internet addresses like google.com.
DNS is name resolution... You send a name and get back an IP address. Maybe IPv4 or IPv6, maybe both depending I know.
IP addressing scheme has NOTHING to do with DNS except as a cross reference.
SOME DHCP clients send a DNS update, but this tends to only be effective on locally administered DNS servers; Almost never ISC BIND based ones and is usually on Windows AD Domain controller DNS servers. You CAN configure DNS updates on ISC BIND, but I don't.
What you're thinking of as "link local address name resolution" actually relies on a multi-cast service known on Linux systems as Avahi and on everything else as Bonjour.
Avahi/Bonjour listens for the multicast broadcasts (from a Avahi/Bonjour process) as interfaces come online, and using routines in glibc, present the information for name resolution to the rest of the system. On Linux systems, this behavior is configured via the file /etc/nsswitch. I have DNS created by me such that if I do:
it works, on IPv4, because the local addresses are fixed.
The issue is replicating the behaviour when IPv6 comes my way with dynamic prefixes. If/when it does, I'll have to concoct a script to do it.
Browsers don't support or not support link local resolution... The system name resolution mechanisms have to be configured for it. How exactly? :-?
The DNS has no problem giving "FE80::21E:BFF:FE08:4CCB" as an answer, but no GUI browser will accept any FE80:: address with the required interface name attached. The support has been intentionally removed, and there is a several year old bugzilla on that.
What can be done on DNS to change this? :-?
You must be talking of something different.
Carlos, you have to do AAA records in the DNS zone file to resolve IPv6 addresses. IPv4 uses A records. But in the mean time, let me google that for you: https://www.cisco.com/c/en/us/support/docs/ip/ip-version-6-ipv6/113328-ipv6-... Link-local addresses are not necessarily bound to the MAC address (configured in a EUI-64 format). Link-local addresses can also be manually configured in the FE80::/10 format These addresses refer only to a particular physical link and are used for addressing on a single link for purposes such as automatic address configuration and neighbor discovery protocol. Link-local addresses can be used to reach the neighboring nodes attached to the same link. The nodes do not need a globally unique address to communicate. Routers will not forward datagrams using link-local addresses. IPv6 routers must not forward packets that have link-local source or destination addresses to other links. All IPv6 enabled interfaces have a link-local unicast address. Notice that link local isn't "necessarily" bound to a MAC address, so there no certain way to determine what interface it's associated with on a LAN (like with arp/rarp) Also notice they are used for AUTOMATIC ADDRESS CONFIGURATION. Routers WILL NOT forward them, so why would you be trying to use them as a permanent host address in a browser? Just for giggles, I happen to have a small block of "real", static IPv6 addresses and I configured one to a host local to my LAN. It works fine in my browser. I'm suspecting that you're banging face first into a violation of the standard. Browser makers know and follow [unless they're MS ;) ] the rules and, I'm guessing, simply discard link locals. As to HOW your system/glibc is configured to to perform name resolution, have a look at the man page for the file /etc/nsswitch. There ARE some uncommon options. I've used MySQL tables and LDAP in there along with YP/NIS, but it can be a wee touch tricky sometimes (NIS used to have a broken slave setup... Not that the binaries had bugs, just the packaged slave setup was incorrect and didn't correctly replicate. I'm not sure if anyone ever fixed that; Few use NIS anymore). I also saw an issue once where someone had deleted the nsswitch file; When that happens you can't ping 127.0.0.1 or localhost. Lots of stuff breaks. I've been running Suse systems for a VERY long time... Long enough that Avahi wasn't even present, let alone enabled, so my few remaining Suse systems don't run it. I made the mistake of turning it on in conjunction with pulse once and had to figure what the sudden traffic storm was. Interesting that OS X doesn't do that.
OS X comes that way, install certain Apple products on a Windows system and you get the needed configs. Linux, you get to fiddle a bit.
Just for fun, fire up Avahi on your system and watch the multicast range... For real fun, turn on pulse audio audio streaming and see what your network does.
Avahi service is running by default on most opensuse machines since years ago.
Telcontar:~ # systemctl status avahi-daemon ● avahi-daemon.service - Avahi mDNS/DNS-SD Stack Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2019-08-08 12:39:39 CEST; 3 days ago Main PID: 1583 (avahi-daemon) Status: "Server startup complete. Host name is Telcontar.local. Local service cookie is 203941546." Tasks: 1 (limit: 4915) CGroup: /system.slice/avahi-daemon.service └─1583 avahi-daemon: running [Telcontar.local]
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable. Telcontar:~ #
There is a reason most router discard multicast and why at one point in time they "invented" the mbone. Multicast can be a VERY not nice thing.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/08/2019 15.54, Bruce Ferrell wrote:
On 8/12/19 12:37 AM, Carlos E. R. wrote:
On 12/08/2019 06.41, Bruce Ferrell wrote:
On 8/11/19 1:19 PM, Carlos E. R. wrote:
On 11/08/2019 21.21, James Knott wrote:
On 2019-08-11 03:04 PM, Per Jessen wrote:
My solution - for something I need to connect to, I put it in the dhcpv6 config and add dynamic dns updates. In fact, every known device gets a dynamic dns update, visiting devices don't and are given a firewall restricted ipv6 range. I use SLAAC and configure the DNS server with the consistent (usually MAC based) address.
How do you configure the DNS if the prefix is changing every time the router reboots or the ISP sees fit?
Just a theoretical cuestion, you know I don't have an actual prefix.
Carlos, in the situation you've outlined, you *don't* configure DNS.
You simply rely on the DNS server provided by the DHCP server.... Where ever that happens to be ISP or locally administered. The DHCP is the router, obviously, and it does not provide local DNS service. It just ask the ISP for internet addresses like google.com.
DNS is name resolution... You send a name and get back an IP address. Maybe IPv4 or IPv6, maybe both depending I know.
IP addressing scheme has NOTHING to do with DNS except as a cross reference.
SOME DHCP clients send a DNS update, but this tends to only be effective on locally administered DNS servers; Almost never ISC BIND based ones and is usually on Windows AD Domain controller DNS servers. You CAN configure DNS updates on ISC BIND, but I don't.
What you're thinking of as "link local address name resolution" actually relies on a multi-cast service known on Linux systems as Avahi and on everything else as Bonjour.
Avahi/Bonjour listens for the multicast broadcasts (from a Avahi/Bonjour process) as interfaces come online, and using routines in glibc, present the information for name resolution to the rest of the system. On Linux systems, this behavior is configured via the file /etc/nsswitch. I have DNS created by me such that if I do:
it works, on IPv4, because the local addresses are fixed.
The issue is replicating the behaviour when IPv6 comes my way with dynamic prefixes. If/when it does, I'll have to concoct a script to do it.
Browsers don't support or not support link local resolution... The system name resolution mechanisms have to be configured for it. How exactly? :-?
The DNS has no problem giving "FE80::21E:BFF:FE08:4CCB" as an answer, but no GUI browser will accept any FE80:: address with the required interface name attached. The support has been intentionally removed, and there is a several year old bugzilla on that.
What can be done on DNS to change this? :-?
You must be talking of something different.
Carlos, you have to do AAA records in the DNS zone file to resolve IPv6 addresses. IPv4 uses A records. But in the mean time, let me google that for you:
https://www.cisco.com/c/en/us/support/docs/ip/ip-version-6-ipv6/113328-ipv6-...
Link-local addresses are not necessarily bound to the MAC address (configured in a EUI-64 format).
Link-local addresses can also be manually configured in the FE80::/10 format
These addresses refer only to a particular physical link and are used for addressing on a single link for purposes such as automatic address configuration and neighbor discovery protocol. Link-local addresses can be used to reach the neighboring nodes attached to the same link. The nodes do not need a globally unique address to communicate. Routers will not forward datagrams using link-local addresses. IPv6 routers must not forward packets that have link-local source or destination addresses to other links. All IPv6 enabled interfaces have a link-local unicast address.
Notice that link local isn't "necessarily" bound to a MAC address, so there no certain way to determine what interface it's associated with on a LAN (like with arp/rarp)
Also notice they are used for AUTOMATIC ADDRESS CONFIGURATION.
Routers WILL NOT forward them, so why would you be trying to use them as a permanent host address in a browser?
Just for giggles, I happen to have a small block of "real", static IPv6 addresses and I configured one to a host local to my LAN. It works fine in my browser.
I'm suspecting that you're banging face first into a violation of the standard.
Browser makers know and follow [unless they're MS ;) ] the rules and, I'm guessing, simply discard link locals.
As to HOW your system/glibc is configured to to perform name resolution, have a look at the man page for the file /etc/nsswitch.
There ARE some uncommon options. I've used MySQL tables and LDAP in there along with YP/NIS, but it can be a wee touch tricky sometimes (NIS used to have a broken slave setup... Not that the binaries had bugs, just the packaged slave setup was incorrect and didn't correctly replicate. I'm not sure if anyone ever fixed that; Few use NIS anymore). I also saw an issue once where someone had deleted the nsswitch file; When that happens you can't ping 127.0.0.1 or localhost. Lots of stuff breaks.
I've been running Suse systems for a VERY long time... Long enough that Avahi wasn't even present, let alone enabled, so my few remaining Suse systems don't run it. I made the mistake of turning it on in conjunction with pulse once and had to figure what the sudden traffic storm was. Interesting that OS X doesn't do that.
You may have some confusion, the thread is long :-) At the point you entered the thread, we were talking about ISP provided IPv6 addresses. In most of the world, the prefix does not change. In Spain the forecast is that it will be dynamic and will change on every router reboot. We were wondering in that situation how to make aware the internal DNS server of the prefix change so that the names point to the correct internal addresses of the internal machines. The DNS on the router is only a cacheing server of the outside, local names can not be assigned. In that situation I would have to script a cron job to modify the DNS on an internal machine when needed. For local addresses I already adapted the DNS server: /etc/named/zone/valinor: Telcontar A 192.168.1.14 MX 10 Telcontar ; AAAA fc00::14 AmonLanc A 192.168.1.15 Isengard A 192.168.1.16 ;Isengard AAAA fc00::16 But I had to disable this because it breaks NFS. Another different issue is that browsers have removed support for link-local addresses, such as <http:///[FE80::21E:BFF:FE08:4CCB%eth0]>, for security reasons, even if such an address is supported by the RFCs and thus should work. They are thinking of changing that RFC, but still, after about a decade, they have not decided how. People that need it resort to Firefox 6, which supports it. That is <https://bugzilla.mozilla.org/show_bug.cgi?id=700999>. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 8/12/19 9:59 AM, Carlos E. R. wrote:
On 12/08/2019 15.54, Bruce Ferrell wrote:
On 8/12/19 12:37 AM, Carlos E. R. wrote:
On 12/08/2019 06.41, Bruce Ferrell wrote:
On 8/11/19 1:19 PM, Carlos E. R. wrote:
On 11/08/2019 21.21, James Knott wrote:
On 2019-08-11 03:04 PM, Per Jessen wrote: > My solution - for something I need to connect to, I put it in the > dhcpv6 > config and add dynamic dns updates. In fact, every known device > gets a > dynamic dns update, visiting devices don't and are given a firewall > restricted ipv6 range. I use SLAAC and configure the DNS server with the consistent (usually MAC based) address.
How do you configure the DNS if the prefix is changing every time the router reboots or the ISP sees fit?
Just a theoretical cuestion, you know I don't have an actual prefix.
Carlos, in the situation you've outlined, you *don't* configure DNS.
You simply rely on the DNS server provided by the DHCP server.... Where ever that happens to be ISP or locally administered. The DHCP is the router, obviously, and it does not provide local DNS service. It just ask the ISP for internet addresses like google.com.
DNS is name resolution... You send a name and get back an IP address. Maybe IPv4 or IPv6, maybe both depending I know.
IP addressing scheme has NOTHING to do with DNS except as a cross reference.
SOME DHCP clients send a DNS update, but this tends to only be effective on locally administered DNS servers; Almost never ISC BIND based ones and is usually on Windows AD Domain controller DNS servers. You CAN configure DNS updates on ISC BIND, but I don't.
What you're thinking of as "link local address name resolution" actually relies on a multi-cast service known on Linux systems as Avahi and on everything else as Bonjour.
Avahi/Bonjour listens for the multicast broadcasts (from a Avahi/Bonjour process) as interfaces come online, and using routines in glibc, present the information for name resolution to the rest of the system. On Linux systems, this behavior is configured via the file /etc/nsswitch. I have DNS created by me such that if I do:
it works, on IPv4, because the local addresses are fixed.
The issue is replicating the behaviour when IPv6 comes my way with dynamic prefixes. If/when it does, I'll have to concoct a script to do it.
Browsers don't support or not support link local resolution... The system name resolution mechanisms have to be configured for it. How exactly? :-?
The DNS has no problem giving "FE80::21E:BFF:FE08:4CCB" as an answer, but no GUI browser will accept any FE80:: address with the required interface name attached. The support has been intentionally removed, and there is a several year old bugzilla on that.
What can be done on DNS to change this? :-?
You must be talking of something different.
Carlos, you have to do AAA records in the DNS zone file to resolve IPv6 addresses. IPv4 uses A records. But in the mean time, let me google that for you:
https://www.cisco.com/c/en/us/support/docs/ip/ip-version-6-ipv6/113328-ipv6-...
Link-local addresses are not necessarily bound to the MAC address (configured in a EUI-64 format).
Link-local addresses can also be manually configured in the FE80::/10 format
These addresses refer only to a particular physical link and are used for addressing on a single link for purposes such as automatic address configuration and neighbor discovery protocol. Link-local addresses can be used to reach the neighboring nodes attached to the same link. The nodes do not need a globally unique address to communicate. Routers will not forward datagrams using link-local addresses. IPv6 routers must not forward packets that have link-local source or destination addresses to other links. All IPv6 enabled interfaces have a link-local unicast address.
Notice that link local isn't "necessarily" bound to a MAC address, so there no certain way to determine what interface it's associated with on a LAN (like with arp/rarp)
Also notice they are used for AUTOMATIC ADDRESS CONFIGURATION.
Routers WILL NOT forward them, so why would you be trying to use them as a permanent host address in a browser?
Just for giggles, I happen to have a small block of "real", static IPv6 addresses and I configured one to a host local to my LAN. It works fine in my browser.
I'm suspecting that you're banging face first into a violation of the standard.
Browser makers know and follow [unless they're MS ;) ] the rules and, I'm guessing, simply discard link locals.
As to HOW your system/glibc is configured to to perform name resolution, have a look at the man page for the file /etc/nsswitch.
There ARE some uncommon options. I've used MySQL tables and LDAP in there along with YP/NIS, but it can be a wee touch tricky sometimes (NIS used to have a broken slave setup... Not that the binaries had bugs, just the packaged slave setup was incorrect and didn't correctly replicate. I'm not sure if anyone ever fixed that; Few use NIS anymore). I also saw an issue once where someone had deleted the nsswitch file; When that happens you can't ping 127.0.0.1 or localhost. Lots of stuff breaks.
I've been running Suse systems for a VERY long time... Long enough that Avahi wasn't even present, let alone enabled, so my few remaining Suse systems don't run it. I made the mistake of turning it on in conjunction with pulse once and had to figure what the sudden traffic storm was. Interesting that OS X doesn't do that.
You may have some confusion, the thread is long :-)
At the point you entered the thread, we were talking about ISP provided IPv6 addresses. In most of the world, the prefix does not change. In Spain the forecast is that it will be dynamic and will change on every router reboot.
We were wondering in that situation how to make aware the internal DNS server of the prefix change so that the names point to the correct internal addresses of the internal machines. The DNS on the router is only a cacheing server of the outside, local names can not be assigned.
In that situation I would have to script a cron job to modify the DNS on an internal machine when needed.
For local addresses I already adapted the DNS server:
/etc/named/zone/valinor:
Telcontar A 192.168.1.14 MX 10 Telcontar ; AAAA fc00::14 AmonLanc A 192.168.1.15
Isengard A 192.168.1.16 ;Isengard AAAA fc00::16
But I had to disable this because it breaks NFS.
Another different issue is that browsers have removed support for link-local addresses, such as <http:///[FE80::21E:BFF:FE08:4CCB%eth0]>, for security reasons, even if such an address is supported by the RFCs and thus should work. They are thinking of changing that RFC, but still, after about a decade, they have not decided how. People that need it resort to Firefox 6, which supports it.
That is <https://bugzilla.mozilla.org/show_bug.cgi?id=700999>.
It's quite possible I am confused... It happens all the time. But that doesn't change the fact that link-local is NOT allowed to traverse a router or the internet, per the spec or, by my understanding, be used for much but automatic configuration... Like you, I don't do a lot with IPv6 though. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-08-12 03:32 PM, Bruce Ferrell wrote:
But that doesn't change the fact that link-local is NOT allowed to traverse a router or the internet, per the spec or, by my understanding, be used for much but automatic configuration... Like you, I don't do a lot with IPv6 though.
It's not that link local addresses are not allowed to be routed or on the Internet, it's they can't be routed, because there is nothing in them to indicate what network they belong on. Even Unique Local addresses can be routed, but are not allowed on the Internet, just like the RFC1918 addresses. Also, you can pick any point on the Internet and you will see link local addresses, as IPv6 requires them to work. In fact, routing is often done through link local addresses. With my pfsense firewall/router, the LAN gateway is fe80::1:1. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/08/2019 21.32, Bruce Ferrell wrote:
On 8/12/19 9:59 AM, Carlos E. R. wrote:
On 12/08/2019 15.54, Bruce Ferrell wrote:
On 8/12/19 12:37 AM, Carlos E. R. wrote:
On 12/08/2019 06.41, Bruce Ferrell wrote:
On 8/11/19 1:19 PM, Carlos E. R. wrote:
On 11/08/2019 21.21, James Knott wrote: > On 2019-08-11 03:04 PM, Per Jessen wrote:
...
Another different issue is that browsers have removed support for link-local addresses, such as <http:///[FE80::21E:BFF:FE08:4CCB%eth0]>, for security reasons, even if such an address is supported by the RFCs and thus should work. They are thinking of changing that RFC, but still, after about a decade, they have not decided how. People that need it resort to Firefox 6, which supports it.
That is <https://bugzilla.mozilla.org/show_bug.cgi?id=700999>.
It's quite possible I am confused... It happens all the time.
But that doesn't change the fact that link-local is NOT allowed to traverse a router or the internet, per the spec or, by my understanding, be used for much but automatic configuration... Like you, I don't do a lot with IPv6 though.
But I have no interest in routing them, never did :-) -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 11/08/2019 21.04, Per Jessen wrote:
Carlos E. R. wrote:
On 11/08/2019 19.55, James Knott wrote:
On 2019-08-11 01:34 PM, Carlos E. R. wrote:
And how do you connect to anything in your lan, if you don't know its address?
Carlos, why is it you seem to be so thick about this? You do not have, as far as I know, a working IPv6 network. You are trying to use link local addresses in a way they weren't intended to be used. Whether it worked in Firefox previously, but now doesn't is irrelevant. If you have a problem with the way Firefox now does things, take it up with them. It is not an issue with link local addresses!
You are missing the point.
This is a theoretical question.
You say I do not need them.
For the record, I agree with James. 100%. I think your issues stem from not having a properly operating ipv6 environment.
To just plug an IPv6 device into the network (not necessarily mine) and it will be autoconfigured, it will get an address. Ok, what address will it get? How do I know that address? How do I connect to that new device without knowing its new IPv6 address?
My solution - for something I need to connect to, I put it in the dhcpv6 config and add dynamic dns updates. In fact, every known device gets a dynamic dns update, visiting devices don't and are given a firewall restricted ipv6 range.
In your case, I would get the LL address and replace 'fe80::' with the prefix you are using (fc00:what:ever:itis).
Ah, well, that's an answer. Thanks. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-08-11 06:24 AM, Carlos E. R. wrote:
It does not respond on anything else on IPv6. It is either IPv4, or that lilnk-local addresses.
On some IoT, the only available address for the initial configuration, is the link-local address.
How are those IoT devices configured? A couple of years ago, when I configured some IP security cameras, I had to create a static ARP for the cameras MAC address, before I could access it with a browser. On the other hand, the manufacturer provided a utility to configure the cameras without having to do that. Regardless, you can't blame that on link local addresses, when the printer manufacturer forces you to do something that wasn't intended with IPv6. Or maybe you can blame Firefox. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/08/2019 12.51, James Knott wrote:
On 2019-08-11 06:24 AM, Carlos E. R. wrote:
It does not respond on anything else on IPv6. It is either IPv4, or that lilnk-local addresses.
On some IoT, the only available address for the initial configuration, is the link-local address.
How are those IoT devices configured?
Using Firefox 6. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Carlos E. R. wrote:
On 11/08/2019 12.51, James Knott wrote:
On 2019-08-11 06:24 AM, Carlos E. R. wrote:
It does not respond on anything else on IPv6. It is either IPv4, or that lilnk-local addresses.
On some IoT, the only available address for the initial configuration, is the link-local address.
How are those IoT devices configured?
Using Firefox 6.
It is interesting that those devices only work with ipv6 - if you had a radvd running, you could probably let them have proper addresses, and configure them with any firefox. -- Per Jessen, Zürich (25.2°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 2019-08-10 07:51 PM, Carlos E. R. wrote:
No, the last part at least is not true. My printer IPv6 part only responds on it. HP designed it to be used, till Firefox removed the support.
Does HP have a Windows based utility for accessing the printer? That might be part of the problem. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/08/2019 13.01, James Knott wrote:
On 2019-08-10 07:51 PM, Carlos E. R. wrote:
No, the last part at least is not true. My printer IPv6 part only responds on it. HP designed it to be used, till Firefox removed the support.
Does HP have a Windows based utility for accessing the printer? That might be part of the problem.
It certainly has, but I've never used it. It is easy enough to configure it over Ipv4. The procedure with most IPv4 gadgets is: Device responds on 192.168.1.1 only. This collides with the router address, so it can not be connected to the home network. Configure a laptop to be 192.168.1.2 or similar. Disconnect laptop from LAN. Connect laptop to new device. Configure new device to new address. Reboot it. Change laptop back to LAN address. Connect new device to LAN. Test connectivity. Whereas on IPv6 it would be: Connect device to LAN. Point firefox 6 to link-local address of new device. Configure device as appropriate for lan. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
* Carlos E.R. <robin.listas@gmx.es> [08-11-19 08:32]:
On 11/08/2019 13.01, James Knott wrote:
On 2019-08-10 07:51 PM, Carlos E. R. wrote:
No, the last part at least is not true. My printer IPv6 part only responds on it. HP designed it to be used, till Firefox removed the support.
Does HP have a Windows based utility for accessing the printer? That might be part of the problem.
It certainly has, but I've never used it. It is easy enough to configure it over Ipv4.
The procedure with most IPv4 gadgets is:
Device responds on 192.168.1.1 only. This collides with the router address, so it can not be connected to the home network. Configure a laptop to be 192.168.1.2 or similar. Disconnect laptop from LAN. Connect laptop to new device. Configure new device to new address. Reboot it. Change laptop back to LAN address. Connect new device to LAN. Test connectivity.
Whereas on IPv6 it would be: Connect device to LAN. Point firefox 6 to link-local address of new device. Configure device as appropriate for lan.
instead of jumping thru all those hoops, why wouldn't you install hplip and configure your printer using hp-setup where you can assign the ip addrs you wish? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/08/2019 14.37, Patrick Shanahan wrote:
* Carlos E.R. <robin.listas@gmx.es> [08-11-19 08:32]:
On 11/08/2019 13.01, James Knott wrote:
On 2019-08-10 07:51 PM, Carlos E. R. wrote:
No, the last part at least is not true. My printer IPv6 part only responds on it. HP designed it to be used, till Firefox removed the support.
Does HP have a Windows based utility for accessing the printer? That might be part of the problem.
It certainly has, but I've never used it. It is easy enough to configure it over Ipv4.
The procedure with most IPv4 gadgets is:
Device responds on 192.168.1.1 only. This collides with the router address, so it can not be connected to the home network. Configure a laptop to be 192.168.1.2 or similar. Disconnect laptop from LAN. Connect laptop to new device. Configure new device to new address. Reboot it. Change laptop back to LAN address. Connect new device to LAN. Test connectivity.
Whereas on IPv6 it would be: Connect device to LAN. Point firefox 6 to link-local address of new device. Configure device as appropriate for lan.
instead of jumping thru all those hoops, why wouldn't you install hplip and configure your printer using hp-setup where you can assign the ip addrs you wish?
Telcontar:~ # hplip If 'hplip' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf hplip Telcontar:~ # rpm -q hplip hplip-3.18.6-lp150.4.3.1.x86_64 Telcontar:~ # Telcontar:~ # /usr/bin/hp-devicesettings warning: hp-devicesettings should not be run as root/superuser. HP Linux Imaging and Printing System (ver. 3.18.6) Device Setup Utility ver. 0.1 Copyright (c) 2001-15 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. error: No device found that support this feature. Telcontar:~ # Telcontar:~ # /usr/bin/hp-devicesettings -d 192.168.1.3 warning: hp-devicesettings should not be run as root/superuser. HP Linux Imaging and Printing System (ver. 3.18.6) Device Setup Utility ver. 0.1 Copyright (c) 2001-15 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. error: No device found that supports this feature. Telcontar:~ # If you refer to the printer own web page, it only allows configuration of IPv4, not 6. The "convoluted procedure" is what we all do to configure any new network gadget, not specifically an HP printer. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [08-11-19 13:26]:
On 11/08/2019 14.37, Patrick Shanahan wrote:
* Carlos E.R. <robin.listas@gmx.es> [08-11-19 08:32]:
On 11/08/2019 13.01, James Knott wrote:
On 2019-08-10 07:51 PM, Carlos E. R. wrote:
No, the last part at least is not true. My printer IPv6 part only responds on it. HP designed it to be used, till Firefox removed the support.
Does HP have a Windows based utility for accessing the printer? That might be part of the problem.
It certainly has, but I've never used it. It is easy enough to configure it over Ipv4.
The procedure with most IPv4 gadgets is:
Device responds on 192.168.1.1 only. This collides with the router address, so it can not be connected to the home network. Configure a laptop to be 192.168.1.2 or similar. Disconnect laptop from LAN. Connect laptop to new device. Configure new device to new address. Reboot it. Change laptop back to LAN address. Connect new device to LAN. Test connectivity.
Whereas on IPv6 it would be: Connect device to LAN. Point firefox 6 to link-local address of new device. Configure device as appropriate for lan.
instead of jumping thru all those hoops, why wouldn't you install hplip and configure your printer using hp-setup where you can assign the ip addrs you wish?
Telcontar:~ # hplip If 'hplip' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf hplip Telcontar:~ # rpm -q hplip hplip-3.18.6-lp150.4.3.1.x86_64 Telcontar:~ # Telcontar:~ # /usr/bin/hp-devicesettings warning: hp-devicesettings should not be run as root/superuser.
yes, iirc run only as <user>
HP Linux Imaging and Printing System (ver. 3.18.6) Device Setup Utility ver. 0.1
Copyright (c) 2001-15 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details.
error: No device found that support this feature. Telcontar:~ #
Telcontar:~ # /usr/bin/hp-devicesettings -d 192.168.1.3 warning: hp-devicesettings should not be run as root/superuser.
HP Linux Imaging and Printing System (ver. 3.18.6) Device Setup Utility ver. 0.1
Copyright (c) 2001-15 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details.
error: No device found that supports this feature. Telcontar:~ #
why are you trying to use hp-devicesettings rather than first setting it up using hp-setup ??? fwiw, I also get the same result running hp-devicesettings, but it is not necessary. again, use: hp-setup as I first said. and run as <user>. or don't as you seem not to want to or you just do not want to follow instructions/suggestions. I will not get a bigger hammer. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/08/2019 20.01, Patrick Shanahan wrote:
* Carlos E. R. <> [08-11-19 13:26]:
On 11/08/2019 14.37, Patrick Shanahan wrote:
* Carlos E.R. <> [08-11-19 08:32]:
Telcontar:~ # /usr/bin/hp-devicesettings -d 192.168.1.3 warning: hp-devicesettings should not be run as root/superuser.
HP Linux Imaging and Printing System (ver. 3.18.6) Device Setup Utility ver. 0.1
Copyright (c) 2001-15 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details.
error: No device found that supports this feature. Telcontar:~ #
why are you trying to use hp-devicesettings rather than first setting it up using hp-setup ???
fwiw, I also get the same result running hp-devicesettings, but it is not necessary. again, use: hp-setup
Ok, hp-setup. It wants to setup my printer afresh, ADD a new printer, not re-configure an existing printer. I will not proceed, I risk changing something that already works. <https://susepaste.org/92831694>
as I first said. and run as <user>.
or don't as you seem not to want to or you just do not want to follow instructions/suggestions. I will not get a bigger hammer.
I know what my printer is capable of, and I know its configuration does NOT ALLOW to write an IPv6 address, only and IPv4 address. I have tried several times over the years. Google finds the printer configuration page: <http://150.217.107.174/info_config_network.html?tab=Networking&menu=NetConfig> Amazingly, it is a real printer connected to Internet. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-08-11 02:26 PM, Carlos E. R. wrote:
I know what my printer is capable of, and I know its configuration does NOT ALLOW to write an IPv6 address, only and IPv4 address. I have tried several times over the years.
Again, why do you need manual configuration. If I want something, other than firewall/router or main desktop system to have a specific address, I do that with a mapping on my DHCP server. You can do the same with IPv6. I have been using IPv6 for over 9 years. I have yet to manually address a device on IPv6. It just isn't needed. This isn't like IPv4 where, if you don't have DHCP, you have to configure address, gateway, subnet mask, etc.. Everything works automatically. As for needing to determine an address, I've already provided a couple of methods. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/08/2019 20.36, James Knott wrote:
On 2019-08-11 02:26 PM, Carlos E. R. wrote:
I know what my printer is capable of, and I know its configuration does NOT ALLOW to write an IPv6 address, only and IPv4 address. I have tried several times over the years.
Again, why do you need manual configuration.
So that I can write the name to IP in the /etc/hosts file or my DNS zone file.
If I want something, other than firewall/router or main desktop system to have a specific address, I do that with a mapping on my DHCP server. You can do the same with IPv6.
No, my router does no mapping of IPv6 addresses. I just tried.
I have been using IPv6 for over 9 years. I have yet to manually address a device on IPv6. It just isn't needed. This isn't like IPv4 where, if you don't have DHCP, you have to configure address, gateway, subnet mask, etc.. Everything works automatically. As for needing to determine an address, I've already provided a couple of methods.
It doesn't say the names of the found addresses, what they are. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Carlos E.R. wrote:
On 11/08/2019 13.01, James Knott wrote:
On 2019-08-10 07:51 PM, Carlos E. R. wrote:
No, the last part at least is not true. My printer IPv6 part only responds on it. HP designed it to be used, till Firefox removed the support.
Does HP have a Windows based utility for accessing the printer? That might be part of the problem.
It certainly has, but I've never used it. It is easy enough to configure it over Ipv4.
The procedure with most IPv4 gadgets is:
Device responds on 192.168.1.1 only. This collides with the router address, so it can not be connected to the home network. Configure a laptop to be 192.168.1.2 or similar. Disconnect laptop from LAN. Connect laptop to new device. Configure new device to new address. Reboot it. Change laptop back to LAN address. Connect new device to LAN. Test connectivity.
Whereas on IPv6 it would be: Connect device to LAN. Point firefox 6 to link-local address of new device.
Run radvd on your network, using some fc00 prefix. That'll allow such devices to auto-configure and you won't need the old firefox. Something like this ought to suffice: (not tested) interface eth0 { AdvSendAdvert on; AdvManagedFlag on; AdvOtherConfigFlag on; too RDNSS dns-server { }; DNSSL search-list { }; prefix fc00:1234:5678:9000:1::/64 { AdvOnLink on; AdvAutonomous on; AdvRouterAddr off; }; }; -- Per Jessen, Zürich (26.0°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/08/2019 15.21, Per Jessen wrote:
Carlos E.R. wrote:
On 11/08/2019 13.01, James Knott wrote:
On 2019-08-10 07:51 PM, Carlos E. R. wrote:
No, the last part at least is not true. My printer IPv6 part only responds on it. HP designed it to be used, till Firefox removed the support.
Does HP have a Windows based utility for accessing the printer? That might be part of the problem.
It certainly has, but I've never used it. It is easy enough to configure it over Ipv4.
The procedure with most IPv4 gadgets is:
Device responds on 192.168.1.1 only. This collides with the router address, so it can not be connected to the home network. Configure a laptop to be 192.168.1.2 or similar. Disconnect laptop from LAN. Connect laptop to new device. Configure new device to new address. Reboot it. Change laptop back to LAN address. Connect new device to LAN. Test connectivity.
Whereas on IPv6 it would be: Connect device to LAN. Point firefox 6 to link-local address of new device.
Run radvd on your network, using some fc00 prefix. That'll allow such devices to auto-configure and you won't need the old firefox.
Is that some dhcp alike for version 6? You still have the problem of finding out what IP is the device at. With IPv4 I can use nmap to scan my entire network to find it. Good look with scanning the IPv6 LAN in a reasonable time. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-08-11 01:28 PM, Carlos E. R. wrote:
Is that some dhcp alike for version 6? You still have the problem of finding out what IP is the device at.
There are 2 ways to assign an address with IPv6, SLAAC and DHCPv6. Either will work, provided you have IPv6 up & running on your network. If you know the MAC address, all you have to do is run the command "ip neighbor show". It will show all the devices that have announced their presence with a neighbor advertisement. By looking through the list, you will find the MAC address and associated IP address(es). You can even add grep to that command to isolate only the addresses for that MAC. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/08/2019 19.48, James Knott wrote:
On 2019-08-11 01:28 PM, Carlos E. R. wrote:
Is that some dhcp alike for version 6? You still have the problem of finding out what IP is the device at.
There are 2 ways to assign an address with IPv6, SLAAC and DHCPv6.
dhcp6 is apparently configured in my router, does nothing.
Either will work, provided you have IPv6 up & running on your network. If you know the MAC address, all you have to do is run the command "ip neighbor show". It will show all the devices that have announced their presence with a neighbor advertisement. By looking through the list, you will find the MAC address and associated IP address(es). You can even add grep to that command to isolate only the addresses for that MAC.
Ok, so now I have to know the MAC address of the new device. Will that automatically given v6 address stay fixed, so that I can map names to addresses in my /etc/hosts file? -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-08-11 02:54 PM, Carlos E. R. wrote:
Ok, so now I have to know the MAC address of the new device. Will that automatically given v6 address stay fixed, so that I can map names to addresses in my /etc/hosts file?
How do you find the link local address, if you don't use one of the methods I described? How do you know an IPv4 address, if you didn't configure it? You try different tests to see what's out there. If you know an IPv4 address, do you automatically know the host name? No you don't. You try something like the host command or check your DNS/DHCP server. Geez Carlos, what in the hell is wrong with you today??? Why do you keep trying to create problems where there are none??? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/08/2019 21.01, James Knott wrote:
On 2019-08-11 02:54 PM, Carlos E. R. wrote:
Ok, so now I have to know the MAC address of the new device. Will that automatically given v6 address stay fixed, so that I can map names to addresses in my /etc/hosts file?
How do you find the link local address, if you don't use one of the methods I described?
Printed in the label. And you have not said if the automatically given IPv6 address will stay fixed.
How do you know an IPv4 address, if you didn't configure it?
Comes printed in the documentation.
You try different tests to see what's out there. If you know an IPv4 address, do you automatically know the host name? No you don't. You try something like the host command or check your DNS/DHCP server.
1) I configure the device on a fixed IPv4 address of my choice. Done that for years. The device documentation explains the procedure, too. 2) I write that and a name in my DNS server. 3) Done. Stays that way for ever.
Geez Carlos, what in the hell is wrong with you today??? Why do you keep trying to create problems where there are none???
I don't see it that way, but you trying to convince me of impossible things. :-/ Most of what you say is absurd. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-08-11 03:12 PM, Carlos E. R. wrote:
And you have not said if the automatically given IPv6 address will stay fixed.
That depends on which one you're talking about. With SLAAC, you will get one consistent address based on the MAC address or a random number. With SLAAC, you will also get a new privacy address every day, each of which is valid four 7 days. You'd use the consistent address when you try to connect to a device. The most recent privacy address for outgoing connections.
Most of what you say is absurd.
Well, I'm the one who has been using IPv6 for over 9 years. I am also a Cisco CCNA. In addition, my reference is this book: http://shop.oreilly.com/product/0636920023432.do I have also done a lot of other self study, including examining a *LOT* of packets with Wireshark. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/08/2019 21.28, James Knott wrote:
On 2019-08-11 03:12 PM, Carlos E. R. wrote:
And you have not said if the automatically given IPv6 address will stay fixed.
That depends on which one you're talking about. With SLAAC, you will get one consistent address based on the MAC address or a random number. With SLAAC, you will also get a new privacy address every day, each of which is valid four 7 days. You'd use the consistent address when you try to connect to a device. The most recent privacy address for outgoing connections.
Ok, the MAC based addresses will have to do.
Most of what you say is absurd.
Well, I'm the one who has been using IPv6 for over 9 years. I am also a Cisco CCNA.
Me too.
In addition, my reference is this book: http://shop.oreilly.com/product/0636920023432.do
I have also done a lot of other self study, including examining a *LOT* of packets with Wireshark.
-- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 11/08/2019 21.41, James Knott wrote:
On 2019-08-11 03:38 PM, Carlos E. R. wrote:
I am also a Cisco CCNA. Me too.
Then you should know more about IPv6. It's been part of the CCNA for years.
We did not touch it. Just read about it a bit. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-08-11 04:16 PM, Carlos E. R. wrote:
Then you should know more about IPv6. It's been part of the CCNA for years. We did not touch it. Just read about it a bit.
How long ago did you do your CCNA? It's been part of the test for years. If all you did was read about it a bit, you couldn't have possibly passed that test. Those CCNA tests are tricky, even when you know your material. When you say you're a CCNA, that means you took the test and got the certificate from Cisco. If you don't have that, you're not a CCNA. You also have to retest on it or one of the related tests every 3 years. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/08/2019 22.37, James Knott wrote:
On 2019-08-11 04:16 PM, Carlos E. R. wrote:
Then you should know more about IPv6. It's been part of the CCNA for years. We did not touch it. Just read about it a bit.
How long ago did you do your CCNA? It's been part of the test for years. If all you did was read about it a bit, you couldn't have possibly passed that test. Those CCNA tests are tricky, even when you know your material.
:-D
When you say you're a CCNA, that means you took the test and got the certificate from Cisco. If you don't have that, you're not a CCNA. You also have to retest on it or one of the related tests every 3 years.
Yes, I got the certificate. 2007, just looked at it. I know (from you, on another ocassion) of the need to retest, but they did not told us that. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-08-11 03:12 PM, Carlos E. R. wrote:
And you have not said if the automatically given IPv6 address will stay fixed.
That depends on which one you're talking about. With SLAAC, you will get one consistent address based on the MAC address or a random number. With SLAAC, you will also get a new privacy address every day, each of which is valid four 7 days. You'd use the consistent address when you try to connect to a device. The most recent privacy address for outgoing connections.
Most of what you say is absurd.
Well, I'm the one who has been using IPv6 for over 9 years. I am also a Cisco CCNA. In addition, my reference is this book: http://shop.oreilly.com/product/0636920023432.do I have also done a lot of other self study, including examining a *LOT* of packets with Wireshark. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
On 11/08/2019 21.01, James Knott wrote:
On 2019-08-11 02:54 PM, Carlos E. R. wrote:
Ok, so now I have to know the MAC address of the new device. Will that automatically given v6 address stay fixed, so that I can map names to addresses in my /etc/hosts file?
How do you find the link local address, if you don't use one of the methods I described?
Printed in the label.
When you start using "fc00:what:ever:itis:1", yuo can replace "fe80::" with that prefix.
And you have not said if the automatically given IPv6 address will stay fixed.
Depends on the device.
Most of what you say is absurd.
Really Carlos, it is not. afaict, James knows very well what he is talking about. -- Per Jessen, Zürich (18.4°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/08/2019 21.51, Per Jessen wrote:
Carlos E. R. wrote:
On 11/08/2019 21.01, James Knott wrote:
On 2019-08-11 02:54 PM, Carlos E. R. wrote:
Ok, so now I have to know the MAC address of the new device. Will that automatically given v6 address stay fixed, so that I can map names to addresses in my /etc/hosts file?
How do you find the link local address, if you don't use one of the methods I described?
Printed in the label.
When you start using "fc00:what:ever:itis:1", yuo can replace "fe80::" with that prefix.
And you have not said if the automatically given IPv6 address will stay fixed.
Depends on the device.
Most of what you say is absurd.
Really Carlos, it is not. afaict, James knows very well what he is talking about.
And me too! But you people are fixed in your ways and do not understand what I say. Just read that Bugzilla, it is not me! The are professionals from all over the world. One of them is the LL RFC writer. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-08-11 04:15 PM, Carlos E. R. wrote:
And me too! But you people are fixed in your ways and do not understand what I say. Just read that Bugzilla, it is not me! The are professionals from all over the world. One of them is the LL RFC writer.
This is a Firefox issue, not link local. For whatever reason, browsers have stopped supporting link local addresses. It doesn't mean that link local is broken. It means that browsers no longer support it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/08/2019 22.32, James Knott wrote:
On 2019-08-11 04:15 PM, Carlos E. R. wrote:
And me too! But you people are fixed in your ways and do not understand what I say. Just read that Bugzilla, it is not me! The are professionals from all over the world. One of them is the LL RFC writer.
This is a Firefox issue, not link local. For whatever reason, browsers have stopped supporting link local addresses. It doesn't mean that link local is broken. It means that browsers no longer support it.
All browsers, in every OS, AFAIK. I did not say broken, just useless because browsers do not support it. CUPS also I understand doesn't. You doubted that this lack of support has any importance, and I tried without success to explain it. Just read the Bugzilla instead of me, they say why they need this support, why they use Firefox 6. Some commented on keeping a separate install of FF 6 just for this purpose. That's what I tried to say in most of this thread. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-08-11 05:03 PM, Carlos E. R. wrote:
I did not say broken, just useless because browsers do not support it. CUPS also I understand doesn't.
You doubted that this lack of support has any importance, and I tried without success to explain it. Just read the Bugzilla instead of me, they say why they need this support, why they use Firefox 6. Some commented on keeping a separate install of FF 6 just for this purpose.
That's what I tried to say in most of this thread.
You have said it's useless because browsers don't support it. That was never the intent of it, though it may have been possible at one point. The purpose of the link local addresses is for stuff like router advertisements, gateways, etc., not browsers. It's so that networks can get off the ground, without any configuration. You get IPv6 from your ISP, then your router announces the network prefix and provides it's link local address for the gateway and more. It's all about auto configuration, not browsers. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/08/2019 23.24, James Knott wrote:
On 2019-08-11 05:03 PM, Carlos E. R. wrote:
I did not say broken, just useless because browsers do not support it. CUPS also I understand doesn't.
You doubted that this lack of support has any importance, and I tried without success to explain it. Just read the Bugzilla instead of me, they say why they need this support, why they use Firefox 6. Some commented on keeping a separate install of FF 6 just for this purpose.
That's what I tried to say in most of this thread.
You have said it's useless because browsers don't support it. That was never the intent of it, though it may have been possible at one point. The purpose of the link local addresses is for stuff like router advertisements, gateways, etc., not browsers. It's so that networks can get off the ground, without any configuration. You get IPv6 from your ISP, then your router announces the network prefix and provides it's link local address for the gateway and more. It's all about auto configuration, not browsers.
Well, for many people it has another purpose that doesn't work. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-08-11 01:28 PM, Carlos E. R. wrote:
With IPv4 I can use nmap to scan my entire network to find it. Good look with scanning the IPv6 LAN in a reasonable time.
From man nmap: -6: Enable IPv6 scanning
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/08/2019 19.50, James Knott wrote:
On 2019-08-11 01:28 PM, Carlos E. R. wrote:
With IPv4 I can use nmap to scan my entire network to find it. Good look with scanning the IPv6 LAN in a reasonable time.
From man nmap: -6: Enable IPv6 scanning
And scan millions of addresses? The fc00:: range is huge. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-08-11 02:56 PM, Carlos E. R. wrote:
On 11/08/2019 19.50, James Knott wrote:
On 2019-08-11 01:28 PM, Carlos E. R. wrote:
With IPv4 I can use nmap to scan my entire network to find it. Good look with scanning the IPv6 LAN in a reasonable time. From man nmap: -6: Enable IPv6 scanning And scan millions of addresses? The fc00:: range is huge.
And perhaps nmap is the wrong tool. It's a port scanner. While it can be used to find hosts, it's not the best way to do that. I mentioned using ip neighbor show. It shows all the IP addresses my computer is aware of. I just fired up Wireshark, to watch for ICMP6 packets, which include neighbor advertisements. It appears a device will advertise itself at around every several seconds (varies with device). So, every IPv6 address on the network will appear in the output of ip neighbor show. You will see all the IP addresses and their MAC address. It will not show host names, so you'll have to do some other checks, just like you would in IPv4. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/08/2019 21.13, James Knott wrote:
On 2019-08-11 02:56 PM, Carlos E. R. wrote:
On 11/08/2019 19.50, James Knott wrote:
On 2019-08-11 01:28 PM, Carlos E. R. wrote:
With IPv4 I can use nmap to scan my entire network to find it. Good look with scanning the IPv6 LAN in a reasonable time. From man nmap: -6: Enable IPv6 scanning And scan millions of addresses? The fc00:: range is huge.
And perhaps nmap is the wrong tool. It's a port scanner. While it can be used to find hosts, it's not the best way to do that.
I had to use it with some gadget I have, I forget which now. Ah, yes, my network controllable power socket strip. The procedure is nmap with some options and grep for a particular response (config web page, probably), that identifies the exact gadget in the network. This is basically the procedure that the manufacturer config program does, too (on Windows).
I mentioned using ip neighbor show. It shows all the IP addresses my computer is aware of. I just fired up Wireshark, to watch for ICMP6 packets, which include neighbor advertisements. It appears a device will advertise itself at around every several seconds (varies with device).
Ah. Did not know about mandatory advertisements. My printer is not in the list, though, but the only IPv6 address it has is the link-local.
So, every IPv6 address on the network will appear in the output of ip neighbor show. You will see all the IP addresses and their MAC address. It will not show host names, so you'll have to do some other checks, just like you would in IPv4.
Well, it is something, yes. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-08-11 03:33 PM, Carlos E. R. wrote:
My printer is not in the list, though, but the only IPv6 address it has is the link-local.
Use Wireshark to look for it. If you don't see it, it's not using IPv6. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/08/2019 21.39, James Knott wrote:
On 2019-08-11 03:33 PM, Carlos E. R. wrote:
My printer is not in the list, though, but the only IPv6 address it has is the link-local.
Use Wireshark to look for it. If you don't see it, it's not using IPv6.
It is using IPv6. A LL address only. I have connected to it in the past. You may find the posts where I did it with FF, long ago. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Carlos E. R. wrote:
On 11/08/2019 15.21, Per Jessen wrote:
Run radvd on your network, using some fc00 prefix. That'll allow such devices to auto-configure and you won't need the old firefox.
Is that some dhcp alike for version 6?
radvd is a router advertisement daemon, every router has one. If you run it on a non-router, it'll also work.
You still have the problem of finding out what IP is the device at.
Yes. Given the right setup, that can be solved with dynamic dns updates.
With IPv4 I can use nmap to scan my entire network to find it. Good look with scanning the IPv6 LAN in a reasonable time.
You do a "ping6 ff02::1%eth0" and replace "fe80::" with your prefix. -- Per Jessen, Zürich (18.3°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
With IPv4 I can use nmap to scan my entire network to find it. Good look with scanning the IPv6 LAN in a reasonable time.
You do a "ping6 ff02::1%eth0" and replace "fe80::" with your prefix.
Scratch that - see what James wrote, 'ip neigh show'. -- Per Jessen, Zürich (18.3°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/08/2019 20.53, Per Jessen wrote:
Carlos E. R. wrote:
On 11/08/2019 15.21, Per Jessen wrote:
Run radvd on your network, using some fc00 prefix. That'll allow such devices to auto-configure and you won't need the old firefox.
Is that some dhcp alike for version 6?
radvd is a router advertisement daemon, every router has one. If you run it on a non-router, it'll also work.
I'm sorry, no idea what that thing does. My router has it, apparently configured by the ISP, but no idea what it does.
You still have the problem of finding out what IP is the device at.
Yes. Given the right setup, that can be solved with dynamic dns updates.
Apparently, my router does not do it for IPv6. What I have found today is "ip neighbour show". It does not show my printer IPv6 address, though, it shows other fe80's.
With IPv4 I can use nmap to scan my entire network to find it. Good look with scanning the IPv6 LAN in a reasonable time.
You do a "ping6 ff02::1%eth0" and replace "fe80::" with your prefix.
Is that a broadcast, or pinging a single host? I don't understand how I can use that to find a particular device of unknown address. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-08-11 03:04 PM, Carlos E. R. wrote:
What I have found today is "ip neighbour show". It does not show my printer IPv6 address, though, it shows other fe80's.
Fire up Wireshark and filter on ICMP6. It will show neighbor and router advertisements & solicitations. If you don't see your printer, it is not even using the link local address, as the advertisements are mandatory. Those advertisements are an essential part of how IPv6 works. On IPv4, you have to use ARP to map an IP address with a MAC. You don't have to with IPv6, as the advertisements always happen. However, you can trigger the advertisement sooner, by using solicitations. There is no similar mechanism in IPv4 to identify routers, other than perhaps multicast ping. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/08/2019 21.20, James Knott wrote:
On 2019-08-11 03:04 PM, Carlos E. R. wrote:
What I have found today is "ip neighbour show". It does not show my printer IPv6 address, though, it shows other fe80's.
Fire up Wireshark and filter on ICMP6. It will show neighbor and router advertisements & solicitations. If you don't see your printer, it is not even using the link local address, as the advertisements are mandatory.
First try this afternoon: Telcontar:~ # ip neighbour show 192.168.1.57 dev eth0 lladdr 44:09:b8:42:c9:44 STALE 192.168.1.16 dev eth0 lladdr 4c:cc:6a:61:50:a1 REACHABLE 192.168.1.1 dev eth0 lladdr f8:8e:85:64:78:f2 REACHABLE 192.168.1.2 dev eth0 lladdr 00:01:02:03:04:05 REACHABLE 192.168.1.3 dev eth0 lladdr 00:1e:0b:08:4c:cb STALE <============ 192.168.1.126 dev eth0 lladdr a0:d3:7a:a5:1d:4c STALE 192.168.1.8 dev eth0 lladdr 88:b6:27:01:72:63 STALE fe80::fa8e:85ff:fe64:78f2 dev eth0 lladdr f8:8e:85:64:78:f2 router STALE fe80::4ecc:6aff:fe61:50a1 dev eth0 lladdr 4c:cc:6a:61:50:a1 STALE fc00::16 dev eth0 lladdr 4c:cc:6a:61:50:a1 STALE Telcontar:~ # It did not show on IPv6. Later, after looking at its config page with firefox: Telcontar:~ # ip neighbour show | grep -i 4C:CB 192.168.1.3 dev eth0 lladdr 00:1e:0b:08:4c:cb STALE fe80::21e:bff:fe08:4ccb dev eth0 lladdr 00:1e:0b:08:4c:cb STALE Telcontar:~ # Telcontar:~ # ping -c 2 FE80::21E:BFF:FE08:4CCB%eth0 PING FE80::21E:BFF:FE08:4CCB%eth0(fe80::21e:bff:fe08:4ccb%eth0) 56 data bytes 64 bytes from fe80::21e:bff:fe08:4ccb%eth0: icmp_seq=1 ttl=64 time=0.352 ms 64 bytes from fe80::21e:bff:fe08:4ccb%eth0: icmp_seq=2 ttl=64 time=0.351 ms --- FE80::21E:BFF:FE08:4CCB%eth0 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1026ms rtt min/avg/max/mdev = 0.351/0.351/0.352/0.018 ms Telcontar:~ # Telcontar:~ # ip neighbour show | grep -i 4C:CB 192.168.1.3 dev eth0 lladdr 00:1e:0b:08:4c:cb STALE fe80::21e:bff:fe08:4ccb dev eth0 lladdr 00:1e:0b:08:4c:cb REACHABLE Telcontar:~ # Telcontar:~ # arp | grep -i 4C:CB bilbo.valinor ether 00:1e:0b:08:4c:cb C eth0 Telcontar:~ #
Those advertisements are an essential part of how IPv6 works. On IPv4, you have to use ARP to map an IP address with a MAC. You don't have to with IPv6, as the advertisements always happen. However, you can trigger the advertisement sooner, by using solicitations. There is no similar mechanism in IPv4 to identify routers, other than perhaps multicast ping.
Good, but this printer is not doing it, apparently. Call the police? :-D I think it may do some own HP broadcast instead, I have noticed it in logs. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Carlos E. R. wrote:
On 11/08/2019 21.20, James Knott wrote:
On 2019-08-11 03:04 PM, Carlos E. R. wrote:
What I have found today is "ip neighbour show". It does not show my printer IPv6 address, though, it shows other fe80's.
Fire up Wireshark and filter on ICMP6. It will show neighbor and router advertisements & solicitations. If you don't see your printer, it is not even using the link local address, as the advertisements are mandatory.
First try this afternoon:
Telcontar:~ # ip neighbour show 192.168.1.57 dev eth0 lladdr 44:09:b8:42:c9:44 STALE 192.168.1.16 dev eth0 lladdr 4c:cc:6a:61:50:a1 REACHABLE 192.168.1.1 dev eth0 lladdr f8:8e:85:64:78:f2 REACHABLE 192.168.1.2 dev eth0 lladdr 00:01:02:03:04:05 REACHABLE 192.168.1.3 dev eth0 lladdr 00:1e:0b:08:4c:cb STALE <============ 192.168.1.126 dev eth0 lladdr a0:d3:7a:a5:1d:4c STALE 192.168.1.8 dev eth0 lladdr 88:b6:27:01:72:63 STALE fe80::fa8e:85ff:fe64:78f2 dev eth0 lladdr f8:8e:85:64:78:f2 router STALE fe80::4ecc:6aff:fe61:50a1 dev eth0 lladdr 4c:cc:6a:61:50:a1 STALE fc00::16 dev eth0 lladdr 4c:cc:6a:61:50:a1 STALE Telcontar:~ #
It did not show on IPv6.
fe80::fa8e:85ff:fe64:78f2 is 192.168.1.1 fe80::4ecc:6aff:fe61:50a1 is 192.168.1.16 fc00::16 is also 192.168.1.16 Didn't you say your printer has a fixed ipv4 of 192.168.1.1 ? -- Per Jessen, Zürich (18.9°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/08/2019 21.56, Per Jessen wrote:
Carlos E. R. wrote:
On 11/08/2019 21.20, James Knott wrote:
On 2019-08-11 03:04 PM, Carlos E. R. wrote:
What I have found today is "ip neighbour show". It does not show my printer IPv6 address, though, it shows other fe80's.
Fire up Wireshark and filter on ICMP6. It will show neighbor and router advertisements & solicitations. If you don't see your printer, it is not even using the link local address, as the advertisements are mandatory.
First try this afternoon:
Telcontar:~ # ip neighbour show 192.168.1.57 dev eth0 lladdr 44:09:b8:42:c9:44 STALE 192.168.1.16 dev eth0 lladdr 4c:cc:6a:61:50:a1 REACHABLE 192.168.1.1 dev eth0 lladdr f8:8e:85:64:78:f2 REACHABLE 192.168.1.2 dev eth0 lladdr 00:01:02:03:04:05 REACHABLE 192.168.1.3 dev eth0 lladdr 00:1e:0b:08:4c:cb STALE <============ 192.168.1.126 dev eth0 lladdr a0:d3:7a:a5:1d:4c STALE 192.168.1.8 dev eth0 lladdr 88:b6:27:01:72:63 STALE fe80::fa8e:85ff:fe64:78f2 dev eth0 lladdr f8:8e:85:64:78:f2 router STALE fe80::4ecc:6aff:fe61:50a1 dev eth0 lladdr 4c:cc:6a:61:50:a1 STALE fc00::16 dev eth0 lladdr 4c:cc:6a:61:50:a1 STALE Telcontar:~ #
It did not show on IPv6.
fe80::fa8e:85ff:fe64:78f2 is 192.168.1.1 fe80::4ecc:6aff:fe61:50a1 is 192.168.1.16 fc00::16 is also 192.168.1.16
Didn't you say your printer has a fixed ipv4 of 192.168.1.1 ?
No. I said that most new devices come from factory with that address, till you change it. That has been the procedure for many years. I have configured that printer several years ago, so it has .3 The procedure I have read for IPv6 devices is to reach their link-local addresses for configuration, because it is known and never changes. That's what this is all about, that the procedure only works with Firefox till version 6. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On Sun, 11 Aug 2019 22:05:40 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
I said that most new devices come from factory with that address, till you change it. That has been the procedure for many years.
Your experience differs from mine then. Most devices (all, IIRC) that I attach to my network get an IP4 address by sending a DHCP request which is answered by my router. I can then discover what address has been assigned by looking at the router's web page, and change it or assign it a static address if I desire. I believe some of the recent IoT devices can also be told to configure themselves to present a wireless AP, which you then connect to with a phone or whatever and tell it about your local environment. You then reboot it and it connects to your network. I haven't ever come across any device that comes up with a fixed address, except for routers which always do IME, and usually but not always as 192.168.1.1. The Fritz!Box comes up as 192.168.178.1 initially, for example. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/08/2019 22.36, Dave Howorth wrote:
On Sun, 11 Aug 2019 22:05:40 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
I said that most new devices come from factory with that address, till you change it. That has been the procedure for many years.
Your experience differs from mine then. Most devices (all, IIRC) that I attach to my network get an IP4 address by sending a DHCP request which is answered by my router. I can then discover what address has been assigned by looking at the router's web page, and change it or assign it a static address if I desire.
I believe some of the recent IoT devices can also be told to configure themselves to present a wireless AP, which you then connect to with a phone or whatever and tell it about your local environment. You then reboot it and it connects to your network.
I haven't ever come across any device that comes up with a fixed address, except for routers which always do IME, and usually but not always as 192.168.1.1. The Fritz!Box comes up as 192.168.178.1 initially, for example.
Well, most of the devices I configure are routers, that may explain why most of those I get come with a fixed address. But also some other devices. Switches, perhaps? One IoT gadget came configured for dhcp, then the Windows app searches for it poking at every IP for a particular response. In Linux, nmap can do similar, if you know the expected response (but they don't explain this). The Chromebook configures via Bluetooth and a WiFi access point it sets up. The BT for identification at least, it prints an ID code on the TV. Then it gets configuration details for the local WiFI out from your own phone, and switches to it. But it does not say what IP it gets, that I had to find out myself somehow. That HP printer also has an LCD panel where we can write an IPv4 address directly. It is the only gadget I have (besides computers/tablets/phones) that says IPv6 supported. Probably the Chromebook too. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-08-11 05:13 PM, Carlos E. R. wrote:
Well, most of the devices I configure are routers, that may explain why most of those I get come with a fixed address. But also some other devices. Switches, perhaps?
That depends on the switch. Consumer grade managed switches generally use DHCP. Industrial grade, from Cisco, Adtran, etc. don't even come with IP enabled. You have to use the serial console, to enable IP, assign addresses, etc. But then you know that from your CCNA. Also, I use firewall/router software called pfSense. While it uses link local addresses, it does not use MAC based addresses. Instead, it's link local address on my LAN is fe80::1:1. I also have a test LAN with the address fe80::1:1. How is that possible? Well, on link local, the full address includes the interface. So, my LAN is actually fe80::1:1%bge0 and test LAN, fe80::1:1%em0. So, you don't always know what the link local address will be, until you power things up. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/08/2019 23.39, James Knott wrote:
On 2019-08-11 05:13 PM, Carlos E. R. wrote:
Well, most of the devices I configure are routers, that may explain why most of those I get come with a fixed address. But also some other devices. Switches, perhaps?
That depends on the switch. Consumer grade managed switches generally use DHCP. Industrial grade, from Cisco, Adtran, etc. don't even come with IP enabled. You have to use the serial console, to enable IP, assign addresses, etc. But then you know that from your CCNA.
There are some middle range switches, which are those I manage, which use a management IP instead. I have seen Cisco routers with a serial console, yes. But none in "real life". Smaller sites.
Also, I use firewall/router software called pfSense. While it uses link local addresses, it does not use MAC based addresses. Instead, it's link local address on my LAN is fe80::1:1. I also have a test LAN with the address fe80::1:1. How is that possible? Well, on link local, the full address includes the interface. So, my LAN is actually fe80::1:1%bge0 and test LAN, fe80::1:1%em0. So, you don't always know what the link local address will be, until you power things up.
-- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 08/11/2019 03:36 PM, Dave Howorth wrote:
Your experience differs from mine then. Most devices (all, IIRC) that I attach to my network get an IP4 address by sending a DHCP request which is answered by my router. I can then discover what address has been assigned by looking at the router's web page, and change it or assign it a static address if I desire.
I believe some of the recent IoT devices can also be told to configure themselves to present a wireless AP, which you then connect to with a phone or whatever and tell it about your local environment. You then reboot it and it connects to your network.
I haven't ever come across any device that comes up with a fixed address, except for routers which always do IME, and usually but not always as 192.168.1.1. The Fritz!Box comes up as 192.168.178.1 initially, for example.
(side note:...) This is why I have always configured a local server for each LAN running ISC dhcpd and bind with dhcp providing dynamic updates to bind. dhcpd is incredibly flexible handling MAC based fixed IP handout or a generic addresses from a range of IPs it hands out on request otherwise. (it has gotten much more capable, but my use of it hasn't changed in a number of years which just barely scratches the surface using simple TSIG auth for zone updates, etc..) It also lets me handle the whole process one-step removed from my router on the LAN side which I've liked for security reasons given the questionable security built into consumer grade routers, etc.. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
On 11/08/2019 20.53, Per Jessen wrote:
Carlos E. R. wrote:
On 11/08/2019 15.21, Per Jessen wrote:
Run radvd on your network, using some fc00 prefix. That'll allow such devices to auto-configure and you won't need the old firefox.
Is that some dhcp alike for version 6?
radvd is a router advertisement daemon, every router has one. If you run it on a non-router, it'll also work.
I'm sorry, no idea what that thing does.
I appreciate that - radvd issues "router advertisements" in response to "router solicitations", that is all. Every IPv6 device on your network will send out "router solicitations" to figure out what the prefix is and how to get out. Maybe be a little careful - devices that prefer ipv6 could end up stuck I think. For /etc/radvd.conf, there is a "clients {};" clause, to restrict to certain clients only.
My router has it, apparently configured by the ISP, but no idea what it does.
But when your ISP does not support it, that is of no use. I hope you don't see any "router advertisements" on your network.
You still have the problem of finding out what IP is the device at.
Yes. Given the right setup, that can be solved with dynamic dns updates.
Apparently, my router does not do it for IPv6.
Which makes sense when it does not have an ipv6 prefix.
With IPv4 I can use nmap to scan my entire network to find it. Good look with scanning the IPv6 LAN in a reasonable time.
You do a "ping6 ff02::1%eth0" and replace "fe80::" with your prefix.
Is that a broadcast, or pinging a single host? I don't understand how I can use that to find a particular device of unknown address.
Yes, ffxx addresses are multicast addresses. ff02::1 is "every node on the local network". -- Per Jessen, Zürich (18.4°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 11/08/2019 21.21, Per Jessen wrote:
Carlos E. R. wrote:
On 11/08/2019 20.53, Per Jessen wrote:
Carlos E. R. wrote:
On 11/08/2019 15.21, Per Jessen wrote:
Run radvd on your network, using some fc00 prefix. That'll allow such devices to auto-configure and you won't need the old firefox.
Is that some dhcp alike for version 6?
radvd is a router advertisement daemon, every router has one. If you run it on a non-router, it'll also work.
I'm sorry, no idea what that thing does.
I appreciate that - radvd issues "router advertisements" in response to "router solicitations", that is all. Every IPv6 device on your network will send out "router solicitations" to figure out what the prefix is and how to get out.
Ah, ok.
Maybe be a little careful - devices that prefer ipv6 could end up stuck I think. For /etc/radvd.conf, there is a "clients {};" clause, to restrict to certain clients only.
My router has it, apparently configured by the ISP, but no idea what it does.
But when your ISP does not support it, that is of no use. I hope you don't see any "router advertisements" on your network.
Not for IPv6.
You still have the problem of finding out what IP is the device at.
Yes. Given the right setup, that can be solved with dynamic dns updates.
Apparently, my router does not do it for IPv6.
Which makes sense when it does not have an ipv6 prefix.
Different thing. My router does IPv6, but it has no outside connection. Still, the configuration page MAC to IPs should be there for IPv6, same as other IPv6 pages, and it isn't.
With IPv4 I can use nmap to scan my entire network to find it. Good look with scanning the IPv6 LAN in a reasonable time.
You do a "ping6 ff02::1%eth0" and replace "fe80::" with your prefix.
Is that a broadcast, or pinging a single host? I don't understand how I can use that to find a particular device of unknown address.
Yes, ffxx addresses are multicast addresses. ff02::1 is "every node on the local network".
Ah, ok. Telcontar:~ # ping -c 2 FE80::1%eth0 PING FE80::1%eth0(fe80::1%eth0) 56 data bytes From fe80::221:85ff:fe16:2d0b%eth0 icmp_seq=1 Destination unreachable: Address unreachable From fe80::221:85ff:fe16:2d0b%eth0 icmp_seq=2 Destination unreachable: Address unreachable --- FE80::1%eth0 ping statistics --- 2 packets transmitted, 0 received, +2 errors, 100% packet loss, time 1030ms Telcontar:~ # No idea who fe80::221:85ff:... is. Not in "ip neighbour show" Telcontar:~ # arp | grep -i fe:16 Telcontar:~ # Telcontar:~ # ping -c 2 fc00::16 PING fc00::16(fc00::16) 56 data bytes 64 bytes from fc00::16: icmp_seq=1 ttl=64 time=0.389 ms 64 bytes from fc00::16: icmp_seq=2 ttl=64 time=0.446 ms --- fc00::16 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1029ms rtt min/avg/max/mdev = 0.389/0.417/0.446/0.035 ms Telcontar:~ # Telcontar:~ # ping -c 2 fc00::1 PING fc00::1(fc00::1) 56 data bytes From fc00::14 icmp_seq=1 Destination unreachable: Address unreachable From fc00::14 icmp_seq=2 Destination unreachable: Address unreachable --- fc00::1 ping statistics --- 2 packets transmitted, 0 received, +2 errors, 100% packet loss, time 1007ms Telcontar:~ # Telcontar:~ # ping -c2 ff02::1 connect: Invalid argument Telcontar:~ # Doesn't seem to work :-? -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Carlos E. R. wrote:
Still, the configuration page MAC to IPs should be there for IPv6, same as other IPv6 pages, and it isn't.
I'm not sure what that is about - static allocations?
Telcontar:~ # ping -c 2 FE80::1%eth0 PING FE80::1%eth0(fe80::1%eth0) 56 data bytes From fe80::221:85ff:fe16:2d0b%eth0 icmp_seq=1 Destination unreachable: Address unreachable From fe80::221:85ff:fe16:2d0b%eth0 icmp_seq=2 Destination unreachable: Address unreachable
--- FE80::1%eth0 ping statistics --- 2 packets transmitted, 0 received, +2 errors, 100% packet loss, time 1030ms
No idea who fe80::221:85ff:... is. Not in "ip neighbour show"
Your own machine, "telcontar" ?
Telcontar:~ # ping -c2 ff02::1 connect: Invalid argument Telcontar:~ #
Doesn't seem to work :-?
You need to specify which network, ie. which interface - ping -c2 ff02::1%eth0 -- Per Jessen, Zürich (15.4°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 12/08/2019 09.09, Per Jessen wrote:
Carlos E. R. wrote:
Still, the configuration page MAC to IPs should be there for IPv6, same as other IPv6 pages, and it isn't.
I'm not sure what that is about - static allocations?
Telcontar:~ # ping -c 2 FE80::1%eth0 PING FE80::1%eth0(fe80::1%eth0) 56 data bytes From fe80::221:85ff:fe16:2d0b%eth0 icmp_seq=1 Destination unreachable: Address unreachable From fe80::221:85ff:fe16:2d0b%eth0 icmp_seq=2 Destination unreachable: Address unreachable
--- FE80::1%eth0 ping statistics --- 2 packets transmitted, 0 received, +2 errors, 100% packet loss, time 1030ms
No idea who fe80::221:85ff:... is. Not in "ip neighbour show"
Your own machine, "telcontar" ?
That one is fe80::221:85ff:fe16:2d0b - so yes, it is.
Telcontar:~ # ping -c2 ff02::1 connect: Invalid argument Telcontar:~ #
Doesn't seem to work :-?
You need to specify which network, ie. which interface -
ping -c2 ff02::1%eth0
Which I tried before and failed. First paragraph above. As that did not work, I tried the other way. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Carlos E. R. wrote:
On 12/08/2019 09.09, Per Jessen wrote:
Telcontar:~ # ping -c2 ff02::1 connect: Invalid argument Telcontar:~ #
Doesn't seem to work :-?
You need to specify which network, ie. which interface -
ping -c2 ff02::1%eth0
Which I tried before and failed. First paragraph above.
I see no such attempt in what you posted. What I do see is "ping -c 2 FE80::1%eth0" ..... Here ia snippet from my system: ping6 -c2 ff02::1%eth0 PING ff02::1(ff02::1) from fe80::221:86ff:fe4f:8ac4 eth0: 56 data bytes 64 bytes from fe80::221:86ff:fe4f:8ac4: icmp_seq=1 ttl=64 time=0.038 ms 64 bytes from fe80::214:c2ff:fe0d:247a: icmp_seq=1 ttl=64 time=0.155 ms (DUP!) 64 bytes from fe80::215:17ff:fe2c:607: icmp_seq=1 ttl=64 time=0.266 ms (DUP!) 64 bytes from fe80::215:60ff:fe57:7f1: icmp_seq=1 ttl=64 time=0.275 ms (DUP!) 64 bytes from fe80::17: icmp_seq=1 ttl=64 time=0.283 ms (DUP!) 64 bytes from fe80::230:48ff:fe76:7d94: icmp_seq=1 ttl=64 time=0.289 ms (DUP!) 64 bytes from fe80::216:3eff:fe11:1107: icmp_seq=1 ttl=64 time=0.750 ms (DUP!) 64 bytes from fe80::21f:33ff:fef7:9cd1: icmp_seq=1 ttl=64 time=0.777 ms (DUP!) 64 bytes from fe80::216:3eff:fe11:1106: icmp_seq=1 ttl=64 time=0.866 ms (DUP!) 64 bytes from fe80::216:3eff:fe11:1108: icmp_seq=1 ttl=64 time=0.874 ms (DUP!) 64 bytes from fe80::216:3eff:fe11:1105: icmp_seq=1 ttl=64 time=0.887 ms (DUP!) 64 bytes from fe80::20b:cdff:fe41:f68d: icmp_seq=1 ttl=64 time=0.348 ms (DUP!) 64 bytes from fe80::214:5eff:fe1b:556a: icmp_seq=1 ttl=64 time=0.379 ms (DUP!) 64 bytes from fe80::217:a4ff:fef8:cc86: icmp_seq=1 ttl=64 time=0.387 ms (DUP!) 64 bytes from fe80::1: icmp_seq=1 ttl=64 time=0.394 ms (DUP!) 64 bytes from fe80::212:79ff:fecf:4b31: icmp_seq=1 ttl=64 time=0.401 ms (DUP!) 64 bytes from fe80::201:80ff:fe3f:be48: icmp_seq=1 ttl=64 time=0.411 ms (DUP!) 64 bytes from fe80::208:2ff:fe58:7fac: icmp_seq=1 ttl=64 time=0.445 ms (DUP!) 64 bytes from fe80::20b:cdff:fe0e:6db1: icmp_seq=1 ttl=64 time=0.453 ms (DUP!) 64 bytes from fe80::21e:bff:fed9:7aac: icmp_seq=1 ttl=64 time=0.460 ms (DUP!) 64 bytes from fe80::215:17ff:fe2c:5f9: icmp_seq=1 ttl=64 time=0.467 ms (DUP!) 64 bytes from fe80::211:aff:fe59:5114: icmp_seq=1 ttl=64 time=0.545 ms (DUP!) [snip] -- Per Jessen, Zürich (15.8°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/08/2019 11.04, Per Jessen wrote:
Carlos E. R. wrote:
On 12/08/2019 09.09, Per Jessen wrote:
Telcontar:~ # ping -c2 ff02::1 connect: Invalid argument Telcontar:~ #
Doesn't seem to work :-?
You need to specify which network, ie. which interface -
ping -c2 ff02::1%eth0
Which I tried before and failed. First paragraph above.
I see no such attempt in what you posted. What I do see is "ping -c 2 FE80::1%eth0" .....
Need new set of eyes.
Here ia snippet from my system:
ping6 -c2 ff02::1%eth0 PING ff02::1(ff02::1) from fe80::221:86ff:fe4f:8ac4 eth0: 56 data bytes 64 bytes from fe80::221:86ff:fe4f:8ac4: icmp_seq=1 ttl=64 time=0.038 ms 64 bytes from fe80::214:c2ff:fe0d:247a: icmp_seq=1 ttl=64 time=0.155 ms (DUP!) 64 bytes from fe80::215:17ff:fe2c:607: icmp_seq=1 ttl=64 time=0.266 ms (DUP!) 64 bytes from fe80::215:60ff:fe57:7f1: icmp_seq=1 ttl=64 time=0.275 ms (DUP!) 64 bytes from fe80::17: icmp_seq=1 ttl=64 time=0.283 ms (DUP!) 64 bytes from fe80::230:48ff:fe76:7d94: icmp_seq=1 ttl=64 time=0.289 ms (DUP!) 64 bytes from fe80::216:3eff:fe11:1107: icmp_seq=1 ttl=64 time=0.750 ms (DUP!) 64 bytes from fe80::21f:33ff:fef7:9cd1: icmp_seq=1 ttl=64 time=0.777 ms (DUP!) 64 bytes from fe80::216:3eff:fe11:1106: icmp_seq=1 ttl=64 time=0.866 ms (DUP!) 64 bytes from fe80::216:3eff:fe11:1108: icmp_seq=1 ttl=64 time=0.874 ms (DUP!) 64 bytes from fe80::216:3eff:fe11:1105: icmp_seq=1 ttl=64 time=0.887 ms (DUP!) 64 bytes from fe80::20b:cdff:fe41:f68d: icmp_seq=1 ttl=64 time=0.348 ms (DUP!) 64 bytes from fe80::214:5eff:fe1b:556a: icmp_seq=1 ttl=64 time=0.379 ms (DUP!) 64 bytes from fe80::217:a4ff:fef8:cc86: icmp_seq=1 ttl=64 time=0.387 ms (DUP!) 64 bytes from fe80::1: icmp_seq=1 ttl=64 time=0.394 ms (DUP!) 64 bytes from fe80::212:79ff:fecf:4b31: icmp_seq=1 ttl=64 time=0.401 ms (DUP!) 64 bytes from fe80::201:80ff:fe3f:be48: icmp_seq=1 ttl=64 time=0.411 ms (DUP!) 64 bytes from fe80::208:2ff:fe58:7fac: icmp_seq=1 ttl=64 time=0.445 ms (DUP!) 64 bytes from fe80::20b:cdff:fe0e:6db1: icmp_seq=1 ttl=64 time=0.453 ms (DUP!) 64 bytes from fe80::21e:bff:fed9:7aac: icmp_seq=1 ttl=64 time=0.460 ms (DUP!) 64 bytes from fe80::215:17ff:fe2c:5f9: icmp_seq=1 ttl=64 time=0.467 ms (DUP!) 64 bytes from fe80::211:aff:fe59:5114: icmp_seq=1 ttl=64 time=0.545 ms (DUP!) [snip]
Ah, ok. cer@Telcontar:~> ping -c2 ff02::1%eth0 PING ff02::1%eth0(ff02::1%eth0) 56 data bytes 64 bytes from fe80::221:85ff:fe16:2d0b%eth0: icmp_seq=1 ttl=64 time=0.043 ms 64 bytes from fe80::221:85ff:fe16:2d0b%eth0: icmp_seq=2 ttl=64 time=0.051 ms --- ff02::1%eth0 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1011ms rtt min/avg/max/mdev cer@Telcontar:~> -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 11/08/2019 15.21, Per Jessen wrote:
Carlos E.R. wrote:
On 11/08/2019 13.01, James Knott wrote:
On 2019-08-10 07:51 PM, Carlos E. R. wrote:
No, the last part at least is not true. My printer IPv6 part only responds on it. HP designed it to be used, till Firefox removed the support.
Does HP have a Windows based utility for accessing the printer? That might be part of the problem.
It certainly has, but I've never used it. It is easy enough to configure it over Ipv4.
The procedure with most IPv4 gadgets is:
Device responds on 192.168.1.1 only. This collides with the router address, so it can not be connected to the home network. Configure a laptop to be 192.168.1.2 or similar. Disconnect laptop from LAN. Connect laptop to new device. Configure new device to new address. Reboot it. Change laptop back to LAN address. Connect new device to LAN. Test connectivity.
Whereas on IPv6 it would be: Connect device to LAN. Point firefox 6 to link-local address of new device.
Run radvd on your network, using some fc00 prefix. That'll allow such devices to auto-configure and you won't need the old firefox.
Still what some of the comments on the firefox bugzilla describe is reaching to an IPv6 only device which is configured for an unknown address prefix/range. The link-local address allows to still connect to it, for examination and/or reconfiguration. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Carlos E. R. wrote:
On 11/08/2019 15.21, Per Jessen wrote:
Carlos E.R. wrote:
On 11/08/2019 13.01, James Knott wrote:
On 2019-08-10 07:51 PM, Carlos E. R. wrote:
No, the last part at least is not true. My printer IPv6 part only responds on it. HP designed it to be used, till Firefox removed the support.
Does HP have a Windows based utility for accessing the printer? That might be part of the problem.
It certainly has, but I've never used it. It is easy enough to configure it over Ipv4.
The procedure with most IPv4 gadgets is:
Device responds on 192.168.1.1 only. This collides with the router address, so it can not be connected to the home network. Configure a laptop to be 192.168.1.2 or similar. Disconnect laptop from LAN. Connect laptop to new device. Configure new device to new address. Reboot it. Change laptop back to LAN address. Connect new device to LAN. Test connectivity.
Whereas on IPv6 it would be: Connect device to LAN. Point firefox 6 to link-local address of new device.
Run radvd on your network, using some fc00 prefix. That'll allow such devices to auto-configure and you won't need the old firefox.
Still what some of the comments on the firefox bugzilla describe is reaching to an IPv6 only device which is configured for an unknown address prefix/range. The link-local address allows to still connect to it, for examination and/or reconfiguration.
I'm not sure I quite get it - how can the prefix be unknown, especially if you have configured it yourself? I'm not so interested in the firefox issues, I have a strong suspicion they are all due to an improperly configured IPv6 environment. -- Per Jessen, Zürich (18.2°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/08/2019 21.08, Per Jessen wrote:
Carlos E. R. wrote:
On 11/08/2019 15.21, Per Jessen wrote:
Carlos E.R. wrote:
On 11/08/2019 13.01, James Knott wrote:
On 2019-08-10 07:51 PM, Carlos E. R. wrote:
No, the last part at least is not true. My printer IPv6 part only responds on it. HP designed it to be used, till Firefox removed the support.
Does HP have a Windows based utility for accessing the printer? That might be part of the problem.
It certainly has, but I've never used it. It is easy enough to configure it over Ipv4.
The procedure with most IPv4 gadgets is:
Device responds on 192.168.1.1 only. This collides with the router address, so it can not be connected to the home network. Configure a laptop to be 192.168.1.2 or similar. Disconnect laptop from LAN. Connect laptop to new device. Configure new device to new address. Reboot it. Change laptop back to LAN address. Connect new device to LAN. Test connectivity.
Whereas on IPv6 it would be: Connect device to LAN. Point firefox 6 to link-local address of new device.
Run radvd on your network, using some fc00 prefix. That'll allow such devices to auto-configure and you won't need the old firefox.
Still what some of the comments on the firefox bugzilla describe is reaching to an IPv6 only device which is configured for an unknown address prefix/range. The link-local address allows to still connect to it, for examination and/or reconfiguration.
I'm not sure I quite get it - how can the prefix be unknown, especially if you have configured it yourself?
Huh? Ah. Because we did not configure that particular gadget, for instance.
I'm not so interested in the firefox issues, I have a strong suspicion they are all due to an improperly configured IPv6 environment.
I think you simply do not understand the issue. Please read the bugzilla instead, I did not write it, perhaps you understand them better than me. <https://bugzilla.mozilla.org/show_bug.cgi?id=700999> It has 45 entries. For instance: 34, 37, 29, 10 17, 32 -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Carlos E. R. wrote:
On 11/08/2019 21.08, Per Jessen wrote:
Carlos E. R. wrote:
On 11/08/2019 15.21, Per Jessen wrote:
Carlos E.R. wrote:
On 11/08/2019 13.01, James Knott wrote:
On 2019-08-10 07:51 PM, Carlos E. R. wrote: > No, the last part at least is not true. My printer IPv6 part > only responds on it. HP designed it to be used, till Firefox > removed the support.
Does HP have a Windows based utility for accessing the printer? That might be part of the problem.
It certainly has, but I've never used it. It is easy enough to configure it over Ipv4.
The procedure with most IPv4 gadgets is:
Device responds on 192.168.1.1 only. This collides with the router address, so it can not be connected to the home network. Configure a laptop to be 192.168.1.2 or similar. Disconnect laptop from LAN. Connect laptop to new device. Configure new device to new address. Reboot it. Change laptop back to LAN address. Connect new device to LAN. Test connectivity.
Whereas on IPv6 it would be: Connect device to LAN. Point firefox 6 to link-local address of new device.
Run radvd on your network, using some fc00 prefix. That'll allow such devices to auto-configure and you won't need the old firefox.
Still what some of the comments on the firefox bugzilla describe is reaching to an IPv6 only device which is configured for an unknown address prefix/range. The link-local address allows to still connect to it, for examination and/or reconfiguration.
I'm not sure I quite get it - how can the prefix be unknown, especially if you have configured it yourself?
Huh?
Ah. Because we did not configure that particular gadget, for instance.
Sure, but when you have configured a local prefix, "fc00:what:ever:itis" and allowed the device to auto-configure.
I'm not so interested in the firefox issues, I have a strong suspicion they are all due to an improperly configured IPv6 environment.
I think you simply do not understand the issue.
I'll admit, that is very possible. :-)
Please read the bugzilla instead, I did not write it, perhaps you understand them better than me.
<https://bugzilla.mozilla.org/show_bug.cgi?id=700999>
It has 45 entries.
I have been running ipv6 since 2006. First steps with a tunnel provider, some years later with a local ADSL provider, since 2012 with PI address space routed by my uplink provider. If all of that report is to do with people using LL addresses, I'm just not interested. -- Per Jessen, Zürich (18.2°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/08/2019 21.47, Per Jessen wrote:
Carlos E. R. wrote:
On 11/08/2019 21.08, Per Jessen wrote:
Carlos E. R. wrote:
On 11/08/2019 15.21, Per Jessen wrote:
Carlos E.R. wrote:
On 11/08/2019 13.01, James Knott wrote: > On 2019-08-10 07:51 PM, Carlos E. R. wrote: >> No, the last part at least is not true. My printer IPv6 part >> only responds on it. HP designed it to be used, till Firefox >> removed the support. > > Does HP have a Windows based utility for accessing the printer? > That might be part of the problem.
It certainly has, but I've never used it. It is easy enough to configure it over Ipv4.
The procedure with most IPv4 gadgets is:
Device responds on 192.168.1.1 only. This collides with the router address, so it can not be connected to the home network. Configure a laptop to be 192.168.1.2 or similar. Disconnect laptop from LAN. Connect laptop to new device. Configure new device to new address. Reboot it. Change laptop back to LAN address. Connect new device to LAN. Test connectivity.
Whereas on IPv6 it would be: Connect device to LAN. Point firefox 6 to link-local address of new device.
Run radvd on your network, using some fc00 prefix. That'll allow such devices to auto-configure and you won't need the old firefox.
Still what some of the comments on the firefox bugzilla describe is reaching to an IPv6 only device which is configured for an unknown address prefix/range. The link-local address allows to still connect to it, for examination and/or reconfiguration.
I'm not sure I quite get it - how can the prefix be unknown, especially if you have configured it yourself?
Huh?
Ah. Because we did not configure that particular gadget, for instance.
Sure, but when you have configured a local prefix, "fc00:what:ever:itis" and allowed the device to auto-configure.
And then the device is moved to another network, or somebody brings it to us, etc.
I'm not so interested in the firefox issues, I have a strong suspicion they are all due to an improperly configured IPv6 environment.
I think you simply do not understand the issue.
I'll admit, that is very possible. :-)
Please read the bugzilla instead, I did not write it, perhaps you understand them better than me.
<https://bugzilla.mozilla.org/show_bug.cgi?id=700999>
It has 45 entries.
I have been running ipv6 since 2006. First steps with a tunnel provider, some years later with a local ADSL provider, since 2012 with PI address space routed by my uplink provider.
If all of that report is to do with people using LL addresses, I'm just not interested.
I pointed to a few paragraph for you to read. All that I said is basically the same they say. The issue I have with LL addresses is what is written in that Bugzilla... And all this time you are trying to tell me that these people are wrong. Well, read it, they don't use my words. That's the issue with LL. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-08-11 08:28 AM, Carlos E.R. wrote:
Whereas on IPv6 it would be: Connect device to LAN. Point firefox 6 to link-local address of new device. Configure device as appropriate for lan.
It appears you're trying to do something that's not intended. Other than link local addresses, you do not appear to have IPv6 on your network. Link local addresses were never intended to be used in the way you are trying. The fact that Firefox removed that capability has nothing to do with whether link local addresses work. They are used for things like router advertisements, for accessing routers and similar. As I mentioned, Microsoft used them, but it's really nothing more than they used to do back in the NetBIOS days, when they directly used the MAC address, rather than IP. As discussed, there are utilities that apparently work without proper IPv6 addresses, just as I could with those cameras. Are you sure that printer config even uses link local addresses? It could be working at the MAC level. All that requires is for the device to announce it's presence through broadcast or multicast with any IP address and the utility then learns the MAC address and goes through it, with no further use of IP. I understand your ISP might not provide IPv6, but I already mentioned he.net as a way around that. Until you get IPv6 working on your network, don't try something like configuring that printer and then claim link local doesn't work, when it's working exactly as intended. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/08/2019 15.57, James Knott wrote:
On 2019-08-11 08:28 AM, Carlos E.R. wrote:
Whereas on IPv6 it would be: Connect device to LAN. Point firefox 6 to link-local address of new device. Configure device as appropriate for lan.
It appears you're trying to do something that's not intended. Other than link local addresses, you do not appear to have IPv6 on your network.
I'm basically posting here stuff that is written in the firefox bugzilla by others, not my own case. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-08-11 01:33 PM, Carlos E. R. wrote:
It appears you're trying to do something that's not intended. Other than link local addresses, you do not appear to have IPv6 on your network. I'm basically posting here stuff that is written in the firefox bugzilla by others, not my own case.
And you have been repeatedly told here, you're trying to do the wrong thing. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* James Knott <james.knott@jknott.net> [08-11-19 13:51]:
On 2019-08-11 01:33 PM, Carlos E. R. wrote:
It appears you're trying to do something that's not intended. Other than link local addresses, you do not appear to have IPv6 on your network. I'm basically posting here stuff that is written in the firefox bugzilla by others, not my own case.
And you have been repeatedly told here, you're trying to do the wrong thing.
following instructions and/or suggestions does not appear to be in the book. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/08/2019 19.51, James Knott wrote:
On 2019-08-11 01:33 PM, Carlos E. R. wrote:
It appears you're trying to do something that's not intended. Other than link local addresses, you do not appear to have IPv6 on your network. I'm basically posting here stuff that is written in the firefox bugzilla by others, not my own case.
And you have been repeatedly told here, you're trying to do the wrong thing.
Tell that to the people in the firefox bugzilla... -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
participants (9)
-
Bruce Ferrell -
Carlos E. R. -
Carlos E.R. -
Dave Howorth -
David C. Rankin -
gumb -
James Knott -
Patrick Shanahan -
Per Jessen