What's new
By:

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

Recent content by Jetblue

  1. J

    VPNDirector (VPN sequence)

    Thanks bennor. This link is great... He says it right there. Bingo. "If OpenVPN client #1 fails, it automatically falls through to OpenVPN client #2. If OpenVPN client #1 eventually recovers, it will automatically return to OpenVPN client #1. That's just the wait it works." All good. He...
  2. J

    VPNDirector (VPN sequence)

    So, I followed the Wiki and sure enough it automatically orders the WGC clients in the rules, based on the Wireguard VPN drop down. You can see below. And just as the Wiki says, it is now using my Failover choice (Toronto) as the primary. Not a huge deal, it means that I have go through...
  3. J

    VPNDirector (VPN sequence)

    Yes, the seven devices shown are going over WAN to bypass the VPN, and everything else goes through the Dallas WGC initially. Some of those devices are on Guest Networks (VLAN) so the IP's are a little different. So if the rules govern... and Dallas WGC goes down, does the VPN director just...
  4. J

    Guest Network Limitation 3006.102.4?

    Will do. And I agree with your comment about the subnet/main network relationship. The fact is... the "pro" version is a little too much GUI... less configuration flexibility. I'm sticking with the non-pro firmware (which works all around) until Asuswrt-Merlin creates a new one. Thx
  5. J

    VPNDirector (VPN sequence)

    I am using the RT-AX88U-Pro on 3004.388.8.4 firmware, successfully using Wireguard (WG) with the VPN Director. I connected to 2 VPN locations (Toronto & Dallas), and I connect to Dallas in my VPN Director, all working fine. The documentation instructs that for a VPN Kill Switch, do not apply...
  6. J

    Guest Network Limitation 3006.102.4?

    Thanks for the response bennor. I was using 3004.388.8.4. I did perform a hard reset, and that helped me to at least access the system. My guest network is almost exactly like yours. What I discovered was that after getting it up and running, it was very unstable. I believe that it has...
  7. J

    Guest Network Limitation 3006.102.4?

    I just upgraded my RT-AX88U Pro to 3006.102.4 and ran into something odd. I did not lose any settings. The word-salad in the release notes regarding the VPN DNS configuration made no sense but my VPN continued to work fine. 1 out of 3 guest networks (VLAN) also persisted, explained in the...
  8. J

    Is this a bug in VPN Director?

    I wanted to update folks on the log output from this below. Just FYI, client 4 is Dallas, client 1 is Toronto. Anything look off here? Aug 5 22:13:58 vpndirector: Routing Device for Toronto from 192.168.50.41 to any through wgc1 Aug 5 22:13:58 wireguard: Forcing 192.168.50.41 to use DNS...
  9. J

    Is this a bug in VPN Director?

    Thanks. Yeah I tried it with no luck. Generated 3 different key pairs... rebooted the router etc... but same result. I think your idea makes perfect sense though. I might add, however.. that you are right about the connection. I can run nslookup and ping commands from the .41 device, but no...
  10. J

    Is this a bug in VPN Director?

    Yes, I imported that from Surfshark. It uses a key that I can create which encrypts the user and pwd and I copy and paste that over. I am allowed to create multiple keys and I use this same key with Dallas. Also this same profile is used for the Toronto ALL rule and it works great. I will...
  11. J

    Is this a bug in VPN Director?

    Yeah, it seems that it is somehow DNS related. Out of frustration I reviewed the Merlin router log. In there it clearly showed that the device was assigned to Toronto, and it also showed two lines forcing the Toronto DNS for that rule. When reviewing Netstat I did see a destination target for...
  12. J

    Is this a bug in VPN Director?

    Yes... So in my above comment... Focusing now on this: 2. If I disable the "Remainder of Toronto WG", then two things happen; --- The secluded device (192.168.50.41) set for Toronto cannot get online whatsoever. --- Everything else goes to Dallas There's only one "ALL" that is going to Dallas...
  13. J

    Is this a bug in VPN Director?

    Thanks for the response. I see that the priority is actually set in the order of the drop down box of the VPN Client tab. So, I went there and deleted the original order and put in the correct order, Toronto first. Now Toronto shows up as a priority WGC1. I altered the rules as follows...
  14. J

    Is this a bug in VPN Director?

    Where are your rules for everything else? I have to put a rule for ALL IP's in the rules, or else it will just send them to the public internet and bypass the VPN. That's the actual problem for me, because it's a catch 22... Each time I put an ALL IP rule in, it nullifies everything after it.
  15. J

    Is this a bug in VPN Director?

    Yes, I saw that... but the logic does not work: For any traffic to go through the VPN there must be a rule for the IP, right? (otherwise it will bypass the VPN by default). So, when a VPN is selected as the top priority for all VPN traffic (WGC1), the second VPN (WGC2) becomes nullified. Once...
See more
Back
Top
✖