Conversation

Notices

1. Embed this notice
   The Psychotic Network Ferret (nuintari@infosec.exchange)'s status on Tuesday, 18-Apr-2023 21:20:16 JST The Psychotic Network Ferret

   I swear to god, all networks, big and small, and of nearly all ages beyond "literally born last week," have an IP swamp. An area of IP addressing that predates any sane documentation and allocation policy. A giant prefix of just icky mess.

   At current job, I have two public /24s, and multiple /16s carved out of RFC1918 space that area fucking mess.

   Previous admin had a policy of, "when in doubt, throw a /22 at it."

   And they aren't all together. But remember, we are talking about a network that uses OSPF where they should use iBGP, and eBGP where they should use OSPF.

   • silverwizard likes this.
   • Embed this notice
     The Psychotic Network Ferret (nuintari@infosec.exchange)'s status on Tuesday, 18-Apr-2023 21:22:45 JST The Psychotic Network Ferret

     in reply to

     • Fritz Adalis

     @FritzAdalis This place was using 172.32.0.0/16.....

     Think about that _real_ hard.

     silverwizard likes this.
   • Embed this notice
     Fritz Adalis (fritzadalis@infosec.exchange)'s status on Tuesday, 18-Apr-2023 21:22:47 JST Fritz Adalis

     in reply to

     @nuintari
     My prev co had a nice ip space. Each site had a /24 or /25, with /27s for printers and servers. All in 192.168/16. Then we got a new guy who insisted on adding subnets in 172.16/12 and 10/8, with no particular design. Then of course we got Docker and they default to 172.17 and developers mostly don't understand networking.

     (Okay, done bitching for now.)

   • Embed this notice
     Fritz Adalis (fritzadalis@infosec.exchange)'s status on Tuesday, 18-Apr-2023 21:25:36 JST Fritz Adalis

     in reply to

     @nuintari
     I presume they were not T-Mobile.

     silverwizard likes this.
   • Embed this notice
     The Psychotic Network Ferret (nuintari@infosec.exchange)'s status on Tuesday, 18-Apr-2023 21:26:50 JST The Psychotic Network Ferret

     • silverwizard

     @silverwizard At a previous job, we were allocated a /23 out of 192.211.0.0/16 from ARIN.

     We ended up migrating our loopbacks and /31s into it, because our original plan, using it for business customers who needed routables in the era of CGNAT, resulted in way too much, "Nooooo! We need a PUBLIC IP!" from idiot IT workers.

     silverwizard likes this.