[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: arp on same wire
- To: misc_(_at_)_openbsd_(_dot_)_org
- Subject: Re: arp on same wire
- From: Mike <mredan_(_at_)_jeke_(_dot_)_fdns_(_dot_)_net>
- Date: Fri, 14 May 2004 14:50:05 -0400 (EDT)
maybe you could enter static arp entries for _everything_ on your internal
network? (huge PITA)
do you really need two interfaces? maybe add an IP alias to one of your
NICs?
heh...and if those messages are the only thing really bugging you...turn
off logging :P
Mike
--
When it rains, it pours. And right now, it is hailing baseball-sized
chunks of misery on the Blue Jays.
On Fri, 14 May 2004, J.D. Bronson wrote:
> At 01:15 PM 05/14/2004, you wrote:
> > > Is this going to cause ARP messages (like in freebsd) and if so, is
> > there a
> > > way to shut them up?
> >
> >P A R E N T A L A D V I S O R Y
> >
> >Using IP on broadcast type networks causes ARP messages.
> >
> >P A R E N T A L A D V I S O R Y
> >
> >Seriously now, do you mean to ask if using both NICs on the same
> >ethernet segment will cause ARP problems, or something like that?
> >
> >Please elaborate.
>
> I mean those dreaded arp messages from one NIC to the OTHER.
> (not normal ones!!!)
>
> "expected a reply from NIC 1 but came in on NIC 2...."
>
>
>
>
>
>
>
> --
> J.D. Bronson
> Aurora Health Care // Information Services // Milwaukee, WI USA
> Office: 414.978.8282 // Email: jd_(_at_)_aurora_(_dot_)_org // Pager: 414.314.8282
Visit your host, monkey.org