I’ve just upgraded from 3.5.4 build 1681 to 3.6.0 build 1805 and it has caused a major problem. Booting from 3.5.4 makes it go away with no other changes, so I’m stumped.
My WAN IP address is 192.168.168.50/24. It sits on my home network, and has another device plugged directly into the second port which is on 192.168.168.51.
The AP mode is set at Router / IP Forwarding although the behavior (as far as my use) is exactly the same if set to Router / NAT.
The LAN (wireless) side address is 192.168.169.50. LAN Gateway is the same. DNS1 is set to 192.168.168.1, which is the router on the home network.
A DHCP Range is set at 192.168.169.102 - 192.168.169.200.
A hardwired static IP with a MAC address sits on 22.214.171.124.
This is set because the AP One Rugged gets disconnected from the home network, but needs to connect and feed DHCP addresses to tablets and iPads that must access the second Ethernet port on 192.168.168.51.
Here s my problem.
When connected under 3.6.0, the tablets on the 169 network can connect to the internet and to the 168 network, but not to the 192.168.168.51 device on the second port of the AP One Rugged. They CAN connect to the AP One Rugged itself (192.168.168.50).
Similarly, devices on the 168 network can connect to the AP One Rugged on .50, but they cannot connect to or ping the device on the second port.
If I boot from the 3.5.4 firmware all is well. It is as if the 3.6.0 firmware is ignoring the second port.
Is this just a bug, or is there a configuration setting I’m missing relating to 3.6.0?