@bruce in passthrough mode, can I use the 2.5Gbps WAN port instead of the 1Gbps LAN port?
Also, I canNOT confirm that the workaround work. The GL-X3000 can get online but unable to passthrough IP.
I followed these steps however I still have this error. As a result even though the Glinet x3000 has an IP and handed one out to my firewall all packets are being dropped.
The interface is connected, but the Internet can't be accessed.
@bruce After copying the new dnsmasq, my X3000 does not give an IP address to my gateway. I haven't been able to test the curl. After copying the dnsmasq you reboot then execute the curl command? Or, after copying you execute the curl then reboot?
It still does not work
The checksum is ok, commands run ok, restart ok, the GL-X3000 is online and stated it is in passthrough mode but unable to passthrough IP to the connected device.
My router without issue, the client gets the modem IP.
If it does not work, please try to reset the network (Long press the reset button 4 seconds, or go to GL GUI > NETWORK > Network mode > Router), and execute this again:
It partially works. When i reboot the downstream router (an ASUS GT-AX11000), it was able to get the passthrough IP from the GL-X3000. However, when I reboot the GL-X3000, all was lost and it's back to private IP. Also, when the GL-X3000 reboot, the 192.168.8.1 admin panel site cannot be accessed after 1 minute into operation.
It appears that whenever the GL-X3000 reboot, the downstream device has to reboot as well to obtain an updated passthrough IP.
Firmware 4.4.13 automatically updates the passthrough IP without requiring downstream device to reboot.
UPDATE: If anyone has an ASUS router, under WAN setting \Internet Connection \Special Requirement from ISP \DHCP Query Frequency \ Normal mode will solve this issue.
I actually have come across this behaviour with 4.4.13 when using it with my Unifi gateway. Not sure if it's a new issue necessarily. I've even come across this with routers that do officially support passthrough mode.
@bruce I have the same problems as the others. After the reboot, the public IP is passed on for about 30 seconds, then the internal IP of the router is given again
@bruce: The installation was successful. Passthrough is also working again. However, I needed two reboots after the update. Before that, no IP address was received by the router. It has been running smoothly for the past hour.
I had to run the curl command twice (4.7.2), but afterwards, passthrough worked just fine through eth1 (LAN), but not eth0 (WAN), as was described before.
IPv6 assignment took a couple of interface restarts on my OPNsense, but that may be because of its interface configuration. I'll play with it some more and see what I can find out.
SSH and the admin page are both accessible at 192.168.8.1.
@PaxRoma Interesting: so other than higher bandwidth, what's the benefit of using the WAN port?
My T-Mobile connection is zippy (400-500Mb), but nowhere near 2.5Gb.