Error map
MAC flapping / broadcast storm (spanning tree loop) Networking: %SW_MATM-4-MACFLAP_NOTIF: Host is flapping between ports / broadcast storm
Networking · layer 2, Network
Centre: this error. First ring: errors it is linked with (7). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.
Directly related (7)
Networking: Duplex mismatch — late collisions, runts and CRC errors on the switch port
One side runs full duplex and the other half duplex, so the link works but is slow and drops packets.
Networking: %CDP-4-NATIVE_VLAN_MISMATCH / device on the wrong VLAN can't reach the gateway
A port or trunk carries a different VLAN than expected, so hosts silently land on the wrong network.
Networking: %PM-4-ERR_DISABLE: psecure-violation error detected on Gi0/5, putting Gi0/5 in err-disable state
The switch shut the port down because a security or protection feature detected a violation.
Networking: Port forwarding configured but the port stays closed — carrier-grade NAT (CGNAT) or double NAT
Your router forwards the port correctly, but another NAT in front of it (your ISP or a second router) blocks inbound connections.
Networking: `arp -n` shows (incomplete) / Destination Host Unreachable — no ARP reply from the next hop
The machine asked "who has this IP?" and nobody on the local network answered.
Networking: Thousands of sockets in CLOSE_WAIT — the application is not closing its side of the connection
The other end closed the connection, but your program never called close(), so the socket stays open.
Networking: connect: Cannot assign requested address — ephemeral port range exhausted by TIME_WAIT connections
The machine ran out of local ports for new outgoing connections to the same destination.
Two steps away (18)
Networking: Network cable unplugged / `ip link` shows NO-CARRIER state DOWN / Ethernet: Network cable unplugged
The network card sees no electrical link, so nothing above it (IP, DNS, browser) can work.
Networking: Interface down — SFP transceiver Loss of Signal / no receive light
A fibre or SFP link is down because the transceiver receives no light.
Networking: netstat -s: segments retransmitted / Wireshark: TCP Retransmission, TCP Dup ACK — packet loss on the path
Packets are being lost, so TCP resends them and throughput collapses.
Networking: %OSPF-5-ADJCHG: Nbr 10.0.0.2 from EXSTART to DOWN — OSPF neighbor stuck in EXSTART/EXCHANGE (MTU mismatch)
Two OSPF routers see each other but never finish exchanging databases, cycling between EXSTART and DOWN.
Networking: dhclient: DHCPDISCOVER on eth0 ... No DHCPOFFERS received. No working leases in persistent database - sleeping.
The client broadcast a DHCP request and no server answered.
Networking: wlan0: WPA: 4-way handshake failed - pre-shared key may be incorrect / WRONG_KEY
The Wi-Fi association started but key negotiation failed, almost always a wrong password.
ssh: connect to host x port 22: Connection timed out
SSH packets get no reply — a firewall/security group drops them, the server is off, or the IP is wrong.
Networking: Wi-Fi keeps disconnecting / signal -80 dBm / wlan0: deauthenticating by local choice (reason=3)
The wireless link is too weak or too noisy to hold, so the client drops and rejoins repeatedly.
Networking: Server reachable from the internet but not from inside the LAN via its public IP — NAT loopback / hairpin NAT not working
Devices on your own network can't use the router's public address to reach a server that is also on that network.
Networking: No Wi-Fi networks found — the Wi-Fi adapter is missing, disabled or its driver failed
The operating system doesn't see a working wireless adapter, so no networks can be listed.
Networking: Windows has detected an IP address conflict / Duplicate address detected by 00:aa:bb:cc:dd:ee
Two devices on the same network are using the same IP address, so traffic reaches the wrong one or neither.
Networking: ping — Destination Host Unreachable / Destination net unreachable (ICMP type 3)
A router (or your own PC) tells you it has no way to deliver the packet to that address.
Go: accept tcp [::]:8080: accept4: too many open files / open x: too many open files
The process reached its file-descriptor limit — usually leaked connections, files or response bodies.
Networking: SSH/HTTPS connects but hangs on large data — path MTU discovery black hole
Small packets pass but full-size ones vanish, so logins work and then transfers or page loads stall.
Networking: nc -vz hangs then times out — firewall silently DROPs packets (REJECT would answer "Connection refused")
A connection attempt gets no answer at all, which points to a firewall dropping the packets rather than a closed port.
Networking: NAT gateway ErrorPortAllocation / SNAT port exhaustion — intermittent outbound connection timeouts
Many instances share few public IPs, and the NAT gateway runs out of source ports for outbound connections.
Networking: TCP: request_sock_TCP: Possible SYN flooding on port 80. Sending cookies. Check SNMP counters.
The server's pending-connection queue filled, so the kernel switched to SYN cookies to survive.
Networking: Wireshark: TCP ZeroWindow, TCP Window Full — the receiver can't keep up and tells the sender to stop
The receiving application isn't reading data fast enough, so its TCP buffer filled and the sender must pause.
Map another error
Popular: 500403400ORA-009331064Critical errorFileNotFoundException assemblyTypeError