I’m setting up DHCP reservations on my home network and came up with a simple schema to identify devices: .100 is for desktops, .200 for mobiles, .010 for my devices, .020 for my wife’s, and so on. Does anyone else use schemas like this? I’ve also got .local DNS names for each device, but having a consistent schema feels nice to be able to quickly identify devices by their IPs.

  • ShunkW@lemmy.worldEnglish
    5·
    1 year ago

    I live alone. So I just have reserved IPs for each of my devices. Any new device gets assigned >200 so that I can easily identify new stuff, or rogue devices - which hasn’t happened lol. The only special IP is my pihole that gets 192.168.1.2 next to my router since I consider it infrastructure basically. Plus pihole is my dhcp server and dns obviously

      • ShunkW@lemmy.worldEnglish
        4·
        1 year ago

        Yeah makes it easier to identify new stuff. Like I recently added a new NAS into my network, and I didn’t have to try and figure out which device it was identified as. Just sitting at 200.1 so I could give it a name and assign a static IP.

  • Bimbleby@lemmy.world
    4·
    1 year ago

    I use it for enterprise scale infrastructure deployments. But for a home network, it seems like unnecessary work.

  • SheeEttin@lemmy.worldEnglish
    3·
    1 year ago

    I don’t.

    I currently use 192.168.6.0/24, set DHCP to 100-199, and statically assign a few servers outside that range. Anything else can use DNS via DHCP because I use Windows for AD/DNS/DHCP.

  • PuppyOSAndCoffee@lemmy.mlEnglish
    31·
    1 year ago

    Sounds like fun but watch out for man in middle…home tech support!

    Remember upper executive mgmt (wife) will have priority demands and expect to bypass all support/ticketing processes c/o direct access/shoulder tap, 24x7.

    Tip - create high priority user stories for your upper exec mgmt needs and your rest activities (sports, call of duty, tinkering in garage/shop/man cave, etc etc etc et al) so your impl supports your key stakeholders while also aligning with your favorite best practices.

    .local is the important part imo—actually, tbh I am not a super fan of the .local dns method and how it punks networks (basically like entering a crowded bar and yelling YO BRAH!) BUT it is simple and low effort (see high pri user stories).

    Good luck with your PI plan, could you include us in PI retrospective so we can learn from you? Godspeed.

    :]