All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roman <maillists@gmx.ch>
To: netfilter@lists.netfilter.org
Subject: Firewall with only one eth0 device: possible?
Date: Tue, 31 May 2005 18:41:22 +0200	[thread overview]
Message-ID: <429C93B2.7040001@gmx.ch> (raw)

Hi,

I have an embedded system running uclinux with just one ethernet device 
and wonder whether or not I can build a firewall in combination with a 
switch (VLAN support, not WLAN).

How I thought it could work is the following:

Configure the eth0 device with an ip and network mask.
Configure the eth0:0 alias device with an ip and network mask different 
from eth0.
Use a switch with VLAN support.
Connect the eth0 linux device to port B of the switch; switch port A 
will then be one side of the firewall and port C the other side.
Configure the switch (VLAN) in a manner so all the incoming traffic on 
switch port A will be routed to port B and all the incoming traffic on 
port B will be routed to port C and back to port A.
Finally everything that enters port C will be routed to port B.


The question about all this is: Will the traffic be filtered between 
eth0 and eth0:0 as if there were two physical devices eth0 and eth1?

Thanks for any remarks on that.

roman


PS.: I know, this is an unusual way to build a firewall, but I simply 
can not change the hardware. For everyone who thinks, it is insecure 
because of none existing  physical separation: please forgive me.





             reply	other threads:[~2005-05-31 16:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-31 16:41 Roman [this message]
2005-05-31 17:53 ` Firewall with only one eth0 device: possible? Taylor, Grant
  -- strict thread matches above, loose matches on Subject: below --
2005-06-01 15:13 Roman
2005-06-01 15:28 ` Taylor, Grant

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=429C93B2.7040001@gmx.ch \
    --to=maillists@gmx.ch \
    --cc=netfilter@lists.netfilter.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.