63

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.

you are viewing a single comment's thread
view the rest of the comments
[-] chiisana@lemmy.chiisana.net 15 points 1 year ago

10.0.0.0/8; so much room for activity.

I currently use 10.0.0.0/24 as infrastructure; 10.10.0.0/24 for hard wired devices; 10.20.0.0/24 for wireless devices; and 10.42.0.0/16 for docker containers provisioned by Rancher.

[-] nutbutter@discuss.tchncs.de 6 points 1 year ago

Can you tell what do the values after / denote? Like /8, /24.

I have seen them in many places. I even use /8 in my Wireguard config. But I do not know what it is. I do not even know its name to look it up online.

[-] Chetyre@lemmy.world 5 points 1 year ago

The term you are looking for is CIDR notation. The / is showing what the subnet mask is. So the subnet mask for a /8 is 255.0.0.0, which would be an extremely large network (over 16 million addresses, this was traditionally known as a Class A).

https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation

[-] chepdamona@sh.itjust.works 2 points 1 year ago

It's called CIDR notation, the number represents how many bits of the whole address represent the "network" part of the address. /8 is equivalent to a subnet mask of 255.0.0.0

this post was submitted on 20 Aug 2023
63 points (90.9% liked)

Selfhosted

40394 readers
415 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS