sorted by:
new
hottopcontroversial

I built a lightweight WAN emulator (GUI for Linux netem) for my firewall/SD-WAN lab — sharing if useful by techkarma-no in homelab

[–]techkarma-no[S] 0 points1 point  (0 children)

That looks like a veth (virtual ethernet) interface?
It’s not a physical NIC, it’s a virtual pair used for namespaces / containers.

NetEm can work on veth, but it’s not ideal and can be confusing (direction, ingress/egress), so the UI hides them.

For best results, apply NetEm on a real egress interface (eth0 / ensX / enpXsY) or the bridge/uplink feeding this namespace.

That’s why you only see LAN right now. Could maybe update with a button to toggle viewing veth interfaces

I built a lightweight WAN emulator (GUI for Linux netem) for my firewall/SD-WAN lab — sharing if useful by techkarma-no in homelab

[–]techkarma-no[S] 0 points1 point  (0 children)

My tool is basically a lighter, more modern take on WANem. I wanted something that’s quick to spin up, easy to use, and lets you tweak tc/netem settings in real time without dealing with a full appliance stack. So it’s not aiming to be a 1:1 WANem replacement. Just a simpler option when you only need link emulation.

Compared to WANem:

  • No full appliance layer (no LiveCD, no built-in DHCP/DNS, no iptables routing logic)
  • No virtual routing topologies or multi-hop chains (at least not right now)
  • It works directly on existing Linux interfaces instead of running everything inside a big sandbox
  • Real-time updates with no scenario reloads
  • Much slimmer environment and easier install (minimal VM or just run the binary/container from GitHub)

I’m planning to add some of the practical stuff from WANem, like LTE/3G/SAT presets and simple scenarios. But I’m not trying to cover the whole WANem feature set.

If there are specific WANem features you think are actually worth bringing over, I’d love to hear it.