I am having a strange issue with my Asus 88U reporting wrong IP for one of my OpenVPN clients. Hoping you would have some idea why.
I have:
Asus 88U
Merlin 380.59
VPN service provider
using OpenVPN client to connect to VPN provider
2 seperate OpenVPN Clients on router
Client 1 is AppleTV4, TCP 443 (Canadian server), Accept DNS Config. [Exlcusive], Policy Rules with IP of AppleTV4.
Client 2 is PC, UDP 443 (Miami-US server), Accept DNS Config. [Exlusive], Policy Rules with IP of PC.
Problem: Both connections are working finewhen turned on and show as connected within the router with no Error. But, when I do a DNS leak test using doileak or ipleak site, the client that is turned on first will show the proper IP VPN address that it is connected to, as it should. When I do a DNS leak test of the other client the IP address that shows up is the same as the client I turned on first. There are no leaks for either, it just wrongly identifies the client that I turned on second with the first client's VPN address. Very odd.
So, basically whatever OpenVPN client is turned on first is the VPN IP that is passed on to the client turned on afterwards even though they each use a different .ovpn server file from different server and one is using TCP and the other is using UDP.
Both LAN and WAN DNS Server is set to 192.168.1.1. I have DNSFilter on with Custom DNS as an OpenNIC DNS IP for the PC client when the PC OpenVPN tunnel is turned off for the PC. NOTE: Turning on or off DNSFilter makes no impact on the above problem with OpenVPN.
Is this a bug with firmware or do I have something setup wrong?
Suggestions for fix are welcome.
Thanks.
Take note that you don't need dnsfiltering with the new firmware so turning that on wont help in anything but confuse the matter further.
Looks like you are having a router conflict. You need to turn the power off cold boot the router. but before you do that disable both clients and make sure you take off start with LAN
What encryption are you using? Sometimes its happens when you use 2 servers from the same company that are on the same subnet.
try turning client 1 on and test it and then turn turn client 1 off
then turn client 2 on and test it .If there is no issues there then its a same subnet issue.
Now turn one client on and off until you have no issues when both clients are on at the same time.
I have seen this problem happen many times although i never saw that happen to me when I used blowfish-cbc
I had 3 clients on at the same time and never had a glitch.
I know Merlin is going to come here and say I am wrong because encryption doesn't matter but I think there is a bug with the aes-128-cbc where although its the preferred method I only started seeing these conflicts when I changed over to AES-128-CBC
and if you use AES-256-CBC good luck to have 2 clients working at the same time.
I really don't have the need to have 2 clients on at the same time. I have them configured but I use one at a time.
Maybe that would be the best solution for you. If you are not using the appleTV and the PC at the same time try doing that.
If not turn each service off and on until you have no issues when both services are ON.
Once that happens you are OK until the next router conflict.
I have seen some real weird things where the router freaks out so much that it actually leaks your local ISP IP address and DNS, scary.
So use multiple clients from the same server with caution.
What Merlin would probably suggest is have 2 separate VPN servers then its different subnets thus having no issues with dns leak.
or try Blowfish-cbc for both clients. Its not that it has ever been cracked and the big problem is with SHA and SHA1
google and Microsoft are trying to get that encryption out of the way because they feel its a security problem because its old technology
so even if you are using aes-128 its no better then blowfish.
Try out blowfish on both clients and see if you get any problems. If you don't stick with it that way.
I hvae 8 mbps modem so I now use AES-256 with sha256 because my bandwidth is not the end of the world
but if bandwidth limitations are an issue for you then try one of the methods I mentioned and see which works for you.
I know I am going to hear it from some people but you have nothing to lose but try