All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Patrick McHardy <kaber@trash.net>
Cc: Harald Welte <laforge@netfilter.org>,
	Netfilter Development Mailinglist
	<netfilter-devel@lists.netfilter.org>
Subject: Re: MASQUERADE + DHCP problem
Date: Mon, 12 Sep 2005 09:34:35 +1000	[thread overview]
Message-ID: <1126481675.9832.3.camel@localhost.localdomain> (raw)
In-Reply-To: <43244826.5020405@trash.net>

On Sun, 2005-09-11 at 17:07 +0200, Patrick McHardy wrote:
> 2) Add a special hack to masquerade to handle DHCP while no
>    local address exists by looking at the port and src/dst
>    address. Incredibly ugly and wrong :)

If IP src is 0.0.0.0, let it through untouched.  Those packets are
presumably not supposed to be masqueraded, so it's the Right Think
AFAICT.

Will that fix DHCP?
Rusty.
-- 
A bad analogy is like a leaky screwdriver -- Richard Braakman

  reply	other threads:[~2005-09-11 23:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-11 15:07 MASQUERADE + DHCP problem Patrick McHardy
2005-09-11 23:34 ` Rusty Russell [this message]
2005-09-11 23:57   ` Patrick McHardy
2005-09-12  3:07     ` David S. Miller
2005-09-12  8:52       ` Patrick McHardy

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=1126481675.9832.3.camel@localhost.localdomain \
    --to=rusty@rustcorp.com.au \
    --cc=kaber@trash.net \
    --cc=laforge@netfilter.org \
    --cc=netfilter-devel@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.