Linux Netfilter discussions
 help / color / mirror / Atom feed
From: whiplash <whiplash@bofhland.org>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Peter Boughton <boughtonp@gmail.com>, netfilter@vger.kernel.org
Subject: Re: simple connection bridging
Date: Mon, 14 Apr 2008 13:01:24 +0200	[thread overview]
Message-ID: <48033984.9060206@bofhland.org> (raw)
In-Reply-To: <alpine.LNX.1.10.0804141244260.9651@fbirervta.pbzchgretzou.qr>

Jan Engelhardt ha scritto:

>>> No need. If you add the interface address, rules for the subnet
>>> will automatically be added, in other words:
>>>
>>>  ip addr add 192.168.1.2/24 dev eth0
>>>
>>> will cause 192.168.1.0/24 to show up in `ip route` (preferred over `route`)
>>> with a 'proto kernel', which says the kernel created this one automatically.
>> Uhm, yes, this is correct.
>> But I was not talking about adding routing on linux box, but on *XP* boxes.
>>
> Right, I already wondered about the strange trailing argument.

Yes, "mask" keyword does not definitively apply to route in Linux. :)

> Then again, why not just use the default route [if it fits]?-
> still needs no extra routes :)

Because I didn't know if the mentioned linux box was the default gateway 
for the two XP boxes...:)

Regards.

  reply	other threads:[~2008-04-14 11:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-12 21:39 simple connection bridging Peter Boughton
2008-04-13  7:12 ` Jan Engelhardt
     [not found] ` <4801622E.1060407@bofhland.org>
2008-04-13 11:10   ` Peter Boughton
2008-04-13 19:02     ` Jan Engelhardt
2008-04-14  7:52       ` whiplash
2008-04-14 10:45         ` Jan Engelhardt
2008-04-14 11:01           ` whiplash [this message]
2008-04-14 19:10             ` Grant Taylor
2008-04-14 19:39             ` Peter Boughton
2008-04-14 20:01               ` Grant Taylor
2008-04-14 22:26                 ` Peter Boughton
2008-04-15  0:14                   ` Grant Taylor
2008-04-15 22:42                     ` Peter Boughton

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=48033984.9060206@bofhland.org \
    --to=whiplash@bofhland.org \
    --cc=boughtonp@gmail.com \
    --cc=jengelh@computergmbh.de \
    --cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox