| 4 Oct 2024 |
 mjm | but like, this hasn't been there for a while and i never noticed | 03:29:57 |
| mjm | so 🤷 | 03:30:06 |
| mjm | anyway, the fstab generator is pretty slick, excited to have it working! | 03:31:22 |
 ElvishJerricco | yea, thanks for testing! | 03:35:39 |
 aloisw | In reply to @elvishjerricco:matrix.org
doesn't btrfs handle large numbers of snapshots absolutely terribly or something? The snapshots themselves are not so much the problem, it's mostly the combination with quota that causes the performance issues. | 12:56:08 |
| 5 Oct 2024 |
|  jeroen left the room. | 13:57:48 |
|  magic_rb changed their profile picture. | 22:17:59 |
| 6 Oct 2024 |
 steveej | i'm trying to set up ipv6 prefix delegation with systemd-networkd on my router. i also run dnsmasq there and i'm not sure how relevant that is.
what i'm wondering is how i can confirm that my router is actually getting a delegated prefix from my ISP's router, or whether it just gets a single IP6 address | 09:35:49 |
| steveej | i believe i set all the necessary options on the router's WAN interface to accept RAs and also use dhcpv6 to ask for a delegated prefix. | 09:36:31 |
 K900 | ip a should show a prefix on the interface | 09:37:05 |
| K900 | If you're getting a prefix | 09:37:12 |
| steveej | do you mind showing me an example output for that? this is the wan interface output
4: wan@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000
inet6 2001:XXX:9d94:4420:d4ac:76ff:fec0:7837/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 7149sec preferred_lft 3549sec
inet6 fdaa:XXX:ddee:0:d4ac:76ff:fec0:7837/64 scope global mngtmpaddr noprefixroute
valid_lft forever preferred_lft forever
inet6 fe80::d4ac:76ff:fec0:7837/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
slightly paranoid so i XXXd some values there
| 09:38:42 |
| K900 | You have a /64 | 09:39:17 |
| K900 | So yes that's a prefix | 09:39:21 |
| K900 | But normally you'd get a /56 from your ISP | 09:40:01 |
| K900 | For prefix delegation to work correctly | 09:40:05 |
| K900 | You can configure it to delegate smaller prefixes | 09:40:18 |
| K900 | But a typical setup would be to have a /48 or /56 for your router, and a /64 per device | 09:41:09 |
| K900 | Which you can't have because you just have a /64 | 09:41:18 |
| steveej | i'm going to try and set PrefixDelegationHint = "::/65"; just to see if it's even considered. i had it set to 57 earlier | 09:42:50 |
| steveej | i don't see anything about PD requests in the journal | 09:43:09 |
| K900 | /65 is probably a bad idea | 09:43:33 |
| K900 | Because there's exactly two /65s in a /64 | 09:43:39 |
| steveej | indeed, i just want to see if the value has any effect | 09:44:25 |
| steveej | it seems like my router is just getting a /64 regardless | 09:44:40 |
| K900 | Yes, that's how it's supposed to work | 09:45:27 |
| steveej | i'm not yet convinced that i'm actually getting a whole prefix on that router. the syntax for the IPv4 is the same: inet 172.16.0.97/12 | 09:48:35 |
| K900 | Actually it looks like networkd doesn't support delegating prefixes smaller than /64 | 09:49:48 |
| K900 | That's technically correct as per the RFC | 09:50:05 |
 Arian | In reply to @k900:0upti.me
But a typical setup would be to have a /48 or /56 for your router, and a /64 per device This is not fully correct. It's /56 for your modem /64 for your router in residential areas | 09:57:41 |
