N66U - No remote access using asuscomm.com after openvpn client is connected.

[Vee Low]

I cannot believe that no-one can give a definitive guide on how to fix this issue when connected to an Open VPN Client.

Merlin, what is the point of having a remote management option, which you cannot access when connected to an Open VPN Client?

Thanks,

Vee

 

[L&LD]

I cannot believe that no-one can give a definitive guide on how to fix this issue when connected to an Open VPN Client.

Merlin, what is the point of having a remote management option, which you cannot access when connected to an Open VPN Client?

Thanks,

Vee

Too many variables, etc.

A definitive answer requires paying a professional for. This is a volunteer based forum.

 

[Vee Low]

I am sorry for my naivity but what are the variables?

When the router is not connected to the OpenVPN Client, the user can access the routers web interface via ddns (no-ip or asuscomm) and as soon as the router connects to an OpenVPN client the web interface is no longer accessible.

I appreciate their could be other reasons, however lets just go with the simple scenario?

Remote Access to the router should be possible whatever service it is running.

This is a serious flaw in the routers operation if the web interface is no longer accessible once connected to the OpenVPN client.

Networking is not my forte and it probably is something to do with routing tables, however I do not see this basic function being a job of a paid professional.

I spend a lot of times on other forums helping others, specifically jailbroken IOS devices and it would be very unlikely that a user would state to another user with a problem (fundamentally a major flaw in the devices operation) that they should resort to a paid service to overcome a problem for what seems like a mandatory feature whether connected to the OpenVPN Client or not.

I am very gratefull for any assistance from volunteers here who have more experience and knowledge in this specific field which is more their forte than mine.

Once again thank you for your feedback.

Vee

 

[JimmyCap]

So, not to add to the fray but I'm seeing similar behavior, albeit a little different. I've configured the Redirect Internet Traffic option under the OpenVPN Client page to use Policy Rules. I've added all of my network machines and devices to use the WAN connection (no reason to waste a GB fiber connection on the PIA VPN) and one machine (VM) using the VPN interface. Since doing that, I can't access that VM from my network, however I can access network resources FROM the VM (Logged into the VM from the host machine). So, it seems to simply be a matter of routing. I'm not that well versed in configuring IP tables otherwise I'd give it a shot. Hopefully this helps though.

 

[sfx2000]

Too many variables, etc.

A definitive answer requires paying a professional for. This is a volunteer based forum.

Interesting issue - most remote Admin type tools on consumer routers - they set up a secure tunnel to a server somewhere on the other side -- OVPN, depending on where it falls within the IP tables rulesets and IP routes, might override the stunnel...

hmmm... don't have an Asus router to check this against...

 

[Vee Low]

What would Teamviewer be doing different to RealVNC to overcome this problem?

Teamviewer is always accesible when connected to OpenVPN client, where RealVNC is not.

Before everybody jumps on the Bandwagon and says why do I not stick with using Teamviewer.

Well I find RealVNC more user friendly with remote administration.

But there must be something that TeamViewer is doing to overcome this problem.

 

[sfx2000]

TeamViewer does hole-punching by logging into a control server on their end - and they connect the dots...

 

[Deuang]

Any update on this, I have had the same problem for months and cannot get around it. As soon as my openvpn client is connected that's the end of me reaching anything at home externally.

Disconnect the vpn client and everything is working again.