[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] Mintnet bug

To: MiNT List <mint@fishpool.com>
Subject: Re: [MiNT] Mintnet bug
From: Michael Schwingen <rincewind@discworld.dascon.de>
Date: Tue, 29 Jun 1999 01:44:29 +0200
In-reply-to: <Pine.LNX.3.96.990628150730.25546C-100000@hal.fishpool.fi>; from Martin-Eric Racine on Mon, Jun 28, 1999 at 03:10:11PM +0300
References: <Pine.LNX.3.96.990628145838.25546B-100000@hal.fishpool.fi> <Pine.LNX.3.96.990628150730.25546C-100000@hal.fishpool.fi>
Sender: owner-mint@fishpool.com

On Mon, Jun 28, 1999 at 03:10:11PM +0300, Martin-Eric Racine wrote:
> PS:  he adds that it is quoted from linux 2.2.x net/ipv4/icmp.c
>      as detailed by Alan Cox.

Yes, I remember seeing such messages since upgrading my linux kernel - it
looked like MintNet replied to a broadcast with some kind of error packet
which it should not, but I can't recall the exact message.

cu
Michael
-- 
Michael Schwingen, Ahornstrasse 36, 52074 Aachen

Follow-Ups:
- Re: [MiNT] Mintnet bug
  - From: Martin-Eric Racine <q-funk@pp.fishpool.com>

References:
- [MiNT] Mintnet bug
  - From: Martin-Eric Racine <q-funk@pp.fishpool.com>
- Re: [MiNT] Mintnet bug
  - From: Martin-Eric Racine <q-funk@pp.fishpool.com>

Prev by Date: Re: [MiNT] libs...
Next by Date: RE: [MiNT] a clean "shutdown" command?
Previous by thread: Re: [MiNT] Mintnet bug
Next by thread: Re: [MiNT] Mintnet bug
Index(es):
- Date
- Thread