• BigDanishGuy@sh.itjust.works
    link
    fedilink
    arrow-up
    11
    ·
    10 days ago

    It’s the /24 mask given on the .42 that’s a little suspicious because that’s not a common range for anything else.

    Well now I know. I operate a ton of /24 subnets in the 172.16.0.0/12 scope. Technically I could fit them in the 192.168.0.0/16 scope, but I have lots of students connecting SoHo wifi-routers to the subnets, and this way it’s pretty easy to tell, if someone put the WAN cable in a LAN port when people are getting 192.168.1.0/24 DHCP offers.

    • u/lukmly013 💾 (lemmy.sdf.org)@lemmy.sdf.org
      link
      fedilink
      English
      arrow-up
      4
      ·
      10 days ago

      but I have lots of students connecting SoHo wifi-routers to the subnets, and this way it’s pretty easy to tell, if someone put the WAN cable in a LAN port when people are getting 192.168.1.0/24 DHCP offers.

      I use 172.31.254.0/23 on my WiFi router. I guess I’d confuse you. /23 to just separate it nicely into 2 /24 blocks.
      172.31.254.0/24 range is for manual assignments and 172.31.255.0/24 range is given out by DHCP.
      I do not need that many IPs, it’s just for convenience.

      I chose this range because of my school as it uses 192.168.0.0/16 range.
      To help mitigate my possible mistakes when connecting to school network, I set the DHCP lease time to just 5 minutes.

      • Trainguyrom@reddthat.com
        link
        fedilink
        English
        arrow-up
        3
        ·
        edit-2
        9 days ago

        172.31.254.0/24 range is for manual assignments and 172.31.255.0/24 range is given out by DHCP. I do not need that many IPs, it’s just for convenience.

        I do similar for my home network, mostly for a combination of future proofing and ease of use.

        Realistically it would probably make more sense to segment it with more networks, but I’m only going to go so far with complexity for my home production