Continues ping, what would be the effect in the network.

I have a software that ping's a device (biometric device with IP address) continuously.

What would be the effect in the network if I do continues ping?

Below is the code?
Private Sub MonitorDeviceConnectivity(ByVal State As Object)
            Dim pingDevice As New System.Net.NetworkInformation.Ping
            Do While True
                Dim Reply As System.Net.NetworkInformation.PingReply = pingDevice.Send(_IPAddress)
                If Not Reply.Status = Net.NetworkInformation.IPStatus.Success Then
                    RaiseEvent EventNetworkDeviceStatus(_IPAddress, _TerminalName, _TerminalCode, False)
                    RaiseEvent EventNetworkDeviceStatus(_IPAddress, _TerminalName, _TerminalCode, True)
                End If
        End Sub

Open in new window

LVL 15
Who is Participating?
Only1RBConnect With a Mentor Commented:
I think that is because you are sending pings really close together.  If you changed the delay for a minute or longer that might stop.  Why not create a service on the machine you are pinging that responds to your request and sends back a response. no response machine is down.  Then you shouldn't have to worry about DoS.
It shouldn't be bad. It's not much different than a hearbeat monitor.  You might have the thread sleep a little longer.
JackOfPHAuthor Commented:
Isn't it DoS (Denial Of Service)? In a network where I am running the software, some of the POS is not properly running, but when I close the software that ping the device.... the POS is running properly.
The new generation of project management tools

With’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

JackOfPHAuthor Commented:
hmmm... I will try to do that, but no creating a service won't work...
JackOfPHAuthor Commented:
It does not work...

Any idea if there is a problem when you do continuous pings?  
They call it the Ping of Death type of DoS.  Here is a website that talks about problems with it and below that is a copy and paste of the section I'm talking about.

Ping of Death
A Ping of Death attack uses Internet Control Message Protocol (ICMP) ping messages. Ping is used to see if a host is active on a network. It also is a valuable tool for troubleshooting and diagnosing problems on a network. As pic-4 illustrates, a normal ping has two messages:

¦Echo request
¦Echo reply


Pinging with 32 bytes of data:

Reply from bytes=32 time=1ms TTL=150
Reply from bytes=32 time=1ms TTL=150
Reply from bytes=32 time=1ms TTL=150
Reply from bytes=32 time=1ms TTL=150

Ping statistics for
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms

With a Ping of Death attack, an echo packet is sent that is larger than the maximum allowed size of 65,536 bytes. The packet is broken down into smaller segments, but when it is reassembled, it is discovered to be too large for the receiving buffer. Subsequently, systems that are unable to handle such abnormalities either crash or reboot.

You can perform a Ping of Death from within Linux by typing ping –f –s 65537. Note the use of the –f switch. This switch causes the packets to be sent as quickly as possible. Often the cause of a DoS attack is not just the size or amount of traffic, but the rapid rate at which packets are being sent to a target.

You can also use the following software tools to perform a Ping of Death attack:

Today, most hosts are hardened against Ping of Death attacks and even attempt to prevent you from sending one, although you might still find some network appliances that are vulnerable.
JackOfPHAuthor Commented:

For a reply...
All Courses

From novice to tech pro — start learning today.