Recent content by tsi08

  • 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!

  1. T

    382.1 broke static route

    Will give that a try and report
  2. T

    382.1 broke static route

    Exactly. I was also very surprised that it worked in the first time but then I could also access the hard drive connected to the router at 192.168.2.1 besides other clients via SMB without even disabling the firewalls on any client. I had NAT and firewall turned off on the router back then. Heck...
  3. T

    382.1 broke static route

    Tried but all my attempts were futile
  4. T

    382.1 broke static route

    I cannot access any client using SMB on the 192.168.2.x subnet although I can ping them. For example I have a laptop connected to the ac68u with 192.168.2.194 as IP; I can both ping and tracert it from the 192.168.1.x network and that's about it. I cant access its shared files/folders. The...
  5. T

    382.1 broke static route

    Accessing any client/routers uplink from the secondary router is never going to be an issue. This works normally in almost all scenarios but in my situation I need access to the secondary router, ac68u and its clients, from the primary router, the ac88u. Port forwarding port 80 on the ac68 does...
  6. T

    382.1 broke static route

    NAT loopback is currently set to asus but I have also tried it on Merlin. Still was a no go.
  7. T

    382.1 broke static route

    Yes I have both firewall and NAT disabled on the ac68u
  8. T

    382.1 broke static route

    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...
  9. T

    382.1 broke static route

    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.
  10. T

    382.1 broke static route

    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
  11. T

    382.1 broke static route

    No go with NAT. I've been struggling with this for the past 2 days now.
  12. T

    382.1 broke static route

    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.
  13. T

    382.1 broke static route

    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...
  14. T

    382.1 broke static route

    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...
  15. T

    382.1 broke static route

    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...
Top