All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexandru Dragoi <alex@zoomnet.ro>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Delay when changing DNAT rules
Date: Sun, 19 Mar 2006 15:29:02 +0000	[thread overview]
Message-ID: <441D78BE.5040303@zoomnet.ro> (raw)
In-Reply-To: <20060319151301.3kb89cl94wc4gso4@www.simplelists.com>

Andrew Beverley wrote:

>Whenever I add or remove a DNAT rule such as:
>
>iptables -A PREROUTING -p tcp --dport 80 -j DNAT --to-destination 192.168.0.1
>
>there is sometimes a delay before the correct nat'ing is done. Can anyone tell
>me why this is? Is it something to do with caching of routing tables? If so, is
>there a way to clear them to ensure that the rule takes effect immediately?
>
>I am building a simple captive portal solution for my network. By default people
>are directed to the local web server as per the rule above, and once logged in
>they are allowed access to the web. When logging in the user is directed to
>their choice of webpage, but this is often not displayed and instead the
>connection is routed once again to the local web server as above. Even deleting
>the DNAT rule altogether seems to sometimes take a while to update.
>
>Andy
>_______________________________________________
>LARTC mailing list
>LARTC@mailman.ds9a.nl
>http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
>  
>
You can try to disable KeepAlive from your apache server.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      reply	other threads:[~2006-03-19 15:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-19 15:13 [LARTC] Delay when changing DNAT rules Andrew Beverley
2006-03-19 15:29 ` Alexandru Dragoi [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=441D78BE.5040303@zoomnet.ro \
    --to=alex@zoomnet.ro \
    --cc=lartc@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 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.