arpalert: [./capture.c 232] pcap_open_live error: eth0: That device is not up

Bug #423883 reported by Fernando
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
arpalert (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: arpalert

I have this error in arpalert:
arpalert: [./capture.c 232] pcap_open_live error: eth0: That device is not up

Well, it seems that arpalert starts BEFORE the eth0 is completely up, so i decided to add the following in /etc/network/if-up.d:
-rw-r--r-- 1 root root 29 2009-09-03 15:08 resetear-arpalert

$cat resetear-arpalert
#! /bin/sh
/etc/init.d/arpalert restart
exit 0

And it works OK!
---------------------------------------------------------------------------------------------------
Platform Information:
----------------------------
lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
---------------------------------------------------------------------------------------------------
apt-cache policy arpalert
arpalert:
  Instalados: 2.0.11-3
  Candidato: 2.0.11-3
  Tabla de versión:
 *** 2.0.11-3 0
        500 http://ar.archive.ubuntu.com jaunty/universe Packages
        100 /var/lib/dpkg/status

Revision history for this message
Fernando (fernando-018) wrote :

I've also renamed the arpalert init script to: /etc/rc2.d/S99arpalert (S99)

But in /var/log/daemon.log i still have:
Sep 3 15:24:12 desktop arpalert: [./capture.c 232] pcap_open_live error: eth0: That device is not up
Sep 3 15:24:15 desktop NetworkManager: <info> (eth0): device state change: 1 -> 2
Sep 3 15:24:15 desktop NetworkManager: <info> (eth0): bringing up device.
Sep 3 15:24:15 desktop NetworkManager: <info> (eth0): preparing device.
Sep 3 15:24:15 desktop NetworkManager: <info> (eth0): deactivating device (reason: 2).
Sep 3 15:24:15 desktop NetworkManager: <info> (eth0): carrier now ON (device state 2)
Sep 3 15:24:15 desktop NetworkManager: <info> (eth0): device state change: 2 -> 3
Sep 3 15:24:15 desktop nm-system-settings: Added default wired connection 'Auto eth0' for /org/freedesktop/Hal/devices/net_00_16_ec_0c_d2_b1
Sep 3 15:24:15 desktop NetworkManager: <info> Activation (eth0) starting connection 'Auto eth0'
Sep 3 15:24:15 desktop NetworkManager: <info> (eth0): device state change: 3 -> 4
Sep 3 15:24:15 desktop NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Sep 3 15:24:15 desktop NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Sep 3 15:24:15 desktop NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Sep 3 15:24:15 desktop NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Sep 3 15:24:15 desktop NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Sep 3 15:24:15 desktop NetworkManager: <info> (eth0): device state change: 4 -> 5
Sep 3 15:24:15 desktop NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Sep 3 15:24:15 desktop NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Sep 3 15:24:15 desktop NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Sep 3 15:24:15 desktop NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Sep 3 15:24:15 desktop NetworkManager: <info> (eth0): device state change: 5 -> 7
Sep 3 15:24:15 desktop NetworkManager: <info> Activation (eth0) Beginning DHCP transaction.
Sep 3 15:24:15 desktop NetworkManager: <info> dhclient started with pid 3517
Sep 3 15:24:15 desktop NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Sep 3 15:24:15 desktop dhclient: Internet Systems Consortium DHCP Client V3.1.1
Sep 3 15:24:15 desktop dhclient: Copyright 2004-2008 Internet Systems Consortium.
Sep 3 15:24:15 desktop dhclient: All rights reserved.
Sep 3 15:24:15 desktop dhclient: For info, please visit http://www.isc.org/sw/dhcp/

Fernando (fernando-018)
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.