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

Re: [MiNT] Mintnet bug

To: Torsten Lang <tlang@dialup.becom.net>
Subject: Re: [MiNT] Mintnet bug
From: Michael Schwingen <rincewind@discworld.dascon.de>
Date: Sun, 4 Jul 1999 23:06:36 +0200
Cc: Martin-Eric Racine <q-funk@pp.fishpool.com>, mint@fishpool.com
In-reply-to: <m110iuM-0000rGC@kermit.dialup.becom.net>; from Torsten Lang on Sun, Jul 04, 1999 at 11:49:58AM +0200
References: <Pine.LNX.3.96.990629082657.29255B-100000@hal.fishpool.fi> <m110iuM-0000rGC@kermit.dialup.becom.net>
Sender: owner-mint@fishpool.com

On Sun, Jul 04, 1999 at 11:49:58AM +0200, Torsten Lang wrote:
> 
> The behaviour was changed in a way that also icmp echo requests to a broadcast
> address (like a ping to 192.168.1.255) are answered by the network kernal.
> This is how Linux behaves and was needed for some Macintosh nfs client (and
> perhaps other sw) that tries to find all systems in the local network by
> sending such broadcasts.

That may be the problem - IIRC, mint also sends some ICMP error message in
reply to such broadcasts (port unreachable?), which gets flagged by Linux as
an error. I will check as soon as I have network in my Milan working again
(no free slots currently).

Any Linux machine with a current kernel (2.2.* at least, I think this came
earlier) and samba running on it should trigger this message.

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

References:
- Re: [MiNT] Mintnet bug
  - From: tlang@dialup.becom.net (Torsten Lang)

Prev by Date: Re: [MiNT] on a 4 Mb machine?
Next by Date: RE: [MiNT] MiNT mouse device inverted Y value
Previous by thread: Re: [MiNT] Mintnet bug
Next by thread: Re: [MiNT] Mintnet bug
Index(es):
- Date
- Thread