Difference between revisions of "Netcfg Tips"

From ArchWiki
Jump to navigation Jump to search
(Enabling WOL)
(redirect like netcfg)
(One intermediate revision by one other user not shown)
Line 1: Line 1:
{{Lowercase title}}
#REDIRECT [[Netctl]]
{{Article summary start}}
{{Article summary text|Collect of tips and tricks for netcfg.}}
{{Article summary heading|Resources}}
{{Article summary wiki|netcfg}}
{{Article summary wiki|Netcfg Troubleshooting}}
{{Article summary end}}
{{Note|Netcfg has been superseded by [[netctl]]}}
=== Enabling WOL ===
Enabling WOL can be accomplished using a POST_UP statement in the profile.
POST_UP='/usr/bin/ethtool -s eth0 wol g'
=== Using jumbo frames ===
Insert the following line to the network profile(s) which require a non-standard MTU value:
POST_UP='/usr/sbin/ip link set eth0 mtu 4000'
The above example is using a 4k jumbo frame.
=== Clean logouts for users connected via sshd ===
Insert the following line to the network profile(s) which will kill all connected sshd sessions upon a network restart/stop:
PRE_DOWN='/usr/bin/pkill sshd'
=== rfkill (enable/disable radio power) ===
netcfg can enable/disable radio for wireless cards equipped with software control of radio. For wireless cards with hardware switches, netcfg can detect disabled hardware switches and fail accordingly.
To enable rfkill support, you need to specify what sort of switch the wireless interface has; hardware or software. This can be set within a profile or at the interface level ({{ic|/etc/network.d/interfaces/$INTERFACE}}; see [[#Per-interface configuration]]).
RFKILL=soft # can be either 'hard' or 'soft'
For some kill switches the rfkill entry in {{ic|/sys}} is not linked to the interface and the {{ic|RFKILL_NAME}} variable needs to be set to the contents of the matching {{ic|/sys/class/rfkill/rfkill#/name}}.
For example, on an Eee PC:
On a mid-2011 Thinkpad:
{{Note|The {{ic|net-auto-wireless}} daemon requires an interface level configuration of rfkill or it will not start.}}
{{Warning|Some devices (at least few SiS cards) can create {{Ic|/sys/class/rfkill/rfkill#}} entries with different names on every switch. Something like this will work in such cases (wifi-only solution!):
RFKILL_NAME=`cat /sys/class/rfkill/rfkill*/name 2> /dev/null || echo ""`</nowiki>}}}}
=== Execute commands before/after interface up/down ===
If your interface requires special actions prior/after the establishment/closure of a connection, you may use the {{ic|PRE_UP}}, {{ic|POST_UP}}, {{ic|PRE_DOWN}}, and {{ic|POST_DOWN}} variables.
For example, if you want to configure your wireless card to operate in ad-hoc mode but you can only change modes when the interface is down, you could use something like this:
PRE_UP="ip link set wlan0 down; iwconfig wlan0 mode ad-hoc"
Or if you want to mount your network shares after a successful connection, you could use:
POST_UP="sleep 5; mount /mnt/shares/nexus/utorrent 2>/dev/null"
Sometimes you may want to run something from netcfg with another user:
POST_UP="su -c '/you/own/command' username"
{{Note|If the commands specified in these properties return anything other than 0 (success), netcfg aborts the current operation. So if you want to mount a certain network share that might not be available at the time of connection (thus returning an error), you could create a separate [[Bash]] script with the mount commands and a {{ic|exit 0}} at the end. Alternatively you can add {{ic|<nowiki>|| true</nowiki>}} to the end of the command that may fail.}}
{{Note|The contents of these variables are evaluated with an {{ic|eval}} statement. Profile and interface variables like {{ic|ESSID}} are available for use, but must be escaped so that their evaluation is deferred to the eval. The easiest way to do that is to use single quotes. For example: {{ic|<nowiki>PRE_UP='echo $ESSID >/tmp/essid'</nowiki>}} will evaluate correctly, regardless where the {{ic|PRE_UP}} command is.}}
=== Intermittent Connection Failure ===
Some driver+hardware combinations drop associations sometimes. Use the pre and post commands to add/remove the driver and use a script like the following to fix the current connection:
log() { logger -t "$( basename $0 )" "$*" ; }
main() {
        local host
        while sleep 1; do
                [[ "$( netcfg current )" = "" ]] && continue
                host=$( route -n | awk '/^ { print $2 }' )
                ping -c1 -w10 $host && continue
                log "trying to reassociate"
                wpa_cli reassociate
                ping -c1 -w10 $host && continue
                log "reassociate failed, reconfiguring network"
                netcfg -r $( netcfg current )
exec 1>/dev/null
[[ $EUID != 0 ]] && { log "must be root"; exit 1; }
for cmd in wpa_cli ping netcfg; do
        ! which $cmd && {
                log "can't find command ${cmd}, exiting..."
                exit 1
log 'starting...'
=== Per-interface configuration ===
Configuration options that apply to all profiles using an interface can be set using {{ic|/etc/network.d/interfaces/$INTERFACE}}. For example:
This is useful for {{ic|wpa_supplicant}} options, rfkill switch support, pre/post up/down scripts and {{ic|net-auto-wireless}}. These options are loaded ''before'' profiles so that any profile-based options will take priority.
{{ic|/etc/network.d/interfaces/$INTERFACE}} may contain any valid profile option, though you are likely to use {{ic|PRE_UP}}/{{ic|DOWN}} and {{ic|POST_UP}}/{{ic|DOWN}} (described in the previous section) or one of the options listed below. Remember that these options are set for ''all'' profiles using the interface; you probably do not want to connect to your work VPN here, for instance, as it will try to connect on ''every'' wireless network!
WPA_GROUP  - Setting the group of the wpa_ctrl interface
WPA_COUNTRY - Enforces local regulatory limitations and allows use of more channels
WPA_DRIVER  - Defaults to wext, may want nl80211 for mac80211 devices
{{Note|{{ic|POST_UP}}/{{ic|POST_DOWN}} require the {{Pkg|wpa_actiond}} package.}}
=== Output hooks ===
netcfg has limited support to load hooks that handle output. By default it loads the {{ic|arch}} hook which provides the familiar output that you see. A syslog logging hook is also included. These can be found at {{ic|/usr/lib/network/hooks}}.
=== ArchAssistant (GUI) ===
A Qt-based netcfg front-end called ArchAssistant exists. It proposes to manage and connect/disconnect profiles from a system tray icon. Automatic wireless detection is also available. This tool is particularly useful for laptop users.
* {{AUR|archassistant}} in the [[Arch User Repository|AUR]]
* [http://www.kde-apps.org/content/show.php/ArchAssistant?content=76760 archassistant on kde-apps.org]
There is also a relatively new GUI for netcfg on qt-apps.org that does only network configuration. You can find it [http://www.qt-apps.org/content/show.php/netcfgGUI?content=99523 here].
=== Netcfg Easy Wireless LAN (newlan) ===
newlan is a mono console application that starts a user-friendly wizard to create [[netcfg]] profiles; it also supports wired connections.
Install the {{AUR|newlan}} package from the [[Arch User Repository|AUR]].
{{ic|newlan}} must be run with root privileges:
# newlan -n mynewprofile
=== wifi-select ===
{{Note|Latest version of netcfg will provide '''wifi-menu''' with functionality equal to that of wifi-select.}}
There is a console tool for selecting wireless networks in "real-time" (in [[NetworkManager]] fashion) called {{Pkg|wifi-select}}. The tool is convenient for use in Internet cafés or other places you are visiting for the first (and maybe the last) time. With this tool, you do not need to create a profile for a new network, just run {{ic|wifi-select wlan0}} as root and choose the desired network.
The tool is currently packaged as {{Pkg|wifi-select}} and is available in the [[Official Repositories|official repositories]].
{{Pkg|wifi-select}} does the following:
* parses {{ic|iwlist scan}} results and presents a list of networks along with their security settings (WPA/WEP/none) using {{Pkg|dialog}}
* if user selects network with existing profile -- just use this profile to connect with {{Pkg|netcfg}}
* if user selects a new network (for example, a Wi-Fi hotspot), {{Pkg|wifi-select}} automatically generates a new profile with corresponding {{ic|$SECURITY}} and asks for the key (if needed). It uses DHCP as {{ic|$IP}} by default
* then, if the connection succeeds, the profile is saved for later usage
* if the connection fails, the user is asked if he or she wants to keep generated profile for further usage (for example to change {{ic|$IP}} to static or adjust some additional options)
* [https://bbs.archlinux.org/viewtopic.php?id=63973 Forum thread] related to development of {{Pkg|wifi-select}}
* [https://github.com/sphynx/wifi-select wifi-select on GitHub]
=== Passing arguments to dhcpcd ===
For example, add this to the desired profile:
DHCP_OPTIONS='-C resolv.conf -G'
The above example prevents {{Pkg|dhcpcd}} from writing to {{ic|/etc/resolv.conf}} and setting any default routes.
==== Speed up DHCP with dhcpcd ====
By default, {{ic|dhcpcd}} confirms that the assigned IP address is not already taken via ARP. If you are confident that it will not be, e.g. in your home network, you can speed up the connection process by about 5 seconds by adding {{ic|--noarp}} to {{ic|DHCP_OPTIONS}}:
If you never want {{ic|dhcpcd}} to perform this check for any connection, you can globally configure this by adding the following line to {{ic|/etc/dhcpcd.conf}}:
=== Using dhclient instead of dhcpcd ===
To use {{Pkg|dhclient}} instead of {{Pkg|dhcpcd}}, simply add {{ic|DHCLIENT<nowiki>=</nowiki>yes}} to the desired profile.
=== Configuring a bridge for use with virtual machines (VMs) ===
To configure a bridge named br0 with a static IP:
DESCRIPTION="bridge br0 static"
To configure a bridge named br0 with a dhcp IP:
DESCRIPTION="bridge br0 dhcp"
Then add the corresponding bridge name to your {{ic|1=NETWORKS=(...)}} in {{ic|/etc/conf.d/netcfg}}.
It can be brought up by calling it directly, or by restarting {{ic|net-profiles}}.
netcfg br0
rc.d restart net-profiles
=== Adding multiple IP addresses to one interface ===
If you want to assign multiple IP addresses to 1 specific interface, this can be done by issuing the relevant {{ic|ip}} command in a {{ic|POST_UP}} statement (which as the name suggests will be executed after the interface has been brought up). Multiple statements can be separated with a {{ic|;}}. So if you for example would want to assign both and to interface eth0; the config would look something among the lines of:
POST_UP='ip addr add dev eth0'}}
=== Adding static routes ===
When wanting to configure static routes, this can be done by issuing the relevant {{ic|ip}} command in a {{ic|POSTUP}} statement (which as the name suggests will be executed after the interface has been brought up). Optionally, a {{ic|PRE_DOWN}} statement can be added to remove said routes when the interface is brought down. Multiple statements can be separated with a {{ic|;}}. In the below example we'll route over interface eth1 and then remove the route when the interface is brought down.
POST_UP='ip route add dev eth1'
PRE_DOWN='ip route del dev eth1'}}
==== Bluetooth tethering with pand ====
You can create a [[netcfg]] profile for easy tethering with your Bluetooth enabled device by using the regular "ethernet" connection and managing the pand connection in the PRE_UP and POST_DOWN hooks. Assuming an already paired device with address {{ic|00:00:DE:AD:BE:EF}}:
DESCRIPTION="Ethernet via pand tethering to Bluetooth device"
PRE_UP="pand -E -S -c ${BTADDR} -e ${INTERFACE} -n 2>/dev/null"
POST_DOWN="pand -k ${BTADDR}"
Then, either as root or using sudo, execute:
# netcfg tether
To bring the interface down and un-tether:
# netcfg down tether

Latest revision as of 15:31, 16 July 2013

Redirect to: