On Mon, Aug 20, 2007 at 09:13:09PM -0400, George wrote:
This is not rocket science but I could not find info on these ports,
need to look further.
For Info about ports, you might consult
http://www.seifried.org/security/ports/
Stefan
--
Das Tieferlegen der Festplattenköpfe erhöht keineswegs
On Sun, Aug 12, 2007 at 01:16:57PM -0700, Wade Richards wrote:
2) If you really don't like the log messages, then reconfigure your firewall
to not
log dropped packets.
Actually, it might be best to just drop (and not log) packets to these ports
which are flowding your messages' log and log
Wade Richards wrote:
Hi George,
You've made a few missteps here.
First, you have assumed that vanguard.com is the reason for the
activity on your firewall. If you look at the IP address for vanguard, you'll
see that it has nothing to do with the IP addresses that are hitting your
firewall.
In browsing vanguard.com I find it slow, also they cause unexpected
logging in my /var/log/messages file. To kill these I updated itpables
to open said ports.
#!/bin/sh
# /opt/sbin/ziptables.vanguard input
#
iptables -I INPUT -j ACCEPT -s 167.206.251.0/24 -p udp \
-m multiport --ports
Hi George,
On Sun, Aug 12, 2007 at 12:58:59PM -0400, George wrote:
In browsing vanguard.com I find it slow, also they cause unexpected
logging in my /var/log/messages file. To kill these I updated itpables
to open said ports.
#!/bin/sh
# /opt/sbin/ziptables.vanguard input
#
iptables
On Sunday 12 August 2007 13:16, Wade Richards wrote:
Opening up ports
to stop log file messages is kind of like removing your armour because
you don't like the loud ping sound of bullets bouncing off it.
Well said. I really couldn't have said it better myself.
The only other thing I could add to
6 matches
Mail list logo
