This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C11B51.6ED77740 Content-Type: text/plain; charset="iso-8859-1" Here is the original post... "Hopefully this is an easy question for someone out there. I am testing out some server monitoring software and would like to simulate a down system by disabling any ping responses coming from this server (running Solaris 6)." Thanks to everyone who responded. Several people suggested either pulling out the cable or running "ifconfig down". Unfortunately I wanted to leave the other network services intact while I was testing this out, so those options weren't viable. I tried setting ip_respond_to_echo_broadcast to 0, but this only disabled broadcast (255) packets. The server would still respond to a ping to it's ip address. The best solution was to temporarily add a route which will redirect all packets from the management host to the loopback... =========== create a route on the remote machine that drops traffic to your management server... eg: route add managementip 127.0.0.1 when your done... route delete managementip 127.0.0.1 =========== Thanks again for all the responses. Bruce Perttunen Unix Systems Administrator Blue Cross Blue Shield of Michigan ------_=_NextPart_001_01C11B51.6ED77740 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Diso-8859-1"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 5.5.2653.12"> <TITLE>SUMMARY: Disable ping</TITLE> </HEAD> <BODY> <P><FONT SIZE=3D2>Here is the original post...</FONT> </P> <BR> <P><FONT SIZE=3D2>"Hopefully this is an easy question for someone = out there. I am testing out some server monitoring software and = would like to simulate a down system by disabling any ping responses = coming from this server (running Solaris 6)."</FONT></P> <BR> <P><FONT SIZE=3D2>Thanks to everyone who responded. Several = people suggested either pulling out the cable or running "ifconfig = down". Unfortunately I wanted to leave the other network = services intact while I was testing this out, so those options weren't = viable.</FONT></P> <P><FONT SIZE=3D2>I tried setting ip_respond_to_echo_broadcast to 0, = but this only disabled broadcast (255) packets. The server would = still respond to a ping to it's ip address. </FONT></P> <P><FONT SIZE=3D2>The best solution was to temporarily add a route = which will redirect all packets from the management host to the = loopback...</FONT></P> <P><FONT SIZE=3D2>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</FONT> <BR><FONT SIZE=3D2>create a route on the remote machine that drops = traffic to your management server... eg:</FONT> <BR><FONT SIZE=3D2>route add managementip 127.0.0.1</FONT> <BR><FONT SIZE=3D2> </FONT> <BR><FONT SIZE=3D2>when your done...</FONT> <BR><FONT SIZE=3D2>route delete managementip 127.0.0.1</FONT> <BR><FONT SIZE=3D2>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</FONT> </P> <P><FONT SIZE=3D2>Thanks again for all the responses.</FONT> </P> <P><FONT SIZE=3D2>Bruce Perttunen</FONT> <BR><FONT SIZE=3D2>Unix Systems Administrator</FONT> <BR><FONT SIZE=3D2>Blue Cross Blue Shield of Michigan</FONT> </P> </BODY> </HTML> ------_=_NextPart_001_01C11B51.6ED77740--Received on Thu Aug 2 13:48:30 2001
This archive was generated by hypermail 2.1.8 : Wed Mar 23 2016 - 16:25:00 EDT