Talk:IPv6

IPv6#ConnMan

Latest comment: 25 December 20193 comments3 people in discussion

This doesn't work for me. man 5 connman-service.config states that Name and Description are the only keys allowed in the global section. If I set IPv6.privacy in a service file instead, everything works as expected. Perhaps someone can confirm that setting the IPv6 privacy extensions for connman does indeed not work as described in the wiki, because I'm still not entirely sure if the wiki is outdated in this regard, or I'm doing something wrong.

Nrio (talk) 22:06, 25 May 2017 (UTC)Reply[reply]

I can confirm that it is in the file /var/lib/connmann/[service]/settings that we find the option.

For my part I use the daemon (which overwrites this file) via the connmanctl front end :

$ connmanctl config [service] ---ipv6 auto preferred

And it's okay.

Maotux (talk) 16:50, 6 June 2019 (UTC)Reply[reply]

I've tried to correct this with this edit. Please check or improve as I'm not a ConnMan user myself. Lonaowna (talk) 23:10, 25 December 2019 (UTC)Reply[reply]

Factual accuracy - Prefer IPv4 over IPv6

Latest comment: 11 January3 comments2 people in discussion

What's the issue or real Q here? Setting precedence in gai.conf is the way to prefer IPv4 over IPv6. What is bash? (talk) 03:41, 10 July 2019 (UTC)Reply[reply]

It's not for setting precedence between IPv4 over IPv6 but for setting precedence between Ipv6 addressing modes.

Here preffer the SLAAC privacy extensions that regularly change the ipv6 address and do not base it on the mac address of the network interface ( unique address can potentially be used to track the network :activity of a device, and the part of the ipv6 address taken from the mac address can greatly help to track a device even when changing the connection location).

Maotux (talk) 23:07, 12 July 2019 (UTC)!Reply[reply]

Ping @Maotux:

I wonder if its the lack of IPv4 addresses in gai.conf that makes you say that?

man 5 gai.conf - the file exists so Linux may comply with RFC 3484, a Microsoft RFC btw, read Section 3.2

Here's some bits from it:

3.2. IPv4 Addresses and IPv4-Mapped Addresses

The destination address selection algorithm operates on both IPv6 and IPv4 addresses.

IPv4 addresses should be treated as having "preferred" (in the RFC 2462 sense) configuration status.

Your reason given is misplaced, "this disables the other default rules". No, it disables the default table, if you have custom rules, setup the appropriate policies and things will work.

What is bash? (talk) 21:15, 11 January 2024 (UTC)Reply[reply]