What's new

Asus RT-AC66U fw merlin vpn problem

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

mariuszpko

New Around Here
Hello,

I have Asus RT-AC66U connected to Internet via GSM USB modem. Device is working on the newest merlin firmware 374.40. The problem is when I create a VPN server and try to connect from Internet site. VPN think that local gateway interface is br0 (ip 192.168.1.1) but real Internet gateway is ppp0 interface (ip :5.60.117.xxx) created by GSM modem.

Guys - what is the way to configure VPN server and have access to it from Internet.

If I want to connect to VPN server from local subnet (192.168.1.x) of course is working fine, but can not connect from Internet.
 
nobody has a vpn problem ?

Hello guys !

Am I the only person with the VPN connection problem? Can anybody help me a little bit, maybe some you want any logs from router.

Like I said before VPN don't want to work, VPN is working inly from LAN, not from Internet. I got only USB GSM modem.

Mario
 
You need to set up a dynamic DNS on your router then traffic from the WAN can reliably be routed to your VPN server.
 
Thanks CaptainSTX for replay,

of course I did DDNS and ip address of wan using domaine name works fine.

I attached ifconfig and route print out, maybe it helps. I have also unblock ping from wan - and ping does not work.

admin@ASUS:/tmp/home/root# ifconfig
br0 Link encap:Ethernet HWaddr 60:A4:4C:69:7E:68
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:837799 errors:0 dropped:0 overruns:0 frame:0
TX packets:1614147 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:97643920 (93.1 MiB) TX bytes:1761832351 (1.6 GiB)

eth0 Link encap:Ethernet HWaddr 60:A4:4C:69:7E:68
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:372742 errors:0 dropped:0 overruns:0 frame:0
TX packets:335857 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:470628482 (448.8 MiB) TX bytes:37600934 (35.8 MiB)
Interrupt:4 Base address:0x2000

eth1 Link encap:Ethernet HWaddr 60:A4:4C:69:7E:68
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:866081 errors:0 dropped:0 overruns:0 frame:451335
TX packets:2000205 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:109981000 (104.8 MiB) TX bytes:2246418546 (2.0 GiB)
Interrupt:3 Base address:0x8000

eth2 Link encap:Ethernet HWaddr 60:A4:4C:69:7E:6C
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:5 Base address:0x8000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MULTICAST MTU:16436 Metric:1
RX packets:35137 errors:0 dropped:0 overruns:0 frame:0
TX packets:35137 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3836745 (3.6 MiB) TX bytes:3836745 (3.6 MiB)

ppp0 Link encap:point-to-Point Protocol
inet addr:46.169.203.122 P-t-P:10.64.64.64 Mask:255.255.255.255
UP POINTOPOINT RUNNING MULTICAST MTU:1500 Metric:1
RX packets:598815 errors:13 dropped:0 overruns:0 frame:0
TX packets:232935 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:806507579 (769.1 MiB) TX bytes:23421010 (22.3 MiB)

tun21 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.8.0.1 P-t-P:10.8.0.2 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP PROMISC MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

vlan1 Link encap:Ethernet HWaddr 60:A4:4C:69:7E:68
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:372740 errors:0 dropped:0 overruns:0 frame:0
TX packets:335850 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:468465115 (446.7 MiB) TX bytes:37337300 (35.6 MiB)


and

admin@ASUS:/tmp/home/root# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.64.64.64 * 255.255.255.255 UH 0 0 0 ppp0
10.8.0.2 * 255.255.255.255 UH 0 0 0 tun21
10.8.0.0 10.8.0.2 255.255.255.0 UG 0 0 0 tun21
192.168.1.0 * 255.255.255.0 U 0 0 0 br0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default 10.64.64.64 0.0.0.0 UG 0 0 0 ppp0


any ideas ?
 
Most cellular networks (in the US at least) block inbound traffic across their networks and are only allowing outbound connections from the device (I can confirm this is the case for Verizon Wireless). In which case you will not be able to connect to the IP address on your ppp interface.

You might want to check with your provider if they allow connections back to their network clients.
 
Most cellular networks (in the US at least) block inbound traffic across their networks and are only allowing outbound connections from the device (I can confirm this is the case for Verizon Wireless). In which case you will not be able to connect to the IP address on your ppp interface.

You might want to check with your provider if they allow connections back to their network clients.


Thanks for answer. Maybe you are right. Is any quick way to check it somehow?
 
Thanks for answer. Maybe you are right. Is any quick way to check it somehow?

Enable logging of dropped packets, then run a port scan from a website such as GRC's Shields Up. See if you actually get dropped packets showing up in your log.
 

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Staff online

Top