Menu
What's new
By:
Filters Better Search

Search results

  • 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. L

    Release Asuswrt-Merlin 3004.388.8_2 is now available

    @eibgrad Thanks for the clarification. Yes, I access the GUI remotely over the WAN, and that's where the issue arose. According to RMerlin, adding the router's IP to the WAN interface resolves this issue. I think he mentioned it's a different implementation now, ensuring the killswitch works...
  2. L

    Release Asuswrt-Merlin 3004.388.8_2 is now available

    @RMerlin Got it, thanks for explaining that. I've added 192.168.1.1 to the WAN interface (Iface WAN). Now I'm able to use 192.168.1.0/24 in OVPN3 without any issues. Thanks so much!
  3. L

    Release Asuswrt-Merlin 3004.388.8_2 is now available

    @RMerlin Thanks! I excluded the router's IP (192.168.1.1), everything started working smoothly again! I needed to route specific devices: some to OVPN1, others to OVPN2, and the rest to OVPN3. (I used the 192.168.1.0/24 subnet in the previous version). Is it possible to exclude the router's...
  4. L

    Release Asuswrt-Merlin 3004.388.8_2 is now available

    I'm experiencing a similar issue. I connected to OVPN1 with the kill switch on and encountered no problems until I added 192.168.1.0/24 to the VPN director. This caused me to lose access to the web UI, and I had to reset the router to regain access. When I set up OVPN1 with the kill switch...
Top