What's new

382.1 broke static route

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

tsi08

Occasional Visitor
I recently got an ac88u which replaced my ac68u as my main router. The ac88u is connected to the internet via PPoE while the ac68u is cascaded to it lan to wan.

ac88u external IP 192.168.1.1 and internal IPs are set to DHCP starting with 192.168.1.2.
ac68u external IP 192.168.1.10 and internal IPs are again set to DHCP starting with 192.168.2.2. Internal IP is set to 192.168.2.1.

Static route set on ac88u 192.168.2.0 255.255.255.0 192.168.1.10.

Before updating to 382.1 the ac88u was on 380.66_4. My ac68u is still on 380.66_4.

I can no longer access my clients connected to the ac68u while I am connected to the ac88u following the update. Everything worked fine on 380.66_4.

Any help will be immensely appreciated!
 
WAN and LAN need to be on different subnet. You will need to change your RT-AC88U configuration.
 
Sorry for the confusion. The RT-AC88U external IP is obtained directly from my ISP while the LAN IP is set at 192.168.1.1 and DHCP set at 192.168.1.2 onwards. Both routers are on different subnets as you can see. I can access clients on the AC88U while connected to the AC68U but not vice versa. I have tried setting the static WAN IP of the RT-AC68U outside of the DHCP zone of the AC88U, for example, at 192.168.1.2 and then DHCP starting at 192.168.1.3 but that also did not work. Disabling NAT on the AC68U also has no effect.

To be honest, I have transmission running through entware on the RT-AC68U which I was able to access from the AC88U before updating to 382.1. Besides SMB, this is what I'm more interested in accessing from any of my computers connected to the primary router. I could do a LAN to LAN cascade in between the two routers but then transmission would not work on the AC68U which would defeat the purpose of my setup.

I am at a loss here. Maybe reverting back to 380.66_4 could fix the issue again since it worked perfectly then. But I'd rather not as I'd prefer to have those routers always updated to the latest Merlin.

Any further inputs?
 
No idea if Asus changed something to routes with 382, that code is now closed-source as they are trying to protect their Dual WAN implementation.
 
Well I'm pretty sure something's changed. Reverted back to 380.66_4 with the same IP ranges and everything is back to normal. Went back to 382.1 and the issue is back again.
Something worth mentioning is that with 382, tracert does find my clients on ac68u, meaning the routing is correct but I just cannot access them via SMB or even open the ac68u's webpage while connected to the ac88u. Pings also go through.
 
tracert does find my clients on ac68u, meaning the routing is correct
Maybe you should change the title as this is not a routing issue.
but I just cannot access them via SMB or even open the ac68u's webpage while connected to the ac88u. Pings also go through.
Maybe you have two separate problems. How are you accessing the SMB share, by IP address I assume not name? Have you enabled "Enable Web Access from WAN" on the AC68U and tried accessing it at 192.168.1.10?
 
Web access from WAN is enabled, NAT disabled and firewall disabled too. I can actually access the webui using http://192.168.1.10:8080/ . I could actually access the webui and SMB using the ac68u internal LAN IP 192.168.2.1 before I updated the ac88u to 382.1. This is distressing.
 
What baffles me the most is that it worked perfectly fine before the update. I could technically go the LAN to LAN way in cascading both routers but then I would lose transmission on the ac68u and I really do not wanna go that way
 
Can you access client devices on the 192.168.2.x network from the 192.168.1.x network? In other words, is it just the router or the whole subnet that is inaccessible?
 
Nope. This is what i have been trying to fix. I have no access to any of my clients on the 192.168.2.x network unless I connect to the ac68u. Accessing the 192.168.1.x network works flawlessly from the 192.168.2.x network.
 
I have no access to any of my clients on the 192.168.2.x network unless I connect to the ac68u.
There seems to be a contradiction here?:confused:
Something worth mentioning is that with 382, tracert does find my clients on ac68u, meaning the routing is correct but I just cannot access them via SMB or even open the ac68u's webpage while connected to the ac88u. Pings also go through.
 
Tracert and pings do go through to 192.168.2.1. OK i've got a hard drive connected to the ac68u for SMB which I used to be able to access from file://192.168.2.1/ That does not work anymore now even though I can ping that address. Http://192.168.2.1/ from the ac88u used to allow me to access the webui of the ac68u, now that does not work either. Accessing transmission at http://192.168.2.1:9091/ and my downloaded files now requires me to connect to the ac68u, otherwise its a no go.

Does this make my issues clearer?
 
So 192.168.2.X can access 192.168.1.X but not the other way around? Could be firewall, is that disabled on the 68U?
 
Yes I have both firewall and NAT disabled on the ac68u
I'd think nat required so that you can access the secondary subnet, but I see you've already tried enabling NAT to no positive effect.

What setting is NAT loopback set to? Wondering if this is changing between f/w flashes.
 
NAT loopback is currently set to asus but I have also tried it on Merlin. Still was a no go.
 
Dunno if this might help.
I run the isp router and disabled wifi and just set a dhcp of 192.168.1.2-5 just in case i needed to use it wired.
I set dmz to 192.168.1.3 which i wire from one port to the ac88u.
I set the asus as static changed the dhcp to 192.168.2.2-254 and it runs all the wireless and normal wired stuff.

Both have nat...i cant turn it off on the isp router..
DMZ from 1 router to the other???
 

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top