i see port 1 is open, should it be open ? what is it used for ?
http://www.grc.com/port_1.htm
..and port 0 <nil> ??

And whatabout if a cs server is behind the fw and i open port 27015 they still cant connect..

It's abnormal to have either of those ports open (esp port 0). What were the results of the GRC scan? They tend to make a big deal if ports aren't "stealthed", but there's actually a really big difference between a port being "closed" and a port being "open". If those two ports are indeed "open", use netstat -pantu or lsof -i to list what applications are listening on those ports.

As far as the cs server, do the same netstat command to see if the cs server daemon is even up and listening for connections, then try temporarily shutting of your firewall and see if you can connect.

well.. regarding the grc scan, port 0 & 1 seems to be sometimes closed and sometimes stealth, the netstat and lsof command didnt show anything either..

and the counter-strike issue, with fw unplugged players can connect as usual, with fw ( port forward any.ip:27015 --> server.ip:27015 ) they cant connect

well.. regarding the grc scan, port 0 & 1 seems to be sometimes closed and sometimes stealth
it's OK, as long as they're closed or "stealthed" and not open. Having ports listed as being "open" indicates that there is a service/daemon listening and accepting connections on that port (which for ports 0 & 1 would be abnormal). A "closed" port indicates that no services are accepting connections on that port and that the system sent back a reply of some sort (ie. icmp port unreachable message). A "stealthed" port simply means that no response at all was received. The difference between closed and stealthed is relatively minor and I tend to think is over-exagerated (often for monetary gain).

the netstat and lsof command didnt show anything either
Good sign as well.

and the counter-strike issue, with fw unplugged players can connect as usual, with fw ( port forward any.ip:27015 --> server.ip:27015 ) they cant connect
Could you post your firewall script, so we can see that rule in context with the rest of the firewall. Make sure to remove/obscure any public IPs. Also, could you describe your setup a little more clearly. How many computers, how are they connected, which one is the firewall, which one has the cs server?

www --> FW ( smoothwall ) --> switch --> servers

the CS server i just a windoze pc ( soon dedicated gnu/linux )

..by the way.. regarding port 0 .. could see in my phpinfo file today " Hostname:Port fuelman.domain.org:0 "

I believe the CS server uses port 27015 udp. By default Smoothwall will only forward the tcp port, not the udp one, so make sure that you specifically select the udp checkbox.

You might also want to consider making the CS server part of a DMZ (orange zone) if you are going to open up public access to it.

I'n not that familiar with PHP, but I'd guess the port 0 setting you are seeing in the phpinfo page is refering to the Apache API that PHP interacts with, not the actual port that Apache listens on (port 80).

gaaahhh.. udp * chewing on keyboard *

im familiar with PHP coding, but had nu clue about how the api works / port 0, thanks for info