Networkmanager and eth0

Hi all!
I'm using networkmanager on a laptop. When I start the laptop it's connected to internet using wlan0, even if I have the ethernet plugged in. If I disable wlan0, and then unplug and plug ethernet again, nothing happen. It's not hardware or router problem (It works fine in other OS and pc's).
Anyone could help me?
That's my /etc/rc.conf
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
# in the hardware clock being left untouched (useful for virtualization)
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="ca_ES.UTF8"
HARDWARECLOCK="UTC"
TIMEZONE="Europe/Madrid"
KEYMAP="es"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(acpi-cpufreq cpufreq_ondemand fuse)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="Arch"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
#eth0="dhcp"
#wlan0="dhcp"
INTERFACES=(!eth0 !wlan0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(@syslog-ng dbus !network !smbnetfs @networkmanager @gdm @bluetooth @alsa @cpufreq @laptop-mode @cups)
The /etc/hosts:
# /etc/hosts: static lookup table for host names
#<ip-address> <hostname.domain.org> <hostname>
127.0.0.1 localhost.localdomain localhost Arch
# End of file
I found this lines on daemon.log, I don't know if It's related..
Mar 5 17:57:33 localhost NetworkManager[1962]: <info> Networking is enabled by state file
Mar 5 17:57:33 localhost NetworkManager[1962]: <info> (eth0): carrier is OFF
Mar 5 17:57:33 localhost NetworkManager[1962]: <info> (eth0): new Ethernet device (driver: 'e1000e' ifindex: 2)
Mar 5 17:57:33 localhost NetworkManager[1962]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0
Mar 5 17:57:33 localhost NetworkManager[1962]: <info> (eth0): now managed
Mar 5 17:57:33 localhost NetworkManager[1962]: <info> (eth0): device state change: 1 -> 2 (reason 2)
Mar 5 17:57:33 localhost NetworkManager[1962]: <info> (eth0): bringing up device.
Mar 5 17:57:33 localhost NetworkManager[1962]: <info> (eth0): preparing device.
Mar 5 17:57:33 localhost NetworkManager[1962]: <info> (eth0): deactivating device (reason: 2).
PD: Sry for my english.

I have installed Wicd and still don't work. I have a daemon or module missing? Help please, there is my lspci -k:
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02)
Subsystem: Toshiba America Info Systems Device 0001
Kernel driver in use: agpgart-intel
Kernel modules: intel-agp
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02)
Subsystem: Toshiba America Info Systems Device 0007
Kernel driver in use: i915
Kernel modules: i915
00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)
Subsystem: Toshiba America Info Systems Device 0001
00:19.0 Ethernet controller: Intel Corporation 82577LC Gigabit Network Connection (rev 06)
Subsystem: Toshiba America Info Systems Device 0001
Kernel driver in use: e1000e
Kernel modules: e1000e
00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
Subsystem: Toshiba America Info Systems Device 0001
Kernel driver in use: ehci_hcd
Kernel modules: ehci-hcd
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06)
Subsystem: Toshiba America Info Systems Device 0001
Kernel driver in use: HDA Intel
Kernel modules: snd-hda-intel
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 06)
Kernel modules: shpchp
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 06)
Kernel modules: shpchp
00:1c.2 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 3 (rev 06)
Kernel modules: shpchp
00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
Subsystem: Toshiba America Info Systems Device 0001
Kernel driver in use: ehci_hcd
Kernel modules: ehci-hcd
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 06)
Subsystem: Toshiba America Info Systems Device 0001
Kernel modules: iTCO_wdt
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA AHCI Controller (rev 06)
Subsystem: Toshiba America Info Systems Device 0001
Kernel driver in use: ahci
Kernel modules: ahci
00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 06)
Subsystem: Toshiba America Info Systems Device 0001
Kernel driver in use: intel ips
Kernel modules: intel_ips
01:00.0 SD Host controller: Ricoh Co Ltd MMC/SD Host Controller (rev 01)
Subsystem: Toshiba America Info Systems Device 0001
Kernel driver in use: sdhci-pci
Kernel modules: sdhci-pci
02:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01)
Subsystem: Askey Computer Corp. Device 7175
Kernel driver in use: brcm80211
Kernel modules: brcm80211
ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02)
Subsystem: Intel Corporation Device 8086
ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02)
Subsystem: Intel Corporation Device 8086
ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02)
Subsystem: Intel Corporation Device 8086
ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 02)
Subsystem: Intel Corporation Device 8086
ff:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
Subsystem: Intel Corporation Device 8086
ff:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
Subsystem: Intel Corporation Device 8086
Last edited by Segura (2011-03-05 22:26:14)

Similar Messages

Having Problems With GNOME3, NetworkManager, and nm-applet

So interesting problem. nm-applet does not connect to wireless networks, both secure and insecure(tried both). When I click on a network to connect to, it does not display the "connecting" icon or anything, it simply does nothing. To debug, I killed NetworkManager and then started it with:
sudo NetworkManager --no-daemon
This is some of the output I received:
NetworkManager[3333]: <info> (eth1): device state change: activated -> disconnected (reason 'user-requested') [100 30 39]
NetworkManager[3333]: <info> (eth1): deactivating device (reason: 39).
dhcpcd[3338]: received SIGTERM, stopping
dhcpcd[3338]: eth1: removing interface
NetworkManager[3333]: <info> (eth1): canceled DHCP transaction, DHCP client pid 3338
NetworkManager[3333]: <warn> (pid 3338) unhandled DHCP event for interface eth1
NetworkManager[3333]: <info> Activation (ra0) starting connection 'Auto scrapheap'
NetworkManager[3333]: <info> (ra0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
NetworkManager[3333]: <info> Activation (ra0) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager[3333]: <info> Activation (ra0) Stage 1 of 5 (Device Prepare) started...
NetworkManager[3333]: <info> Activation (ra0) Stage 2 of 5 (Device Configure) scheduled...
NetworkManager[3333]: <info> Activation (ra0) Stage 1 of 5 (Device Prepare) complete.
NetworkManager[3333]: <info> Activation (ra0) Stage 2 of 5 (Device Configure) starting...
NetworkManager[3333]: <info> (ra0): device state change: prepare -> config (reason 'none') [40 50 0]
NetworkManager[3333]: <info> Activation (ra0/wireless): access point 'Auto scrapheap' has security, but secrets are required.
NetworkManager[3333]: <info> (ra0): device state change: config -> need-auth (reason 'none') [50 60 0]
NetworkManager[3333]: <info> Activation (ra0) Stage 2 of 5 (Device Configure) complete.
NetworkManager[3333]: <warn> No agents were available for this request.
NetworkManager[3333]: <info> (ra0): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
NetworkManager[3333]: <warn> Activation (ra0) failed for access point (scrapheap)
NetworkManager[3333]: <info> Marking connection 'Auto scrapheap' invalid.
NetworkManager[3333]: <warn> Activation (ra0) failed.
NetworkManager[3333]: <info> (ra0): device state change: failed -> disconnected (reason 'none') [120 30 0]
NetworkManager[3333]: <info> (ra0): deactivating device (reason: 0).
NetworkManager[3333]: <info> Activation (ra0) starting connection 'Auto AFK - Fucking Bitches'
NetworkManager[3333]: <info> (ra0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
NetworkManager[3333]: <info> Activation (ra0) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager[3333]: <info> Activation (ra0) Stage 1 of 5 (Device Prepare) started...
NetworkManager[3333]: <info> Activation (ra0) Stage 2 of 5 (Device Configure) scheduled...
NetworkManager[3333]: <info> Activation (ra0) Stage 1 of 5 (Device Prepare) complete.
NetworkManager[3333]: <info> Activation (ra0) Stage 2 of 5 (Device Configure) starting...
NetworkManager[3333]: <info> (ra0): device state change: prepare -> config (reason 'none') [40 50 0]
NetworkManager[3333]: <info> Activation (ra0/wireless): access point 'Auto AFK - Fucking Bitches' has security, but secrets are required.
NetworkManager[3333]: <info> (ra0): device state change: config -> need-auth (reason 'none') [50 60 0]
NetworkManager[3333]: <info> Activation (ra0) Stage 2 of 5 (Device Configure) complete.
NetworkManager[3333]: <warn> No agents were available for this request.
NetworkManager[3333]: <info> (ra0): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
NetworkManager[3333]: <warn> Activation (ra0) failed for access point (AFK - Fucking Bitches)
NetworkManager[3333]: <info> Marking connection 'Auto AFK - Fucking Bitches' invalid.
NetworkManager[3333]: <warn> Activation (ra0) failed.
NetworkManager[3333]: <info> (ra0): device state change: failed -> disconnected (reason 'none') [120 30 0]
NetworkManager[3333]: <info> (ra0): deactivating device (reason: 0).
This is the output right after I disconnected from my ethernet connection, which I should mention works fine through nm-applet. Just a little background knowledge, this is a fresh install of gnome3, and I followed the ArchLinux wiki article on NetworkManager. I should also mention, that I have never been prompted for a password, and I have tried manually entering the password using nm-connection-editor, to no avail.

First of all, thanks for your response. In no particular order:
Here is my rc.conf-
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
# startup and during the boot process. If set to 'no', the C locale is used.
# HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
# in the hardware clock being left untouched (useful for virtualization)
# Note: Using "localtime" is discouraged.
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
# VERBOSE: Verbose level (from 1 to 8). man 3 syslog for level info
LOCALE="en_US.UTF-8"
DAEMON_LOCALE="no"
HARDWARECLOCK="UTC"
TIMEZONE="America/Chicago"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
VERBOSE="3"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
MOD_AUTOLOAD="yes"
MODULES=(!rt2870sta !rt2800pci !rt2x00pci !rt2800lib !rt2800usb !rt2x00usb !rt2x00lib rt3572sta)
# Udev settle timeout (default to 30)
UDEV_TIMEOUT=30
# Scan for FakeRAID (dmraid) Volumes at startup
USEDMRAID="no"
# Scan for BTRFS volumes at startup
USEBTRFS="no"
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="SOLID"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
INTERFACES=(!eth0 !ra0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
# If something other takes care of your hardware clock (ntpd, dual-boot...)
# you should disable 'hwclock' here.
DAEMONS=(hwclock syslog-ng netfs crond dbus networkmanager gdm)
This is what happens when I attempt to connect to a wireless network in my daemon.log:
May 24 19:41:57 localhost NetworkManager[2650]: <info> (ra0): supplicant interface state: inactive -> disconnected
May 24 19:42:43 localhost NetworkManager[2650]: <info> (ra0): supplicant interface state: disconnected -> inactive
May 24 19:52:39 localhost NetworkManager[2650]: <info> Activation (ra0) starting connection 'Auto AFK - Fucking Bitches'
May 24 19:52:39 localhost NetworkManager[2650]: <info> (ra0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
May 24 19:52:39 localhost NetworkManager[2650]: <info> Activation (ra0) Stage 1 of 5 (Device Prepare) scheduled...
May 24 19:52:39 localhost NetworkManager[2650]: <info> Activation (ra0) Stage 1 of 5 (Device Prepare) started...
May 24 19:52:39 localhost NetworkManager[2650]: <info> Activation (ra0) Stage 2 of 5 (Device Configure) scheduled...
May 24 19:52:39 localhost NetworkManager[2650]: <info> Activation (ra0) Stage 1 of 5 (Device Prepare) complete.
May 24 19:52:39 localhost NetworkManager[2650]: <info> Activation (ra0) Stage 2 of 5 (Device Configure) starting...
May 24 19:52:39 localhost NetworkManager[2650]: <info> (ra0): device state change: prepare -> config (reason 'none') [40 50 0]
May 24 19:52:39 localhost NetworkManager[2650]: <info> Activation (ra0/wireless): access point 'Auto AFK - Fucking Bitches' has security, but secrets are required.
May 24 19:52:39 localhost NetworkManager[2650]: <info> (ra0): device state change: config -> need-auth (reason 'none') [50 60 0]
May 24 19:52:39 localhost NetworkManager[2650]: <info> Activation (ra0) Stage 2 of 5 (Device Configure) complete.
May 24 19:52:39 localhost NetworkManager[2650]: <warn> No agents were available for this request.
May 24 19:52:39 localhost NetworkManager[2650]: <info> (ra0): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
May 24 19:52:39 localhost NetworkManager[2650]: <warn> Activation (ra0) failed for access point (AFK - Fucking Bitches)
May 24 19:52:39 localhost NetworkManager[2650]: <info> Marking connection 'Auto AFK - Fucking Bitches' invalid.
May 24 19:52:39 localhost NetworkManager[2650]: <warn> Activation (ra0) failed.
May 24 19:52:39 localhost NetworkManager[2650]: <info> (ra0): device state change: failed -> disconnected (reason 'none') [120 30 0]
May 24 19:52:39 localhost NetworkManager[2650]: <info> (ra0): deactivating device (reason: 0).
May 24 19:52:39 localhost NetworkManager[2650]: <info> (ra0): reset MAC address to 00:00:00:00:00:00
May 24 19:52:40 localhost NetworkManager[2650]: <info> Policy set 'Wired connection 2' (eth1) as default for IPv4 routing and DNS.
And this is what gets printed in my kernel.log when I attempt to connect to a wireless network:
May 24 19:57:14 localhost kernel: [76209.155402] ===>rt_ioctl_giwscan. 6(6) BSS returned, data->length = 998
May 24 19:57:14 localhost kernel: [76209.157419] ===>rt_ioctl_giwscan. 6(6) BSS returned, data->length = 998
May 24 19:57:22 localhost kernel: [76216.809056] ra0: no IPv6 routers present
May 24 19:57:36 localhost kernel: [76231.105479] (Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
May 24 19:57:36 localhost kernel: [76231.105482] (Reassign Efuse for 3x7x/3x9x/53xx) Size=0x3c [3c0-3fb]
May 24 19:57:36 localhost kernel: [76231.364008] RTMP_TimerListAdd: add timer obj fa284038!
May 24 19:57:36 localhost kernel: [76231.364011] RTMP_TimerListAdd: add timer obj fa284080!
May 24 19:57:36 localhost kernel: [76231.364012] RTMP_TimerListAdd: add timer obj fa2840c8!
And it doesn't work in fallback mode. It does pretty much the same thing.
Last edited by jayd3e (2011-05-25 01:17:29)

[SOLVED] NetworkManager and UMTS/3G

I have a problem with NetworkManager and its Applet (the GNOME one)
In Ubuntu 10.04 it works fine with NM and in Archlinux it works flawless with wvdial but not with NetworkManager
It just tells me that i dont have any UMTS/3G devices (which is just nonsense)
Is that a bug in NetworkManager or am i doing something wrong?
//Edit: Oh damm i just forget the optional dependency "modemmanager"... solved
Last edited by Vamp898 (2010-06-14 00:43:24)

Your edit got me one step further, now I see that device also in networkmanager here finally. Thank you!
If someone tries to click onto "configure" for "mobile broadband" and its greyed out: Click "configure" for wired, leave that window open and just click "configure" in the main networkmanager window again. Then the network connections box from gnome 2 comes up and allows to configure 3G entries. (not a gnome bug, but a feature;)

Can't connect to mobile broadband with NetworkManager and Huawei E1550

Hi,
I'm trying to connect to mobile broadband internet (3G) using my Huawei E1550 HSDPA USB Stick and NetworkManager but it won't work.
At first, the LED on the usb device seems to indicate that the connection is established, but immediately afterwards it starts blinking again (which shows that no connection is established).
nm-applet then tells me that I've been disconnected (although the connection was never established).
I installed usb_modeswitch and modemmanager and enabled modemmanager with the systemctl command.
The ID of the device is 12d1:140c, which is supposed to be right after the modeswitch.
Here is the relevant log:
[stecklars@Lars-NB ~]$ sudo NetworkManager --no-daemon --log-level=INFO
NetworkManager[1450]: <warn> (cdc-wdm0): failed to look up interface index
NetworkManager[1450]: <info> (cdc-wdm0): new Broadband device (driver: 'option1, qmi_wwan' ifindex: 0)
NetworkManager[1450]: <info> (cdc-wdm0): exported as /org/freedesktop/NetworkManager/Devices/2
NetworkManager[1450]: <info> (cdc-wdm0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
NetworkManager[1450]: <info> (cdc-wdm0): deactivating device (reason 'managed') [2]
NetworkManager[1450]: <info> (cdc-wdm0): device state change: unavailable -> disconnected (reason 'none') [20 30 0]
NetworkManager[1450]: <info> (cdc-wdm0) modem state changed, 'disabled' --> 'enabling' (reason: user-requested)
NetworkManager[1450]: <info> (cdc-wdm0) modem state changed, 'enabling' --> 'registered' (reason: user-requested)
NetworkManager[1450]: <info> WWAN now enabled by management service
NetworkManager[1450]: <info> Activation (cdc-wdm0) starting connection 'Verbindung mit event.vodafone.de'
NetworkManager[1450]: <info> (cdc-wdm0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
NetworkManager[1450]: <info> NetworkManager state is now CONNECTING
NetworkManager[1450]: <info> Activation (cdc-wdm0) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager[1450]: <info> Activation (cdc-wdm0) Stage 1 of 5 (Device Prepare) started...
NetworkManager[1450]: <info> Activation (cdc-wdm0) Stage 1 of 5 (Device Prepare) complete.
NetworkManager[1450]: <info> (cdc-wdm0) modem state changed, 'registered' --> 'connecting' (reason: user-requested)
NetworkManager[1450]: <info> (cdc-wdm0) modem state changed, 'connecting' --> 'connected' (reason: user-requested)
NetworkManager[1450]: <info> Activation (cdc-wdm0) Stage 2 of 5 (Device Configure) scheduled...
NetworkManager[1450]: <info> Activation (cdc-wdm0) Stage 2 of 5 (Device Configure) starting...
NetworkManager[1450]: <info> (cdc-wdm0): device state change: prepare -> config (reason 'none') [40 50 0]
NetworkManager[1450]: <info> (cdc-wdm0): bringing up device.
NetworkManager[1450]: <info> Activation (cdc-wdm0) Stage 2 of 5 (Device Configure) successful.
NetworkManager[1450]: <info> Activation (cdc-wdm0) Stage 3 of 5 (IP Configure Start) scheduled.
NetworkManager[1450]: <info> Activation (cdc-wdm0) Stage 2 of 5 (Device Configure) complete.
NetworkManager[1450]: <info> Activation (cdc-wdm0) Stage 3 of 5 (IP Configure Start) started...
NetworkManager[1450]: <info> (cdc-wdm0): device state change: config -> ip-config (reason 'none') [50 70 0]
NetworkManager[1450]: <info> Activation (wwp0s26f7u3i1) Beginning DHCPv4 transaction (timeout in 45 seconds)
NetworkManager[1450]: <info> dhcpcd started with pid 1596
NetworkManager[1450]: <info> Activation (cdc-wdm0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
NetworkManager[1450]: <info> Activation (cdc-wdm0) Stage 3 of 5 (IP Configure Start) complete.
NetworkManager[1450]: <info> Activation (cdc-wdm0) Stage 4 of 5 (IPv6 Configure Timeout) started...
NetworkManager[1450]: <info> Activation (cdc-wdm0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
dhcpcd[1596]: version 6.0.5 starting
dhcpcd[1596]: wwp0s26f7u3i1: soliciting an IPv6 router
dhcpcd[1596]: wwp0s26f7u3i1: ipv6rs_sendprobe: sendmsg: Cannot assign requested address
NetworkManager[1450]: <info> (wwp0s26f7u3i1): DHCPv4 state changed nbi -> preinit
dhcpcd[1596]: wwp0s26f7u3i1: soliciting a DHCP lease
dhcpcd[1596]: wwp0s26f7u3i1: removing interface
NetworkManager[1450]: <info> (wwp0s26f7u3i1): DHCPv4 state changed preinit -> stop
NetworkManager[1450]: <info> (cdc-wdm0): device state change: ip-config -> unmanaged (reason 'removed') [70 10 36]
NetworkManager[1450]: <info> (cdc-wdm0): deactivating device (reason 'removed') [36]
dhcpcd[1596]: exited
NetworkManager[1450]: <info> (wwp0s26f7u3i1): canceled DHCP transaction, DHCP client pid 1596
NetworkManager[1450]: <warn> (12) failed to find interface name for index
NetworkManager[1450]: nm_system_iface_flush_routes: assertion 'iface != NULL' failed
NetworkManager[1450]: <warn> (12) failed to find interface name for index
NetworkManager[1450]: <warn> (12) failed to find interface name for index
NetworkManager[1450]: nm_system_iface_flush_routes: assertion 'iface != NULL' failed
NetworkManager[1450]: <warn> (12) failed to find interface name for index
NetworkManager[1450]: <info> (cdc-wdm0): cleaning up...
NetworkManager[1450]: <info> (cdc-wdm0): taking down device.
NetworkManager[1450]: <info> NetworkManager state is now DISCONNECTED
NetworkManager[1450]: <warn> (pid 1596) unhandled DHCP event for interface wwp0s26f7u3i1
NetworkManager[1450]: <warn> (cdc-wdm0) failed to disconnect modem: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 'org.freedesktop.ModemManager1.Modem.Simple' on object at path /org/freedesktop/ModemManager1/Modem/1
I'd be thankful if you could help me.
Lars

Here is the relevant part of dmesg, when the connection drops:
[ 1300.891794] option1 ttyUSB0: option_instat_callback: error -108
[ 1300.892296] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
[ 1300.892316] option 4-3:1.0: device disconnected
[ 1300.894497] qmi_wwan 4-3:1.1 wwp0s26f7u3i1: unregister 'qmi_wwan' usb-0000:00:1a.7-3, WWAN/QMI device
[ 1300.906958] option1 ttyUSB1: usb_wwan_indat_callback: resubmit read urb failed. (-2)
[ 1300.906966] option1 ttyUSB1: usb_wwan_indat_callback: resubmit read urb failed. (-2)
[ 1300.906969] option1 ttyUSB1: usb_wwan_indat_callback: resubmit read urb failed. (-2)
[ 1300.912513] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
[ 1300.912535] option 4-3:1.3: device disconnected
[ 1300.912830] option1 ttyUSB2: usb_wwan_indat_callback: resubmit read urb failed. (-2)
[ 1300.912837] option1 ttyUSB2: usb_wwan_indat_callback: resubmit read urb failed. (-2)
[ 1300.912840] option1 ttyUSB2: usb_wwan_indat_callback: resubmit read urb failed. (-2)
[ 1300.917744] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
[ 1300.917759] option 4-3:1.4: device disconnected
[ 1301.787207] hub 4-0:1.0: Cannot enable port 3. Maybe the USB cable is bad?
[ 1302.653814] hub 4-0:1.0: Cannot enable port 3. Maybe the USB cable is bad?
[ 1303.520436] hub 4-0:1.0: Cannot enable port 3. Maybe the USB cable is bad?
[ 1304.387195] hub 4-0:1.0: Cannot enable port 3. Maybe the USB cable is bad?
[ 1304.387273] usb 4-3: USB disconnect, device number 20
[ 1304.993295] usb 4-3: new high-speed USB device number 22 using ehci-pci
[ 1305.132944] option 4-3:1.0: GSM modem (1-port) converter detected
[ 1305.133319] usb 4-3: GSM modem (1-port) converter now attached to ttyUSB0
[ 1305.137914] qmi_wwan 4-3:1.1: cdc-wdm0: USB WDM device
[ 1305.138503] qmi_wwan 4-3:1.1 wwan0: register 'qmi_wwan' at usb-0000:00:1a.7-3, WWAN/QMI device, ea:38:f6:b1:32:0b
[ 1305.138955] option 4-3:1.3: GSM modem (1-port) converter detected
[ 1305.139320] usb 4-3: GSM modem (1-port) converter now attached to ttyUSB1
[ 1305.139537] option 4-3:1.4: GSM modem (1-port) converter detected
[ 1305.139717] usb 4-3: GSM modem (1-port) converter now attached to ttyUSB2
[ 1305.139997] usb-storage 4-3:1.5: USB Mass Storage device detected
[ 1305.140144] scsi33 : usb-storage 4-3:1.5
[ 1305.143268] usb-storage 4-3:1.6: USB Mass Storage device detected
[ 1305.144927] scsi34 : usb-storage 4-3:1.6
[ 1305.183447] systemd-udevd[1917]: renamed network interface wwan0 to wwp0s26f7u3i1
[ 1306.157713] scsi 33:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2
[ 1306.161464] scsi 34:0:0:0: Direct-Access HUAWEI MMC Storage 2.31 PQ: 0 ANSI: 2
[ 1306.168217] sr0: scsi-1 drive
[ 1306.168445] sr 33:0:0:0: Attached scsi CD-ROM sr0
[ 1306.178582] sd 34:0:0:0: [sdc] Attached SCSI removable disk
EDIT: Wow, got it working using wvdial. Would prefer to use NetworkManager and ModemManager, however. Any idea why it isn't working using those?
Last edited by stecklars (2014-01-23 18:50:45)

Network bridge problems linking wwan0 and eth0 [SOLVED]

Hi There,
I have just got working a 3G modem which appears as device wwan0. I am trying to link this interface to my wired ethernet eth0.
wwan0 seems to work fine with network manager, getting a IP address via dhcp works just fine and I can use the interface.
However, when I disable network manager and try to bring up the bridge with "netcfg up bridge" it times out, failing to get an lease with dhcp.
My /etc/network.d/bridge file contains the following:
INTERFACE="br0"
CONNECTION="bridge"
DESCRIPTION="Bridge wired and wireless connection"
BRIDGE_INTERFACES="eth0 wwan0"
IP="dhcp"
#FWD_DELAY=10
As per the wiki, I have tried using various values for FWD_DELAY (i.e 10 7 5,4,3,2,1,0) but nothing ..
The relevant sections of /etc/rc.conf are:
NETWORKS=(bridge)
DAEMONS=( ... net-profiles !networkmanager ...)
It seems that DHCP via networkmanager is the only way the interface gets an IP. I even tried "dhcpd br0" or "dhcpd wwan0" and they both time out.
Anyone have any suggestions?
Last edited by bmentink (2012-05-15 22:02:00)

Hi,
Ok I have this working now, here are the steps I used.
1. Allowed NetworkManager to setup the 3G Interface wwan0 with DHCP ..
2. Disabled my eth0 interface from Networkmanager by putting an entry in /etc/Networkmanager/Networkmanager.conf
3. Manually configured eth0 with a static IP of 192.168.0.1
4. did the "echo 1 > /proc/sys/net/ipv4/ip_forward" thing for IP forwarding
5. did the following with iptables:
iptables -t nat -A POSTROUTING -o wwan0 -j MASQUERADE
rc.d save iptables
rc.d start iptables
6. Connected my wireless router "wan" port to eth0 and configured for 192.168.0.2 IP address and DNS servers dished up from the network ..
( .. looked at the entries in /etc/resolve.conf on the PC I am sharing the internet )
I can then connect to my wireless lan with my other computers..and on to the internet ... yahoo .. :-)
The only issue I have with this setup is getting the 3G interface to connect automatically to the network .. I ticked the box in networkmanager, but it doesn't seem to work
if I reboot the PC or take the usb T stick out and plug back in, I have to manually connect to the network with networkmanager. Does anyone know how to do this automatically ..
[edit] seems this is a known bug ... you can only auto connect when the interface power is set to "on", but stupidly it defaults to "off"
Thanks,
B.
Last edited by bmentink (2012-05-14 07:56:04)

[SOLVED] Networkmanager and special ascii characters kde issue

cannot connect to ssid with french characters like 'é' and other chars in networkmanager kde
it work fine in gnome but in kde the networkmanager dont recognize non english letters
have any one a way to use Hex value instead of ascii in ssid
Last edited by jambi (2014-07-14 00:03:43)

You need to configure the profile manually in
/etc//etc/NetworkManager/system-connections/
then create a file named
(null) 1
[connection]
id=(null) 1
type=802-11-wireless
[802-11-wireless]
ssid="SSID IN HEX"
mode=infrastructure
mac-address=xx:xx:xx:xx:xx
security=802-11-wireless-security
[802-11-wireless-security]
key-mgmt='wireless security'
auth-alg=open
psk=password
you can convert from ascii to hex using terminal
echo 'ssid' | xxd -u -p
connectioneditor in kde need more handling functions to be added . i hope in next release they build a robust connectioneditor
Last edited by kortez (2014-07-07 21:15:45)

[SOLVED] Disable/remove NetworkManager, and use netctl

Hello!
I just installed arch linux and gnome shell with only few applications. I was using netctl-auto, which I enabled using systemctl during the installation. Everything was worked fine, until I installed the packages tlp and tlp-rdw. They pulled in NetworkManager as a dependency and now I can only use this and not netctl. When I try to uninstall NetworkManager it doesn't allow me, because of some applications that depend on it. One of them is "telepathy-mission-control" and appearantly gnome-shell is depending on that... I have no idea why this complication suddenly occurs, since everything was working fine until I installed tlp, tlp-rdw and its dependencies.
Can anyone tell me how to disable or preferably completely remove NetworkManager in favor of netctl, so we can be re-united and live happily in netctl-auto-harmony once again?
Last edited by AlexanderHolmgaard (2015-04-16 12:27:16)

kenwong wrote:
ooo wrote: and adding it to NoExtract in your pacman.conf
Do you mean that in the pacman.conf file I make it like this?
NoExtract=/etc/xdg/autostart/nm-applet.desktop
yes. see 'man pacman.conf' for details.
EDIT: actually it looks like that can't have that first /, so this should work better:
NoExtract=etc/xdg/autostart/nm-applet.desktop
Last edited by ooo (2015-04-16 15:05:18)

[SOLVED]eth1 and eth0 keep switching

Ok I've got two NIC's in this computer, one refuses to get an IP address from DHCP the other work perfectly fine. However each time I start up the one that previously was eth0 is now eth1 and vise versa.
eth0="dhcp"
INTERFACES=(eth0)
00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev f3) # WORKS
05:0c.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13) # BORK
[01:21 AM][desktop:~]# uname -rm
2.6.30-ARCH x86_64
Last edited by fumbles (2009-07-01 04:05:07)

http://wiki.archlinux.org/index.php/Ude … _Each_Boot

[SOLVED] NetworkManager and DNS

Hello,
Is there any way to set and make permanent DNS adress with NetworkManager? I'd like to use OpenDNS so I edited /etc/resolv.conf and it works till next system restart. What am I supposed to do to make DNS adress permanent?:/
EDIT: Something gone wrong.
EDIT: Solved, it's new NetworkManager 0.7.
Last edited by MilosC (2009-03-08 02:10:32)

My all time favorite way to do this is to put your isp (or OpenDNS addresses, etc) into your router via it's own configuration page. I've never had to mess around with resolv.conf, dhclient etc this way for over 5 years and let the box pick it up from your router.
After making the change in the router, restart networking, or reboot.

KDE networkmanager and sharing mobile internet connection to wlan

I'm not so expert in networking only a user.
I use KDE 4.6.1. I have a netbook with Atheros AR5001 Wireless Network Adapter driver ath5k. I have installed networkmanagement 20110226-1 and networkmanager 0.8.2-3.
I connect to the internet with a mobile broadband connection CDMA/EDVO that is well recognized and connect well.
I used to share the connection with other notebook.
But I can't create an ad-hoc shared connection.
After installing dnsmasq and follow the instruction finded here: https://wiki.archlinux.org/index.php/Sh … _interface
Configure dnsmasq. Make the following changes to /etc/dnsmasq.conf (uncomment if necessary):
domain-needed
bogus-priv
interface=wlan0
dhcp-range=10.42.43.1,10.42.43.100,12h
Start dnsmasq as root:
/etc/rc.d/dnsmasq start
Finally, set firewall to forward connections to and from the Internet for clients connecting to your wlan. This is done by issuing (you guessed it right, as root again):
iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE
Now it reply this error from the log
Mar 14 07:09:05 netbook-pc NetworkManager[2084]: <error> [1300082945.419707] [nm-device-wifi.c:1544] nm_device_wifi_set_mode(): (wlan0): error setting mode 2
The NetworkManager enter in a loop of trying to connect.
Can anyone help me?

According to that blogpost (mentioned in above post - http://lamarque-lvs.blogspot.com/2011/0 … ging.html), the bug has been solved and:
Plasma NM does not follow KDE SC release schedule. I tested this code yesterday with KDE 4.4.4 and it worked. It is just a matter of distributions updating their packages with this code.
And from https://bugs.launchpad.net/ubuntu/+sour … bug/725041 (same bug, reported for network-manager package in Ubuntu):
This bug was fixed in the package network-manager - 0.8.4~git.20110228t143901.5cdded6-0ubuntu1
Archlinux currently uses networkmanager 0.8.3-0.20110113, any chances of anyone including these updates anytime soon?

No route to openvpn server when using networkmanager and wireless

Since some weeks I can not connect to openvpn networks via WIFI when using the networkmanager. Connecting manually there is no problem.
When I connect my laptop via LAN (enp0s25) and establish an openvpn connection everything works as expected:
[me@laptop ~]$ ip route show
default via 10.101.2.173 dev tun0 proto static metric 1024
10.101.2.173 dev tun0 proto kernel scope link src 10.101.2.174
172.17.2.0/24 dev enp0s25 proto kernel scope link src 172.17.2.25
172.17.2.0/24 dev enp0s25 proto kernel scope link src 172.17.2.25 metric 203
xxx.xx.xx.xxx via 172.17.2.1 dev enp0s25 proto static metric 1
When connecting to the internet via WIFI (wlp3s0) the VPN connection is established but there is no route to the VPN server:
[me@laptop~]$ ip route show
default via 10.101.2.173 dev tun0 proto static metric 1024
10.101.2.173 dev tun0 proto kernel scope link src 10.101.2.174
172.17.2.0/24 dev wlp3s0 proto kernel scope link src 172.17.2.38
When I add the route manually everything works fine:
ip route add xxx.xx.xx.xxx via 172.17.2.1 dev wlp3s0 proto static metric 1
Any ideas?

There are two problems here. The first is a firewall problem. Although the Open MQ port mapper running on port 7676 wasn't being blocked, the port that mq tcp port was. I was able to solve this by creating an ssh tunnel and specifying a mqtcp connection.
"Table 182 Message Broker Addressing Schemes"
http://docs.sun.com/app/docs/doc/820-4916/6ngbm6hp4?a=view#gbnnt
f.setProperty(ConnectionConfiguration.imqAddressList,"mqtcp://" + host + ":32782/jms");This solution is less than ideal, since the mq tcp port can change. In fact, if you reference the original post, you can see it has already changed on me. I could write code to determine what the port is and create my own tunnel, but that doesn't seem worth the effort just yet.
The second problem is the lack of helpful error message. It's the sort of problem where you can't really blame any one party too much. Open MQ and Java are both just reporting the error message that they are given by the operating system. They should do a bit more than that.

NetworkManager and the missing domain

I was facing this issue, after i changed one of my domains ip, i was unable to resolve its name on my arch machine (ping mydomain) , my first thought was delayed propagation of dns, but that was not the case, on another machine i could reach it , if i turned my vpn on i could reach it.
Now comes what is driving me crazy, i try refreshing all dns caches i read could exist on the arch wiki to no avail, i also created a network profile with a different dns server (it works!) trouble is after a reboot a new profile appears in gnome network and the profile i created has to be manually activated.
So why my domain is unreachable on my machine alone?
How to i prevent NetworkManager from creating a profile on boot so it can stick with the one i created?
Man i am trying to solve this for 3 days with no avail its becoming darn obsessive! this issue need to go away from my (almost) perfect functioning arch machine!

Using the change in the forums to highlight your angst about the future of the FC Studio product is an interesting parallel. I'll stay with it.
We all need a bit of time to see just how this new way of sharing knowledge works. If you don't find the thing your looking for right away it doesn't mean its gone. In the discussions under the link to this section Final Cut Studio You'll find three tabs at the top. In the tab labeled All Content your find the discussions broken down into the various products under the studio banner.
Some early reaction to the new version of Final Cut were negative because its appearance was perceived as a dumbed down version. The reality is the UI redesign and added features are a step forward in the area editing. As for the future of products like Color, DVDSP, Motion and SoundtrackPro, (I trying not to speculate) I'm sure that the kind of improvements seen in Final Cut Pro will also be apart of the next versions of those products.
TOnyTOny

[SOLVED] Problem with Networkmanager and two WiFi cards

I have two WiFi cards, one onboard my laptop, one USB. I use the USB one since gets a stronger signal, but the other one tries to connect.
Is there a way of stoping that.
I don't want to cancel the possibility of using it, just when I plug the USB antenna.
Thank you
Last edited by Frezeeer (2013-02-10 20:41:24)

progandy wrote:Is there an entry for your onboard wifi in rfkill? Then block it when pluggin in the usb stick and unblock it lateron.
Thanks for the reply.
This is what I get:
$ rfkill list
0: samsung-wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
1: samsung-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
3: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
4: phy1: Wireless LAN
Soft blocked: no
Hard blocked: no
If I try to "block" either number 2 or number 4. The WiFi disconects. It's as if they were the same card.
Any ideas?
Once again thank you

Slow boot with systemd due to NetworkManager and laptop-mode-tools

ernestas ~ $ systemd-analyze blame
25787ms NetworkManager.service
3440ms laptop-mode-tools.service
1792ms systemd-logind.service
1573ms systemd-modules-load.service
1519ms home.mount
1305ms polkit.service
977ms systemd-udevd.service
903ms systemd-sysctl.servic
What could be the underlying problem? How do I solve it?

Okay. I no longer use laptop-mode-tools, but NetworkManager still seems to be slow:
ernestas ~ $ systemd-analyze blame
3592ms NetworkManager.service
3013ms systemd-logind.service
869ms dev-sda7.swap
762ms home.mount
666ms systemd-modules-load.service
546ms systemd-udev-trigger.service
523ms systemd-udevd.service
500ms dev-hugepages.mount
479ms sys-kernel-debug.mount
Last edited by ernetas (2012-11-03 16:01:44)

Eth0 and eth1 are improperly configured [Solved]

*Interfaces solved by reassigning Mac addresses for both interfaces and reflecting those changes in rc.conf
DHCP is no longer working for me and my HP Mini-1125nr netbook is no longer able to get online via ifplugd. This adds to my ongoing battle with Broadcom-wl (I installed it from the AUR) and Arch wireless in general. It seems my interfaces are not setup correctly. I'm using the wiki and google, but not winning the war. At boot network fails and declares
wlan0: unknown interface: no such device
current rc.conf chunks (see my previous config which had working eth0 dhcp)
MOD_AUTOLOAD="no"
MODULES=(lib80211_crypt_tkip wl !b43 !ssb snd-hda-intel atl1)
eth0="dhcp"
wlan0="dhcp"
INTERFACES=(wlan0 eth0)
My NETWORKS is still default (main) as I have not setup a network manager beyond ifplugd
DAEMONS=(syslog-ng hal network netfs @crond @alsa @ifplugd)
ifconfig -a note: wlan missing and eth0 has no inet addr or mask
eth0 Link encap:Ethernet HWaddr 0C:60:76:2D:E9:B6
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:16 Base address:0xc000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
iwconfig
lo no wireless extensions
eth0 IEEE 802.11 Nickname:""""
Access Point: Not-Associated
Link Quality:5 Signal level:0 Noise level:0
Rx invalid nwid:0 invalid:crypt invalid misc:0
lsmod | grep wl
wl 1944061 0
lib80211 3158 2 wl, lib80211_crypt_tkip
lspci -vnn | grep 14e4
01:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g [14e4:4315] (rev 01)
lspci -v (written by hand so I'm just putting in the important bits)
Broadcom BCM4312
Kernel Driver in use: wl
Kernel modules: wl, ssb
Atheros AR8132 / L1c Gigabit Etheret Adapter (rev c0)
Kernel modules: atl1c
Last edited by medianmajik (2011-01-23 19:35:02)

You can name the interfaces whatever you like:
https://wiki.archlinux.org/index.php/Co … es_varying
Last edited by schuay (2010-11-11 06:52:10)

Networkmanager and eth0

Similar Messages

Maybe you are looking for