Re: [Freemint-discuss] Weird problem with MiNTnet

[Miro K. <mir...@gm...>]

Just to post an update on this... it went away the same way it appeared --
without any plausible explanation. What I did was to reassemble the
SuperVidel, connect everything together and voila, now ping 127.0.0.1
worked and so did NetUSBee's networking. I had to reseat Svethlana's cable
and voila, it started to work as well (otherwise I was seeing a lot of
error reports from svethlana's driver).

How all of this is connected to pinging localhost, I do not know.

On Thu, 14 Aug 2025 at 00:19, Miro Kropáček <mir...@gm...> wrote:

> Typo: Dec 2024. Oh and I tried also older FreeMiNT versions (1.16, 1.17,
> 1.18...)
>
> On Thu, 14 Aug 2025 at 00:16, Miro Kropáček <mir...@gm...>
> wrote:
>
>> Speaking of weird problems... today I have encountered something equally
>> strange and without any clue what has caused it.
>>
>> Basically I tried to reinstall my system from scratch. So I download the
>> bootable snapshot, add ping and set up some basic static IP. Pinging my PC
>> doesn't work. Router ditto. Local IP ditto. 127.0.0.1 ditto. All I see is
>> "PING .... 56 data bytes" and that's it, no response. I can interrupt it
>> with CTRL+C any time.
>>
>> So I stared at it for a while and then I tried to boot the same CF card
>> from Hatari on my PC. Didn't bother with anything else than ping 127.0.0.1
>> and ... it worked. Swapped back to the Falcon ... didn't work.
>>
>> Reverted back to the snapshot, and just added 'ping' into /bin (even
>> deleted the two xif drivers in $SYSDIR). Same result: Hatari OK, real
>> machine not OK. Tried in both 030 and 060 mode.
>>
>> Booting with MP enabled, nothing out of ordinary spotted. Tried to copy a
>> huge ZIP file from Hatari to CF card and unzip it on Falcon (to make sure
>> that IDE reading is OK): all fine.
>>
>> Then I tried to download a snapshot from Dec 2014, which I vaguely
>> remember using: same result. Then I deleted basically everything but
>> mint.prg and inet4.xdd: same result.
>>
>> As a last resort, I tried to boot the same card and default snapshot on
>> another Falcon and ... ping worked! So that leaves me perplexed... I could
>> understand all sorts of reasons why the actual network interface doesn't
>> work. But pinging 127.0.0.1 ??? The Falcon with non-working ping is even
>> recapped, in perfect health otherwise.
>>
>> So I swapped the last thing -- the CF adapter which was holding the card
>> (from the working Falcon), and even removed SuperVidel in the process (not
>> active at that time, booting in 030 mode!) ... ping still stubbornly
>> refuses to work.
>>
>> As an act of desperation, I even cleaned NVRAM on the falcon, as the
>> working one has a dead NVRAM battery so it's booting into ST LOW. No help.
>>
>> I'm totally clueless. I guess I could try to remove the CT60e but
>> that's... that's just terrible. I guess I'll try to force myself into
>> debugging this further (i.e. to recompile 'ping' from Vincent's source
>> code) as it smells like a nice issue to look at but still, I cannot think
>> of any explanation other than "bad luck".
>>
>> On Sun, 18 May 2025 at 22:11, Jo Even Skarstein via Freemint-discuss <
>> fre...@li...> wrote:
>>
>>> Ok, haven't had much time to spend on real hardware the last month, but
>>> sat down Friday night
>>> and tried to figure out what the problem was. I suspected either a
>>> Linux/Windows update, or a
>>> router update. Most likely the latter, as the problem started at the
>>> exact same time on all my
>>> computers.
>>>
>>> Turns out that it's a routing issue with my router, and probably my
>>> MiNTnet configuration. When I
>>> access other devices on my LAN from MiNTnet, all LAN traffic goes via
>>> the router - which is set up
>>> as the default route. For some unknown to me reason (I know very little
>>> about network configuration)
>>> this suddenly caused all my non-MiNTnet machines to not be able to
>>> communicate with my MiNTnet
>>> machines. Looks like packets where received by MiNTnet, but the response
>>> never reached the other
>>> machine. Except if that machine runs MiNTnet as well.
>>>
>>> Adding a route specifically to my LAN solved the issue. However, the
>>> dhclient script does not do this
>>> so I can't use DHCP anymore. Or I probably could if I modified the
>>> dhclient script, but that involves
>>> another thing I don't know much and don't like - shell scripts.
>>>
>>> Jo Even
>>>
>>>
>>>
>>> On Thu, 17 Apr 2025 19:02:57 +0000, Jo Even Skarstein via
>>> Freemint-discuss <fre...@li...> wrote:
>>>
>>> >> I've ran into a weird problem with MiNTnet. Suddenly none of my
>>> Ataris running MiNTnet are available to other devices on my LAN, except the
>>> router. Networking between my Ataris works normally, and I can ping my
>>> other devices (PC's running Linux or Windows) from my Ataris but not vice
>>> versa. I can't access any servers on my PC's from my Ataris, but any
>>> external servers (ftp, http, mail...) works fine. This happened suddenly
>>> and at the same time for all my Ataris, so the problem is not caused by any
>>> changes on the Atari side.
>>> >>
>>> >> What's strange is that if I boot TOS and run UIPtool instead of
>>> MiNT/MiNTnet everything works fine. The Atari is assigned the same IP as
>>> under MiNTnet (using DHCP in both cases), but with UIPtool running I can
>>> access the Atari from any device on my LAN.
>>> >>
>>> >> Any idea on what's going on?
>>> >>
>>> >> Jo Even
>>> >>
>>> >>
>>> >> _______________________________________________
>>> >> Freemint-discuss mailing list
>>> >> Fre...@li...
>>> >> https://lists.sourceforge.net/lists/listinfo/freemint-discuss
>>>
>>>
>>> _______________________________________________
>>> Freemint-discuss mailing list
>>> Fre...@li...
>>> https://lists.sourceforge.net/lists/listinfo/freemint-discuss
>>>
>>
>>
>> --
>> http://mikro.atari.org
>>
>
>
> --
> http://mikro.atari.org
>


-- 
http://mikro.atari.org