SlickVPN connection

Post new topic   Reply to topic    DD-WRT Forum Index -> Advanced Networking
Author Message
SDMatt
DD-WRT Novice


Joined: 14 Apr 2017
Posts: 15

PostPosted: Thu Jul 16, 2020 2:53    Post subject: SlickVPN connection Reply with quote
Is anyone successfully using SlickVPN with the OpenVPN client built into DD WRT?

I've got a Netgear R7000 on v3.0-r36070M kongac (05/31/18), following the directions here: https://www.slickvpn.com/tutorials/dd-wrt-v-25000/

Any help would be appreciated... Thanks

Here's the part of the log on the connecti
on screen:

Clientlog:
20200715 19:02:36 W WARNING: Using --management on a TCP port WITHOUT passwords is STRONGLY discouraged and considered insecure
20200715 19:02:36 W WARNING: file '/tmp/openvpncl/client.key' is group or others accessible
20200715 19:02:36 W WARNING: file '/tmp/openvpncl/credentials' is group or others accessible
20200715 19:02:36 I OpenVPN 2.4.6 arm-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on May 31 2018
20200715 19:02:36 I library versions: OpenSSL 1.1.0h 27 Mar 2018 LZO 2.09
20200715 19:02:36 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:16
20200715 19:02:36 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
20200715 19:02:36 I TCP/UDP: Preserving recently used remote address: [AF_INET]146.112.61.106:8888
20200715 19:02:36 Socket Buffers: R=[180224->180224] S=[180224->180224]
20200715 19:02:36 I UDPv4 link local: (not bound)
20200715 19:02:36 I UDPv4 link remote: [AF_INET]146.112.61.106:8888
20200715 19:03:36 N TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
20200715 19:03:36 N TLS Error: TLS handshake failed
20200715 19:03:36 I SIGUSR1[soft tls-error] received process restarting
20200715 19:03:36 Restart pause 5 second(s)
20200715 19:03:41 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
20200715 19:03:41 I TCP/UDP: Preserving recently used remote address: [AF_INET]146.112.61.106:8888
20200715 19:03:41 Socket Buffers: R=[180224->180224] S=[180224->180224]
20200715 19:03:41 I UDPv4 link local: (not bound)
20200715 19:03:41 I UDPv4 link remote: [AF_INET]146.112.61.106:8888
20200715 19:03:55 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200715 19:03:55 D MANAGEMENT: CMD 'state'
20200715 19:03:55 MANAGEMENT: Client disconnected
20200715 19:03:55 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200715 19:03:55 D MANAGEMENT: CMD 'state'
20200715 19:03:55 MANAGEMENT: Client disconnected
20200715 19:03:55 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200715 19:03:55 D MANAGEMENT: CMD 'state'
20200715 19:03:55 MANAGEMENT: Client disconnected
20200715 19:03:55 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200715 19:03:55 D MANAGEMENT: CMD 'status 2'
20200715 19:03:55 MANAGEMENT: Client disconnected
20200715 19:03:55 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200715 19:03:55 D MANAGEMENT: CMD 'log 500'
20200715 19:03:55 MANAGEMENT: Client disconnected
20200715 19:04:13 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200715 19:04:13 D MANAGEMENT: CMD 'state'
20200715 19:04:13 MANAGEMENT: Client disconnected
20200715 19:04:13 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200715 19:04:13 D MANAGEMENT: CMD 'state'
20200715 19:04:13 MANAGEMENT: Client disconnected
20200715 19:04:13 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200715 19:04:13 D MANAGEMENT: CMD 'state'
20200715 19:04:13 MANAGEMENT: Client disconnected
20200715 19:04:13 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200715 19:04:13 D MANAGEMENT: CMD 'status 2'
20200715 19:04:13 MANAGEMENT: Client disconnected
20200715 19:04:13 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200715 19:04:13 D MANAGEMENT: CMD 'log 500'
20200715 19:04:13 MANAGEMENT: Client disconnected
20200715 19:04:16 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200715 19:04:16 D MANAGEMENT: CMD 'state'
20200715 19:04:16 MANAGEMENT: Client disconnected
20200715 19:04:16 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200715 19:04:16 D MANAGEMENT: CMD 'state'
20200715 19:04:16 MANAGEMENT: Client disconnected
20200715 19:04:16 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200715 19:04:16 D MANAGEMENT: CMD 'state'
20200715 19:04:16 MANAGEMENT: Client disconnected
20200715 19:04:16 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200715 19:04:16 D MANAGEMENT: CMD 'status 2'
20200715 19:04:16 MANAGEMENT: Client disconnected
20200715 19:04:16 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200715 19:04:16 D MANAGEMENT: CMD 'log 500'
20200715 19:04:16 MANAGEMENT: Client disconnected
20200715 19:04:19 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200715 19:04:19 D MANAGEMENT: CMD 'state'
20200715 19:04:19 MANAGEMENT: Client disconnected
20200715 19:04:19 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200715 19:04:19 D MANAGEMENT: CMD 'state'
20200715 19:04:19 MANAGEMENT: Client disconnected
20200715 19:04:19 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200715 19:04:19 D MANAGEMENT: CMD 'state'
20200715 19:04:19 MANAGEMENT: Client disconnected
20200715 19:04:19 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200715 19:04:19 D MANAGEMENT: CMD 'status 2'
20200715 19:04:19 MANAGEMENT: Client disconnected
20200715 19:04:19 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200715 19:04:19 D MANAGEMENT: CMD 'log 500'
20200715 19:04:19 MANAGEMENT: Client disconnected
20200715 19:04:23 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200715 19:04:23 D MANAGEMENT: CMD 'state'
20200715 19:04:23 MANAGEMENT: Client disconnected
20200715 19:04:23 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200715 19:04:23 D MANAGEMENT: CMD 'state'
20200715 19:04:23 MANAGEMENT: Client disconnected
20200715 19:04:23 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200715 19:04:23 D MANAGEMENT: CMD 'state'
20200715 19:04:23 MANAGEMENT: Client disconnected
20200715 19:04:23 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200715 19:04:23 D MANAGEMENT: CMD 'status 2'
20200715 19:04:23 MANAGEMENT: Client disconnected
20200715 19:04:23 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200715 19:04:23 D MANAGEMENT: CMD 'log 500'
Sponsor
egc
DD-WRT Guru


