> On Thu, Feb 10, 2005 at 11:27:35AM +0100, Andre Oppermann wrote:
> > > On Wed, Feb 09, 2005 at 09:48:18PM +0100, Andre Oppermann wrote:
> > > > The problem is with locally generated packets which go the wrong way.
> > > > This gets nasty when the box has to generate some path MTU discovery
> > >
On Wed, Feb 23, 2005 at 09:38:03PM +0300, Maxim Konovalov scribed:
> >
> > Just a ping on this one - I've received several emails from
> > people off the list asking if I'd found a fix for the problem.
> > It seems like it would be grand if you could commit your fix
> > to 5-STABLE instead of waiti
On Tue, 22 Feb 2005, 10:59-0500, David G. Andersen wrote:
> On Wed, Feb 09, 2005 at 06:33:11PM +0100, Andre Oppermann scribed:
> > "David G. Andersen" wrote:
> > >
> > > The last messages I saw in the archives about kern/73129 indicated
> > > that it was going to be fixed "shortly"
> > >
> > > (73
On Wed, Feb 09, 2005 at 06:33:11PM +0100, Andre Oppermann scribed:
> "David G. Andersen" wrote:
> >
> > The last messages I saw in the archives about kern/73129 indicated
> > that it was going to be fixed "shortly"
> >
> > (73129 is the "IPFW misbehavior in RELENG_5 thread" -- it's no longer
> >
Gleb Smirnoff wrote:
>
> On Thu, Feb 10, 2005 at 11:27:35AM +0100, Andre Oppermann wrote:
> A> > On Wed, Feb 09, 2005 at 09:48:18PM +0100, Andre Oppermann wrote:
> A> > A> The problem is with locally generated packets which go the wrong way.
> A> > A> This gets nasty when the box has to generate s
On Thu, Feb 10, 2005 at 11:27:35AM +0100, Andre Oppermann wrote:
A> > On Wed, Feb 09, 2005 at 09:48:18PM +0100, Andre Oppermann wrote:
A> > A> The problem is with locally generated packets which go the wrong way.
A> > A> This gets nasty when the box has to generate some path MTU discovery
A> > A> I
Gleb Smirnoff wrote:
>
> On Wed, Feb 09, 2005 at 09:48:18PM +0100, Andre Oppermann wrote:
> A> The problem is with locally generated packets which go the wrong way.
> A> This gets nasty when the box has to generate some path MTU discovery
> A> ICMP message and such. What I implemented is the corr
On Wed, Feb 09, 2005 at 09:48:18PM +0100, Andre Oppermann wrote:
A> The problem is with locally generated packets which go the wrong way.
A> This gets nasty when the box has to generate some path MTU discovery
A> ICMP message and such. What I implemented is the correct thing to do
A> and prevents
"David G. Andersen" wrote:
>
> On Wed, Feb 09, 2005 at 01:58:28PM -0500, David G. Andersen scribed:
> > On Wed, Feb 09, 2005 at 06:33:11PM +0100, Andre Oppermann scribed:
> > > >
> > > > (Barring that, has anyone patched it in their own system, and if so,
> > > > would you mind sending me the patc
On Wed, Feb 09, 2005 at 01:58:28PM -0500, David G. Andersen scribed:
> On Wed, Feb 09, 2005 at 06:33:11PM +0100, Andre Oppermann scribed:
> > >
> > > (Barring that, has anyone patched it in their own system, and if so,
> > > would you mind sending me the patch? I dislike running custom kernel
> >
On Wed, Feb 09, 2005 at 06:33:11PM +0100, Andre Oppermann scribed:
> >
> > (Barring that, has anyone patched it in their own system, and if so,
> > would you mind sending me the patch? I dislike running custom kernel
> > code on these machines, but I'm happy to do so to get things working. :)
>
"David G. Andersen" wrote:
>
> The last messages I saw in the archives about kern/73129 indicated
> that it was going to be fixed "shortly"
>
> (73129 is the "IPFW misbehavior in RELENG_5 thread" -- it's no longer
> possible to use ipfw fwd to perform policy routing).
>
> This bug is on my criti
The last messages I saw in the archives about kern/73129 indicated
that it was going to be fixed "shortly"
(73129 is the "IPFW misbehavior in RELENG_5 thread" -- it's no longer
possible to use ipfw fwd to perform policy routing).
This bug is on my critical path for getting my network entirely swa
13 matches
Mail list logo
