Port forwarding not working on GL-B1300 after the 4.x firmware upgrade

npburns224 · 2023-12-21T06:50:43.971Z

I have been using my Raspberry Pi as a Wireguard server for years without any issue.
After upgrading my router to firmware version 4.3.7, my client devices can no longer connect.

I have tried the following without success:

Hard reset router with Uboot. Installed firmware version 4.3.7.
Wiped Raspberry Pi boot drive and performed a fresh OS installation.
Assigned a static IP to my Raspberry Pi.
Set up a Wireguard server on Raspberry Pi using PiVPN.
Forwarded port 51820 on my Raspberry Pi’s IP address using the router’s web interface.

My network is setup as follows:
Comcast Modem (bridge mode) → GL-B1300 (router mode) → switch → Raspberry Pi (Wireguard server)

My Raspberry Pi has been assigned a static IP of 192.168.1.2.
I am using Cloudflare for DNS (1.1.1.1, 1.0.0.1).

Here is my port forward configuration:

IMG_02301198×1238 79.9 KB

The only change I have introduced to my setup within the last several months has been updating the router’s firmware, so I am assuming that’s where the problem must lie.

The built-in Wireguard server on the router appears to work just fine, however I would prefer to continue using my Raspberry Pi.

hansome · 2023-12-21T12:11:21.144Z

Please export log
http://192.168.8.1/#/logview

npburns224 · 2023-12-21T15:55:41.818Z

Here are my logs:
logread.zip (24.9 KB)

hansome · 2023-12-22T07:30:07.804Z

I checked the debug info, and nothing special.
Please ensure the Raspberry Pi gateway is B1300 so traffic can get back originated from port forward.

npburns224 · 2023-12-22T07:36:09.263Z

The Raspberry Pi is connected to a switch plugged directly into my router. I have also verified that it’s using the assigned static IP.

As I mentioned in my post, I haven’t changed anything about my setup other than upgrading the router’s firmware. This setup was operational immediately before the upgrade.

hansome · 2023-12-22T07:44:33.606Z

Can you type the command in RaspberryPi terminal

ip route

npburns224 · 2023-12-22T07:56:24.704Z

pi@raspberrypi:~ $ ip route
default via 192.168.1.1 dev eth0 proto dhcp src 192.168.1.2 metric 202 
10.71.121.0/24 dev wg0 proto kernel scope link src 10.71.121.1 
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
192.168.1.0/24 dev eth0 proto dhcp scope link src 192.168.1.2 metric 202 
pi@raspberrypi:~ $

hansome · 2023-12-22T08:12:14.207Z

I ran out of ideas. My b1300 4.3.7 port forward for wireguard works fine.

npburns224 · 2023-12-22T08:25:54.686Z

I’m not too sure either. I thought I might see some improvement after a fresh install on both the router and Pi, but unfortunately things are still the same.

I’ve been running this exact setup for nearly 5 years, so it’s a real head scratcher.