Joined: 18 Mar 2014
Posts: 12885
Location: Netherlands

PostPosted: Thu Jul 16, 2020 6:20    Post subject: Reply with quote
Their instructions do not look too bad.

the main problem is:
Code:
20200715 19:03:36 N TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)


Which indicates a network error, you cannot reach the server so try another server and or port, preferably use TCP instead of UDP (TCP has fewer connections problems but can be a bit slower)

Always reboot after changing anything.

You are using an old build, SlickVPN actually points to the one and only place where you can find proper updates, but it should work anyway.

Other helpful readings: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324087

_________________
Routers:Netgear R7000, R6400v1, R6400v2, EA6900 (XvortexCFE), E2000, E1200v1, WRT54GS v1.
Install guide R6400v2, R6700v3,XR300:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=316399
Install guide R7800/XR500: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=320614
Forum Guide Lines (important read):https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324087
SDMatt
DD-WRT Novice


Joined: 14 Apr 2017
Posts: 15

PostPosted: Thu Jul 16, 2020 15:06    Post subject: Reply with quote
OK. tried another host using TCP.

Now it looks like the error is related to a connect reset.

I've tried a few of the ports that SlickVPN says should work (8888, 443) - all with no luck.

I might try a firmware update... but I was hoping to avoid that if I could - as I have a number of statically assigned DHCP entries that I'd need to copy and paste back in :-/

Thanks again




Clientlog:
20200716 07:43:17 W WARNING: Using --management on a TCP port WITHOUT passwords is STRONGLY discouraged and considered insecure
20200716 07:43:17 W WARNING: file '/tmp/openvpncl/client.key' is group or others accessible
20200716 07:43:17 W WARNING: file '/tmp/openvpncl/credentials' is group or others accessible
20200716 07:43:17 I OpenVPN 2.4.6 arm-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on May 31 2018
20200716 07:43:17 I library versions: OpenSSL 1.1.0h 27 Mar 2018 LZO 2.09
20200716 07:43:17 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:16
20200716 07:43:17 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
20200716 07:43:17 I TCP/UDP: Preserving recently used remote address: [AF_INET]185.151.12.218:8888
20200716 07:43:17 Socket Buffers: R=[87380->87380] S=[16384->16384]
20200716 07:43:17 I Attempting to establish TCP connection with [AF_INET]185.151.12.218:8888 [nonblock]
20200716 07:43:18 I TCP connection established with [AF_INET]185.151.12.218:8888
20200716 07:43:18 I TCPv4_CLIENT link local: (not bound)
20200716 07:43:18 I TCPv4_CLIENT link remote: [AF_INET]185.151.12.218:8888
20200716 07:43:18 TLS: Initial packet from [AF_INET]185.151.12.218:8888 sid=3b9a4050 5dcc85d0
20200716 07:43:18 W WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
20200716 07:43:18 VERIFY OK: depth=1 C=US ST=CA L=VPN O=VPN OU=VPN CN=VPN name=VPN emailAddress=VPN
20200716 07:43:18 VERIFY KU OK
20200716 07:43:18 Validating certificate extended key usage
20200716 07:43:18 NOTE: --mute triggered...
20200716 07:43:39 3 variation(s) on previous 3 message(s) suppressed by --mute
20200716 07:43:39 N Connection reset restarting [-1]
20200716 07:43:39 I SIGUSR1[soft connection-reset] received process restarting
20200716 07:43:39 Restart pause 5 second(s)
20200716 07:43:44 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
20200716 07:43:44 I TCP/UDP: Preserving recently used remote address: [AF_INET]185.151.12.218:8888
20200716 07:43:44 Socket Buffers: R=[87380->87380] S=[16384->16384]
20200716 07:43:44 I Attempting to establish TCP connection with [AF_INET]185.151.12.218:8888 [nonblock]
20200716 07:43:45 I TCP connection established with [AF_INET]185.151.12.218:8888
20200716 07:43:45 I TCPv4_CLIENT link local: (not bound)
20200716 07:43:45 I TCPv4_CLIENT link remote: [AF_INET]185.151.12.218:8888
20200716 07:43:46 TLS: Initial packet from [AF_INET]185.151.12.218:8888 sid=8269b129 0201e5ba
20200716 07:43:46 VERIFY OK: depth=1 C=US ST=CA L=VPN O=VPN OU=VPN CN=VPN name=VPN emailAddress=VPN
20200716 07:43:46 VERIFY KU OK
20200716 07:43:46 NOTE: --mute triggered...
20200716 07:44:07 4 variation(s) on previous 3 message(s) suppressed by --mute
20200716 07:44:07 N Connection reset restarting [-1]
20200716 07:44:07 I SIGUSR1[soft connection-reset] received process restarting
20200716 07:44:07 Restart pause 5 second(s)
20200716 07:44:12 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
20200716 07:44:12 I TCP/UDP: Preserving recently used remote address: [AF_INET]185.151.12.218:8888
20200716 07:44:12 Socket Buffers: R=[87380->87380] S=[16384->16384]
20200716 07:44:12 I Attempting to establish TCP connection with [AF_INET]185.151.12.218:8888 [nonblock]
20200716 07:44:13 I TCP connection established with [AF_INET]185.151.12.218:8888
20200716 07:44:13 I TCPv4_CLIENT link local: (not bound)
20200716 07:44:13 I TCPv4_CLIENT link remote: [AF_INET]185.151.12.218:8888
20200716 07:44:13 TLS: Initial packet from [AF_INET]185.151.12.218:8888 sid=9fff5759 72c6989e
20200716 07:44:13 VERIFY OK: depth=1 C=US ST=CA L=VPN O=VPN OU=VPN CN=VPN name=VPN emailAddress=VPN
20200716 07:44:13 VERIFY KU OK
20200716 07:44:13 NOTE: --mute triggered...
20200716 07:44:35 4 variation(s) on previous 3 message(s) suppressed by --mute
20200716 07:44:35 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200716 07:44:35 D MANAGEMENT: CMD 'state'
20200716 07:44:35 MANAGEMENT: Client disconnected
20200716 07:44:35 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200716 07:44:35 D MANAGEMENT: CMD 'state'
20200716 07:44:35 MANAGEMENT: Client disconnected
20200716 07:44:35 N Connection reset restarting [-1]
20200716 07:44:35 I SIGUSR1[soft connection-reset] received process restarting
20200716 07:44:35 Restart pause 5 second(s)
20200716 07:44:35 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200716 07:44:35 D MANAGEMENT: CMD 'state'
20200716 07:44:35 MANAGEMENT: Client disconnected
20200716 07:44:35 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200716 07:44:35 D MANAGEMENT: CMD 'status 2'
20200716 07:44:35 MANAGEMENT: Client disconnected
20200716 07:44:35 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200716 07:44:35 D MANAGEMENT: CMD 'log 500'



20200716 07:44:35 4 variation(s) on previous 3 message(s) suppressed by --mute
20200716 07:44:35 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200716 07:44:35 D MANAGEMENT: CMD 'state'
20200716 07:44:35 MANAGEMENT: Client disconnected
20200716 07:44:35 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200716 07:44:35 D MANAGEMENT: CMD 'state'
20200716 07:44:35 MANAGEMENT: Client disconnected
20200716 07:44:35 N Connection reset restarting [-1]
20200716 07:44:35 I SIGUSR1[soft connection-reset] received process restarting
20200716 07:44:35 Restart pause 5 second(s)
20200716 07:44:35 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200716 07:44:35 D MANAGEMENT: CMD 'state'
20200716 07:44:35 MANAGEMENT: Client disconnected
20200716 07:44:35 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200716 07:44:35 D MANAGEMENT: CMD 'status 2'
20200716 07:44:35 MANAGEMENT: Client disconnected
20200716 07:44:35 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200716 07:44:35 D MANAGEMENT: CMD 'log 500'
20200716 07:44:35 MANAGEMENT: Client disconnected
20200716 07:44:40 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
20200716 07:44:40 I TCP/UDP: Preserving recently used remote address: [AF_INET]185.151.12.218:8888
20200716 07:44:40 Socket Buffers: R=[87380->87380] S=[16384->16384]
20200716 07:44:40 I Attempting to establish TCP connection with [AF_INET]185.151.12.218:8888 [nonblock]
20200716 07:44:41 I TCP connection established with [AF_INET]185.151.12.218:8888
20200716 07:44:41 I TCPv4_CLIENT link local: (not bound)
20200716 07:44:41 I TCPv4_CLIENT link remote: [AF_INET]185.151.12.218:8888
20200716 07:44:41 TLS: Initial packet from [AF_INET]185.151.12.218:8888 sid=7200c491 2461cdeb
20200716 07:44:41 VERIFY OK: depth=1 C=US ST=CA L=VPN O=VPN OU=VPN CN=VPN name=VPN emailAddress=VPN
20200716 07:44:41 VERIFY KU OK
20200716 07:44:41 NOTE: --mute triggered...
20200716 07:45:00 4 variation(s) on previous 3 message(s) suppressed by --mute
20200716 07:45:00 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200716 07:45:00 D MANAGEMENT: CMD 'state'
20200716 07:45:00 MANAGEMENT: Client disconnected
20200716 07:45:00 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200716 07:45:00 D MANAGEMENT: CMD 'state'
20200716 07:45:00 MANAGEMENT: Client disconnected
20200716 07:45:00 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200716 07:45:00 D MANAGEMENT: CMD 'state'
20200716 07:45:00 MANAGEMENT: Client disconnected
20200716 07:45:01 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200716 07:45:01 D MANAGEMENT: CMD 'status 2'
20200716 07:45:01 MANAGEMENT: Client disconnected
20200716 07:45:01 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20200716 07:45:01 D MANAGEMENT: CMD 'log 500'
19691231 16:00:00
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 14221
Location: Texas, USA

PostPosted: Thu Jul 16, 2020 15:13    Post subject: Reply with quote
Simple solution: Upgrade without resetting. No need to reset unless you run into issues.
_________________
"Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT
Pogo - A minimal level of ability is expected and needed...
DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)

----------------------
Linux User #377467 counter.li.org / linuxcounter.net
SDMatt
DD-WRT Novice


Joined: 14 Apr 2017
Posts: 15

PostPosted: Thu Jul 16, 2020 15:20    Post subject: Reply with quote
kernel-panic69 wrote:
Simple solution: Upgrade without resetting. No need to reset unless you run into issues.


...not saying that won't work, but that seems to go against everything I've ever read about doing the 30-30-30 before an upgrade :-/
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 14221
Location: Texas, USA

PostPosted: Thu Jul 16, 2020 15:33    Post subject: Reply with quote
You don't 30-30-30 a Broadcom ARM router, you may brick it, bootloop it, or put it in recovery mode.
_________________
"Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT
Pogo - A minimal level of ability is expected and needed...
DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)

----------------------
Linux User #377467 counter.li.org / linuxcounter.net
SDMatt
DD-WRT Novice


Joined: 14 Apr 2017
Posts: 15

PostPosted: Thu Jul 16, 2020 18:52    Post subject: Reply with quote
Am I confusing this with an Atheros based router (30-30-30)?
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 14221
Location: Texas, USA

PostPosted: Thu Jul 16, 2020 21:24    Post subject: Reply with quote
No, you are confusing it with Broadcom MIPSR1 (WRT54* series and similar), MIPSR2 (Linksys E-Series, not EA-Series/ARM). Although, the latter I really do not think it requires it, I think that is just old philosophy carrying over without proper verification. I've reset several MIPSR2 Broadcom routers without doing a 30/30/30 on stock, FreshTomato, and DD-WRT using the reset button. You don't 30/30/30 any other router but those old things. Some routers will wind up bricking good if you do.
_________________
"Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT
Pogo - A minimal level of ability is expected and needed...
DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)

----------------------
Linux User #377467 counter.li.org / linuxcounter.net
SDMatt
DD-WRT Novice


Joined: 14 Apr 2017
Posts: 15

PostPosted: Fri Jul 17, 2020 2:02    Post subject: Reply with quote
Thanks for the info kernel-panic69

Truth be told, most of my dd-wrt experience comes from the old WRT54 series. The firmware "just worked" for me, and was amazing. I even had the PPTP server going on it before it seemed like it got too sketchy to use.

It's only now that I'm trying to do more with these newer routers that things are getting a bit muddled for me.

Hopefully, the OpenVPN client in a newer build will fix my issue here.
SDMatt
DD-WRT Novice


Joined: 14 Apr 2017
Posts: 15

PostPosted: Fri Jul 17, 2020 19:57    Post subject: Reply with quote
OK.. got it working.

The main issue is determining what host to use, as the write up on the slickvpn site is a little vague (at least IMHO)

I ended up installing the SlickVPN Windows client and mirroring its config over into DD-WRT.

I have this running on a test router (Atheros based), and it's basically double nat'ed (a router behind a router) - but I see no reason why this won't work. Unfortunately, I need to coordinate this config change with the rest of the household so I don't interrupt their COVID lockdown induced internet binge.
jbrines
DD-WRT Novice


Joined: 21 Mar 2019
Posts: 39

PostPosted: Tue Sep 29, 2020 23:11    Post subject: Reply with quote
SDMatt wrote:
OK.. got it working.

The main issue is determining what host to use, as the write up on the slickvpn site is a little vague (at least IMHO)

I ended up installing the SlickVPN Windows client and mirroring its config over into DD-WRT.

I have this running on a test router (Atheros based), and it's basically double nat'ed (a router behind a router) - but I see no reason why this won't work. Unfortunately, I need to coordinate this config change with the rest of the household so I don't interrupt their COVID lockdown induced internet binge.


I am doing something similar, what was it you did to resolve it?
Display posts from previous:    Page 1 of 1
Post new topic   Reply to topic    DD-WRT Forum Index -> Advanced Networking 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 cannot attach files in this forum
You cannot download files in this forum