Selfhosted

39158 readers

381 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

115

I'm new to networking and self-hosting and have no idea where to start. (self.selfhosted)

submitted 8 months ago* (last edited 8 months ago) by vale to c/[email protected]

29 comments fedilink hide all child comments

I've been slowly working my way though a list of skills to learn, both to put on my resume and as personal growth. Networking is the next thing on this list. I am not sure what I am looking for, but I want to start another project. I have built many a personal computer, but the world of networking is a pretty foreign concept to me.

I have experience with building computers and a minor glance at the network-side of things. I've set up a Pi-Hole or two and set a basic CUPS server up on a RPi0w, but beyond that, I have no idea what I'm doing, or even what the possibilities are. I just see posts like this and think that it's a pretty cool hardware project.

Is there any resources you recommend to start learning, maybe what the hardware does? From my outsider's perspective, I see a lot of people's racks have at least a router, switch, and firewall, along with various other machines.

E: thank you all for the suggestions! I'll have to take some time to figure out what to do first

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 24 points 8 months ago* (last edited 8 months ago) (1 children)

Not necessarily in this order:

Learn the OSI and TCP/IP layer models.
Learn the fundamentals of IPv4 and IPv6. (Absolutely learn to count bits for IPv4)
Learn and understand the use-cases for routers, switches, and firewalls.
Learn about DNS. (Domain Name System)
Learn about DHCP. (Dynamic Host Configuration Protocol)
Learn important Port Numbers for important Services. (SSH is Port 22, for example. The range of port numbers from 1024 to 49151 are "registered ports" that are generally always the same)
Learn about address classes. (A, B, C are the main ones)
Learn about hardware addresses (MAC address) and how to use ARP to find them.

And more! This is just off the top of my head. Until you've studied a lot more, please, for your own sake, don't open your selfhosted ervices to the wider internet and just keep them local.

And just for fun, a poem:

The inventor of the spanning tree protocol, Radia Perlman, wrote a poem to describe how it works. When reading the poem it helps to know that in math terms, a network can be represented as a type of graph called a mesh, and that the goal of the spanning tree protocol is to turn any given network mesh into a tree structure with no loops that spans the entire set of network segments.

I think that I shall never see

A graph more lovely than a tree.

A tree whose crucial property

Is loop-free connectivity.

A tree that must be sure to span

So packets can reach every LAN.

First, the root must be selected.

By ID, it is elected.

Least cost paths from root are traced.

In the tree, these paths are placed.

A mesh is made by folks like me,

Then bridges find a spanning tree.

— Radia Perlman Algorhyme

[–] [email protected] 5 points 8 months ago (1 children)

Classful networking is well past dead, that’s kinda pointless. Learn VLSM and general subnetting basics instead.

[–] [email protected] 2 points 8 months ago* (last edited 8 months ago) (1 children)

I mean, isn't it important to understand the fundamentals so you can understand VLSM better?

Like math, a lot of this knowledge works better when you know the fundamentals and basics, which help you conceptualize the bigger ideas.

On a personal level, I would have had a lot harder time understanding VLSM if I hadn't had the basic fundamentals of traditional subnetting and classful networking under my belt.

[–] [email protected] 4 points 8 months ago (1 children)

There’s nothing inherently important to classful networking you learn that’s necessary for VLSM. They amount to common convention based on subnet size, and even then nearly nobody actually uses A or B sized subnets except as summary routes, which again, is not inherent to classful networking.

Classful networking has been obsolete for thirty years for good reason, you gain nothing from restricting yourself in that way.

[–] [email protected] 2 points 8 months ago (1 children)

How are you "restricting" yourself by learning that it exists? Nobody is saying "learn about it and use it and never consider anything else." They asked what fundamentals they should know for networking, and I dumped what I considered the "fundamentals."

[–] [email protected] 1 points 8 months ago

Nothing actually uses classful networking anymore. Any situation where classful network concepts are implemented is necessarily limiting the capabilities of the network. As such it’s completely useless to bother spending time learning it.