linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bert hubert <ahu@ds9a.nl>
To: Marc Haber <mh+linux-kernel@zugschlus.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.21 sending out "need to fragment" on wrong interface
Date: Wed, 12 Nov 2003 15:26:19 +0100	[thread overview]
Message-ID: <20031112142619.GA21966@outpost.ds9a.nl> (raw)
In-Reply-To: <20031103072917.GA18992@torres.ka0.zugschlus.de>

On Mon, Nov 03, 2003 at 08:29:17AM +0100, Marc Haber wrote:
> Hi,
> 
> I am using a Linux machine with freeS/WAN for my connectivity. The
> default route points to the IPSEC link. It has recently begun to send
> out "need to fragment" packets on the wrong interface.

Linux-kernel is mostly about unpatched kernels, have you taken this up with
the freeswan people?



-- 
http://www.PowerDNS.com      Open source, database driven DNS Software 
http://lartc.org           Linux Advanced Routing & Traffic Control HOWTO

      reply	other threads:[~2003-11-12 14:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-03  7:29 2.4.21 sending out "need to fragment" on wrong interface Marc Haber
2003-11-12 14:26 ` bert hubert [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=20031112142619.GA21966@outpost.ds9a.nl \
    --to=ahu@ds9a.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mh+linux-kernel@zugschlus.de \
    /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;
as well as URLs for NNTP newsgroup(s).