Search the Community
Showing results for tags 'dedicated'.
Hello everyone, just got my VPN yesterday with streaming IP. My question is, when using the streaming IP it says to use TCP protocol and Port 443. But when not using the dedicated streaming IP, should I put it back to UDP and AUTO protocol? Or should I just leave it on TCP and 443 port for both streaming IP and regular vpn?
Hi all, I could really use your assistance and input with the setup of my DD-WRT router with a Dedicated IP. I have been struggling with this for a while now and about to throw in the towel. Please forgive my newby-ness... my tech skills from bygone days of app development are quite rusty I'm running an older Netgear with DD-WRT v24-sp2 (03/25/13) as a gateway. I have another router without VPN. I flashed the router myself and, with much assistance from TorGuard Support (you guys are awesome), I finally got the darned thing running a VPN. The only problem is that it was not using my Dedicated IP. After much "internet education", I managed to work through some of the configuration. I now have internet access through it... BUT I have 3 persistent problems: it takes ages for the VPN to get established when the router reboots my real location and IP are visible... not the IP and location of the VPN connection keeps dropping and re-initiating (see log below) I'm likely doing something very wrong, but for the life of me I can't figure out what it is. Below are the screenshot of my OpenVPN Client setup, as well as an extract of my last log (I replaced my dedicated IP with [X.X.X.X]. If anyone could provide me some direction or feedback, I would be really be grateful! State Server: : Local Address: Remote Address: Client: RECONNECTING: connection-reset Local Address: Remote Address: Log 20180602 11:20:21 Socket Buffers: R=[87380->131072] S=[16384->131072] 20180602 11:20:21 I Attempting to establish TCP connection with [AF_INET]126.96.36.199:443 [nonblock] 20180602 11:20:22 I TCP connection established with [AF_INET]188.8.131.52:443 20180602 11:20:22 I TCPv4_CLIENT link local: [undef] 20180602 11:20:22 I TCPv4_CLIENT link remote: [AF_INET]184.108.40.206:443 20180602 11:20:22 TLS: Initial packet from [AF_INET]220.127.116.11:443 sid=78501a3c b15bd1dc 20180602 11:20:23 N Connection reset restarting  20180602 11:20:23 I SIGUSR1[soft connection-reset] received process restarting 20180602 11:20:23 Restart pause 5 second(s) 20180602 11:20:28 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts