Bridging problems on IP address conflict

Eduardo Meyer dudu.meyer at gmail.com
Wed Mar 7 15:46:52 UTC 2007


On 1/25/07, Peter Jeremy <peterjeremy at optushome.com.au> wrote:
> On Thu, 2007-Jan-25 12:01:46 -0200, Eduardo Meyer wrote:
> >bridge0: flags=8043<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> >       ether ac:de:48:df:0d:8c
> >       priority 32768 hellotime 2 fwddelay 15 maxage 20
> >       member: fxp0 flags=3<LEARNING,DISCOVER>
> >       member: em0 flags=3<LEARNING,DISCOVER>
> >
> >bridge1: flags=8043<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> >       ether ac:de:48:fe:cd:41
> >       priority 32768 hellotime 2 fwddelay 15 maxage 20
> >       member: xl1 flags=3<LEARNING,DISCOVER>
> >       member: xl0 flags=3<LEARNING,DISCOVER>
> >
> >And my system constantly reports:
> >
> >arp: 00:13:20:1c:33:22 is using my IP address XX.YY.ZZ.KK!
> >
> >several (thoundsands of) times. In fact this ARP is my own fxp0
> >interface, and this is the only interface that has this IP. What
> >should I do? Ass IP on the bridge0 interface instead of the fxp0
> >bridge member? Or anything else?
>
> You don't say what version of FreeBSD you are running (there were some
> bridge(4) fixes between 6.1 and 6.2) or what ifconfig shows for the
> bridge members.
>
> This may be indicative of a loop in your switch network - is there any
> way that packets leaving fxp0 can re-appear on em0, xl0 or xl1?
>
> Based on a previous thread, you probably should put the IP address
> on the bridge device, though that should not be related to your problem.
>
> --
> Peter Jeremy
>
>

5.5-STABLE system. The topology:

- em0 and xl0 crossover (straight from router) to freebsd bridge
- fxp0 and xl1 on a common switch (maybe causing a loop?)

Added the IP on the bridge device and the loop is gone.

10x

-- 
===========
Eduardo Meyer
pessoal: dudu.meyer at gmail.com
profissional: ddm.farmaciap at saude.gov.br


More information about the freebsd-stable mailing list