New answers tagged

4

The CIDR notation for the range of IP addresses 208.73.180.0 - 208.73.183.255 is 208.73.180.0/22. Expressing in binary: 208.73.180.0 -> 11010000.01001001.10110100.00000000 208.73.183.255 -> 11010000.01001001.10110111.11111111 ^^^^^^^^ ^^^^^^^^ ^^^^^^ There are 22 leading bits which will be identical for all addresses in that ...


0

Even though the man page lists nmcli con status as a valid command, The above solution provided by Hugo Heden returns an error "Error: Object 'status' is unknown, try 'nmcli help'" I'm using nmcli 1.2.2 (nmcli -v) and I've tested and modified the following for /etc/NetworkManager/dispatcher.d/vpn-up and it worked like a charm. #! /bin/bash ...


0

Actually from the log is not possible to diagnose what really happen. But the PPTP protocol has difficulties in passing trough firewalls, so it could be the case. In solution of similar problem I found and confirmed that the problem was on local Internet provider. For PPTP VPN protocol you need to have open port 1723. Different VPN protocols have different ...


0

To the question: "How can I associate a script to OpenVPN so that it runs when the VPN is connected successfully?" I want to point out that Lekensteyn provided an excellent answer. But, at the time his answer was composed, it lacked a little clarity on how openvpn command line arguments should be provided to start openvpn on an ubuntu machine, especially so ...


0

On 16.04, you could try building and installing network-manager-l2tp which is a L2TP/IPsec VPN plugin for NetworkManager. See the following page for the package prerequisites and strongSwan AppArmor workaround: https://github.com/nm-l2tp/network-manager-l2tp/issues/12 also as that page mentions upgrade to NetworkManager 1.2.2 or later. Issue the ...


0

I continued search and i had a solution. The problem was that the VPN server was a VM, and the VirtualBox setting was not set to promiscuous mode. I changed settings: Seettings -> network -> advanced settings -> set Promiscuous mode to "Allow All". After i did, everything start working fine. Problem solved.


0

As that is a quite old thread I'm not sure if still of interest. If you still want to use the NetworkManager to connect to a VPN you can add a simple udev rule like that: KERNEL=="vpn0", RUN+="/PATH_TO_THE_SCRIPT/SCRIPT_NAME" This should run any script after the VPN is created.


1

I had exactly the same issue. I searched for a whole day to understand why this happened. In my case, the root cause was caught in syslog in an entry: nm-pptp-service-17364 warn[decaps_gre:pptp_gre.c:347]: short read (-1): Message too long. Apparently the cause was a MTU setting in the WLAN adapter that was too big. By default it is set to automatic. What ...


1

For VirtualBox with windows host and linux(mint) guest, go to the Network UI tab and set for "Adapter" => "Attached to : NAT" and "Adapter type : Paravirtualized network". After that start your VM and you should be able to use VPN network.


0

The config can be more restrictive ufw --force reset ufw default deny incoming # Use the VPN tunnel for all traffic ufw default deny outgoing ufw allow out on tun0 ufw allow in on tun0 ufw allow out $port/$protocol # e.g. 1234/udp, depending on your OpenVPN client config # Prefer resolved hosts to connect to your VPN, enable only if your VPN provider ...


0

Perhaps you upgraded your distro to the beta version. You should re-install and re-setup. About the Windows 10 partition, you can try TestDisk to try to recover the lost partition. There are some other commercial products also. If you can't recover, if you have the serial, you can download Windows 10 directly from Microsoft. (Sometimes your notebook have a ...


0

I searched around and found an answer from a fedora user. After connecting the vpn, with the tunnel running, give the following command in lxterminal: mango@mango:~$ ifconfig ppp0 | grep inet which returns mango@mango:~$ inet addr:10.10.29.2 P-t-P:1.1.1.1 Mask:255.255.255.255 This indicates that the network adapter ppp0 is established and that I need ...


0

version 11.4.0.323 seems to have this issue resolved.


1

Start by downloading this: https://www.privateinternetaccess.com/openvpn/openvpn.zip and extract it somewhere. That archive contains 3 important files: ca.crt, crl.pem and YourServer.ovpn (e.g. Germany.ovpn), copy those to /etc/openvpn/. Rename the .ovpn file to .conf and add a line auth-user-pass secrets Create a new file /etc/openvpn/secrets with your PIA ...


0

You can always check it if it's running by using the following command: pgrep iked if you get a result, it means the process is running if not run the below command: sudo /usr/sbin/iked it starts service


0

I think iptables would do something for you. First, activate packet forwarding: $ echo 1 > /proc/sys/net/ipv4/ip_forward Redirect your traffic from 50.60.70.80:105 to 10.8.0.105:80 $ iptables -t nat -A PREROUTING -d 50.60.70.80 -p tcp --dport 105 -j DNAT --to-destination 10.8.0.105:80 Make the Iptables marquerade the requisition: $ iptables -t ...



Top 50 recent answers are included