Originally posted by: Corey0808
Originally posted by: n0cmonkey
Originally posted by: Corey0808
If there is absolutely no response they also know a machine there.
Could you elaborate on this a little please? I'm interested.
The lack of ICMP host/network unreachables gives you away.
I indeed fund that file and here it is
# Disable response to broadcasts.
# You don't want yourself becoming a Smurf amplifier.
net.ipv4.icmp_echo_ignore_broadcasts = 1
# enable route verification on all interfaces
net.ipv4.conf.all.rp_filter = 1
# enable ipV6 forwarding
#net.ipv6.conf.all.forwarding = 1
what is a smurf amplifier?
That's what I figured. Thanks.
oldman420 ---
There is a couple ways you could go about making your machine not respond to a ping. I'm not that familiar with Suse 10 so I'm just shooting from the hip here. Try looking for a file called /etc/sysctl.conf. In that file there is a line that looks like the following:
net.ipv4.icmp_echo_ignore_broadcasts = 1
Make sure it is uncommented and set to 1. Making changes to this file will be saved upon reboot so it's the optimum place to make the change. There are also some other variables in that file that should be changed to. They are:
net.ipv4.conf.all.rp_filter = 1
net.ipv4.conf.default.rp_filter = 1
net.ipv4.tcp_syncookies = 1
net.ipv4.conf.all.accept_source_route = 0
net.ipv4.conf.default.accept_source_route = 0
I hope this helps!
::EDIT:: Just a quick note. Sysctl support has to be enabled in the kernel for this file to exist.