EarthBoundX5 DD-WRT Novice

Joined: 10 Mar 2009 Posts: 23
|
Posted: Fri Mar 07, 2025 19:38 Post subject: Linksys MX4300 - Port Forwarding Not Working When QoS Enable |
|
EDIT: Port forwarding is successful in the first few seconds of Applying Router settings. Specifically, if I click apply on the UPnP page, for a short moment during/immediately after, external port checks will see my forwarded ports as open.
EDIT 2: It appears if I disable QoS, port forwarding works! HTB / FQ_CODEL are what I was using for QoS. This seems like a bug?
Port Forwarding seems to be non-functional with any builds I try for the MX4300. Given how regularly used this function is, I have a hard time believing it's anything but a misconfiguration on my end...however a factor could be my means of connecting to the Internet being less common?
==Backstory==
I've been using DD-WRT for 15+ years, with many different routers, Internet connections, and environments. Never had an issue with Port Forwarding. I can navigate the UI, but CLI is not my strength with it.
I just moved to a Linksys MX4300 last month, from an Asus RT-AC68U. I cleanly flashed the MX4300 with r58730, and was previously using r45385 on the RT-AC68U. Lots had changed (such as Switch Config being gone or interfaces named different), but I did my best to replicate the configuration from old to new manually (no attempt at restoring from backup).
I used to host services, game servers, voice chat, and the like; but now I'm pretty much just hosting Plex (TCP Port 32400) for my personal use outside the home. With the new router, I was getting some odd behavior with Plex, but things were still "working". I upgraded to r58976, and suddenly, nothing was working with regards to Plex or any port forwarding. I tried r59468 and r59582, and still nothing worked. I reverted to r58730 and restored config from backup before upgrading. Plex started to "work" externally again; however, this is when I noticed port forwarding in general didn't seem to be working as expected.
I've tried something as basic as forwarding a port to a web server (Using Port 56562), and it's completely inaccessible externally.
Upgraded to r60121, same issues.
==WAN INFO==
DSL, Modem configured for Transparent Bridging. Should be no Double NAT. Router connects via PPPoE. Router IP is the same as WhatIsMyIP.com.
The following commands are present to allow me to access the modem UI:
Startup
Code: | ifconfig `nvram get wan_ifname`:0 192.168.0.2 netmask 255.255.255.0 |
Firewall
Code: | iptables -t nat -I POSTROUTING -o `nvram get wan_ifname` -d 192.168.0.0/24 -j MASQUERADE |
==Test Cases / Random Info==
RouterIP:Port - Does not forward to server (I feel this is a smoking gun to my problem, but I don't know enough to know why)
ServerIP:Port - Server responds
ExternalIP:Port, Internally - Server responds
ExternalIP:Port, Externally - No response
Disabled SPI Firewall - No changes
Rebooting the modem, randomly it seems, the port forwarding will work. During a reboot, I've been able to hit the web server externally at least 3 times, making no changes but the reboot.
Removed WAN related Firewall config - No changes
External Port Checking Tools all report the ports forwarded as not being open.
I have IPv6 disabled, but random devices seem to respond to pings with IPv6 addresses for some reason. I feel this is another possible smoking gun.
==Router Details==
DD-WRT build: DD-WRT v3.0-r60121 std (03/07/25)
Router brand / model: Linksys MX4300
Operating & wireless modes: Gateway & AP
==Sticky Requested Outputs==
See attachments for outputs and logging. |
|