| 2 Jun 2025 |
 ElvishJerricco | Charles: just use MulticastDNS | 01:05:29 |
 hexa | mdns does that | 01:05:32 |
| hexa | https://search.nixos.org/options?channel=25.05&from=0&size=50&sort=relevance&type=packages&query=nssmdns | 01:05:45 |
| hexa | but what I personally do is announce a stable ULA prefix, ignore privacy extensions, and configure global dns to point to these addresses | 01:06:12 |
| hexa | * but what I personally do is announce a stable ULA prefix, disable privacy extensions, and configure global dns to point to these addresses | 01:06:21 |
| ElvishJerricco | for systems not using avahi, systemd-resolved can also do it | 01:06:36 |
 Charles | thanks for the hints | 01:09:42 |
| Charles | with this, should i be setting DHCP = true; or just "ipv4"? | 01:10:11 |
| hexa | you need dhcpv6 for this to work | 01:10:45 |
| ElvishJerricco | Isn't DHCPv6 how you receive your delegated prefix? | 01:10:49 |
| ElvishJerricco | you just don't need to be running a DHCPv6 server | 01:11:15 |
| Charles |
Note that DHCPv6 will by default be triggered by Router Advertisements, if reception is enabled, regardless of this parameter. By explicitly enabling DHCPv6 support here, the DHCPv6 client will be started in the mode specified by the WithoutRA= setting in the [DHCPv6] section, regardless of the presence of routers on the link, or what flags the routers pass. See IPv6AcceptRA=.
| 01:11:29 |
| hexa | yeah, if they send RA with other flag | 01:11:42 |
| hexa | * yeah, if they send RA with managed or other flag | 01:11:53 |
| hexa | you can try running rdisc6 against wan | 01:12:03 |
| hexa | to find out what their router advertisements send | 01:12:27 |
| hexa | * to find out what their router advertisements are | 01:12:29 |
| hexa | the package is ndisc6 | 01:12:44 |
| hexa | # rdisc6 ppp0
Soliciting ff02::2 (ff02::2) on ppp0...
Hop limit : undefined ( 0x00)
Stateful address conf. : No
Stateful other conf. : Yes
Mobile home agent : No
Router preference : medium
Neighbor discovery proxy : No
Router lifetime : 1800 (0x00000708) seconds
Reachable time : unspecified (0x00000000)
Retransmit time : unspecified (0x00000000)
Source link-layer address: 28:DE:E5:70:16:E9
MTU : 1492 bytes (valid)
Prefix : 2001:16b8:a027:8551::/64
On-link : Yes
Autonomous address conf.: Yes
Valid time : 259200 (0x0003f480) seconds
Pref. time : 172800 (0x0002a300) seconds
from fe80::2ade:e5ff:fe70:16e9
| 01:14:01 |
| hexa | mine says it offers stateful other config | 01:14:18 |
| hexa | router adverts are part of stateless autoconfig | 01:14:40 |
| hexa | and dhcpv6 also has a stateless mode | 01:14:54 |
| hexa | but stateful dhcpv6 means getting addresses on a lease | 01:15:04 |
| Charles | i get 3 sections like that | 01:16:07 |
| Charles | they all look the same, here's the last one:
Hop limit : 64 ( 0x40)
Stateful address conf. : Yes
Stateful other conf. : Yes
Mobile home agent : No
Router preference : medium
Neighbor discovery proxy : No
Router lifetime : 1800 (0x00000708) seconds
Reachable time : 90000 (0x00015f90) milliseconds
Retransmit time : 1000 (0x000003e8) milliseconds
Source link-layer address: 00:1C:73:00:00:99
MTU : 9192 bytes (valid)
Prefix : fd00:0:d:4::/64
On-link : Yes
Autonomous address conf.: No
Valid time : 2592000 (0x00278d00) seconds
Pref. time : 604800 (0x00093a80) seconds
Prefix : 2001:558:100d:5a::/64
On-link : Yes
Autonomous address conf.: No
Valid time : 2592000 (0x00278d00) seconds
Pref. time : 604800 (0x00093a80) seconds
Prefix : fd00:0:101:41::/64
On-link : Yes
Autonomous address conf.: No
Valid time : 2592000 (0x00278d00) seconds
Pref. time : 604800 (0x00093a80) seconds
from fe80::21c:73ff:fe00:99
| 01:17:21 |
| Charles | thankfully there's no at-signs in this :^) | 01:17:30 |
| hexa | so for some reason they announce two different ULA prefixes | 01:18:16 |
| hexa | w/e | 01:18:21 |
| hexa | L2-3 means it would autostart DHCPv6 when it got this router advertiseement | 01:18:44 |
| hexa | * L2-3 means it would autostart DHCPv6 when it got this router advertisement | 01:18:46 |
