RU Contact us
NET / 01 of 09 · Networks

A network where the cause is found in minutes, not weeks

We design, rebuild and troubleshoot data center and office networks. We follow the whole packet path, from the access port to the application.

When people call us
  • 01An app is slow “sometimes” while ping looks perfect
  • 02The VPN stays up, but large files fail
  • 03Since a switch was replaced, the network blinks once a day
  • 04Nobody can say exactly how traffic flows between sites
+Networks: ink illustration
MTU / tunnel drops packets above 1438
STP / root bridge on an access switch
NET / 01Findings are illustrative
+
Day one

What we check first

  • Capture the real L2/L3 topology and compare it with the diagram
  • Check MTU and MSS on every tunnel and provider handoff
  • Review STP roles, error counters and duplex on trunk ports
  • Check for asymmetric routes through stateful firewalls
Tool

How much MTU is left inside the tunnel

Estimate for IPv4. ESP: AES-GCM, tunnel mode.

+
Failure patterns

Where it usually breaks

A

MTU black hole

ICMP “fragmentation needed” is filtered, so TCP sessions stall on large packets. Small requests pass, so monitoring stays green.

B

Asymmetric route

The request crosses one firewall and the reply another. The stateful firewall drops half of the sessions.

C

Accidental STP root

A new switch with default priority becomes the root bridge, and core traffic flows through an access port.

+
Outcome

What you keep

  • A current L2/L3 diagram with addressing
  • Findings with priority and a way to verify each
  • A change plan with a rollback for every step
← ESC

Hard problems

SEC →

Information security

+
Contact

Describe your task

Tell us what is happening and what has been tried. The engineer who will handle it replies.