

Screw them! We’ll build our own peertube, with blackjack, and hookers
Screw them! We’ll build our own peertube, with blackjack, and hookers
That means Bedrock unless you use the Geyser tool someone else mentioned to allow Bedrock to connect to Java but I have no experience with that and am not sure how reliably it would actually work as they are quite different versions of the game. I have no idea how it would handle mods that are not supported by the Bedrock clients for example.
First you need to understand the difference between Bedrock edition and Java edition. Bedrock is for consoles, phones and Windows, it’s the default version that Microsoft pushes now. It’s not compatible with Java clients or Java servers. So if you’re planning to have the kid play on Switch or something like that, it’s not going to work.
Assuming you’re clear on all that, you have a few options for Java servers, you can run a plain jane vanilla server (the one that Microsoft provides) fairly easily but it has some limitations, and it’s not the most manageable solution. Modded servers are much more capable and flexible but also can be a little more complex in some cases. Overall, I’ve found Purpur the easiest and most sustainable choice at least a few years ago when I was looking for the right choice it seemed like most people agreed this was the best option. Fabric is another great option, especially if you want to use mods! Fabric has a huge modding ecosystem, second only to Forge.
However I also need to mention that I’ve got a heavily modded Forge-based server running right now and I really didn’t find that any more difficult to set up than any of the others. Even though people usually complain about forge being “difficult” somehow. So take that for what it’s worth. I think it doesn’t really matter THAT much which server software you use unless you have specific requirements around things like mods, spawn protection, and other kinds of configuration that are probably most useful for large, public servers.
If you do want to run a bedrock server, it gets a little more complicated as you might have to break some things out of the walled garden. I haven’t had a lot of success with that but I understand it is possible.
Florida is basically the unofficial US Capitol now, so it would be confusing and ambiguous to have it associated with the traditional forms of unexpected insanity. Now it’s going to be an entirely new kind of unexpected insanity, so Ohio has been selected to represent the old kind of unexpected insanity that Florida used to represent.
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 a
which 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 <UP> 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 r
which 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
ping
the 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.8
will 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.com
and 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!