All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Steffen Heil" <lists@steffen-heil.de>
To: 'KOVACS Krisztian' <hidden@balabit.hu>
Cc: netfilter@lists.netfilter.org
Subject: RE: Daisy Chaining two computers?
Date: Mon, 20 Mar 2006 18:31:09 +0100	[thread overview]
Message-ID: <006901c64c44$13d8a4d0$0b4613ac@shs1> (raw)
In-Reply-To: <200603201452.43715@nienna>

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

Hi

>   If you don't have a shortage of (internal) IP addresses, 
> then use software bridging on the linux box. It's very easy 
> to set up and completely transparent.

You don't need more IPs that would be Nat.
Since both systems shall act, as if they were directly connected to the
network, you want a switch / bridge.

I would recommend using a hardware switch, as is gives you more ports at
very low prices nowadays and you can reboot the linux system independent of
your windows box.
If there is a reason that you cannot use a real hardware switch, you can use
a linux software bridge. It will basicly be identical to a hardware switch,
but switch ports are more limited and the linux box must be running all the
time. Even reboots will (shortly) interrupt the network connection of you
other box.

However, if you don't plan to use the linux box as hardware firewall in
front of windows, then there is no benefit and I would definitely pefer a
real hardware switch.

And be warned, that when running as a bridge, the mac of you windows station
will still be seen at the network (remeber the linux bridge acts as a real
hardware switch).

Regards,
  Steffen

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3055 bytes --]

      reply	other threads:[~2006-03-20 17:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-19 21:56 Daisy Chaining two computers? Vann H. Walke
2006-03-20 13:52 ` KOVACS Krisztian
2006-03-20 17:31   ` Steffen Heil [this message]

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='006901c64c44$13d8a4d0$0b4613ac@shs1' \
    --to=lists@steffen-heil.de \
    --cc=hidden@balabit.hu \
    --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.