All of lore.kernel.org
 help / color / mirror / Atom feed
From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Firewall+NAT: only succeeds for SOME external sites??
Date: Fri, 21 Sep 2001 09:51:41 +0000	[thread overview]
Message-ID: <marc-lartc-100106589726950@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100102468021752@msgid-missing>

On Fri, Sep 21, 2001 at 11:43:10AM +0200, sebastien Robart wrote:
> i use pppoe and nat too. I have problems with 2 sites (63.238.77.237 and 
> 195.101.41.250) only when i change the mru option (rp-pppoe), not the 
> mtu. And problem are only for box behind the gateway, directly from the 
> gateway i have no problem.
> seem a masq + mru bug. (don't ask me what is mru, i didn't have found 
> something on it)

When using pppoe with masquerading, or any networking at all, use MSS
Clamping, either in the pppoe-daemon or in iptables itself. This solves a
lot or problems with path MTU discovery.

Regards,

bert

-- 
http://www.PowerDNS.com          Versatile DNS Software & Services
Trilab                                 The Technology People
Netherlabs BV / Rent-a-Nerd.nl           - Nerd Available -
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/

  parent reply	other threads:[~2001-09-21  9:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-20 22:24 [LARTC] Firewall+NAT: only succeeds for SOME external sites?? Chris Rankin
2001-09-21  6:17 ` Stef Coene
2001-09-21  7:19 ` Chris Rankin
2001-09-21  9:43 ` sebastien Robart
2001-09-21  9:51 ` bert hubert [this message]
2001-09-23 22:35 ` sebastien Robart

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=marc-lartc-100106589726950@msgid-missing \
    --to=ahu@ds9a.nl \
    --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.