AmigaOS 4's Roadshow stack comes with IPFilter as firewall, but there's no GUI to configure it. See SYS:Documentation/IP-Filter/ for the documentation.
If your Quake server suddenly doesn't start any more, then there's probably some other problem than the firewall. The server should start even if incoming traffic from outside is blocked.
Maybe not, but if you didn't know it existed it's very unlikely you've enabled it. It's not on by default.
I would check that you haven't changed the port number of the quake server in the quake config file. (client and server settings need to match).
Then check that your ips really are what you think they are, DHCP often gives predictable ips then some friend comes round with a iPhone logs into your wifi and takes out a log lease on one of your ips....
Hmmm just wondered why it worked earlier with OS4.1up6? I'm sure I haven't done that earlier.
Edit surely it should work, I start Quake and create Network game. It uses port 2600 (haven't change it). Trying to join game, I type IP, so it tries to connect specifig IP and port? No need to routing.
maybe nobody is playing? have you tried to have a similar setup connected to your quake server? if yes, sure it isn't that system with non opened ports?
Sam460ex 2GB 120Gb SSD&1Tb HD7750 Envy24HT A-Eon Drv 2.10+Warp3D New Uboot Apollo v4 Standalone
I don't know for Quake but I use AmiVNC regularly and I can connect on the Sam460 from the PC and yes I have OS4FE installed. Maybe you can try to boot the FE CD and set your network from there and test or you can install on a different partition and test from there. You need to have some skills doing this. Don't mess with your system.
is it win7-8-10 computer you have? didn't the remove ipx/tcp? so you have to ad them your self to those windows.. if you had win xp you would now.. im not entirely sure about this, just sharing my thoughts
Sam460ex 2GB 120Gb SSD&1Tb HD7750 Envy24HT A-Eon Drv 2.10+Warp3D New Uboot Apollo v4 Standalone
My suggestion would be to start with simple tests and work out from there...
First, in the Amiga shell type:
ShowNetStatus
Look to see what your "local host address" is. That's the IP address of that machine on your LAN.
Then go to another machine, open a shell and see if you can ping your Amiga by typing:
ping <<YOUR IP ADDRESS FROM ABOVE>>
That will at least tell you if you are in contact with your Amiga.
If that ping test fails then you know you aren't even getting to your Amiga, let alone a specific port. That could be a problem with your router/switch, the foreign machine or your Amiga (but your Amiga is online, right?).
The more machines you can run ping tests to/from the more it will tell you about where the problem lies. If none of the machines on your LAN can reach the Amiga, the problem would seem to be there. If none can reach your peecee, there's the problem, etc.
Once you are certain you have good connections to/from all the machines you're using, then worry about ports, servers, etc.