!tCyGickeVqkHsYjWnh:nixos.org

NixOS Networking

921 Members
Declaratively manage your switching, routing, wireless, tunneling and more.267 Servers

Load older messages


SenderMessageTime
2 Jun 2025
@hexa:lossy.networkhexa* and router advertisements basically send the prefix and tell the client it can pick an address inside that prefix00:14:17
@charles:computer.surgeryCharlesi see00:16:30
@charles:computer.surgeryCharles 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:lossy.networkhexabecause a unique route should go in one direction00:18:27
@hexa:lossy.networkhexa* because a unique route should go onto one dedicated interface00:18:38
@hexa:lossy.networkhexa* because a route should go onto one dedicated interface00:18:42
@hexa:lossy.networkhexaif you only have one LAN interface it doesn't matter00:18:54
@hexa:lossy.networkhexabut once you have multiple you'll see that each gets its own /6400:19:14
@hexa:lossy.networkhexamultiple LAN interfaces may make sense if you intend to separate them for any reason00:19:40
@hexa:lossy.networkhexaiot/things, guests, wlan/lan, management, you name it00:20:04
@charles:computer.surgeryCharleshmm 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:lossy.networkhexayeah00:21:28
@hexa:lossy.networkhexaonce you don't bridge and use the ports individually, or you start using vlans, that'll change00:21:50
@hexa:lossy.networkhexaalso, your isp may be shit (it probably is) and only give you another /64 😄 00:22:54
@hexa:lossy.networkhexawhich is stupid, because they have lots of ipv6 address space00:23:11
@charles:computer.surgeryCharles
[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:lossy.networkhexa

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:computer.surgeryCharles does that unreachable line mean i actually have a /60? 00:23:51
@hexa:lossy.networkhexaa /60 would support 2^(64-60) /64 subnets00:23:55
@hexa:lossy.networkhexayes, it does00:24:15
@hexa:lossy.networkhexa
unreachable 2001:16b8:b426:6500::/56 dev lo proto dhcp metric 1024 pref medium
00:24:25
@hexa:lossy.networkhexa🙂 00:24:29
@charles:computer.surgeryCharles i dismissed that line since it says unreachable and also says lo instead of en-wan lol 00:25:02
@charles:computer.surgeryCharleslucky you lol00:25:08
@hexa:lossy.networkhexa* a /60 would support 2^(64-60) = 16 /64 subnets00:25:10
@hexa:lossy.networkhexawell it means it terminates locally00:25:22
@hexa:lossy.networkhexait doesn't send traffic toward it over wAN00:25:28
@hexa:lossy.networkhexa* it doesn't send traffic toward it over WAN00:25:30
@charles:computer.surgeryCharlesah00:25:36
@hexa:lossy.networkhexaand now you configure more specific routes and they'll get preferred00:25:51

Show newer messages


Back to Room ListRoom Version: 6