Thanks for your response, Ewan!
>> Is there any other software firewall solution suitable for public HTTP
>> server with quite high traffic and users served? I tried few recommended
>> like Outpost firewall, they usually die on my servers.
> if we put the logging issue aside for the moment (see above) what
> functionality don't you have from the RRAS firewall?
1. I have 1 NIC with 8 IP addresses assigned for different services. 2 of
them supposed to be used for 2 websites. Now, even if I allow all traffic
to TCP port 80 in inbound filters, I'm not receiving packets to port 80
until I enable Web Server NAT on "Services and Ports" tab of the connection
properties in "IP Routing -> NAT/Basic firewall". But this mapping works for
only one IP address on the interface. In other words, there is no way to
allow service on the sme port on 2 out of 8 IP addresses if those addresses
sit on one NIC.
I guess, I'm missing something.
2. I have 3 servers that communicate trough public interfaces. To simplify
things, before locking down interserver communication, I allowed all traffic
between my 3 servers and ran into strange situation. All traffic from server
A to server B is being blocked (any TCP connection attempt stucks at
SYN_SENT, pings don't go). B -> A and all other traffic goes through fine. I
tried all magic passes, including allowing all traffic (sure, I got my
Iass.exe DOSed in 90 seconds), and reinstalling RRAS on the servers A and
B - still, I can't help it. And having no statistics on dropped packets
drives me nuts - I don't have enough information on what's going on.
3. Sometimes investigation of dropped packets statistics is very helpful.
I'm not a guru of all the services I'm using, I may not allow something only
because I don't know or forget about that particular port. It also helps to
identify port scanning, probes, DOS and other hack attempts.
Best regards,
Dmitry
|