| 2 Jun 2025 |
 Charles | i see | 00:12:06 |
 hexa | 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 | because with autoconfig there is algorithm to generate a collision free host suffix | 00:12:42 |
| hexa | * because with autoconfig there is an algorithm to generate a collision free host suffix | 00:12:49 |
| hexa | and it requires 64 bits on the host side | 00:12:59 |
| hexa | * because with autoconfig there is an algorithm (EUI-64) to generate a collision free host suffix | 00:13:39 |
| hexa | * and that requires 64 bits on the host side | 00:13:48 |
| hexa | and router advertisements basically send the prefix side and tell the client it can pick an address inside that prefix | 00:14:08 |
| hexa | * 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 | because a unique route should go in one direction | 00:18:27 |
| hexa | * because a unique route should go onto one dedicated interface | 00:18:38 |
| hexa | * because a route should go onto one dedicated interface | 00:18:42 |
| hexa | if you only have one LAN interface it doesn't matter | 00:18:54 |
| hexa | but once you have multiple you'll see that each gets its own /64 | 00:19:14 |
| hexa | multiple LAN interfaces may make sense if you intend to separate them for any reason | 00:19:40 |
| hexa | iot/things, guests, wlan/lan, management, you name it | 00:20:04 |
| Charles | hmm to be clear i think i just want a single "network", at least right now, my router has 4 physical ports, one is wan and 3 are bridged as lan, shouldn't one /64 be sufficient for that? | 00:21:10 |
| hexa | yeah | 00:21:28 |
| hexa | once you don't bridge and use the ports individually, or you start using vlans, that'll change | 00:21:50 |
| hexa | also, your isp may be shit (it probably is) and only give you another /64 😄 | 00:22:54 |
| hexa | which is stupid, because they have lots of ipv6 address space | 00:23:11 |
| Charles | [root@green:~]# ip -6 route
2001:558:100d:5a::/64 dev en-wan proto ra metric 1024 expires 2591998sec pref medium
2601:1c1:8400:a440::/64 dev br-lan proto kernel metric 256 expires 341762sec pref medium
unreachable 2601:1c1:8400:a440::/60 dev lo proto dhcp metric 1024 pref medium
fd00:0:d:4::/64 dev en-wan proto ra metric 1024 expires 2591998sec pref medium
fd00:0:101:41::/64 dev en-wan proto ra metric 1024 expires 2591998sec pref medium
fe80::/64 dev br-lan proto kernel metric 256 pref medium
fe80::/64 dev en-wan proto kernel metric 256 pref medium
default nhid 3750293650 via fe80::21c:73ff:fe00:99 dev en-wan proto ra metric 1024 expires 1798sec pref medium
| 00:23:27 |
| hexa |
I just tried requesting a /56 with dhcpcd, but Comcast only gave me a /60 in return. Were you able to get a /56 on consumer Xfinity?
| 00:23:31 |
| Charles | does that unreachable line mean i actually have a /60? | 00:23:51 |
| hexa | a /60 would support 2^(64-60) /64 subnets | 00:23:55 |
| hexa | yes, it does | 00:24:15 |
