Zgemma - IPTV VPN Wont Connect

hiranuk

Member
Hi

I have a Zgemma box and an IPTV service. for a few days i have been trying to setup a VPN i have tried 2 differnet VPN providers the latest one is IPvanish. I followed this guide

https://www.tech2guides.co.uk/how-to-setup-vpn-on-enigma2-openatv/

I did exactly what it said but when i got and start the VPN i can see it saying "Running", but after a few seconds the channel stops working. when i do the w-get command to find out the IP there is no IP. when i stop the VPN i see my ISP IP.

Can anyone help. I have tried a london VPN file and US VPN file both have the same results.
 
Hi Mate,

Try a smart DNS service this stops your isp seeing what your viewing as well and is easily set up through your router. So going direct for all your devices, your IP address will stay the same.
 
yes you will have to log on to the box usually 192.168.1.1 and the username and password is on the back of the box username is probably admin. You will see a DNS option you change this to the smart dns service details.
 
virgin hubs are notoriously bad, a cheap router and the virgin one placed in modem mode is always a better option
 
but im not sure this will solve the problem the purpose of this is so that when the the ISP block the IP they are giving me i wont get any tv channels however ipvanish when it works will show a different ip so that isp will block their own ip but i will still have channels as im on a ipvanish ip.
 
virgin hubs are notoriously bad, a cheap router and the virgin one placed in modem mode is always a better option

I have a router, if i put that behined the virgin and virgin in modem only mode will i still need the smart DNS service?
 
you don't 'need' anything, with a decent non-mainstream provider you don't even need a vpn or smart dns, some actually prohibit it

Have you tried looking at the logs for openvpn to see what it's upto when its causing the issue?
 
i get this in the logs. not sure where the problem is

Mon Oct 2 22:56:28 2017 WARNING: file 'login.txt' is group or others accessible
Mon Oct 2 22:56:28 2017 OpenVPN 2.4.3 mipsel-oe-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Jun 27 2017
Mon Oct 2 22:56:28 2017 library versions: OpenSSL 1.0.2j 26 Sep 2016, LZO 2.09
Mon Oct 2 22:56:28 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]104.238.169.58:1198
Mon Oct 2 22:56:28 2017 UDP link local: (not bound)
Mon Oct 2 22:56:28 2017 UDP link remote: [AF_INET]104.238.169.58:1198
Mon Oct 2 22:56:29 2017 [5bc088f4659c42693c6d0f2e325306e9] Peer Connection Initiated with [AF_INET]104.238.169.58:1198
Mon Oct 2 22:56:30 2017 auth-token received, disabling auth-nocache for the authentication token
Mon Oct 2 22:56:30 2017 TUN/TAP device tun0 opened
Mon Oct 2 22:56:30 2017 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Mon Oct 2 22:56:30 2017 /sbin/ip link set dev tun0 up mtu 1500
Mon Oct 2 22:56:30 2017 /sbin/ip addr add dev tun0 local 10.81.10.6 peer 10.81.10.5
Mon Oct 2 22:56:30 2017 Initialization Sequence Completed
Mon Oct 2 22:56:31 2017 event_wait : Interrupted system call (code=4)
Mon Oct 2 22:56:31 2017 /sbin/ip addr del dev tun0 local 10.81.10.6 peer 10.81.10.5
Mon Oct 2 22:56:31 2017 SIGTERM[hard,] received, process exiting
 
you don't 'need' anything, with a decent non-mainstream provider you don't even need a vpn or smart dns, some actually prohibit it

Have you tried looking at the logs for openvpn to see what it's upto when its causing the issue?

