Your Proxmox network has parts you never configured

Type "proxmox network" into a search box and one of the suggestions that comes back is topology visualizer. People are looking for a picture of their own setup, and it is tempting to read that as wanting decoration. It is not decoration. It is a data shape problem.

Why the question keeps getting asked

The relationship you want to see is guest, then bridge, then physical port. Proxmox VE stores the first half of that inside each guest's configuration: this guest has a network device, and that device attaches to a named bridge. The second half lives in the host's network configuration: this bridge has these ports.

Both halves are recorded precisely and neither is hidden. But the join between them is not stored anywhere, and no screen performs it. So the answer to "which guests are on this bridge" does not exist as a view. It exists as a task: open each guest, read one line, keep a tally in your head.

With three guests that is fine. With thirty it is an afternoon, and an afternoon of work is a question that does not get asked.

The picture has more parts than the configuration file

Here is what makes a drawing worth more than a careful reading of the config. A running host has network parts that appear on their own.

On a small host used to check this, two bridges were configured by hand. The running system had a third, created automatically because the firewall was enabled for one guest's interface. Nobody wrote it, nobody named it, and it exists only while that guest runs.

The same host had seven virtual cable ends connecting running guests to bridges. None of them appear in any configuration file either. They are created when a guest starts and disappear when it stops.

So the honest description is that your network has a static part that you wrote and a live part that the system builds around it. Read only the config and you see the plan. Read only the running interfaces and you see a list of names with no story. Neither one is the shape.

The thing a picture catches immediately

That same host had two bridges and eleven guest interfaces, all of them on one bridge. The second bridge existed, was configured, was up, and carried nothing.

Nothing is wrong with that. It might be deliberate, kept ready for a network that has not arrived yet. The point is narrower: nothing on any screen said so. Its emptiness is only visible from above, and it stays invisible until the day somebody renames it, removes it, or assumes it is in use and builds on it.

Empty things do not raise alarms. They just quietly change what you believe about your own machine.

Three questions a list cannot answer

What is on this bridge? A list of bridges tells you they exist. It does not tell you who is riding them.

Which physical port does this guest's traffic actually leave through? The guest names a bridge. The bridge names a port, or a bond, which names two ports. That chain is two or three lookups long, and it is the chain that matters when a cable is unplugged.

What breaks if I take this interface down? This is the question people ask before maintenance and answer with a guess. It is the same join, read backwards.

What Proxmox VE actually gives you

More than the tone of this article might suggest, and it is worth being exact rather than dramatic.

Each node has a network view listing interfaces, bridges, bonds and VLANs, with what is active now and what is only written down for the next reload. Each guest's hardware view shows its network devices and the bridge each one attaches to. For people who want networks defined rather than assembled, there is a software defined networking section with zones and virtual networks.

All of it is precise. What none of it does is put the two ends of the relationship on the same screen.

What Atlas does, and what it does not

Atlas draws that join. Guests, the bridges they attach to, the ports underneath, in one picture instead of one guest at a time, including the parts that exist only while things are running.

What it does not do is configure networking. It does not create bridges, it does not move a guest to a different network, and it will not stop you from designing something odd. A picture of a bad layout is still a bad layout, drawn more clearly.

The value is narrower than it first appears, and worth stating plainly: it converts a question you would have to work for into a question you can just look at. Questions that are cheap to ask get asked, and the ones that never get asked are where the surprises live.