> > 17:17:17.297430 arp reply raven.umnh.utah.edu is-at 0:a0:c9:df:6c:83
> > 17:17:17.297522 arp reply raven.umnh.utah.edu is-at 0:a0:c9:df:6d:e8
> >
> > when the machine is pinged - even though eth1, the 0:a0:c9:df:6d:e8
> > interface has only an EtherTalk address. 'ifconfig eth1 -arp' kills the
> > spurrious replies, but also kills netatalk. Is this a kernel problem, a
> > configuration problem, or a problem with my head?
>
> Since the interface is down for IP it definitely looks like a bug to me
If it answers, it means that the interface is not down.
Apparently, he configured IP on eth1 earlier and did not disable it then.
"ifconfig eth1 0.0.0.0" does not disable IP for bootp folks:
it still receives broadcasts and packets destined to addresses
of another interfaces.
IP is disabled either by explicit address deletion ("ip addr del")
or by dirty trick with ifconfig sort of:
ifconfig eth1:tmp 10.0.0.1
ifconfig eth1:tmp down
Alexey
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/