Arch Linux

bonkmaykr

Member

Registered: 2022-12-22

Posts: 15

[SOLVED] GeyserMC port will only forward over Wi-Fi, not ethernet.

I'm running a crossplay Minecraft Paper server at thewinnerscircle.duckdns.org. It's running off of EndeavourOS using iptables as the firewall.

Everything is configured correctly in iptables and on the router itself. I followed the precise directions according to the Arch Wiki, however, players on the Bedrock edition of Minecraft cannot join unless the server is running over Wi-Fi.

Java edition players can connect just fine, and the server's website on port 80 is working fine as well. This is strictly a problem with the port created by GeyserMC. When connected over ethernet, port 19132 only opens up to LAN, not the public. Disabling the firewall with systemctl doesn't seem to fix anything.

Here's my iptables config at time time of me writing this:

:PREROUTING ACCEPT [2565:179938]
:OUTPUT ACCEPT [3808:832694]
-A PREROUTING -p tcp -m tcp --dport 21 -j CT --helper ftp
COMMIT
# Completed on Tue Aug 29 03:59:46 2023
# Generated by iptables-save v1.8.9 (nf_tables) on Tue Aug 29 03:59:46 2023
*filter
:INPUT DROP [0:0]
:FORWARD DROP [0:0]
:OUTPUT ACCEPT [3806:832263]
:TCP - [0:0]
:UDP - [0:0]
-A INPUT -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 8 -m conntrack --ctstate NEW -j ACCEPT
-A INPUT -p udp -m conntrack --ctstate NEW -j UDP
-A INPUT -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN -m conntrack --ctstate NEW -j TCP
-A INPUT -p tcp -j REJECT --reject-with tcp-reset
-A INPUT -p tcp -m state --state NEW -m tcp --dport 21 -j ACCEPT
-A TCP -p tcp -m tcp --dport 22 -j ACCEPT
-A TCP -p tcp -m tcp --dport 80 -j ACCEPT
-A TCP -p tcp -m tcp --dport 443 -j ACCEPT
-A TCP -p tcp -m tcp --dport 20 -j ACCEPT
-A TCP -p tcp -m tcp --dport 21 -j ACCEPT
-A TCP -p tcp -m tcp --dport 25565 -j ACCEPT
-A TCP -p tcp -m tcp --dport 19132 -j ACCEPT
-A TCP -p tcp -m tcp --dport 19133 -j ACCEPT
-A UDP -p udp -m udp --dport 25565 -j ACCEPT
-A UDP -p tcp -m tcp --dport 19133 -j ACCEPT
-A UDP -p tcp -m tcp --dport 19132 -j ACCEPT
-A UDP -p udp -m udp --dport 19133 -j ACCEPT
-A UDP -p udp -m udp --dport 19132 -j ACCEPT
COMMIT
# Completed on Tue Aug 29 03:59:46 2023

And these are my network adapters:

0000:01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
0000:02:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01)

Last edited by bonkmaykr (2023-09-01 21:01:03)

---

I bought shoes from my drug dealer. I dunno what he laced them with, but I've been tripping all day.
Website - KangWorlds - Screw Gravity!

bonkmaykr

Member

Registered: 2022-12-22

Posts: 15

Re: [SOLVED] GeyserMC port will only forward over Wi-Fi, not ethernet.

"Everything is configured correctly in iptables and on the router itself"

Well, that was a lie...

I took a look at my adapters one more time through "ip a" and it turns out the ethernet the system was prioritizing over Wifi was on 192.168.1.32, not 192.168.1.35, which was the address I port forwarded.

The Paper server listened for both and forced the connections to go through to ethernet anyway after players pinged, but Geyser's port didn't do this, so anytime the ethernet cable was plugged in Linux was forcing Geyser face first into the router's firewall.

This was a pretty silly mistake on my part! I'll be marking the thread as solved

---

I bought shoes from my drug dealer. I dunno what he laced them with, but I've been tripping all day.
Website - KangWorlds - Screw Gravity!