Mon Oct 2 22:56:28 2017 WARNING: file 'login.txt' is group or others accessible
Mon Oct 2 22:56:28 2017 OpenVPN 2.4.3 mipsel-oe-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Jun 27 2017
Mon Oct 2 22:56:28 2017 library versions: OpenSSL 1.0.2j 26 Sep 2016, LZO 2.09
Mon Oct 2 22:56:28 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]104.238.169.58:1198
Mon Oct 2 22:56:28 2017 UDP link local: (not bound)
Mon Oct 2 22:56:28 2017 UDP link remote: [AF_INET]104.238.169.58:1198
Mon Oct 2 22:56:29 2017 [5bc088f4659c42693c6d0f2e325306e9] Peer Connection Initiated with [AF_INET]104.238.169.58:1198
Mon Oct 2 22:56:30 2017 auth-token received, disabling auth-nocache for the authentication token
Mon Oct 2 22:56:30 2017 TUN/TAP device tun0 opened
Mon Oct 2 22:56:30 2017 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Mon Oct 2 22:56:30 2017 /sbin/ip link set dev tun0 up mtu 1500
Mon Oct 2 22:56:30 2017 /sbin/ip addr add dev tun0 local 10.81.10.6 peer 10.81.10.5
Mon Oct 2 22:56:30 2017 Initialization Sequence Completed
Mon Oct 2 22:56:31 2017 event_wait : Interrupted system call (code=4)
Mon Oct 2 22:56:31 2017 /sbin/ip addr del dev tun0 local 10.81.10.6 peer 10.81.10.5
Mon Oct 2 22:56:31 2017 SIGTERM[hard,] received, process exiting
 
you don't 'need' anything, with a decent non-mainstream provider you don't even need a vpn or smart dns, some actually prohibit it

Have you tried looking at the logs for openvpn to see what it's upto when its causing the issue?
this is my most recent log

Tue Oct 3 22:52:29 2017 WARNING: file 'login.txt' is group or others accessible
Tue Oct 3 22:52:29 2017 OpenVPN 2.4.3 mipsel-oe-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Jun 27 2017
Tue Oct 3 22:52:29 2017 library versions: OpenSSL 1.0.2j 26 Sep 2016, LZO 2.09
Tue Oct 3 22:52:29 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]209.197.30.84:443
Tue Oct 3 22:52:29 2017 Socket Buffers: R=[163840->163840] S=[163840->163840]
Tue Oct 3 22:52:29 2017 UDP link local: (not bound)
Tue Oct 3 22:52:29 2017 UDP link remote: [AF_INET]209.197.30.84:443
Tue Oct 3 22:52:29 2017 TLS: Initial packet from [AF_INET]209.197.30.84:443, sid=632032a7 d03e5725
Tue Oct 3 22:52:29 2017 VERIFY OK: depth=1, C=US, ST=FL, L=Winter Park, O=IPVanish, OU=IPVanish VPN, CN=IPVanish CA, emailAddress=support@ipvanish.com
Tue Oct 3 22:52:29 2017 VERIFY X509NAME OK: C=US, ST=FL, L=Winter Park, O=IPVanish, OU=IPVanish VPN, CN=nyc-a08.ipvanish.com, emailAddress=support@ipvanish.com
Tue Oct 3 22:52:29 2017 VERIFY OK: depth=0, C=US, ST=FL, L=Winter Park, O=IPVanish, OU=IPVanish VPN, CN=nyc-a08.ipvanish.com, emailAddress=support@ipvanish.com
Tue Oct 3 22:52:30 2017 Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 2048 bit RSA
Tue Oct 3 22:52:30 2017 [nyc-a08.ipvanish.com] Peer Connection Initiated with [AF_INET]209.197.30.84:443
Tue Oct 3 22:52:32 2017 SENT CONTROL [nyc-a08.ipvanish.com]: 'PUSH_REQUEST' (status=1)
Tue Oct 3 22:52:37 2017 SENT CONTROL [nyc-a08.ipvanish.com]: 'PUSH_REQUEST' (status=1)
Tue Oct 3 22:52:42 2017 SENT CONTROL [nyc-a08.ipvanish.com]: 'PUSH_REQUEST' (status=1)
Tue Oct 3 22:52:46 2017 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1 bypass-dhcp,dhcp-option DNS 198.18.0.1,dhcp-option DNS 198.18.0.2,rcvbuf 262144,explicit-exit-notify 5,route-gateway 172.21.20.1,topology subnet,ping 20,ping-restart 40,ifconfig 172.21.20.35 255.255.254.0'
Tue Oct 3 22:52:46 2017 Option 'explicit-exit-notify' in [PUSH-OPTIONS]:5 is ignored by previous <connection> blocks
Tue Oct 3 22:52:46 2017 OPTIONS IMPORT: timers and/or timeouts modified
Tue Oct 3 22:52:46 2017 OPTIONS IMPORT: explicit notify parm(s) modified
Tue Oct 3 22:52:46 2017 OPTIONS IMPORT: --sndbuf/--rcvbuf options modified
Tue Oct 3 22:52:46 2017 Socket Buffers: R=[163840->327680] S=[163840->163840]
Tue Oct 3 22:52:46 2017 OPTIONS IMPORT: --ifconfig/up options modified
Tue Oct 3 22:52:46 2017 OPTIONS IMPORT: route options modified
Tue Oct 3 22:52:46 2017 OPTIONS IMPORT: route-related options modified
Tue Oct 3 22:52:46 2017 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Tue Oct 3 22:52:46 2017 Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
Tue Oct 3 22:52:46 2017 Data Channel Encrypt: Using 256 bit message hash 'SHA256' for HMAC authentication
Tue Oct 3 22:52:46 2017 Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
Tue Oct 3 22:52:46 2017 Data Channel Decrypt: Using 256 bit message hash 'SHA256' for HMAC authentication
Tue Oct 3 22:52:46 2017 ROUTE_GATEWAY 192.168.0.1/255.255.255.0 IFACE=eth0 HWADDR=00:15:c0:37:a9:c4
Tue Oct 3 22:52:46 2017 TUN/TAP device tun0 opened
Tue Oct 3 22:52:46 2017 TUN/TAP TX queue length set to 100
Tue Oct 3 22:52:46 2017 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Tue Oct 3 22:52:46 2017 /sbin/ip link set dev tun0 up mtu 1500
Tue Oct 3 22:52:46 2017 /sbin/ip addr add dev tun0 172.21.20.35/23 broadcast 172.21.21.255
Tue Oct 3 22:52:46 2017 /sbin/ip route add 209.197.30.84/32 via 192.168.0.1
Tue Oct 3 22:52:46 2017 /sbin/ip route add 0.0.0.0/1 via 172.21.20.1
Tue Oct 3 22:52:46 2017 /sbin/ip route add 128.0.0.0/1 via 172.21.20.1
Tue Oct 3 22:52:46 2017 Initialization Sequence Completed
 
