Difference between revisions of "Wicd"

From ArchWiki
Jump to: navigation, search
m (→‎Cause #2: improved language)
m (Edited openvpn into openvpn-client, because that's what the service is called now)
 
(74 intermediate revisions by 32 users not shown)
Line 1: Line 1:
 +
[[Category:Network configuration]]
 
[[de:Wicd]]
 
[[de:Wicd]]
 
[[es:Wicd]]
 
[[es:Wicd]]
 
[[fr:Wicd]]
 
[[fr:Wicd]]
 
[[it:Wicd]]
 
[[it:Wicd]]
 +
[[ja:Wicd]]
 
[[tr:Wicd]]
 
[[tr:Wicd]]
−
[[zh-CN:Wicd]]
+
[[zh-hans:Wicd]]
−
[[Category:Networking]]
+
{{Related articles start}}
−
[[Category:Wireless Networking]]
+
{{Related|Network configuration}}
−
{{Article summary start}}
+
{{Related|Wireless network configuration}}
−
{{Article summary text|Covers installation and configuration of Wicd – an open source wired and wireless network manager for Linux which aims to provide a simple interface to connect to networks with a wide variety of settings.}}
+
{{Related|:Category:Network configuration}}
−
{{Article summary heading|Overview}}
+
{{Related articles end}}
−
{{Article summary text|{{Networking overview}}}}
 
−
{{Article summary end}}
 
  
−
[http://www.wicd.net/ Wicd] is a network connection manager that can manage wireless and wired interfaces, similar and an alternative to [[NetworkManager]]. Wicd is written in [[Python]] and [[GTK+]], requiring fewer dependencies than other network managers. Alternatively, a version of Wicd for [[KDE]], written in [[Qt]], is available from the [[Arch User Repository]]. Wicd can also run from the terminal in a curses interface, requiring no X server session or task panel (see [[#Running Wicd]]).
+
[https://launchpad.net/wicd Wicd] is a network connection manager that can manage wireless and wired interfaces, similar and an alternative to [[NetworkManager]]. Wicd is written in [[Python]] and [[GTK+]]. Alternatively, a version of Wicd for [[KDE]], written in [[Qt]], is available from the [[Arch User Repository]]. Wicd can also run from the terminal in a curses interface, requiring no X server session or task panel (see [[#Running Wicd in Text Mode]]).
  
−
==Installation==
+
== Installation ==
  
 
=== Base package ===
 
=== Base package ===
−
[[pacman|Install]] {{Pkg|wicd}}, available in the [[Official Repositories]]. It includes everything needed to run the wicd daemon and the {{ic|wicd-cli}} and {{ic|wicd-curses}} interfaces.
 
  
−
=== GTK client ===
+
[[Install]] the {{Pkg|wicd}} package. It includes everything needed to run the wicd daemon and the {{ic|wicd-cli}} and {{ic|wicd-curses}} interfaces.
−
For a GTK front-end, install {{Pkg|wicd-gtk}}, available in the [[Official Repositories|official repositories]]. It includes everything needed to run the GTK interface of wicd and the autostart file for the client to appear in the system tray.
+
 
 +
=== GTK+ client ===
 +
 
 +
For a GTK+ front-end, install {{Pkg|wicd-gtk}}, available in the official repositories. It includes everything needed to run the GTK interface of wicd and the autostart file for the client to appear in the system tray.
  
 
=== KDE client ===
 
=== KDE client ===
−
For a KDE front-end, install {{AUR|wicd-kde}}, available in the [[Arch User Repository]].   
+
 
 +
For a KDE front-end, install {{AUR|wicd-kde}}{{Broken package link|{{aur-mirror|wicd-kde}}}}, available in the [[AUR]].   
  
 
=== Notifications ===
 
=== Notifications ===
−
To enable visual notifications about network status, you need to install the {{Pkg|notification-daemon}}.
 
  
−
If you are not using [[GNOME]], you will want to install {{Pkg|xfce4-notifyd}} instead of the notification-daemon, because it pulls a lot of unnecessary GNOME packages.
+
To enable visual notifications about network status, you need to install the packages {{Pkg|notification-daemon}} and {{Pkg|python2-notify}}.
 +
 
 +
If you are not using [[GNOME]], you may want to install {{Pkg|xfce4-notifyd}} instead of the notification-daemon, because it pulls a lot of unnecessary GNOME packages.
  
 
=== Alternative ===
 
=== Alternative ===
−
The {{AUR|wicd-bzr}} buildscript is available in the [[AUR]], which should build the latest development branch.
+
 
 +
The {{AUR|wicd-bzr}}{{Broken package link|package not found}} buildscript is available in the [[AUR]], which should build the latest development branch.
 
If you need an alternative version or you just want to roll your own package, you can easily build it using [[ABS]].
 
If you need an alternative version or you just want to roll your own package, you can easily build it using [[ABS]].
  
−
==Getting Started==
+
== Getting started ==
 +
 
 +
=== Initial setup ===
  
−
===Initial Setup===
 
 
Wicd provides a daemon that must be started.  
 
Wicd provides a daemon that must be started.  
  
 
{{Warning | Running multiple network managers ''will'' cause problems, so it is important to ''disable all other network management daemons''.}}
 
{{Warning | Running multiple network managers ''will'' cause problems, so it is important to ''disable all other network management daemons''.}}
  
−
First, stop all previously running network daemons:
+
First, stop all previously running network daemons (like netctl, netcfg, dhcpcd, NetworkManager).
  
−
# systemctl stop netcfg
+
Disable any existing network management services, including {{ic|netctl}}, {{ic|netcfg}}, {{ic|dhcpcd}}, and {{ic|networkmanager}}. Refer to [[Systemd#Using units]].
−
# systemctl stop dhcpcd
 
−
# systemctl stop NetworkManager
 
  
−
Disable any existing network management services, including {{ic|netcfg}}, {{ic|dhcpcd}}, and {{ic|networkmanager}}. Refer to [[Systemd#Using_units]].
+
{{Note|You might need to stop and disable the '''network''' daemon instead of '''netctl''', which is a current replacement for '''network''' service. If unsure, try disabling both.}}
  
−
{{Note | You might need to stop and disable the '''network''' daemon instead of '''netcfg''', which is a current replacement for '''network''' service. If unsure, try disabling both.}}
+
[[Start/enable]] the {{ic|wicd.service}} systemd unit.
  
−
Start the wicd service:
+
Add your account to '''users''' group:
−
# systemctl start wicd
 
  
−
Enable the service at system start up:
+
  # gpasswd -a USERNAME users
−
  # systemctl enable wicd.service
 
  
−
Add your account to '''network''' group:
+
{{Note|The Unix group that D-Bus allows to access ''wicd'' is subject to change, and it may be different than ''users''. Check which policy group is specified in {{ic|/etc/dbus-1/system.d/wicd.conf}}, and add your user to that group.}}
  
−
# gpasswd -a USERNAME network
+
If you added your user to a new group, log out and then log in.
  
−
{{Note | The Unix group that dbus allows to access '''wicd''' is subject to change, and may be different than ''network''.  Check which policy group is specified in {{ic|/etc/dbus-1/system.d/wicd.conf}}, and add your user to that group.}}
+
=== Running Wicd in Desktop Environment===
  
−
If you added your user to a new group, log out and then log in.
+
If you have installed the {{pkg|wicd-gtk}} and entered the desktop environment. Open a virtual terminal to run one of the following commands.
  
−
===Running Wicd===
+
* To start Wicd as system service, [[start]] the {{ic|wicd.service}} systemd unit.
  
−
To load Wicd, run:
+
* To load Wicd, run:
  
 
  $ wicd-client
 
  $ wicd-client
  
−
To force it to start minimized in the notification area, run:
+
* To force it to start minimized in the notification area, run:
  
 
  $ wicd-client --tray
 
  $ wicd-client --tray
  
−
If your desktop environment does not have a notification area, run:
+
* If your desktop environment does not have a notification area, or if you don't want wicd to show tray icon, run:
  
 
  $ wicd-client -n
 
  $ wicd-client -n
  
−
The above commands will only work if you have installed the {{pkg|wicd-gtk}}. If you did not install {{pkg|wicd-gtk}} then use wicd-cli or wicd-curses:
+
=== Running Wicd in Text Mode===
 +
 
 +
If you did not install {{pkg|wicd-gtk}} then use wicd-cli or wicd-curses:
  
 
  $ wicd-curses
 
  $ wicd-curses
Line 86: Line 90:
 
{{Note | Wicd does not prompt you for a passkey. To use encrypted connections (WPA/WEP), expand the network you want to connect to, click '''Advanced''' and enter the needed info.}}
 
{{Note | Wicd does not prompt you for a passkey. To use encrypted connections (WPA/WEP), expand the network you want to connect to, click '''Advanced''' and enter the needed info.}}
  
−
==== Autostart ====
+
{{Note|''wicd-curses'' is less stable than ''wicd-gtk'', and is known to crash regularly. If a crash occurs when attempting to configure a wireless network, try {{AUR|wicd-patched}}}}
−
The {{pkg|wicd-gtk}} package puts a file in {{ic|/etc/xdg/autostart/wicd-tray.desktop}}, which will autostart {{ic|wicd-client}} upon login to your DE/WM. If so, enabling the service with {{ic|systemctl}} is sufficient.  
+
 
 +
=== Switching WPA supplicant driver ===
 +
 
 +
''Wicd'' still suggests to "almost always" use Wext as WPA supplicant driver and defaults to it. This is [http://linuxwireless.org/en/developers/Documentation/Wireless-Extensions/index.html#Do_we_still_use_WE_.3F outdated behavior]. One should use nl80211 instead, except with old drivers that do not support it. The relevant option is located in ''Preferences > Advanced Settings''.
 +
 
 +
=== Autostart ===
 +
 
 +
The {{Pkg|wicd-gtk}} package puts a file in {{ic|/etc/xdg/autostart/wicd-tray.desktop}}, which will autostart {{ic|wicd-client}} upon login to your DE/WM. If so, [[enable]] the {{ic|wicd}} systemd unit.
  
 
If {{ic|/etc/xdg/autostart/wicd-tray.desktop}} does not exist, you can add '''wicd-client''' to your DE/WM startup to have the application start when you log in.
 
If {{ic|/etc/xdg/autostart/wicd-tray.desktop}} does not exist, you can add '''wicd-client''' to your DE/WM startup to have the application start when you log in.
Line 93: Line 104:
 
{{Note|If '''wicd-client''' is added to DE/WM startup when {{ic|/etc/xdg/autostart/wicd-tray.desktop}} exists, you will have an issue of two {{ic|wicd-client}} instances running.}}
 
{{Note|If '''wicd-client''' is added to DE/WM startup when {{ic|/etc/xdg/autostart/wicd-tray.desktop}} exists, you will have an issue of two {{ic|wicd-client}} instances running.}}
  
−
===Scripts===
+
=== Scripts ===
 +
 
 
Wicd has the ability to run scripts during all stages of the connection process (post/pre connect/disconnect).
 
Wicd has the ability to run scripts during all stages of the connection process (post/pre connect/disconnect).
−
Simply place a script inside the relevant stage folder within /etc/wicd/scripts/ and make it executable.
+
Simply place a script inside the relevant stage folder within {{ic|/etc/wicd/scripts/}} and make it executable.
  
 
The scripts are able to receive three parameters, these being:  
 
The scripts are able to receive three parameters, these being:  
Line 102: Line 114:
 
  $3 - the BSSID (gateway MAC).
 
  $3 - the BSSID (gateway MAC).
  
−
====Stop ARP spoofing attacks====
+
==== Stop ARP spoofing attacks ====
  
 
The script below can be used to set a static ARP, to stop ARP spoofing attacks.
 
The script below can be used to set a static ARP, to stop ARP spoofing attacks.
−
Simply change the values within the case statement to match those of the networks you want to set static ARP entries for.
+
Simply change the values within the case statement to match those of the networks you want to set static ARP entries for. Launch it as root:
  
 
  #!/bin/bash
 
  #!/bin/bash
Line 115: Line 127:
 
  if [ "${connection_type}" == "wireless" ]; then
 
  if [ "${connection_type}" == "wireless" ]; then
 
   
 
   
−
        #Change below to match your networks.
+
        #Change below to match your networks.
−
        case "$essid" in
+
        case "$essid" in
−
                YOUR-NETWORK-NAME-ESSID)
+
        YOUR-NETWORK-NAME-ESSID)
−
                        sudo arp -s 192.168.0.1 00:11:22:33:44:55
+
                arp -s 192.168.0.1 00:11:22:33:44:55
−
                        ;;
+
          ;;
−
                Netgear01923)
+
          Netgear01923)
−
                        sudo arp -s 192.168.0.1 10:11:20:33:40:50
+
                arp -s 192.168.0.1 10:11:20:33:40:50
−
                        ;;
+
          ;;
−
                ANOTHER-ESSID)
+
          ANOTHER-ESSID)
−
                        sudo arp -s 192.168.0.1 11:33:55:77:99:00
+
                arp -s 192.168.0.1 11:33:55:77:99:00
−
                        ;;
+
          ;;
−
                *)
+
          *)
−
                        echo "Static ARP not set. No network defined."
+
                echo "Static ARP not set. No network defined."
−
                        ;;
+
          ;;
 
         esac
 
         esac
 
  fi
 
  fi
  
−
====Change MAC using macchanger====
+
==== Change MAC using macchanger ====
 +
 
 +
See [[MAC address spoofing#systemd + macchanger + dhcpcd (no NetworkManager)]]{{Broken section link}}.
  
 
The script below can be used to change the MAC address of your network interfaces.
 
The script below can be used to change the MAC address of your network interfaces.
  
−
To change the MAC whenever you connect to a network, place this script under {{ic|/etc/wicd/scripts/preconnect/}}
+
To change the MAC whenever you connect to a network, place this script under {{ic|/etc/wicd/scripts/preconnect/}}.
  
 
Take a look at {{ic|macchanger --help}} to adjust the macchanger command to your liking.
 
Take a look at {{ic|macchanger --help}} to adjust the macchanger command to your liking.
Line 146: Line 160:
  
 
if [[ "${connection_type}" == "wireless" ]]; then
 
if [[ "${connection_type}" == "wireless" ]]; then
−
    ip link set wlan0 down
+
        ip link set wlp2s0 down
−
    macchanger -A wlan0
+
        macchanger -A wlp2s0
−
    ip link set wlan0 up
+
        ip link set wlp2s0 up
 
elif [[ "${connection_type}" == "wired" ]]; then
 
elif [[ "${connection_type}" == "wired" ]]; then
−
    ip link set eth0 down
+
        ip link set enp1s0 down
−
    macchanger -A eth0
+
        macchanger -A enp1s0
−
    ip link set eth0 up
+
        ip link set enp1s0 up
 +
fi
 +
</nowiki>}}
 +
 
 +
==== Start/stop openvpn client ====
 +
 
 +
Put the following script in {{ic|/etc/wicd/scripts/postconnect/}}, to be able to restart openvpn client when wireless connected to specific ESSID, and replace the {{ic|YOUR_WIFI_ESSID}} with your ESSID.
 +
 
 +
{{bc|<nowiki>
 +
#!/bin/sh
 +
 
 +
ESSID="YOUR_WIFI_ESSID"
 +
 
 +
if [ $1 == "wireless" ]; then
 +
if [ $2 == "$ESSID" ]; then
 +
systemctl restart openvpn-client@client
 +
fi
 
fi
 
fi
 
</nowiki>}}
 
</nowiki>}}
  
−
==Troubleshooting==
+
Put the following script in {{ic|/etc/wicd/scripts/predisconnect/}}, to stop openvpn client when wireless disconnected from specific ESSID and replace the {{ic|YOUR_WIFI_ESSID}} with your ESSID.
  
−
=== Failed to get IP address ===
+
{{bc|<nowiki>
−
If wicd repeatedly fails to get an IP address using the default dhcpcd client, try installing and using '''dhclient''' instead:
+
#!/bin/sh
−
# pacman -S dhclient
 
−
Do not forget to select dhclient as the primary dhcp client in wicd options afterwards!
 
  
−
If wicd can get an IP address for a wired interface and is unable to get an IP address for a wireless interface, try disabling the wireless card's powersaving features:
+
ESSID="YOUR_WIFI_ESSID"
−
# iwconfig wlan0 power off
 
  
−
=== Random disconnecting ===
+
if [ $1 == "wireless" ]; then
 +
if [ $2 == "$ESSID" ]; then
 +
systemctl stop openvpn-client@client
 +
fi
 +
fi
 +
</nowiki>}}
  
−
====Cause #1====
+
== Troubleshooting ==
−
If dmesg says {{ic|1=wlan0: deauthenticating from MAC by local choice (reason=3)}} and you lose your Wi-Fi connection, it is likely that you have a bit too aggressive power-saving on your Wi-Fi card[http://us.generation-nt.com/answer/gentoo-user-wireless-deauthenticating-by-local-choice-help-204640041.html]. Try disabling the wireless card's power-saving features:
 
−
# iwconfig wlan0 power off
 
  
−
If you have the package {{pkg|pm-utils}} installed, it may be the reason power-saving is on in your system[http://uselessuseofcat.com/?p=67]. You can put {{bc|#!/bin/sh
+
See [[Network configuration#Troubleshooting]] for troubleshooting wired connections and [[Wireless network configuration#Troubleshooting]] for troubleshooting wireless connections. This section covers only problems specific to ''wicd''.
−
/sbin/iwconfig wlan0 power off}} into the file {{ic|/etc/pm/power.d/wireless}} (create it if it does not exist and make it executable) and see if things get better.
 
  
−
If your card does not support {{ic|iwconfig wlan0 power off}}, check the '''BIOS''' for power management options. Disabling PCI-Express power management in the BIOS of a Lenovo W520 resolved this issue.
+
=== Autoconnect on resume from hibernation/suspension ===
  
−
====Cause #2====
+
If for some reasons autoconnect on resume from hibernation or suspension does not work automatically, you can manually restart Wicd by enabling the following service file for your user; see [[systemd/User#Basic setup]].
−
If you are experiencing frequent disconnections with wireless and dmesg shows messages such as
 
  
−
{{ic|1=ieee80211 phy0: wlan0: No probe response from AP xx:xx:xx:xx:xx:xx after 500ms, disconnecting}}
+
{{hc|~/.config/systemd/user/wicd@resume.service|<nowiki>
 +
[Unit]
 +
Description=Restart Wicd autoconnect service on resume
 +
After=suspend.target
  
−
try changing the channel bandwidth to {{ic|20MHz}} through your router's settings page.
+
[Service]
 +
Type=oneshot
 +
User=%i
 +
RemainAfterExit=no
 +
ExecStart=/usr/share/wicd/daemon/autoconnect.py
 +
 
 +
[Install]
 +
WantedBy=suspend.target
 +
</nowiki>}}
  
 
=== Importing pynotify failed, notifications disabled ===
 
=== Importing pynotify failed, notifications disabled ===
−
In case the {{pkg|python2-notify}} package did not get installed automatically. You can [[pacman|install]] it from [[Official Repositories]].
 
  
−
=== Dbus connection error message ===
+
In case the {{pkg|python2-notify}} package did not get installed automatically. You can [[install]] it from [[official repositories]].
  
−
Otherwise you will get dbus error messages and not be able to connect to networks.
+
=== D-Bus connection error message ===
  
−
* '''NOTE:''' If wicd suddenly stopped working and it complains about dbus, it is quite likely that you just need to remove wicd fully, including and all its configuration files, and re-install it from scratch:
+
If wicd suddenly stopped working and it complains about D-Bus, it is quite likely that you just need to remove wicd fully, including and all its configuration files, and re-install it from scratch by first removing {{pkg|wicd}}. Then remove its configuration files:
−
  pacman -R wicd
+
  # rm -rf /etc/wicd /var/log/wicd /etc/dbus-1/system.d/wicd*
−
rm -Rf /etc/wicd /var/log/wicd /etc/dbus-1/system.d/wicd*
+
Then reinstall the package.
−
pacman -S wicd
+
Check this link for more details: https://bbs.archlinux.org/viewtopic.php?pid=577141#p577141  
−
Check this link for more details: https://bbs.archlinux.org/viewtopic.php?pid=577141#p577141
 
  
−
Wicd-client also throws a dbus connection error message ("Could not connect to wicd's D-Bus interface.") when wicd is not running due to a problem with a config file. It seems that sometimes an empty account gets added to /etc/wicd/wired-settings.conf in which case you simply have to remove the
+
Wicd-client also throws a D-Bus connection error message ("Could not connect to wicd's D-Bus interface.") when wicd is not running due to a problem with a config file. It seems that sometimes an empty account gets added to {{ic|/etc/wicd/wired-settings.conf}} in which case you simply have to remove the
 
  []  
 
  []  
 
and restart wicd.
 
and restart wicd.
  
−
When running wicd daemon with `rc.d` it won't print error that `pid` file is created. If you are sure wicd isn't running remove this file:
+
If the above does not work, you could try https://bbs.archlinux.org/viewtopic.php?pid=1268721
−
  rm /var/run/wicd/wicd.pid
+
 
 +
=== Problems after package update ===
 +
 
 +
Sometimes the wicd client fails to load after a package update due to D-Bus errors. A solution is to [[stop]] {{ic|wicd.service}}, remove the configuration files in the {{ic|/etc/wicd/}} directory, and [[start]] {{ic|wicd.service}}.
  
−
===Problems after package update===
+
=== Note about graphical sudo programs ===
−
Sometimes the wicd client fails to load after a package update due to D-Bus errors.
 
  
−
A solution is to remove the config files in the {{ic|/etc/wicd/}} directory.
+
If you are receiving an error about wicd failing to find a graphical sudo program, install one of {{Pkg|gksu}}, {{AUR|ktsuss}}, or {{Pkg|kdebase-runtime}}, then use the relative command:
−
# systemctl stop wicd
 
−
# rm /etc/wicd/*.conf
 
−
# systemctl start wicd
 
  
−
===Note about graphical sudo programs===
 
−
If you are receiving an error about wicd failing to find a graphical sudo program, run one of the following commands:
 
 
  $ ktsuss wicd-client -n
 
  $ ktsuss wicd-client -n
  
Line 220: Line 254:
 
  $ kdesu wicd-client -n
 
  $ kdesu wicd-client -n
  
−
These programs require the ktsuss (found in the AUR), gksu, and kdesu packages, respectively.
+
=== Eduroam ===
−
 
 
−
===Making eduroam work with wicd===
 
−
 
 
−
{{Note|You may try the AUR package {{AUR|wicd-eduroam}} first. It will appear in wicd as "eduroam". If it does not work for you, try the following.}}
 
  
−
This profile will only work for eduroam institutions which use TTLS and will not work for PEAP.
+
See [[WPA2 Enterprise#Wicd]]{{Broken section link}}.
  
−
Save the following as {{ic|/etc/wicd/encryption/templates/ttls-80211}}
+
=== Two instances of wicd-client (and possibly two icons in tray) ===
−
{{hc|/etc/wicd/encryption/templates/ttls-80211|<nowiki>
 
−
name = TTLS for Wireless
 
−
author = Alexander Clouter
 
−
version = 1
 
−
require anon_identity *Anonymous_Username identity *Identity password *Password
 
−
optional ca_cert *Path_to_CA_Cert cert_subject *Certificate_Subject
 
−
-----
 
−
ctrl_interface=/var/run/wpa_supplicant
 
−
network={
 
−
      ssid="$_ESSID"
 
−
      scan_ssid=$_SCAN
 
  
−
      key_mgmt=WPA-EAP
+
See the note in [[#Running Wicd]]{{Broken section link}} about the autostart file in {{ic|/etc/xdg/autostart}} and the forum post and bug report provided in [[#External Links]]{{Broken section link}}. Essentially, if {{ic|/etc/xdg/autostart/wicd-tray.desktop}} exists, remove it.  You only need the {{ic|wicd}} service enabled in systemd.
−
      eap=TTLS
 
  
−
      ca_cert="$_CA_CERT"
+
=== Bad password using PEAP with TKIP/MS-CHAPv2 ===
−
      subject_match="$_CERT_SUBJECT"
 
−
 
−
      phase2="auth=MSCHAPv2 auth=PAP"
 
  
−
      anonymous_identity="$_ANON_IDENTITY"
+
The connection template PEAP with TKIP/MS-CHAPv2 requires the user to enter the path to a CA certificate besides entering username and password. However this can cause troubles resulting in an error message of a bad password [https://bbs.archlinux.org/viewtopic.php?pid=990385]. A possible solution is the usage of PEAP with GTC instead of TKIP/MS-CHAPv2 which does not require one to enter the path of the CA cert.
−
      identity="$_IDENTITY"
 
−
      password="$_PASSWORD"
 
−
}
 
−
</nowiki>}}
 
  
−
Open a terminal
+
=== Wicd skips obtaining IP address on wlp ===
  
−
cd /etc/wicd/encryption/templates
+
This can be caused by dhcpcd running alongside wicd as systemd service. A solution would be to stop/disable '''dhcpcd'''.
−
echo ttls-80211 >> active
 
  
−
Open wicd, choose TTLS for Wireless in the properties of eduroam, and enter the appropriate settings for your institution. The format of the subject match should be something like "/CN=server.example.com".
+
=== dhcpcd not running ===
  
−
NB. This only works in my institution by commenting {{ic|subject_match}}, which is not secure, but at least it connects.
+
Normally it should not be required, nor recommended to run the dhcpcd service next to wicd. However, if you encounter the error message that dhcpcd is not running, then you can try [[start]]ing the {{ic|dhcpcd}} systemd unit and see if you encounter any incompatibilities when using both services at the same time.
  
−
===Two instances of wicd-client (and possibly two icons in tray)===
+
Alternatively, as a workaround you might consider switching to {{Pkg|dhclient}} in the Wicd settings.
−
See the note in [[Wicd#Running_Wicd]] about the autostart file in {{ic|/etc/xdg/autostart}} and the forum post and bug report provided in [[Wicd#External_Links]]. Essentially, if {{ic|/etc/xdg/autostart/wicd-tray.desktop}} exists, you only need the {{ic|wicd}} service enabled in systemd and should remove it from your DE/WM autostart file.
 
  
−
===Bad password using PEAP with TKIP/MSCHAPV2===
+
{{Note|If you get ''send_packet: Network is unreachable'' errors, then try increasing the timeout in /usr/share/dhclient/dhclient.conf.}}
−
The connection template PEAP with TKIP/MSCHAPV2 requires the user to enter the path to a CA certificate besides entering username and password. However this can cause troubles resulting in a error message of a bad password [https://bbs.archlinux.org/viewtopic.php?pid=990385 *]. A possible solution is the usage of PEAP with GTC instead of TKIP/MSCHAPV2 which does not require to enter the path of the CA cert.
 
  
−
===Wicd skips obtaining IP address on WLAN===
+
== See also ==
−
This can be caused by dhcpcd running alongside wicd as systemd service. A solution would be to stop/disable dhcpcd.
 
−
# systemctl stop dhcpcd
 
−
# systemctl disable dhcpcd
 
  
−
==External links==
+
* [https://bbs.archlinux.org/viewtopic.php?id=114803 Forum post] about two instances of wicd-client and {{ic|/etc/xdg/autostart}}
−
*[http://www.wicd.net/download.php Note on interfaces at the official site]
+
* [https://bugs.archlinux.org/task/22423 Bug report mentioning /etc/xdg/autostart and wicd-client behavior]
−
*[https://bbs.archlinux.org/viewtopic.php?id=114803 Forum post about two instances of wicd-client and /etc/xdg/autostart]
 
−
*[https://bugs.archlinux.org/task/22423 Bug report mentioning /etc/xdg/autostart and wicd-client behavior]
 

Latest revision as of 23:13, 12 October 2017

Related articles

Wicd is a network connection manager that can manage wireless and wired interfaces, similar and an alternative to NetworkManager. Wicd is written in Python and GTK+. Alternatively, a version of Wicd for KDE, written in Qt, is available from the Arch User Repository. Wicd can also run from the terminal in a curses interface, requiring no X server session or task panel (see #Running Wicd in Text Mode).

Installation

Base package

Install the wicd package. It includes everything needed to run the wicd daemon and the wicd-cli and wicd-curses interfaces.

GTK+ client

For a GTK+ front-end, install wicd-gtk, available in the official repositories. It includes everything needed to run the GTK interface of wicd and the autostart file for the client to appear in the system tray.

KDE client

For a KDE front-end, install wicd-kdeAUR[broken link: archived in aur-mirror], available in the AUR.

Notifications

To enable visual notifications about network status, you need to install the packages notification-daemon and python2-notify.

If you are not using GNOME, you may want to install xfce4-notifyd instead of the notification-daemon, because it pulls a lot of unnecessary GNOME packages.

Alternative

The wicd-bzrAUR[broken link: package not found] buildscript is available in the AUR, which should build the latest development branch. If you need an alternative version or you just want to roll your own package, you can easily build it using ABS.

Getting started

Initial setup

Wicd provides a daemon that must be started.

Warning: Running multiple network managers will cause problems, so it is important to disable all other network management daemons.

First, stop all previously running network daemons (like netctl, netcfg, dhcpcd, NetworkManager).

Disable any existing network management services, including netctl, netcfg, dhcpcd, and networkmanager. Refer to Systemd#Using units.

Note: You might need to stop and disable the network daemon instead of netctl, which is a current replacement for network service. If unsure, try disabling both.

Start/enable the wicd.service systemd unit.

Add your account to users group: 

# gpasswd -a USERNAME users
Note: The Unix group that D-Bus allows to access wicd is subject to change, and it may be different than users. Check which policy group is specified in /etc/dbus-1/system.d/wicd.conf, and add your user to that group.

If you added your user to a new group, log out and then log in.

Running Wicd in Desktop Environment

If you have installed the wicd-gtk and entered the desktop environment. Open a virtual terminal to run one of the following commands.

  • To start Wicd as system service, start the wicd.service systemd unit.
  • To load Wicd, run:
$ wicd-client
  • To force it to start minimized in the notification area, run:
$ wicd-client --tray
  • If your desktop environment does not have a notification area, or if you don't want wicd to show tray icon, run:
$ wicd-client -n

Running Wicd in Text Mode

If you did not install wicd-gtk then use wicd-cli or wicd-curses: 

$ wicd-curses
Note: Wicd does not prompt you for a passkey. To use encrypted connections (WPA/WEP), expand the network you want to connect to, click Advanced and enter the needed info.
Note: wicd-curses is less stable than wicd-gtk, and is known to crash regularly. If a crash occurs when attempting to configure a wireless network, try wicd-patchedAUR

Switching WPA supplicant driver

Wicd still suggests to "almost always" use Wext as WPA supplicant driver and defaults to it. This is outdated behavior. One should use nl80211 instead, except with old drivers that do not support it. The relevant option is located in Preferences > Advanced Settings.

Autostart

The wicd-gtk package puts a file in /etc/xdg/autostart/wicd-tray.desktop, which will autostart wicd-client upon login to your DE/WM. If so, enable the wicd systemd unit.

If /etc/xdg/autostart/wicd-tray.desktop does not exist, you can add wicd-client to your DE/WM startup to have the application start when you log in.

Note: If wicd-client is added to DE/WM startup when /etc/xdg/autostart/wicd-tray.desktop exists, you will have an issue of two wicd-client instances running.

Scripts

Wicd has the ability to run scripts during all stages of the connection process (post/pre connect/disconnect). Simply place a script inside the relevant stage folder within /etc/wicd/scripts/ and make it executable.

The scripts are able to receive three parameters, these being: 

$1 - the connection type (wireless/wired).
$2 - the ESSID (network name).
$3 - the BSSID (gateway MAC).

Stop ARP spoofing attacks

The script below can be used to set a static ARP, to stop ARP spoofing attacks. Simply change the values within the case statement to match those of the networks you want to set static ARP entries for. Launch it as root: 

#!/bin/bash
#Set the parameters passed to this script to meaningful variable names.
connection_type="$1"
essid="$2"
bssid="$3"

if [ "${connection_type}" == "wireless" ]; then

        #Change below to match your networks.
        case "$essid" in
        YOUR-NETWORK-NAME-ESSID)
                arp -s 192.168.0.1 00:11:22:33:44:55
         ;;
         Netgear01923)
                arp -s 192.168.0.1 10:11:20:33:40:50
         ;;
         ANOTHER-ESSID)
                arp -s 192.168.0.1 11:33:55:77:99:00
         ;;
         *)
                echo "Static ARP not set. No network defined."
         ;;
       esac
fi

Change MAC using macchanger

See MAC address spoofing#systemd + macchanger + dhcpcd (no NetworkManager)[broken link: invalid section].

The script below can be used to change the MAC address of your network interfaces.

To change the MAC whenever you connect to a network, place this script under /etc/wicd/scripts/preconnect/.

Take a look at macchanger --help to adjust the macchanger command to your liking. 

#!/usr/bin/env bash

connection_type="$1"

if [[ "${connection_type}" == "wireless" ]]; then
        ip link set wlp2s0 down
        macchanger -A wlp2s0
        ip link set wlp2s0 up
elif [[ "${connection_type}" == "wired" ]]; then
        ip link set enp1s0 down
        macchanger -A enp1s0
        ip link set enp1s0 up
fi

Start/stop openvpn client

Put the following script in /etc/wicd/scripts/postconnect/, to be able to restart openvpn client when wireless connected to specific ESSID, and replace the YOUR_WIFI_ESSID with your ESSID. 

#!/bin/sh

ESSID="YOUR_WIFI_ESSID"

if [ $1 == "wireless" ]; then
	if [ $2 == "$ESSID" ]; then
		systemctl restart openvpn-client@client
	fi
fi

Put the following script in /etc/wicd/scripts/predisconnect/, to stop openvpn client when wireless disconnected from specific ESSID and replace the YOUR_WIFI_ESSID with your ESSID. 

#!/bin/sh

ESSID="YOUR_WIFI_ESSID"

if [ $1 == "wireless" ]; then
	if [ $2 == "$ESSID" ]; then
		systemctl stop openvpn-client@client
	fi
fi

Troubleshooting

See Network configuration#Troubleshooting for troubleshooting wired connections and Wireless network configuration#Troubleshooting for troubleshooting wireless connections. This section covers only problems specific to wicd.

Autoconnect on resume from hibernation/suspension

If for some reasons autoconnect on resume from hibernation or suspension does not work automatically, you can manually restart Wicd by enabling the following service file for your user; see systemd/User#Basic setup. 

~/.config/systemd/user/wicd@resume.service
[Unit]
Description=Restart Wicd autoconnect service on resume
After=suspend.target

[Service]
Type=oneshot
User=%i
RemainAfterExit=no
ExecStart=/usr/share/wicd/daemon/autoconnect.py

[Install]
WantedBy=suspend.target

Importing pynotify failed, notifications disabled

In case the python2-notify package did not get installed automatically. You can install it from official repositories.

D-Bus connection error message

If wicd suddenly stopped working and it complains about D-Bus, it is quite likely that you just need to remove wicd fully, including and all its configuration files, and re-install it from scratch by first removing wicd. Then remove its configuration files: 

# rm -rf /etc/wicd /var/log/wicd /etc/dbus-1/system.d/wicd*

Then reinstall the package. Check this link for more details: https://bbs.archlinux.org/viewtopic.php?pid=577141#p577141

Wicd-client also throws a D-Bus connection error message ("Could not connect to wicd's D-Bus interface.") when wicd is not running due to a problem with a config file. It seems that sometimes an empty account gets added to /etc/wicd/wired-settings.conf in which case you simply have to remove the 

[]

and restart wicd.

If the above does not work, you could try https://bbs.archlinux.org/viewtopic.php?pid=1268721

Problems after package update

Sometimes the wicd client fails to load after a package update due to D-Bus errors. A solution is to stop wicd.service, remove the configuration files in the /etc/wicd/ directory, and start wicd.service.

Note about graphical sudo programs

If you are receiving an error about wicd failing to find a graphical sudo program, install one of gksu, ktsussAUR, or kdebase-runtime, then use the relative command: 

$ ktsuss wicd-client -n

$ gksudo wicd-client -n

$ kdesu wicd-client -n

Eduroam

See WPA2 Enterprise#Wicd[broken link: invalid section].

Two instances of wicd-client (and possibly two icons in tray)

See the note in #Running Wicd[broken link: invalid section] about the autostart file in /etc/xdg/autostart and the forum post and bug report provided in #External Links[broken link: invalid section]. Essentially, if /etc/xdg/autostart/wicd-tray.desktop exists, remove it. You only need the wicd service enabled in systemd.

Bad password using PEAP with TKIP/MS-CHAPv2

The connection template PEAP with TKIP/MS-CHAPv2 requires the user to enter the path to a CA certificate besides entering username and password. However this can cause troubles resulting in an error message of a bad password [1]. A possible solution is the usage of PEAP with GTC instead of TKIP/MS-CHAPv2 which does not require one to enter the path of the CA cert.

Wicd skips obtaining IP address on wlp

This can be caused by dhcpcd running alongside wicd as systemd service. A solution would be to stop/disable dhcpcd.

dhcpcd not running

Normally it should not be required, nor recommended to run the dhcpcd service next to wicd. However, if you encounter the error message that dhcpcd is not running, then you can try starting the dhcpcd systemd unit and see if you encounter any incompatibilities when using both services at the same time.

Alternatively, as a workaround you might consider switching to dhclient in the Wicd settings.

Note: If you get send_packet: Network is unreachable errors, then try increasing the timeout in /usr/share/dhclient/dhclient.conf.

See also

Retrieved from "https://wiki.archlinux.org/index.php?title=Wicd&oldid=493015"