net-tools breaks network access

Mr. Pjer · 2011-06-11 13:22:50

This is all done on an HP Pavillion dv-6000

Today, I wanted to install Arch on this machine, however, I had trouble getting the installer to connect through eth0. Everything worked fine when I used wireless. Now, however, I can't seem to get networking working when the net-tools package is installed. Without it, eth0 works normally after obtaining an IP address with dhcpcd, however, as soon as I install net-tools and reboot, the same method does not work. Dhcp finishes fine, however, anything that I try to ping, except localhost, returns "Unknown host" for hostnames and network unreachable for IPs.

As far as I can tell, there is a conflict somewhere between net-tools and my network setup.

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="Europe/Zagreb"
KEYMAP="croat"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
VERBOSE="3"

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

# 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)

#   - gateway: default route (ignored for DHCP)
# 
# Static IP example
# interface=eth0
# address=192.168.0.2
# netmask=255.255.255.0
# gateway=192.168.0.1
#
# DHCP example
# interface=eth0
# address=
# netmask=
# gateway=

interface=eth0
address=
netmask=
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=(hwclock syslog-ng network netfs crond dbus

Am I missing something?

karol · 2011-06-11 13:42:10

Mr. Pjer wrote:

Am I missing something?

The closing ')' in the last line ;P

Can you post 'ifconfig -a' when you're using net-tools and things don't work?

falconindy · 2011-06-11 14:49:23

This doesn't really make sense. When 'interface' is defined, you're using the new iproute2 logic. Without address defined, dhcpcd takes over, with zero regard for iproute2 or net-tools being installed on the system. Sounds like something else is using net-tools and sabotaging your connection. Is there something in /etc/rc.local we should know about?

Mr. Pjer · 2011-06-12 13:09:57

karol wrote:

Mr. Pjer wrote:
Am I missing something?
Can you post 'ifconfig -a' when you're using net-tools and things don't work?

If I install net-tools, network works until I reboot.
This is ifconfig -a before a reboot:

eth0 Link encap:Ethernet HWaddr 00:16:36:A7:16:A7 
 inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
 inet6 addr: fe80::216:36ff:fea7:16a7/64 Scope:Link
 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
 RX packets:14931 errors:0 dropped:0 overruns:0 frame:0
 TX packets:10813 errors:0 dropped:0 overruns:0 carrier:0
 collisions:0 txqueuelen:1000 
 RX bytes:14968031 (14.2 Mb) TX bytes:1751802 (1.6 Mb)
 Interrupt:18 Memory:da000000-da020000

and this is after, when things stop working:

eth0 Link encap:Ethernet HWaddr 00:16:36:A7:16:A7 
 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
 RX packets:7 errors:0 dropped:0 overruns:0 frame:0
 TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
 collisions:0 txqueuelen:1000 
 RX bytes:4158 (4.0 Kb) TX bytes:3940 (3.8 Kb)
 Interrupt:18 Memory:da000000-da020000

falconindy wrote:

Sounds like something else is using net-tools and sabotaging your connection. Is there something in /etc/rc.local we should know about?

Here is the rc.local:

#!/bin/bash
#
# /etc/rc.local: Local multi-user startup script.
#

(nothing was added to it)

What I also noticed is that routes aren't properly created when dhcp finishes with net-tools installed.

Arch Linux

#1 2011-06-11 13:22:50

net-tools breaks network access

#2 2011-06-11 13:42:10

Re: net-tools breaks network access

#3 2011-06-11 14:49:23

Re: net-tools breaks network access

#4 2011-06-12 13:09:57

Re: net-tools breaks network access

Board footer