| 2 Jun 2025 |
 hexa (clat on linux when) | and on the LAN side | 00:10:06 |
| hexa (clat on linux when) | networkConfig.DHCPPrefixDelegation = true;
| 00:10:12 |
| hexa (clat on linux when) | * \networkConfig.DHCPPrefixDelegation = true;
| 00:10:17 |
| hexa (clat on linux when) | * networkConfig.DHCPPrefixDelegation = true;
| 00:10:22 |
| hexa (clat on linux when) | this means it will request a /56 prefix on WAN | 00:10:30 |
| hexa (clat on linux when) | and try to delegate that to the LAN interface | 00:10:37 |
| hexa (clat on linux when) | which means it puts a /64 subnet onto your LAN interface | 00:11:02 |
| hexa (clat on linux when) | when that is in place, all you need is | 00:11:17 |
| hexa (clat on linux when) | networkConfig.IPv6SendRA = true;
| 00:11:23 |
| hexa (clat on linux when) | on the LAN side to send router advertisements | 00:11:34 |
 Charles | i see | 00:12:06 |
| hexa (clat on linux when) | this all hinges on your ISP actually delegating you a prefix | 00:12:09 |
| Charles | why | 00:12:15 |
| Charles | right | 00:12:18 |
| hexa (clat on linux when) | because with autoconfig there is algorithm to generate a collision free host suffix | 00:12:42 |
| hexa (clat on linux when) | * because with autoconfig there is an algorithm to generate a collision free host suffix | 00:12:49 |
| hexa (clat on linux when) | and it requires 64 bits on the host side | 00:12:59 |
| hexa (clat on linux when) | * because with autoconfig there is an algorithm (EUI-64) to generate a collision free host suffix | 00:13:39 |
| hexa (clat on linux when) | * and that requires 64 bits on the host side | 00:13:48 |
| hexa (clat on linux when) | and router advertisements basically send the prefix side and tell the client it can pick an address inside that prefix | 00:14:08 |
| hexa (clat on linux when) | * and router advertisements basically send the prefix and tell the client it can pick an address inside that prefix | 00:14:17 |
| Charles | i see | 00:16:30 |
| Charles | well, i guess i don't get why that has to be for each lan interface, why can't the bridge interface have 1 /64 and be sufficient | 00:17:45 |
| hexa (clat on linux when) | because a unique route should go in one direction | 00:18:27 |
| hexa (clat on linux when) | * because a unique route should go onto one dedicated interface | 00:18:38 |
| hexa (clat on linux when) | * because a route should go onto one dedicated interface | 00:18:42 |
| hexa (clat on linux when) | if you only have one LAN interface it doesn't matter | 00:18:54 |
| hexa (clat on linux when) | but once you have multiple you'll see that each gets its own /64 | 00:19:14 |
| hexa (clat on linux when) | multiple LAN interfaces may make sense if you intend to separate them for any reason | 00:19:40 |
| hexa (clat on linux when) | iot/things, guests, wlan/lan, management, you name it | 00:20:04 |
