From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: BUG in mtu-disc ;-)
Date: Fri, 23 Nov 2012 13:46:14 +0100 [thread overview]
Message-ID: <1353674774.14956.29.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <50AE7910.7020107@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2430 bytes --]
Merged.
On Thu, 2012-11-22 at 20:12 +0100, Stefan Schantl wrote:
> Hello Alexander,
>
> thank you for the bug reports. Those problems only occurs if the Path
> MTU Discovery feature never has been configured.
>
> I already had written and commited a patch for the issues, but that
> one hasn't work correctly.
>
> With my latest patch, the problems have been solved:
>
> http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=1647059d74d406c1b3a114b8e0578765223fd19f
>
> Best regards,
>
> Stefan
>
> > HI
> >
> > Another bug:
> >
> > when downloading a clientpackage, the line "mtu-disc" is in the
> > config file, which is not so good.
> >
> >
> >
> > Alexander Marx
> >
> >
> > Fachinformatiker Systemintegration
> >
> >
> >
> >
> > Am 21.11.2012 05:17, schrieb Alexander Marx:
> >
> > > Hi Stevee!
> > > with my latest tries to debug the ccd code, i FOUND A BUG!
> > >
> > > We phoned yesterday and erik told us that his openvpn server was
> > > not able to start anymore.
> > > The reason: mtu-disc entry in server.conf
> > >
> > > Please try the following.
> > >
> > > When creating / or even only editing a roadwarrior and saving, the
> > > serverconf is written. Unfortunately, within a client , there is
> > > no mtu-discovery, but "writeserverconf" does not take care of it.
> > > So there is a line written in server.conf which looks like:
> > > "mtu-disc" but without option (because value is not generated when
> > > editing/creating a client)
> > >
> > > While this option is now defective in the server.conf, the server
> > > does not start anymore.
> > >
> > > please have a look at server.conf (after the routing entries)
> > > after editing/creating a client and also at writeserverconf
> > > function.
> > >
> > >
> > > Alex
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > Development mailing list
> > > Development(a)lists.ipfire.org
> > > http://lists.ipfire.org/mailman/listinfo/development
> >
> >
> >
> > _______________________________________________
> > Development mailing list
> > Development(a)lists.ipfire.org
> > http://lists.ipfire.org/mailman/listinfo/development
>
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
parent reply other threads:[~2012-11-23 12:46 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <50AE7910.7020107@ipfire.org>]
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=1353674774.14956.29.camel@rice-oxley.tremer.info \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox