-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Resending, lets see if Telefonica behaves properly now. On 2011-01-06 18:46, Per Jessen wrote:
Carlos E. R. wrote:
But it is a terrible format!
Yes, it is unusual having an IP-address in the URL, normally it would be a name, but the %ethX extension doesn't work with a name (as far as I have seen). Btw, the FE80::21E:BFF:FE08:4CCB%eth0 format also works with e.g. ssh and telnet. It is handled by the getaddrinfo() function. I suspect there must be a way of specifying a name plus devicename, but I haven't found it yet.
I meant terrible compared to an IPv4 numerical address. There is no need for brackets nor for the interface.
Having to add a 6 to the ping, specify the interface in pings or web browsing... Perhaps it is a question of routing tables :-?
It is a problem specific to link-local addresses - if you were to use global unicast addresses, i.e. "plain" IPv6 addresses, there is no problem. If you can assign your own IPv6 addresses to the printer, you could try using the fec0 prefix - it's deprecated, but was meant to be site-local.
Well, I certainly want local-only addresses, not global addresses. I read somewhere that old v4 addresses could be mapped to new v6 addresses. Some prefix, then the old 192.168... (I need a good read on all this...)
What would happen if I modify my bind dns configuration in an unfathomable way, so that the returned address for the printer is the v6 one instead of the v4 one, would I have to write the port too? That's absurd. It is, isn't it?
If you change the A record and make it an AAAA instead with a proper IPv6 address, it'll work just fine. I tried it with a link-local address, and I couldn't get it to work with the %ethX notation.
No, I don't want to put the eth part :-) So add an AAAA record. But also add the reverse file somehow, too.
And where from did the printer get that address? I did not configure it, it was HP, the manufacturer. Perhaps I should configure instead the equivalent v6 address to the v4 addr.
It's automatically configured; the fe80 prefix means "link-local", the rest is an encoding of MAC-address of the interface.
Ahh! I see. And I don't need routing tables, because we write the eth0 port in the address given to firefox. If I would be using names, how would the routing know on which ether port is that MAC address? Routing tables are done by prefixes common to many machines. Unless the operating system does discovery and automatic routing...
Is there an IPv6 manual for dummies?
I'm sure there are many good books out there, but I can't recommend anyone specific. Sofar I've managed with a couple good wikipedia articles and googling a lot.
I'm more lazy than that, I would prefer a book in paper, or a really good, simple, web page. :-) - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAk0mJDIACgkQtTMYHG2NR9XmwQCdFtkZUWtg41pZvYW0ser1BYMq CIAAnReOHHL5JnueDtCESgVGWgyOXapi =wMgo -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org