WS-SW-FIREWALL-MIB :: wsSwFirewallDosStatsTable

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › WS-SW-FIREWALL-MIB › wsSwFirewallDosStatsTable

wsSwFirewallDosStatsTable

Module: WS-SW-FIREWALL-MIB

OID (symbolic): WS-SW-FIREWALL-MIB::wsSwFirewallDosStatsTable

OID (numeric): 1.3.6.1.4.1.388.14.2.16.1.1.1.3

Node type: OBJECT-TYPE

Access: not-accessible

Description: This Table shows the stats related to each kind of DoS attacks supported by the switch, few of them can be configured in the wsSwFirewallDoSChecksTable.

1. Smurf DoS Attack: ICMP echo packets destined to a broadcast IP address. Attackers use this type of packet to bring down a target host by spoofing its IP address and flooding it with ICMP echo responses.

2. Twinge DoS Attack: False ICMP control packets going through the wireless switch.

3. Invalid IP Protocol DoS Attack: Packets with invalid IP protocol value in the IP header. Some applications can use non-assigned IP protocol numbers to send malicious packets.

4. Ascend DoS Attack: Protocol is UDP, destination port is 9, UDP packet is mal-formed.

5. Chargen DoS Attack: The attack consists of a flood of UDP datagram's sent to the subnet broadcast address with the destination port set to 19 (chargen) and a spoofed source IP address.

6. Fraggle DoS Attack: When a perpetrator sends a large number of UDP echo (ping) traffic at IP broadcast addresses, all of it having a fake source address

7. ICMP Router Solicit DoS Attack: If the packet received from the network is an ICMP packet type 10 then it's an ICMP router discovery messages called Router Solicitations.

8. ICMP Router Advertisement DoS Attack: Route advertisements are used by neighboring hosts to configure their route table. These messages can be used by attackers to configure routes on hosts to re-direct traffic.

9. IP Source Route Option DoS Attack: Packets with source route option set in IP header.

10. Snork DoS Attack: UDP or TCP packets with destination port set to 135 and source port set to either 7,19 or 135. This can cause packets to be exchanged indefinitely between the two hosts causing them to slow down.

11. FTP Bounce DoS Attack: FTP packets if the IP address encoded in the PORT command does not match the IP address of the FTP client.

12. TCP Intercept DoS Attack: TCP SYN flood attacks.

13. Bcast/Mcast Icmp DoS: By default we consider bcast-mcast ICMP as DoS and drop the packets.

14. TCP Header Fragmented DoS Attack: TCP packets if the TCP header spans across IP fragments.

15. WINNUKE DoS Attack: Out of band data to the target computer on TCP port 139 (NetBIOS),

16. LAND DoS Attack: The attack involves sending a spoofed TCP SYN packet (connection initiation) with the target host's IP address and an open port as both source and destination.

17. UDP Short Header DoS Attack: A UDP header is a minimum of 8-bytes long. However, some systems (like BeOS) will crash when they receive UDP traffic with header length less than eight

18. TCP Bad Sequence DoS Attack: These types of attack are usually man-in-the-middle attacks where the attacker injects a packet with invalid sequence number to terminate the connection.

19. TCP FIN Scan DoS Attack: It attempts to close a non-existent connection on the server. Either way, it is an error, but systems sometimes give back different error results depending upon whether the desired service is available or not. As a result, the attacker doesn't trigger the normal logging of the system. However, this type of scan does result in weird network traffic.

20. TCP NULL Scan DoS Attack: A TCP frame with a sequence number of zero and all control bits are set to zero.

21. TCP XMAS Scan DoS Attack: A TCP frame with a sequence number of zero and the FIN, URG, and PUSH bits are all set.

22. TCP Post SYN Scan DoS Attack: This attack is caused when an attacker tries to send TCP packet with SYN flag set after the connection is established.

23. IP TTL zero DoS Attack: An IP packet set with ttl zero leading the packet to be dropped before reaching it's destination.

24. IP Spoof DoS Attack: IP datagram is treated as spoofed if the source IP address does not belong to the subnet from where the packet arrived. Most of the DoS attacks use spoofed IP addresses so that it is difficult to trace the origin of the attack.

OID Breakdown

Upper-level ancestors (9 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.388symbolSYMBOL-DSSS-ENTERPRISE-PRIVATE-MIB
1.3.6.1.4.1.388.14wsWS-SMI
1.3.6.1.4.1.388.14.2wsSwWS-SMI
Numeric OIDNameModule
1.3.6.1.4.1.388.14.2.16wsSwFirewallWS-SW-FIREWALL-MIB
1.3.6.1.4.1.388.14.2.16.1wsSwFirewallMibModuleWS-SW-FIREWALL-MIB
1.3.6.1.4.1.388.14.2.16.1.1wsSwFirewallMIBWS-SW-FIREWALL-MIB
1.3.6.1.4.1.388.14.2.16.1.1.1wsSwFirewallDosWS-SW-FIREWALL-MIB
1.3.6.1.4.1.388.14.2.16.1.1.1.3wsSwFirewallDosStatsTableWS-SW-FIREWALL-MIB