From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Markske@Linux-network.be" Date: Sat, 17 May 2003 18:10:11 +0000 Subject: Re: [LARTC] Software bridge problem MIME-Version: 1 Content-Type: multipart/mixed; boundary="----=_NextPart_000_00AD_01C31CB0.523DA7A0" Message-Id: List-Id: References: In-Reply-To: To: lartc@vger.kernel.org This is a multi-part message in MIME format. ------=_NextPart_000_00AD_01C31CB0.523DA7A0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I think you need to assing your ip on the bridge /sbin/ip addr add 10.10.10.2/24 brd + dev br0 /sbin/ip route add default via 10.10.10.1 Markske http://www.linux-network.be/knowledge/bridge.php ----- Original Message -----=20 From: Henrik Ramberg=20 To: lartc@mailman.ds9a.nl=20 Sent: Saturday, May 17, 2003 2:11 PM Subject: [LARTC] Software bridge problem Dear list. I have a problem I hope someone can help me with. I am currently = developing a "transparent" software bridge that=20 connects a local area network to the Internet. eth0 is connected to = the "Internet" and eth1 is connected=20 to the LAN. The program is working just fine and packets are routed = perfectly through the box. However my=20 problems goes as follows: eht0 has got an IP stack so that the box can = surf around on Internet (this is an=20 necessity), while eth1 is protocol less. I want the clients in the LAN = to reach the IP stack on eth0=20 via eth1 in order to recieve stats on whats been downloaded etc. In = this situation packets for eth0 would be recieved on eth1 and the go through my bridge and then sent out on = eth0 as every other packet. Then when eth0 has sent the packets it would recieve the newly sent packets in = normal manner. However this does not=20 seem to work. I have used pktdump to verify that packets are recieved = on eth1 and sent out on eth0.=20 The problem is that the IP stack will not accept the packets it sends = out itself and just drops them. WHY?=20 Is there a remedy to my problem?? I am currently running Linux = 2.2.22-compact kernel.=20 All replies will be deeply appreciated. Regards, Henrik Ramberg ------=_NextPart_000_00AD_01C31CB0.523DA7A0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I think you need to assing your ip on = the=20 bridge
/sbin/ip addr add 10.10.10.2/24 brd + = dev=20 br0
/sbin/ip route add default via=20 10.10.10.1
 
Markske
http://www.linu= x-network.be/knowledge/bridge.php
----- Original Message -----
From:=20 Henrik = Ramberg=20
Sent: Saturday, May 17, 2003 = 2:11=20 PM
Subject: [LARTC] Software = bridge=20 problem

Dear list.
 
I have a problem I hope someone can = help me with.=20 I am currently developing a "transparent" software bridge that =
connects a=20 local area network to the Internet. eth0 is connected to the = "Internet" and=20 eth1 is connected
to the LAN. The program is working just fine and = packets=20 are routed perfectly through the box. However my
problems goes as = follows:=20 eht0 has got an IP stack so that the box can surf around on Internet = (this is=20 an
necessity), while eth1 is protocol less. I want the clients in = the LAN=20 to reach the IP stack on eth0
via eth1 in order to recieve stats = on whats=20 been downloaded etc. In this situation packets for eth0 would
be = recieved=20 on eth1 and the go through my bridge and  then sent out on eth0 = as every=20 other packet. Then when
eth0 has sent the packets it would recieve = the=20 newly sent packets in normal manner. However this does not
seem to = work. I=20 have used pktdump to verify that packets are recieved on eth1 and sent = out on=20 eth0.
The problem is that the IP stack will not accept the packets = it=20 sends out itself and just drops them. WHY?
Is there a remedy to my = problem??  I am currently running Linux 2.2.22-compact kernel.=20
 
All replies will be deeply=20 appreciated.
 
Regards,
Henrik=20 Ramberg
------=_NextPart_000_00AD_01C31CB0.523DA7A0-- _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/