[opensuse] How to start a program (wicd) at boot
Hello all, I'm trying to connect at work to a WiFi controlled by a Windows WPA2-Enterprise setup. I've put back the original HD that has a Windows 10 install on it and had no problem connecting. Network manager (13.2) does see the network and let me enter username and password, but no success as to a connection (always comes back asking for the password). I've googles a lot, this sort of problem allready have been encoutered (and solved) on other distributions. Until now I could not solve it on openSUSE. So I decided to remove NM and go back to wicd. One Click Install fails because I don't have Firefox, but I managed to install from rpms. Wicd does work, but it asks for the root password and regularely fails on start. Mor googling told me I should start wicd on boot, but all the instructions are outdated and don't works (chkconfig on 12.3 but does not seem to be there anymore, some hints about systemd and new commands but nothing works either. I'm wondering if I should install 13.1 instead - or look for another distribution... Thierry -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
18.09.2015 19:37, Thierry de Coulon пишет:
Hello all,
I'm trying to connect at work to a WiFi controlled by a Windows WPA2-Enterprise setup.
WPA2 Enterprise is common umbrella for quite different authentication protocols which are using very different authentication parameters. Do you know which one is used?
I've put back the original HD that has a Windows 10 install on it and had no problem connecting. Network manager (13.2) does see the network and let me enter username and password, but no success as to a connection (always comes back asking for the password).
I've googles a lot, this sort of problem allready have been encoutered (and solved) on other distributions. Until now I could not solve it on openSUSE.
So I decided to remove NM and go back to wicd. One Click Install fails because I don't have Firefox, but I managed to install from rpms.
Wicd does work, but it asks for the root password and regularely fails on start. Mor googling told me I should start wicd on boot, but all the instructions are outdated and don't works (chkconfig on 12.3 but does not seem to be there anymore,
Of course it is there. Even in Tumbleweed, not to mention 13.2. But looking at spec file, wicd provides systemd unit definition so "systemctl enable wicd; systemctl start wicd" should probably suffice.
some hints about systemd and new commands but nothing works either.
I'm wondering if I should install 13.1 instead - or look for another distribution...
Whatever works for you ... but if you say what you tried to autostart wicd someone may be able to help. "nothing works" is pretty bad starting point. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Friday 18 September 2015 18.50:58 Andrei Borzenkov wrote:
18.09.2015 19:37, Thierry de Coulon пишет:
Hello all,
I'm trying to connect at work to a WiFi controlled by a Windows WPA2-Enterprise setup.
WPA2 Enterprise is common umbrella for quite different authentication protocols which are using very different authentication parameters. Do you know which one is used?
What I could get from the Windows 10 setup is: <network name> 802.11n WPA2-Enterprise PEAP primary DNS: <name> When NetworkManager tries to connect, it seems it fails getting some "secret" which I understand should be received after some handshaking between my machine and the network (I can't get the exact message now as I am home). (...)
Wicd does work, but it asks for the root password and regularely fails on start. Mor googling told me I should start wicd on boot, but all the instructions are outdated and don't works (chkconfig on 12.3 but does not seem to be there anymore,
Of course it is there. Even in Tumbleweed, not to mention 13.2.
You are right. Actually, I had instructions to "chkconfig network on", which fails with "no such file or directory" and I assumed that was chkconfig, seems it's rather "network" that is no more there. But then the instructions on https://en.opensuse.org/SDB:Wicd are for 11.1 or 12.1 so...
But looking at spec file, wicd provides systemd unit definition so "systemctl enable wicd; systemctl start wicd" should probably suffice.
"Systemctl enable wicd" works "systemctl start wicd" did not, but after a reboot it did. I now no more need to give the root password, wicd starts and I can connect to my wired network. However I could no more connect to my WiFi, wicd kept saying the password is bad (which is not the case)... until I figured that to get wicd really working you must actually totaly disable networking in Yast (wicked had a DHCP setting for wireless that was overriding wicd's settings
Whatever works for you ... but if you say what you tried to autostart wicd someone may be able to help. "nothing works" is pretty bad starting point.
I tried some commands starting with systemctl, but I obviously did not have the right syntax. Now that I have wicd working, I see "PEAP with TKIP/MSCHAPV2" thaht looks promising, I'll give it a try next time I'm at work. Thank you Thierry -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
18.09.2015 22:41, Thierry de Coulon пишет:
On Friday 18 September 2015 18.50:58 Andrei Borzenkov wrote:
18.09.2015 19:37, Thierry de Coulon пишет:
Hello all,
I'm trying to connect at work to a WiFi controlled by a Windows WPA2-Enterprise setup.
WPA2 Enterprise is common umbrella for quite different authentication protocols which are using very different authentication parameters. Do you know which one is used?
What I could get from the Windows 10 setup is:
<network name> 802.11n WPA2-Enterprise PEAP primary DNS: <name>
If you are connecting to Windows this likely means MS-CHAP inner protocol; in this case it should be fully supported by NM; see e.g. screenshot here: https://bbs.archlinux.org/viewtopic.php?id=155893 You likely need to have CA certificate to verify server identity but you will need it with any other implementation as well. ...
Now that I have wicd working, I see "PEAP with TKIP/MSCHAPV2" thaht looks promising, I'll give it a try next time I'm at work.
And NM offers PEAP with MSCHAP as well ... and both of them are using wpa_supplicant anyway, they simply pass configuration information to it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Saturday 19 September 2015 07.17:42 Andrei Borzenkov wrote:
If you are connecting to Windows this likely means MS-CHAP inner protocol; in this case it should be fully supported by NM; see e.g. screenshot here: https://bbs.archlinux.org/viewtopic.php?id=155893
You likely need to have CA certificate to verify server identity but you will need it with any other implementation as well.
That's the problem: I am not supposed to or it's hidden (I can ask). We connect to this WiFi with a user name and a password (the same we use to directly connect through the desktop computers). It works on iOS It works on Andoid It works on Windows All of these without ever knowing anything about a certificate (there is a MacAddress filter to prevent external machines from connecting). I know it _can_ work with Linux because a collegue does (albeit from Debian). He uses wicd, that's why I want to try. NM does see the network but seems unable to get the credentials accepted (I had to use "no certificate required" as "save" is not activated otherwise. I tried with the Gnome3 applet and the Trinity applet, same problem: the "enter your password screen" keeps comming back. I'll give wicd a try on Tuesday (Monday is a holliday here). Thierry -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
19.09.2015 11:46, Thierry de Coulon пишет:
On Saturday 19 September 2015 07.17:42 Andrei Borzenkov wrote:
If you are connecting to Windows this likely means MS-CHAP inner protocol; in this case it should be fully supported by NM; see e.g. screenshot here: https://bbs.archlinux.org/viewtopic.php?id=155893
You likely need to have CA certificate to verify server identity but you will need it with any other implementation as well.
That's the problem: I am not supposed to or it's hidden (I can ask).
It is nor server certificate but CA (Certificate Authority) which signed server certificate. So it depends whether your IT issues them themselves or they request them from official external CA. If you have own CA, you sure should have certificate installed on Windows.
We connect to this WiFi with a user name and a password (the same we use to directly connect through the desktop computers).
It works on iOS It works on Andoid It works on Windows
All of these without ever knowing anything about a certificate (there is a MacAddress filter to prevent external machines from connecting).
I know it _can_ work with Linux because a collegue does (albeit from Debian). He uses wicd, that's why I want to try.
NM does see the network but seems unable to get the credentials accepted (I had to use "no certificate required" as "save" is not activated otherwise.
This sounds like https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/110447...; you can check whether workaround described there works for you. If yes, you should open bug report for openSUSE.
I tried with the Gnome3 applet and the Trinity applet, same problem: the "enter your password screen" keeps comming back.
I'll give wicd a try on Tuesday (Monday is a holliday here).
Thierry
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Saturday 19 September 2015 11.13:09 Andrei Borzenkov wrote:
It is nor server certificate but CA (Certificate Authority) which signed server certificate. So it depends whether your IT issues them themselves or they request them from official external CA.
If you have own CA, you sure should have certificate installed on Windows.
We were never told about one, that's all I know. But I know the IT guy (who actually is a woman.. ) so I will ask
This sounds like https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/11044 76; you can check whether workaround described there works for you. If yes, you should open bug report for openSUSE.
I'll take a look at that too, although I feel a little out of my depth here. I could live with Windows if I need to connect and Linux for work, but I somehow feels I want to find a Linux way. I'll try, ask and report :) Thank you Thierry -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Saturday 19 September 2015 12.37:34 Thierry de Coulon wrote:
If you have own CA, you sure should have certificate installed on Windows. (...) This sounds like https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/110 44 76; you can check whether workaround described there works for you. If yes, you should open bug report for openSUSE.
OK, so after a lot of trial and error I did manage to connect, although: - I had to use PEAP with GTC (which is poposed by wicd). I tried this per chance, as I did not know what it means but PEAP with MSCHAP did not work. I then get asked the two only things I have: name and password. I've tried to repeat this with Network Manager, but it did not work. there is no "PEAP with GTC" and the mask needed to choose PEAP and GTC as an advanced setting answered I did not have the right priviledge to save this setup and it would not connect. Now as I understand NetworkManager requires a client to set it up. TDE's client is probably too "old" (no idea if it has been updated) and Gnome and KDE are not on the machine so either Network Manager can't, or my setup does not let me set it upo correctly. Anyway, openSUSE 13.2 + TDE + wicd + PEAP with GTC works, which is the important thing. Thierry -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
Andrei Borzenkov -
Thierry de Coulon