Unable to connect to router from outside LAN

[macster2075]

Maybe your "modem's" public IP address has changed. Are you using DDNS on the Asus router?

Yes.. this is what I've been using for a while and it worked until recently.

 

[macster2075]

I also checked my modem's public IP and it matches the dns server.

 

[ColinTaylor]

I also checked my modem's public IP and it matches the dns server.

It would be worth checking that the config file that your VPN client is using has your DDNS name in there rather than an IP address.

 

[macster2075]

It would be worth checking that the config file that your VPN client is using has your DDNS name in there rather than an IP address.

This is what the config file shows...

# Config generated by Asuswrt-Merlin 386.7, requires OpenVPN 2.4.0 or newer.

client
dev tun
proto udp
remote 192.168.254.64 1194
resolv-retry infinite
nobind
float
ncp-ciphers AES-256-GCM:AES-128-GCM:AES-256-CBC:AES-128-CBC
keepalive 15 60
auth-user-pass
remote-cert-tls server

 

[macster2075]

If I can't make it work again, I may try to use a Powerline Adapter to connect my work computer to the router if I set the Modem in bridge mode. The only thing I worry about is, I make and receive voip calls for work and I know Powerline Adapters are very sensitive to interference and it could make me drops calls.

I rather not have to do this and I prefer to get it to work as it was before with these same settings. Not sure what happened since I didn't make any changes to the modem. I rarely ever connect to the modem to do anything at all. So I am confused as to why it would just stop working.

 

[ColinTaylor]

This is what the config file shows...

# Config generated by Asuswrt-Merlin 386.7, requires OpenVPN 2.4.0 or newer.

client
dev tun
proto udp
remote 192.168.254.64 1194
resolv-retry infinite
nobind
float
ncp-ciphers AES-256-GCM:AES-128-GCM:AES-256-CBC:AES-128-CBC
keepalive 15 60
auth-user-pass
remote-cert-tls server

The remote line in the config is wrong.

Change "remote 192.168.254.64 1194" so that is has your DDNS name instead of 192.168.254.64. For example:

remote mydns.asuscomm.com 1194

 

[macster2075]

do you mean this?

 

[macster2075]

If the config is wrong, why would Asus generate a config with the wrong info.. and also, how come it's been working fine all this time?

 

[ColinTaylor]

do you mean this?
View attachment 44705

Probably not, I don't use that DDNS service so don't know how that works. It's whatever you used in post #22.

If the config is wrong, why would Asus generate a config with the wrong info.. and also, how come it's been working fine all this time?

I can only guess that the config file your client is using was generated sometime in the past. It would only have worked if you were testing it from inside your LAN. That config file will not work from the internet.

 

[macster2075]

I just generated it today and it shows the same thing. It's the same config info I've been using for a while. I would go to the store and I would connect to the router without issues.
It stopped connecting just a few days ago.

 

[macster2075]

This is the page on how to setup DnsoMatic which is part of OpenDns.

DNS-O-Matic | Faq

DNS-O-Matic (dnsomatic.com) provides you a free and easy way to announce your dynamic IP changes to multiple services with a single update.

www.dnsomatic.com

 

[ColinTaylor]

I just generated it today and it shows the same thing. It's the same config info I've been using for a while. I would go to the store and I would connect to the router without issues.
It stopped connecting just a few days ago.

I can't guess what's happened with your router, but 192.168.254.64 is not a public IP address therefore it will never be reachable from the internet.

This is the page on how to setup DnsoMatic which is part of OpenDns.

DNS-O-Matic | Faq

DNS-O-Matic (dnsomatic.com) provides you a free and easy way to announce your dynamic IP changes to multiple services with a single update.

www.dnsomatic.com

That's all Greek to me. Just use the DDNS name you created.

 

[macster2075]

Not sure what you mean by "use the ddns name you created".
I didn't create the ddns name, I just made an account which is the username (my email) and password... that's it. No ddns name was issued.
All the info for this particular ddns is listed on my post #21

 

[ColinTaylor]

OK. Looking on YouTube it seems like you're only using DnsoMatic to tell OpenDNS what your IP address so that it can do DNS filtering. In other words, you are not using it as a DDNS service (despite the name).

So, without a DDNS name you will have to take the public IP address you found earlier and use that in the client's config file instead of 192.168.254.64.

Of course, when that IP address changes in the future you will have to manually update it again.

 

[macster2075]

Right, I use OpenDns for content filtering and I thought since DnsOmatic was in the list of ddns, I was ok to use it.
So I thought I was killing 2 birds with one shot.. dnsomatic was updating OpenDns with my public IP automatically and I can also connect to my router from outside the LAN.

Now, I have a VPN (true VPN) running on the router, so that IP would be from the VPN services not my actual IP.. is this going to be a conflict?

 

[macster2075]

OpenDns has an updater app for Windows that updates OpenDns with my public IP, but it only works when I am not using a VPN. Once I disconnect from the VPN (true vpn), then the updater starts working.
So I guess I won't be able to use OpenDns along with a VPN unless I manually update the IP address, which I am not planning on doing