I have been looking at VPN options and am considering IPVanish but they are only offering Ubuntu, Fedora, Kali, Mint, Lubuntu or Pos!OS.
Open VPN is already on my system so what is the issue that keeps openSUSE from being supported?
Should I just press on and try it? I suspect a subscription will be involved.
Grateful for advice please.
Budge
Because they’re an american company if it it doesn’t Fedora or Debian based, they don’t understand anything about it.
That being said, IPVanish just uses normal openvpn configuration files, just like every other VPN provider. It’s not OS dependent.
The following are the instructions for installing IPVanish on Fedora
https://support.ipvanish.com/hc/en-us/articles/360002686834-How-to-Configure-OpenVPN-in-Fedora-
Skimming the page,
It describes setting up a VPN connection using Network Manager.
The instructions should also work on Tumbleweed but with the following modifications…
- Oddly, the instructions don’t describe installing OpenVPN (or any other VPN protocol). I doubt this is automatic on Fedora, and on openSUSE you definitely need to install OpenVPN separately and I’d recommend also any OpenVPN packages which might be useful for your specific Desktop.
- The screenshots look typical of what is seen in a Gnome Desktop. Network Manager looks different in the various Desktops that can be installed in openSUSE which means although Network Manager’s functionality doesn’t change, what you see will likely be different than the screenshots.
- I’d guess that the extracted IPVanish VPN files should work fine because they should only be specific to OpenVPN and not specific to any distro or OS.
Yes, you will need to purchase a subscription to IPVanish, but you can also typically ask for a 24 hr free trial… Most VPN providers will allow you to trial their product using a special account for a short period of time.
If you need help setting up, you can probably get help in this Forum.
Setting up VPNs to any Provider is generally the same no matter who they are.
TSU
Hi to Miuku & Tsu2 and many thanks for the advice. Will proceed as suggested but have just bumped into a past problem:
I had been having problems with Network Manager (NM) on my system so will have to look into this before I spend time on VPN.
In short when I open the NM applet I get two wired connections both shown as Wired connection 1. One is shown as (eno1) and the second (enp0s26f1u2).
My problem is that this “connection” appears to taken as the default so whenever I need to go on line I have to disconnect the strange connection and accept eno1.
I posted on this earlier and meanwhile changed to wicked. The problem appeared at about the time I posted and was not able to sort it. I believe the problem is caused by an USB adaptor on my mouse and I have no idea why it should appear in my NM. If I could just get the default changed so that eno1 is used in preference I could ignore the other.
Any suggestions would be appreciated other than removing the adaptor!
PS, I think I have it now as I have changed the configuration automatic setting.
I will try it now.
Budge.
You can delete the unwanted NM connection via it’s editor any time you like. The connection profiles live in /etc/NetworkManager/system-connections/ directory. They can be edited/deleted directly. For example a connection named DHCP
sudo nano /etc/NetworkManager/system-connections/DHCP
sudo rm -f /etc/NetworkManager/system-connections/DHCP
I’ve been using protonvpn. It’s free, open source and just works. It uses openvpn protocol.
The free tier has servers in 3 countries: US, Japan and somewhere else. The pay plan starts at $4 and, oddly, 4 EUR. The free plan has always been satisfactory for my low level needs. I use it on opensuse, windows and android.
Hi Deano,
I am not at the problem machine at present but the issue is that there should not be two connections named Wired connection 1. Also when rebooted my settings should not be wiped. There is a bug underlying this but thanks for the suggestion. I shall try editing the connections directly. Meanwhile I was under the impression that these were built at boot time and not created by me, just adjusted as required. Will report back.
Many thanks again.
Budge.
Can you show what is listed please?
ls -l /etc/NetworkManager/system-connections/
nmcli c
Yes, AFAIR an “automatically created” connection is generated if none otherwise exist (I guess for casual users), but I generally add and name my connections in my laptop, as I touch multiple network environments as part of my job as a network engineer. I also have VPN connectivity to the large network I manage for remote situations, so used to configuring these.
Hi Deano, will do as you suggest when I am back at workstation tomorrow. Am on laptop at present and do not have any problems. I assume that chronyd is working correctly and syncing without delay as I have just checked time and date setting. I had a warning that my system was configured with RTC in local time zone. I have changed this to UTC and now have:-
timedatectl status
Local time: Sat 2020-10-03 00:05:18 BST
Universal time: Fri 2020-10-02 23:05:18 UTC
RTC time: Fri 2020-10-02 23:05:18
Time zone: Europe/London (BST, +0100)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
I have looked at the system time tracking and looks ok to me but I am out of my depth here.
chronyc tracking
Reference ID : 55C7D666 (85.199.214.102)
Stratum : 2
Ref time (UTC) : Fri Oct 02 22:26:25 2020
System time : 0.000140618 seconds fast of NTP time
Last offset : -0.000132657 seconds
RMS offset : 0.000411288 seconds
Frequency : 5.919 ppm slow
Residual freq : +0.024 ppm
Skew : 1.368 ppm
Root delay : 0.027465684 seconds
Root dispersion : 0.001172717 seconds
Update interval : 64.9 seconds
Leap status : Normal
Will get back to you and many thanks for your help.
Budge.
Hi Budgie2. Best not to mix issues in threads. It can lead to confusing and convoluted discussions.
Please forgive me. Returning to the matter in hand and restarting NM.
First on deleting unwanted NM connections, there is only the one connection shown in /etc/NetworkManager/system-connections/
Here are the results of the commands you asked for:-
alastair@ibmserv2:~> ls -l /etc/NetworkManager/system-connections/
total 4
-rw------- 1 root root 289 Oct 2 15:46 Wired connection 1.nmconnection
alastair@ibmserv2:~> nmcli c
NAME UUID TYPE DEVICE
Wired connection 1 60e3c531-85e6-349f-9c95-e6fb7bdcdcfd ethernet eno1
alastair@ibmserv2:~>
However when I left click on the NM applet icon there are two shown:-
Wired connection 1 (eno1)
Wired connection 1 (enp0s26f1u2)
On booting the system defaults to the enp0s26f1u2 “connection” which of course does not work.
If I left click on NM icon and select Connect for the eno1 connection all is well and I have a connection.
If I right click on the NM icon, select Configure Network Connections and open the System Settings Module only one connection is shown.
Selecting the General configuration tab, the option selection boxes and priority drop down and set these, my selection appears in both Wired connection 1 choices.
To clarify, on left clicking NM icon I can select and connect to either of the two offered “Network connection 1” and then open the systems settings module. Whatever General configuration tab choices I then make are repeated in both Wired connection 1 choices.
Having made such choices, on reboot Wired connection 1 (enp0s26f1u2) is always connection that is started but then fails actually to connect.
Phew. I hope this explains my problem and that it makes sense.
Bottom line is I believe there is a bug underlying all this but if you have a fix it would be very much appreciated.
This thread has been corrupted by me. There is an outstanding bug in NM but it works once I have booted and selected the correct network but I think I should start over with VPN.
You could have NM ignore that interface is desired. Refer…
man NetworkManager.conf
*“KEYFILE SECTION”
However, can you first confirm that two wired interfaces are actually present (or perhaps this is just a “renamed” version of the other?)
/usr/sbin/hwinfo --network
ip a
Hi Deano,
Away from machine now and on laptop . Will run the commands and report back in the morning but FYI again; there is only one network cable connected.
The other device which is shown as a network connection named Wired connection 1 (enp0s26f1u2) is not a lan connection but actually an USB adaptor which I use to convert my old mouse and keyboard which have PS/2 connectors. Why an USB device should appear as if it were a network connection is beyond me.
To help explain further and compare; using an identical machine my networks show on my Debian KDE desktop but in that case the network connections are correctly numbered as Network connection 1 (eno1) and Network connection 2 (enp0s26f1u2) with automatic connection and priority configured correctly and retained as set following booting. I shall send screenshots when I am back at my desk.
Thanks again,
Budge.
Yep, I get that. We’re still in investigation mode. 
The other device which is shown as a network connection named Wired connection 1 (enp0s26f1u2) is not a lan connection but actually an USB adaptor which I use to convert my old mouse and keyboard which have PS/2 connectors. Why an USB device should appear as if it were a network connection is beyond me.
This makes no sense to me (unless the device is a NIC as well). In any case run the commands already given to provide some definitive information to us. Otherwise we can only speculate.
To help explain further and compare; using an identical machine my networks show on my Debian KDE desktop but in that case the network connections are correctly numbered as Network connection 1 (eno1) and Network connection 2 (enp0s26f1u2) with automatic connection and priority configured correctly and retained as set following booting. I shall send screenshots when I am back at my desk.
Ok, good.
Thanks again,
Budge.[/QUOTE]
You have one single connection profile that is suitable for multiple interfaces. Connection profile can be activated only once. If you want this connection profile to apply to specific interface, then you can either set MAC address of this interface in connection profile (via GUI) or add interface-name attribute to connection definition (by using nmcli/nmtui or editing file with connection definition directly).
Normally when you modify auto-generated wired connection profile (and this obviously was auto-generated profile judging by its name) NM automatically adds interface-name attribute which binds this profile to single interface. Show content of connection definition.
You can also simply blacklist interface that you do not want to use (set it to unmanaged).
By default NM attempts to automatically configure any existing wired interface which has link up so no manual configuration is required at all. Any reason you needed to mess with it?
I hope this explains my problem and that it makes sense.
Bottom line is I believe there is a bug underlying all this
The only bug here is posting in completely unrelated subforum.
Hi Deano,
I have checked out the man pages as you suggested and see there is an option, as you indicate for me to have the offending “connection” unmanaged. Might need some guidance with details but at least the right tools are there.
Here is the result of the first command which explains why the usb is getting involved:-
alastair@ibmserv2:~> /usr/sbin/hwinfo --network
103: None 02.0: 10701 Ethernet
[Created at net.126]
Unique ID: QTdc.ndpeucax6V1
Parent ID: NotL.UiIC1YKJsA9
SysFS ID: /class/net/eno2
SysFS Device Link: /devices/pci0000:00/0000:00:01.0/0000:0b:00.1
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "bnx2"
Driver Modules: "bnx2"
Device File: eno2
HW Address: 34:40:b5:93:38:d1
Permanent HW Address: 34:40:b5:93:38:d1
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #61 (Ethernet controller)
104: None 00.0: 10700 Loopback
[Created at net.126]
Unique ID: ZsBS.GQNx7L4uPNA
SysFS ID: /class/net/lo
Hardware Class: network interface
Model: "Loopback network interface"
Device File: lo
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown
105: None 01.0: 10701 Ethernet
[Created at net.126]
Unique ID: zHNY.ndpeucax6V1
Parent ID: wcdH.UiIC1YKJsA9
SysFS ID: /class/net/eno1
SysFS Device Link: /devices/pci0000:00/0000:00:01.0/0000:0b:00.0
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "bnx2"
Driver Modules: "bnx2"
Device File: eno1
HW Address: 34:40:b5:93:38:d0
Permanent HW Address: 34:40:b5:93:38:d0
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #19 (Ethernet controller)
106: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: F165.ndpeucax6V1
Parent ID: rg_L.W3Bp+6TvMh5
SysFS ID: /class/net/enp0s26f1u2
SysFS Device Link: /devices/pci0000:00/0000:00:1a.1/usb4/4-2/4-2:1.0
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "cdc_ether"
Driver Modules: "cdc_ether"
Device File: enp0s26f1u2
HW Address: 36:40:b5:93:38:d5
Permanent HW Address: 36:40:b5:93:38:d5
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #92 (USB Host-to-Host link)
ip a
And here is the result of ip command:-
alastair@ibmserv2:~> ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 34:40:b5:93:38:d0 brd ff:ff:ff:ff:ff:ff
altname enp11s0f0
inet 192.168.169.219/25 brd 192.168.169.255 scope global dynamic noprefixroute eno1
valid_lft 50639sec preferred_lft 50639sec
inet6 fe80::7685:41f1:9f59:ce8a/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: eno2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 34:40:b5:93:38:d1 brd ff:ff:ff:ff:ff:ff
altname enp11s0f1
4: enp0s26f1u2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
link/ether 36:40:b5:93:38:d5 brd ff:ff:ff:ff:ff:ff
alastair@ibmserv2:
Now we can see more detail of why the usb is confusing the system but the way it is working on my system is not as it should be. I think your suggestion of setting
unmanaged-devices
is the way to go.
I apologise once more for encouraging this thread to wander miles from the OP topic and will do whatever is needed to move it if appropriate and many thanks for the excellent advice.
Still OT I do consider there is a bug underlying this given that the settings are not maintained on re-boot and when compared with my Debian/KDE system. Should I try and report bug?
Regards,
Budge.
Have you configured NM to activate the connection automatically for the eno1 Ethernet interface? Show us the NM configuration as defined in /etc/NetworkManager/system-connections/…
BTW, moving this thread to Network/Internet subforum.
I have, many times. Here is a screenshot:-
file:///home/alastair/Screenshot_20201004_104031.png
I hope this screenshot works. It is intended to show the system-connections and the highlighted automatic connection in General configuration tab of my Wired connection 1 which is the one selected and in operation.
My point is that at present, if I select the other Wired connection 1 (enp0s26f1u2) this also shows a highlighted automatic connection. If I remove the highlight then both interface highlights are removed and if I reboot the Wired connection 1 (enp0s26f1u2) is the one which is always used, resulting in no connection and all the other problems I have had with chrony.
I believe your suggested fix is the way to go as this should prevent NetworkManager from using the “wrong” interface.
PS. The screenshot didn’t work on first attempt. How do I include this please?