On Wednesday 14 December 2005 11:19, Jim Ford wrote:
>
> Hmm - it doesn't work for me!
>
> I put:
> 0.0.0.0/0udp1025:1032
> in /etc/shorewall/blacklist
> and:
> BLACKLIST_LOGLEVEL=""
> in /etc/shorewall/shorewall.conf
>
> and am still getting udp packets targeting 1025 to 1032.
Di
To cut down on the amount of clutter appearing in my firewall log, I silently
blacklist certain traffic.
In shorewall.conf, I set BLACKLIST_LOGLEVEL="". Then
in /etc/shorewall/blacklist, I have the equivalent of:
0.0.0.0/0 tcp 57
0.0.0.0/0 tcp
On Sunday 11 December 2005 06:56, Jim Ford wrote:
> I'm seeing lots of probes, mainly UDP, targetting ports 1025 to 1032 on my
> firewall. I've had a look at grc.com (very informative) and it seems that
> these ports are targetted by trojans. Is what I'm seeing an attempt to see
> if a trojan has o
I'm seeing lots of probes, mainly UDP, targetting ports 1025 to 1032 on my
firewall.
I've had a look at grc.com (very informative) and it seems that these ports are
targetted by trojans. Is what I'm seeing an attempt to see if a trojan has
opened
any of these ports?
Wish I could understand what
