Re: Are we ready for ipv6-mostly networks?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The easy way is definitely pushing both IPv6 and IPv4 addresses of any service into DNS. Use at least mdns (which is not resolving also IPv6 in our default configuration sadly), which converts names to ipaddress  and back. That in my opinion is the target. To use human friendly names, not IP addresses. Sure, IPv4 are shorter and easier to type in or even spell. But we need the address bits, there is no workaround. IP addresses are not user-friendly way.

Dnsmasq for example creates name<->IP address mapping for every machine asking DHCP from it. That is the way to go. Name your machine and reference it by name from others. Avahi is a good alternative for locating your device, even when network does not do mapping to it. If some device does not insert names automatically (hello Mikrotik!), ask their vendor to fix that. Usage of IP addresses should be reduced to strictly necessary minimum. Copy & paste should help with that.

Tomorrow is IPv6 Seminar at Prague [3], I am going to attend that. I have still many questions, I am not really IPv6 guru (yet?).

On 05. 06. 23 15:27, Michal Schorm wrote:
Thought:
(disclaimer: I don't know much about networking)
IPv4 addresses are in some cases 'human readable' / 'human usable' /
'human friendly'.

How can one set up a temporary network of several devices for a LAN
party or any similar connecting application use cases?
 From my own experience, the vast majority of people have no idea that
when one tells you "write in: ten zero zero eight", they have to put
dots in between. Because they have no idea what IP address is and how
it's formatted.

I can't imagine I would say this out loud to even a tech experienced
person and they would get it right the first time.
1a01:4204:b07d:af00:21c6:542a:611:73ea

For real addresses which users actually has to type it is usually better.

dns.google: 2001:4860:4860::8844

dns9.quad9.net: 2620:fe::9


Not mentioning all the times I need to connect devices in many rooms
across several floors in the whole building.

Is there any easy way to keep exchanging the IP address 'human usable' ?

No. But we have DNS there for decades to make them human usable. We just need to use it everytime we can. Autoconfigure it when possible. What I am not sure is how should SLAAC allocated addresses be paired with a name provided by the network, into which they are connected to. It is supported with DHCP(v6), but I don't know a good way for router advertisements. A question for experts!

Though domain name services is the area I am expert in already. If there is integration missing in some area, fill a bug! Even to me.

--

Michal Schorm
Software Engineer
Core Services - Databases Team
Red Hat

--

On Thu, May 25, 2023 at 10:51 PM Petr Menšík <pemensik@xxxxxxxxxx> wrote:
Hello everyone,

I have attended recently csnog.eu conference [1], where some interesting
presentations took place. They were usually in Czech, so it is not
something I am going to share more. But what took my interest were ipv6
readiness with some exceptions. Fedora is ready to be run on dual-stack
IPv4 and IPv6 networks just fine. But the presentation were about future
case where we run most hosts on IPv6 network only, but allow some older
devices to take and use also IPv4 address.

Fortunately there is roughly the same presentation[2] in English, which
took the place on RIPE 85 meeting. What catched my interest were talk
about Windows 11 and Apple systems are ready, but not really talk about
how any linux distribution is ready for such situation. It seems to me
we should improve the support for mentioned mechanisms in Fedora.

What do you think about it?

[1] https://indico.csnog.eu/event/13/contributions/121/
[2] https://ripe85.ripe.net/archives/video/923/
3. https://www.cesnet.cz/akce/seminar-ipv6-2023/

--
Petr Menšík
Software Engineer, RHEL
Red Hat, http://www.redhat.com/
PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux