From: Etienne Pretorius <etiennep@kingsley.co.za>
To: "Kirti S. Bajwa" <kbajwa@tibonline.net>, bridge@lists.osdl.org
Subject: Re: [Bridge] Error in Bridge Settings!!
Date: Thu, 29 Jun 2006 08:35:03 +0200 [thread overview]
Message-ID: <44A37497.4010108@kingsley.co.za> (raw)
In-Reply-To: <00ae01c69abf$5f9ec6f0$20ed150c@SunShine>
[-- Attachment #1: Type: text/plain, Size: 4007 bytes --]
Let me first explain that I have the same problem in my Ethernet bridge
setup.
What I have determined, that there is a loop in my network but STP is
preventing a packet broacast storm. I have switches instead of hubs but
my primary bridge is broadcasting packets somehow, because when I unplug
the primary's Ethernet from our internal network then those messages
stop appearing. I am in the process of re-setting up that bridge so that
*hopefully* I wont be seeing this message in future. I wander if it
might be the HUBs you using.... they might be broadcasting any packet to
all ports and so your bridge will receive its own packets back to it?
Like I said - I have the same problem, but the setup still works and I
am trying to remove loops in my network to see if that *really* is the
cause to the error message.
Kind Regards
Etienne
Kirti S. Bajwa wrote:
>
> Hello Bridge List:
>
>
>
> Please help a newbie!
>
>
>
> I have setup two freshly installed CentOS 4.3 servers and have setup
> redundant BRIDGE. My plan is to have the 'redundant' BRIDGE working
> and then I will add 'Shorewall' Firewall to these two servers. On both
> machines, I have included the following lines in '/etc/rc.local' so
> that the BRIDGE will be ACTIVE after BOOT:
>
>
>
> /etc/rc.local
>
> =========
>
> ** # ****Setup**** ****BRIDGE**** (****First**** ****Bridge****)**
>
> ** brctl addbr tibbr1**
>
> ** brctl addif tibbr1 eth0**
>
> ** brctl addif tibbr1 eth1**
>
> ** ifconfig tibbr1 up**
>
> ** ifconfig tibbr1 12.21.237.2 netmask 255.255.255.0**
>
> ** brctl setageing tibbr1 300**
>
> ** brctl stp tibbr1 on**
>
> ** brctl setbridgeprio tibbr1 100**
>
> ** brctl setpathcost tibbr1 eth0 100**
>
> ** brctl setpathcost tibbr1 eth1 100**
>
> *reboot *
>
>
>
> =========
>
> Similar lines are included in the second server except the bridge name
> is 'tibbr2', IP addr is 12.21.237.4 & bridge & path costs are 200.
>
> MAC addresses on each server are as follows:
>
>
>
> Server 1:
>
> eth0: 00:80:ad:16:f3:25
>
> eth1: 00:30:1b:38:c6:41
>
>
>
> Server 2:
>
> eth0: 00:80:ad:16:e6:43
>
> eth1: 00:30:1b:38:c4:c9
>
>
>
> PROBLEM:
>
> -------------
>
> When I boot one of the servers, I get the following errors:
>
>
>
> eth1: received packet with own address as source address
>
> eth0: received packet with own address as source address
>
>
>
> What are these errors & why they are appearing?
>
>
>
> If I no-op (#) the following lines, the error disappear:
>
>
>
> **# ifconfig tibbr1 up**
>
> **# ifconfig tibbr1 12.21.237.2 netmask 255.255.255.0**
>
>
>
>
>
> FYI, my current hardware setup is as follows:
>
>
>
> T1 Line
>
> |
>
> Cisco 26XX Router
>
> |
>
> HUB -----à HUB (Current Network)
>
> |
>
> ----------------------------
>
> | eth0
> |
>
> fw1 fw2
>
> | eth1 |
>
> -----------------------------
>
> |
>
> HUB
>
> |
>
> (Future: additional Servers)
>
>
>
> Please HELP! How can I fix the settings so the above listed PROBLEM is
> resolved!!
>
>
>
> Kirti
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Bridge mailing list
> Bridge@lists.osdl.org
> https://lists.osdl.org/mailman/listinfo/bridge
>
[-- Attachment #2: Type: text/html, Size: 20514 bytes --]
next prev parent reply other threads:[~2006-06-29 6:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-28 14:30 [Bridge] Error in Bridge Settings!! Kirti S. Bajwa
2006-06-29 6:35 ` Etienne Pretorius [this message]
2006-06-29 14:34 ` Kirti S. Bajwa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44A37497.4010108@kingsley.co.za \
--to=etiennep@kingsley.co.za \
--cc=bridge@lists.osdl.org \
--cc=kbajwa@tibonline.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox