On Tuesday 24 June 2003 02:02 am, Jose Luis Abuelo Sebio wrote:
[...]
> First I assign an IP address to each NIC
> BridgeA
> eth0 10.0.1.1
> eth1 192.168.1.1
> eth2 192.168.2.1
>
> and I set them up with the command Ifconfig
> Ifconfig eth0 up
> Ifconfig eth1 up
> Ifconfig eth2 up
> (To do this I had to install netutils.lrp because ifup
> didn�t seem to work)
>
> so I did the same in bridgeB
>
> eth0 10.0.1.2
> eth1 192.168.1.2
> eth2 192.168.2.2
> and I set them up with ifconfig again.
[...]
> It works if I do the bridge with the phisical
> interfaces eth0,eth1,eth2
> Bridge Orense
> eth0, eht1 eth2

Well, I haven't setup a bridge in some time, so correct me
if I'm off-base here. Last I checked, bridging is NOT a 
function of routing and does NOT use ip addresses/routes/etc..
You simply bring up the interfaces as 'bridge-interfaces' w/o
further configuration and the whole thing works similar to a
switch. From what you have posted, I'm very surprised anything
works at all period as a bridge, but I'm assuming that much
may have changed in the last couple of years.......
-- 
~Lynn Avants
Linux Embedded Appliance Firewall Developer
http://leaf.sourceforge.net
http://guitarlynn.homelinux.org:81


-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html

Reply via email to