WRT54GS VPN issues

Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware
Author Message
sjgoel
DD-WRT Novice


Joined: 17 Apr 2019
Posts: 4

PostPosted: Wed Apr 17, 2019 2:15    Post subject: WRT54GS VPN issues Reply with quote
I am trying to setup a secondary VPN router (Linksys WRT54GS ​v1.1 ​running DD-WRT​ v3.0-r37305 mega 10/10/18​) behind the primary router (AT&T Arris BGW210), using NordVPN UDP protocol. I enabled IP Passthrough on the primary router.
I followed the steps enlisted at the NordVPN website (https://nordvpn.com/tutorials/dd-wrt/openvpn-gui/) word-by-word but:

- I get error: RECONNECTING network-unreachable
- NTP time differs though I have chosen correct time zone as well as NTP server IP.

​I have searched the forums and tried whatever has been suggested, but to no avail.​ Log enclosed.

Please help.

Thanks​

Clientlog:
19691231 19:00:18 W WARNING: Using --management on a TCP port WITHOUT passwords is STRONGLY discouraged and considered insecure
19691231 19:00:18 W WARNING: file '/tmp/openvpncl/ta.key' is group or others accessible
19691231 19:00:18 W WARNING: file '/tmp/openvpncl/credentials' is group or others accessible
19691231 19:00:18 I OpenVPN 2.4.6 mipsel-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Oct 10 2018
19691231 19:00:18 I library versions: OpenSSL 1.1.1 11 Sep 2018 LZO 2.09
19691231 19:00:18 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:16
19691231 19:00:18 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
19691231 19:00:19 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
19691231 19:00:19 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
19691231 19:00:19 I TCP/UDP: Preserving recently used remote address: [AF_INET]207.189.2.219:1194
19691231 19:00:19 Socket Buffers: R=[109568->109568] S=[109568->109568]
19691231 19:00:19 I UDPv4 link local: (not bound)
19691231 19:00:19 I UDPv4 link remote: [AF_INET]207.189.2.219:1194
19691231 19:00:19 N write UDPv4: Network is unreachable (code=128)
19691231 19:00:19 I Network unreachable restarting
19691231 19:00:19 I SIGUSR1[soft network-unreachable] received process restarting
19691231 19:00:19 Restart pause 5 second(s)
19691231 19:00:24 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
19691231 19:00:24 I TCP/UDP: Preserving recently used remote address: [AF_INET]207.189.2.219:1194
19691231 19:00:24 Socket Buffers: R=[109568->109568] S=[109568->109568]
19691231 19:00:24 I UDPv4 link local: (not bound)
19691231 19:00:24 I UDPv4 link remote: [AF_INET]207.189.2.219:1194
19691231 19:00:24 N write UDPv4: Network is unreachable (code=128)
19691231 19:00:24 I Network unreachable restarting
19691231 19:00:24 I SIGUSR1[soft network-unreachable] received process restarting
19691231 19:00:24 Restart pause 5 second(s)
19691231 19:00:29 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
19691231 19:00:29 I TCP/UDP: Preserving recently used remote address: [AF_INET]207.189.2.219:1194
19691231 19:00:29 Socket Buffers: R=[109568->109568] S=[109568->109568]
19691231 19:00:29 I UDPv4 link local: (not bound)
19691231 19:00:29 I UDPv4 link remote: [AF_INET]207.189.2.219:1194
19691231 19:00:29 N write UDPv4: Network is unreachable (code=128)
19691231 19:00:29 I Network unreachable restarting
19691231 19:00:29 I SIGUSR1[soft network-unreachable] received process restarting
19691231 19:00:29 Restart pause 5 second(s)
19691231 19:00:34 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
19691231 19:00:34 I TCP/UDP: Preserving recently used remote address: [AF_INET]207.189.2.219:1194
19691231 19:00:34 Socket Buffers: R=[109568->109568] S=[109568->109568]
19691231 19:00:34 I UDPv4 link local: (not bound)
19691231 19:00:34 I UDPv4 link remote: [AF_INET]207.189.2.219:1194
19691231 19:00:34 N write UDPv4: Network is unreachable (code=128)
19691231 19:00:34 I Network unreachable restarting
19691231 19:00:34 I SIGUSR1[soft network-unreachable] received process restarting
19691231 19:00:34 Restart pause 5 second(s)
19691231 19:00:39 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
19691231 19:00:39 I TCP/UDP: Preserving recently used remote address: [AF_INET]207.189.2.219:1194
19691231 19:00:39 Socket Buffers: R=[109568->109568] S=[109568->109568]
19691231 19:00:39 I UDPv4 link local: (not bound)
19691231 19:00:39 I UDPv4 link remote: [AF_INET]207.189.2.219:1194
19691231 19:00:39 N write UDPv4: Network is unreachable (code=128)
19691231 19:00:39 I Network unreachable restarting
19691231 19:00:39 I SIGUSR1[soft network-unreachable] received process restarting
19691231 19:00:39 Restart pause 10 second(s)
19691231 19:00:49 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
19691231 19:00:49 I TCP/UDP: Preserving recently used remote address: [AF_INET]207.189.2.219:1194
19691231 19:00:49 Socket Buffers: R=[109568->109568] S=[109568->109568]
19691231 19:00:49 I UDPv4 link local: (not bound)
19691231 19:00:49 I UDPv4 link remote: [AF_INET]207.189.2.219:1194
19691231 19:00:49 N write UDPv4: Network is unreachable (code=128)
19691231 19:00:49 I Network unreachable restarting
19691231 19:00:49 I SIGUSR1[soft network-unreachable] received process restarting
19691231 19:00:49 Restart pause 20 second(s)
19691231 19:00:53 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19691231 19:00:53 D MANAGEMENT: CMD 'state'
19691231 19:00:53 MANAGEMENT: Client disconnected
19691231 19:00:53 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19691231 19:00:53 D MANAGEMENT: CMD 'state'
19691231 19:00:53 MANAGEMENT: Client disconnected
19691231 19:00:53 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19691231 19:00:53 D MANAGEMENT: CMD 'state'
19691231 19:00:53 MANAGEMENT: Client disconnected
19691231 19:00:53 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19691231 19:00:53 D MANAGEMENT: CMD 'status 2'
19691231 19:00:53 MANAGEMENT: Client disconnected
19691231 19:00:54 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19691231 19:00:54 D MANAGEMENT: CMD 'log 500'
19691231 19:00:00
Sponsor
Per Yngve Berg
DD-WRT Guru


Joined: 13 Aug 2013
Posts: 6870
Location: Romerike, Norway

PostPosted: Wed Apr 17, 2019 14:23    Post subject: Reply with quote
VPN is discussed in the Advanced Networking Forum. I'm sure some of the experts there will help you.

What throughput do you expect? The weak CPU of that router will not give you more than 1 Mbit/s over VPN.
sjgoel
DD-WRT Novice


Joined: 17 Apr 2019
Posts: 4

PostPosted: Wed Apr 17, 2019 14:27    Post subject: Reply with quote
Per Yngve Berg wrote:
VPN is discussed in the Advanced Networking Forum. I'm sure some of the experts there will help you.

What throughput do you expect? The weak CPU of that router will not give you more than 1 Mbit/s over VPN.


Thanks. Will check the other forum.

I am on a 100Mbps connection and using a GL-AR300 mini VPN router, which gives me about 6-7 mbps. I thought Linksys would improve this....!! I know it is quite an old router.
Per Yngve Berg
DD-WRT Guru


Joined: 13 Aug 2013
Posts: 6870
Location: Romerike, Norway

PostPosted: Wed Apr 17, 2019 14:50    Post subject: Reply with quote
https://wikidevi.com/wiki/Linksys_WRT54GS_v1.1

It's a 200 Mhz CPU.

https://wikidevi.com/wiki/GL.iNet_GL-AR300M
sjgoel
DD-WRT Novice


Joined: 17 Apr 2019
Posts: 4

PostPosted: Wed Apr 17, 2019 14:53    Post subject: Reply with quote
Per Yngve Berg wrote:
https://wikidevi.com/wiki/Linksys_WRT54GS_v1.1

It's a 200 Mhz CPU.

https://wikidevi.com/wiki/GL.iNet_GL-AR300M


Thanks. Is clear, that this is of no use.
jwh7
DD-WRT Guru


Joined: 25 Oct 2013
Posts: 2670
Location: Indy

PostPosted: Wed Apr 17, 2019 14:53    Post subject: Reply with quote
Per Yngve Berg wrote:
What throughput do you expect? The weak CPU of that router will not give you more than 1 Mbit/s over VPN.
mrjcd has stated VPN on old WRT54's to max out at 6 Mb/s in the ideal best case, but that 2-3 is more realistic. But ya, still slow. :-/

@sjgoel You should clock the GS to 250 for some throughput improvement. Research the build threads; you may need an older build to get VPN working; mrjcd used VPN on a WRT54 with 33492 and 33986. Also note that newer builds with openVPN 2.4 need a couple settings:
egc wrote:
OpenVPN 2.4 is stable but you have to tweak your config with: `mtu-disc yes` & `proto udp4`

_________________
# NAT/SFE/CTF: limited speed w/ DD # Repeater issues # DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo #
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250
|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
sjgoel
DD-WRT Novice


Joined: 17 Apr 2019
Posts: 4

PostPosted: Wed Apr 17, 2019 14:57    Post subject: Reply with quote
jwh7 wrote:

@sjgoel You should clock the GS to 250 for some throughput improvement. Research the build threads; you may need an older build to get VPN working; mrjcd used VPN on a WRT54 with 33492 and 33986. Also note that newer builds with openVPN 2.4 need a couple settings


I think it is meaningless if GS would only give 5-6 mbps max. The current router is already giving better than this.

Thanks.
Display posts from previous:    Page 1 of 1
Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum