Etienne: Your response makes sense. In my case, if I enter the script manually, the message goes away. That's why your response makes sense. Since the process works, I am going to leave it to that. Thanks. Kirti -----Original Message----- From: Etienne Pretorius [mailto:etiennep at kingsley.co.za] Sent: Thursday, June 29, 2006 2:35 AM To: Kirti S. Bajwa; bridge at lists.osdl.org Subject: Re: [Bridge] Error in Bridge Settings!! 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 at lists.osdl.org https://lists.osdl.org/mailman/listinfo/bridge -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osdl.org/pipermail/bridge/attachments/20060629/0b0005c0/attachment-0001.htm
