Conversation

Notices

1. Embed this notice
   Jason Tubnor 🇦🇺 (tubsta@soc.feditime.com)'s status on Wednesday, 14-May-2025 04:45:12 JST Jason Tubnor 🇦🇺

   • FKA ZOG
   @zog I enjoy my two /48 . Every vlan gets a /64. Go nuts
   • Embed this notice
     feld (feld@friedcheese.us)'s status on Wednesday, 14-May-2025 04:45:11 JST feld

     in reply to

     • FKA ZOG
     @Tubsta @zog isn't there a BCP that says to assign a /56 to customers instead of a /48 which should be reserved for POPs? weird, that's a lot of addresses tho
   • Embed this notice
     feld (feld@friedcheese.us)'s status on Wednesday, 14-May-2025 05:41:21 JST feld

     in reply to

     • FKA ZOG
     @Tubsta @zog "easier" until you want things like "reverse DNS working" which requires DHCPv6, a thing nobody should be subjected to
     
     I don't have IPv6 anymore but I started building out a tool to generate PTRs by pushing the output of "ndp -a --libxo json" on my firewall to an API endpoint
   • Embed this notice
     Jason Tubnor 🇦🇺 (tubsta@soc.feditime.com)'s status on Wednesday, 14-May-2025 05:41:22 JST Jason Tubnor 🇦🇺

     in reply to

     • FKA ZOG
     • feld
     @feld @zog /56 came from the #IPv4 way of thinking. Consensus and modern network design call for a /48 per site/campus so network engineers can layout their networks without the worry of having to renumber because of design choices 10 years earlier.
     
     This also gives you the ability to route the whole site separately as a /48 is as small as you can go for eBGP. Many benefits, no downsides. This is why everyone should move to #IPv6, things are just so much easier.