All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ray Leach <raymondl@knowledgefactory.co.za>
To: Netfilter Mailing List <netfilter@lists.netfilter.org>
Subject: Re: iptables masquerade cache  problems
Date: Mon, 29 Sep 2003 13:19:26 +0200	[thread overview]
Message-ID: <1064834366.16245.24.camel@raylinux.internal> (raw)
In-Reply-To: <200309291304.46583.woksy@ether.net1.nerim.net>

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

On Mon, 2003-09-29 at 13:04, Mickael DILY wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi, i have already had this problem with windows clients. It seems it's not a 
> bug from your linux box, but only from the windows client, whose still have 
> your old ip in cache. For my part, i don't know how to work around for this 
> bug
> 
You need to use ipconfig on the windows clients to flush the dns and
routing cache. See the docs on ipconfig /? on winblows.

> Le Lundi 29 Septembre 2003 10:23, lu a écrit :
>  Hi,
>  I have two lines that were masqueraded, one ADSL and another is ISDN for
>  backup. When the line ADSL is broken  I switch the line to ISDN. The problem
>  is: when I use ping to test (ping -t from windows client), after the line
>  was switched to ISDN, the source address was still that of ADSL  instead of
>  ISDN. But, when I stopped the ping from client for a while, all things went
>  well. It seems a problem of cache. What is the work-around for it? At a
>  moment I just down the ADSL interface.  You can do this test with two lan
>  interfaces.
>  The Configuration is:
>  	iptables -t nat -A POSTROUTING -o hsb0 -j MASQUERADE    # for ADSL
>  	iptables -t nat -A POSTROUTING -o ippp0 -j MASQUERADE    # for ISDN
> 
>  	default gw dev was hsb0  (ADSL)
>  	when ADSL was down then :
>  	route del default dev hsb0
>  	route add default dev ippp0
> 
> 
>  Best regards,
>  Jianliang Lu
> 
>  TieSse s.p.a      Ivrea (to) Italy
>  j.lu@tiesse.com
>  luj@libero.it
>  http://www.tiesse.com
> 
> - -- 
> - - M. DILY, administrateur réseau, geek :-)
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.7 (GNU/Linux)
> 
> iD8DBQE/eBHIzEzekoYhlpsRAnbvAJwMYms5Vg+d0gVfoPH3rJ/jV7s1LgCfTyKN
> SJ8P+jawRbS97afL3VxnNKg=
> =ZeBt
> -----END PGP SIGNATURE-----
-- 
--
Raymond Leach <raymondl@knowledgefactory.co.za>
Network Support Specialist
http://www.knowledgefactory.co.za
"lynx -source http://www.rchq.co.za/raymondl.asc | gpg --import"
Key fingerprint = 7209 A695 9EE0 E971 A9AD  00EE 8757 EE47 F06F FB28
--

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2003-09-29 11:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-29  8:23 iptables masquerade cache problems lu
2003-09-29 11:04 ` Mickael DILY
2003-09-29 11:19   ` Ray Leach [this message]
2003-09-29 13:17     ` Mickael DILY
2003-09-29 13:55       ` Ray Leach

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=1064834366.16245.24.camel@raylinux.internal \
    --to=raymondl@knowledgefactory.co.za \
    --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.