there seems to be an issue with either your certificate or conf file, have you attempted to start from scratch?

are you using a plain text editor like notepad?
 
there seems to be an issue with either your certificate or conf file, have you attempted to start from scratch?

are you using a plain text editor like notepad?
What i have done is downloaded a few opvn files and then changed them to Client.conf, and then in the etc folder everytime one of them did not work id delete it and then FTP over another one, tried 4 different opvn files.
my password i enterd on notepad++ and named it login in my windows direction it came up saved as login.txt so i ftp's that the the etc folder

the certificate is the only one that ipvanish supply, i have not edited it so i dont this its that.

when you say i need to start from scratch do you mean i should re flash the Open ATV 6 image to my box?
 
I just know that I had a right ballache getting openvpn to run right the first time I used it

I found starting from scratch helped, could be something silly you’ve done/not done


Sent from my iPhone using Tapatalk
 
I've had problems with getting VPN to work on Virgin media myself...

It was setup correctly on someone's box, working perfectly fine on plusnet, then, when got to virgin, it would stop working... Logged in to vm superhub, changed the firewall ports, and still wouldn't work.

Tried it on the PC, and it worked fine on virgin. But on e2 box, just nothing...

I'm guessing maybe need to get a new router, and put superhub in to modem mode, and let it work like that... Oh well, lol
 
Its already been mentioned, but virgin hubs are a total pain for VPN.
The solution I found that works is to change the nameserver settings on your enigma 2 box.
To do this on a zgemma h2s running woosh follow steps below...

menu
setup
system
network
device setup
nameserver setttings
change nameserver 1 to 8.8.8.8
change nameserver 2 to 8.8.4.4

like i said works for me, the only downside is you need to repeat this after every reboot.
 
Back
Top