Bug 337130 - arpwatch ignores second interface
Summary: arpwatch ignores second interface
Status: RESOLVED DUPLICATE of bug 149003
Alias: None
Product: openSUSE 10.3
Classification: openSUSE
Component: Network (show other bugs)
Version: Final
Hardware: x86 openSUSE 10.3
: P5 - None : Minor (vote)
Target Milestone: ---
Assignee: Roman Drahtmueller
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-26 16:24 UTC by Forgotten User PQKW3NFi6R
Modified: 2008-11-12 10:33 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Forgotten User PQKW3NFi6R 2007-10-26 16:24:43 UTC
arpwatch invoked as
/usr/sbin/arpwatch -N -i eth0 -i tr0
ignores interface eth0. It only watches tr0. If I exchange the interfaces in /etc/sysconfig/arpwatch so it reads ARPWATCH_INTERFACE="tr0 eth0" then the running daemon only watches eth0. Only the last "-i ifX" seems to survive. This worked ok in openSUSE 10.2 so I took the binary /usr/sbin/arpwatch from 10.2 but funny enough that didn't work either! Might be one of the dependant libraries? ldd shows linux-gate.so.1, libresolv.so.2, libpcap.so.0 and libc.so.6 and ld-linux.so.2 but I didn't try further. Instead as a workaround I modfied the start/stop script to invoke arpwatch for each interface configured with additional "-f arp.ifX.dat" flag which works fine. Part of /etc/init.d/arpwatch now reads
----8<----
if [ -n "$ARPWATCH_INTERFACE" ]; then
    for ifX in $ARPWATCH_INTERFACE; do
        $ARPWATCH $ARPWATCH_ARGS -f arp.$ifX.dat -i $ifX
        rc_status -v
    done
else
    startproc $ARPWATCH $ARPWATCH_ARGS
    rc_status -v
fi
----8<----
and "ps ax|grep arpwatch" shows it running twice:
/usr/sbin/arpwatch -N -f arp.eth0.dat -i eth0
/usr/sbin/arpwatch -N -f arp.tr0.dat -i tr0
Comment 1 Roman Drahtmueller 2008-11-12 10:33:03 UTC
Fixed for 11.1 and SLE11.
Thank you for the report!

*** This bug has been marked as a duplicate of bug 149003 ***