The problem is that if I try to open a website hosted on an IP address
of dimenoc.com (example http://thai-cuisine.pai-nai.com) I get
something what looks like a port scan from 32930 and up. And as result
the website doesn't open, I belief that the problem is not only with
my Linux box, all I'm also sure that some other Linux computers can
visit my website…as I can see in my stats.

I use Fedora Core 3, Kernel 2.6.10.770, Firestarter 1.0.1 (as Firewall)

It gets really weird if I say that I have no problems with my Windows
computer which uses the same network to get to the internet, it not
helps if I swap network IP address from Windows comp to Linux comp and
visa versa. And I can say on the Windows computer the ports higher
then 32930 are closed (I have it closed with software and even if I
close it with my hardware Firewall)

Here some lines from my Firewall log….

Time:Mar 19 12:33:25 Direction: Inbound In:eth0 Out: Port:32944 Source:72.29.66.135 Destination:192.168.0.8 Length:44 TOS:0x00 Protocol:TCP Service:Unknown
Time:Mar 19 12:33:40 Direction: Inbound In:eth0 Out: Port:32945 Source:72.29.66.135 Destination:192.168.0.8 Length:44 TOS:0x00 Protocol:TCP Service:Unknown
Time:Mar 19 12:33:42 Direction: Inbound In:eth0 Out: Port:32945 Source:72.29.66.135 Destination:192.168.0.8 Length:44 TOS:0x00 Protocol:TCP Service:Unknown
Time:Mar 19 12:33:42 Direction: Inbound In:eth0 Out: Port:32944 Source:72.29.66.135 Destination:192.168.0.8 Length:44 TOS:0x00 Protocol:TCP Service:Unknown
Time:Mar 19 12:33:50 Direction: Inbound In:eth0 Out: Port:32944 Source:72.29.66.135 Destination:192.168.0.8 Length:44 TOS:0x00 Protocol:TCP Service:Unknown
Time:Mar 19 12:33:57 Direction: Inbound In:eth0 Out: Port:32945 Source:72.29.66.135 Destination:192.168.0.8 Length:44 TOS:0x00 Protocol:TCP Service:Unknown
Time:Mar 19 12:34:02 Direction: Inbound In:eth0 Out: Port:32944 Source:72.29.66.135 Destination:192.168.0.8 Length:44 TOS:0x00 Protocol:TCP Service:Unknown
Time:Mar 19 12:34:17 Direction: Inbound In:eth0 Out: Port:32945 Source:72.29.66.135 Destination:192.168.0.8 Length:44 TOS:0x00 Protocol:TCP Service:Unknown
Time:Mar 19 12:34:18 Direction: Inbound In:eth0 Out: Port:32944 Source:72.29.66.135 Destination:192.168.0.8 Length:44 TOS:0x00 Protocol:TCP Service:Unknown
Time:Mar 19 12:34:25 Direction: Inbound In:eth0 Out: Port:32945 Source:72.29.66.135 Destination:192.168.0.8 Length:44 TOS:0x00 Protocol:TCP Service:Unknown
Time:Mar 19 12:34:42 Direction: Inbound In:eth0 Out: Port:32944 Source:72.29.66.135 Destination:192.168.0.8 Length:44 TOS:0x00 Protocol:TCP Service:Unknown
Time:Mar 19 12:34:57 Direction: Inbound In:eth0 Out: Port:32945 Source:72.29.66.135 Destination:192.168.0.8 Length:44 TOS:0x00 Protocol:TCP Service:Unknown................---/ /------------

Sorry I not post all lines because it is just going up 1 port for
hours if I let it go…..

Since these two ports (32944 and 32945) are common to RPC based services and to Windows Messaging Service, our trouble may be due to a firewall setting that is trying to prevent exploitation. Please view the following URL:

http://www.securityreference.com/com...000/32945.html

The problem is fixed....

All the glory go's to Firestarter (http://www.fs-security.com) version 1.0.3. fixed, as expected, all the problems.

So I can stay with probably the easiest to use Firewall manager for Linux....