Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: Problem behind my DMZ
Date: Fri, 9 Jan 2004 10:57:18 +0000	[thread overview]
Message-ID: <200401091057.19282.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <Law9-F354jsKlkag7KO00012b91@hotmail.com>

On Friday 09 January 2004 9:54 am, Martin Leduc wrote:

> > Is your IP forwarding turned on?
>
> Yes, it is.  Can you explain to me why /32 against /28 netmask, or tell me
> where I can get the documentation?

The /32 and /28 netmasks operate quite simply:

On one interface you use a /32 netmask, which means there is only one 
accessible IP on that network - that of the router leading to the Internet.

On the other interface you use a /28 netmask, which means there are 16 IP 
addresses (14 usable) accessible on that network.

Linux uses its routing table entries from most specific to least specific, so 
if a packet for the one IP address on the /32 network needs to be routed, it 
will go in the direction of the Internet.   If a packet for any other address 
in your public IP range needs to be routed, it won't match the /32 but it 
will match the /28, so it will go to the internal network.

The fact that the two network ranges overlap does not matter (despite what you 
may read in introductory networking books - this is beyond introductory 
networking).

Regards,

Antony.

-- 
Documentation is like sex.
When it's good, it's very very good.
When it's bad, it's still better than nothing.

                                                     Please reply to the list;
                                                           please don't CC me.



  reply	other threads:[~2004-01-09 10:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-09  9:54 Problem behind my DMZ Martin Leduc
2004-01-09 10:57 ` Antony Stone [this message]
2004-01-09 15:26 ` Ramin Dousti
  -- strict thread matches above, loose matches on Subject: below --
2004-01-12 12:08 Martin Leduc
2004-01-10 13:26 Martin Leduc
2004-01-10 12:55 Martin Leduc
2004-01-09  2:19 Martin Leduc
2004-01-09  4:14 ` Ramin Dousti
2004-01-08 17:46 Martin Leduc
2004-01-08 17:53 ` Antony Stone
2004-01-08 17:12 Martin Leduc
2004-01-08 17:22 ` Antony Stone
2004-01-08 15:53 Martin Leduc
2004-01-08 16:16 ` Antony Stone
2004-01-08 18:10   ` Ramin Dousti
2004-01-08 17:17     ` Antony Stone
2004-01-08 19:18       ` Ramin Dousti
2004-01-08  0:19 Martin Leduc
2004-01-08  2:27 ` Chris Brenton
2004-01-08 16:31   ` Michael Gale

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=200401091057.19282.Antony@Soft-Solutions.co.uk \
    --to=antony@soft-solutions.co.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox