Selfhosted
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:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
I don't use arch (shocking I know), so I can't help you directly, but I will recommend instead that you invest some effort in learning about the Linux networking stack. It's very powerful and can be very complicated, but usually the only thing you need to do to get it working is something very simple. Basically all distributions use the Linux kernel networking stack under the hood, usually with only a few user-interface sprinkles on top. Sometimes that can get in your way, but usually it doesn't. All the basic tools you need should be accessible through the terminal.
The most basic things you can check are
ip awhich should show a bunch of interfaces, the one you're particularly interested in is obviously the wired interface. This will tell you if it's considered and whether it has an "inet" address (among other things). If it doesn't, you need to get the interface configured and brought up somehow, usually by a DHCP broadcast. Network Manager is usually responsible for this in most distributions. Arch seems to have some information here.If those things look good, next step is to look at
ip rwhich will tell you the routes available. The most important one is the default route, this will tell your system where to send traffic when it isn't local, and usually sends traffic to an internet gateway, which should've been provided by DHCP and is usually your router, but could also be a firewall, the internet modem itself, or something else. The route will tell it what IP the gateway has, and what interface it can be found on.Assuming that looks good, see if you can
pingthe gateway IP. If your packets aren't getting through (and back) that suggests something is wrong on a lower level, the kernel firewall might be dropping the packets (configuring the kernel firewall is a whole topic in itself) or one of the IPs is not valid and is not registered properly on the network, or the physical (wiring) or the hardware on either end is not functioning or misconfigured.If you can ping the gateway successfully, the next step is to see if you can ping the internet itself by IP.
ping 8.8.8.8will reach out to one of Google's DNS servers which is what I usually use as a quick test. If you get no response then it's either not forwarding your traffic out to the internet, or the internet is not able to get responses back to it, and ultimately back to you. Or Google is down, but that's not very likely.If you've gotten this far and 8.8.8.8 is responding to you, then congratulations, you HAVE internet access! What you might NOT have is DNS service, which is what translates names into IP addresses. A quick test for DNS is simply to
ping google.comand like before, if that fails either your DNS is broken or Google is down, which is still not very likely.Hopefully this will help you at least start to find out where things are going wrong. From there, hopefully you can at least steer your investigation in the right direction. Good luck!