All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Henrik Ramberg" <newspost@start.no>
To: lartc@vger.kernel.org
Subject: [LARTC] Software bridge problem
Date: Sat, 17 May 2003 12:11:19 +0000	[thread overview]
Message-ID: <marc-lartc-105317352327422@msgid-missing> (raw)

[-- Attachment #1: Type: text/plain, Size: 1250 bytes --]

Dear list.

I have a problem I hope someone can help me with. I am currently developing a "transparent" software bridge that 
connects a local area network to the Internet. eth0 is connected to the "Internet" and eth1 is connected 
to the LAN. The program is working just fine and packets are routed perfectly through the box. However my 
problems goes as follows: eht0 has got an IP stack so that the box can surf around on Internet (this is an 
necessity), while eth1 is protocol less. I want the clients in the LAN to reach the IP stack on eth0 
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 
seem to work. I have used pktdump to verify that packets are recieved on eth1 and sent out on eth0. 
The problem is that the IP stack will not accept the packets it 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. 

All replies will be deeply appreciated.

Regards,
Henrik Ramberg

[-- Attachment #2: Type: text/html, Size: 1806 bytes --]

             reply	other threads:[~2003-05-17 12:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-17 12:11 Henrik Ramberg [this message]
2003-05-17 15:33 ` [LARTC] Software bridge problem Stef Coene
2003-05-17 18:10 ` Markske@Linux-network.be

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=marc-lartc-105317352327422@msgid-missing \
    --to=newspost@start.no \
    --cc=lartc@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.