operstate reports unknown on working network interfaces

jecaro · 2012-07-20 09:15:01

Hi,

I've just discovered Archlinux. So I've installed it on my computers and I'm very happy with them as they feel responsive again

But I'm running into a little weird problem. My network interfaces eth0 and lo report unknown through the files /sys/class/net/{eth0,lo}/operstate. They should report up as they are both working properly. But in xmobar, the network command outputs nothing in this case. Restarting the network does not bring them to up either. The only way I've found to switch eth0 to up is to unplug the ethernet cable, ping the network, then operstate reports down, plug it back and ping again then operstate report sup (and xmobar shows up its stats ).

Has anyone else been through this issue ?

Cheers,

Jean-Charles

Trilby · 2012-07-20 13:30:59

Do you get any errors or warnings during boot? There have been a couple of recent threads (which I haven't followed) about a warning of eth0 not recognized during boot and subsequent network problems. If you get a similar warning this might be related.

Alternately, is your rc.conf set up properly? Can you post the contents here (in [ code ] ... [ /code ] tags).

edit: my "lo" also reports "unknown" I suspect that may be normal. But if your network daemon is running properly "eth0" should report "up".

Last edited by Trilby (2012-07-20 13:32:43)

jecaro · 2012-07-20 19:35:22

No, I've got no problem with eth0 either in dmesg or in daemon.log. I dont understand why lo should report unknown as it's actually up. Anyway 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, using "" makes hwclock fall back
#   to the value in /var/lib/hwclock/adjfile
# TIMEZONE: timezones are found in /usr/share/zoneinfo
#   Note: if unset, the value in /etc/localtime is used unchanged
# 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="en_US.UTF-8"
DAEMON_LOCALE="no"
HARDWARECLOCK="UTC"
TIMEZONE="Europe/Paris"
KEYMAP="fr"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
#   Replace every !module by an entry as on the following line in a file in
#   /etc/modprobe.d:
#     blacklist module
#   See "man modprobe.conf" for details.
#
MODULES=()

# 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="djezon"

# Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
#
# Wired network setup
#   - interface: name of device (required)
#   - address: IP address (leave blank for DHCP)
#   - netmask: subnet mask (ignored for DHCP) (optional, defaults to 255.255.255.0)
#   - broadcast: broadcast address (ignored for DHCP) (optional)
#   - gateway: default route (ignored for DHCP)
# 
# Static IP example
# interface=eth0
# address=192.168.0.2
# netmask=255.255.255.0
# broadcast=192.168.0.255
# gateway=192.168.0.1
#
# DHCP example
# interface=eth0
# address=
# netmask=
# gateway=

interface=eth0
address=
netmask=
broadcast=
gateway=

# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"

# Enable these netcfg profiles at boot-up. These are useful if you happen to
# need more advanced network features than the simple network service
# supports, such as 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 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=(preload hwclock syslog-ng network acpid dbus @alsa @sshd @crond @psd)

alphaniner · 2012-07-20 20:13:39

My ../lo/operstate reads unknown as well, but operstate of my four nics is correct. I'm still running 3.4.4 though.

BTW, thanks for bringing this file to my attention. I can use it in my script in place of the pipe-kludge I'm currently using.

Last edited by alphaniner (2012-07-20 20:15:49)

Trilby · 2012-07-20 20:24:35

Thanks jecaro, your rc.conf looks in order. Unfortunately, I don't know what the next step would be in your troubleshooting. The issues I was curious about are ruled out.

Arch Linux

#1 2012-07-20 09:15:01

operstate reports unknown on working network interfaces

#2 2012-07-20 13:30:59

Re: operstate reports unknown on working network interfaces

#3 2012-07-20 19:35:22

Re: operstate reports unknown on working network interfaces

#4 2012-07-20 20:13:39

Re: operstate reports unknown on working network interfaces

#5 2012-07-20 20:24:35

Re: operstate reports unknown on working network interfaces

Board footer