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

Re: [MiNT] Mintnet bug

To: MiNT mailing list <mint@fishpool.com>
Subject: Re: [MiNT] Mintnet bug
From: Michael Schwingen <rincewind@discworld.dascon.de>
Date: Tue, 13 Jul 1999 20:56:46 +0200
In-reply-to: <19990705030937.E1270@zowee.rz.uni-sb.de>; from Guido Flohr on Mon, Jul 05, 1999 at 03:09:37AM +0200
References: <Pine.LNX.3.96.990629082657.29255B-100000@hal.fishpool.fi> <m110iuM-0000rGC@kermit.dialup.becom.net> <19990705030937.E1270@zowee.rz.uni-sb.de>
Sender: owner-mint@fishpool.com

On Mon, Jul 05, 1999 at 03:09:37AM +0200, Guido Flohr wrote:
> 
> Fine, but what about the bug that was reported? Could you track that down?
> I think that has top priority because we cannot afford to have a bad
> reputation for MiNT's behavior in a network.

OK, for completeness once again to the list (Thorsten already has this):

.1 is my PC, running windows during this test
.2 is the Linux machine
.5 is the Milan

20:52:03.002057 192.168.11.1.138 > 192.168.11.255.138: udp 177
20:52:03.002057 192.168.11.5 > 192.168.11.1: icmp: 192.168.11.255 udp port 138 unreachable

and Linux reports
"192.168.11.5 sent an invalid ICMP error to a broadcast".

(in this environment, I get about one of these messages per minute on the
Linux console, scrolling away all useful ISDNlog messages).

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

References:
- Re: [MiNT] Mintnet bug
  - From: tlang@dialup.becom.net (Torsten Lang)
- Re: [MiNT] Mintnet bug
  - From: "Guido Flohr" <gufl0000@stud.uni-sb.de>

Prev by Date: Re: [MiNT] mintbin
Next by Date: [MiNT] Security
Previous by thread: Re: [MiNT] Mintnet bug
Next by thread: [MiNT] MiNTLib 0.52 corrupted!!
Index(es):
- Date
- Thread