Firewall

Proxmox from scratch · Part 5

Networking inside Proxmox

So far every guest in this series has been plugged into vmbr0, and I told you to keep the default. In this part we look at what that means, how to split guests into separate networks, and how to find out what a guest is actually doing on the network.

How Proxmox networking works

Linux bridges (vmbr0)

A bridge is a switch made of software. Your guests’ virtual network cards plug into it, and so does a physical network port on the server. The installer sets up exactly one: it “creates a single bridge named vmbr0, which is connected to the first Ethernet card” [1]. The server’s own IP address sits on that bridge as well.

Teams and Copilot are moving to cloud.microsoft: check your allow-lists before October

Two of the most used Microsoft 365 web addresses are changing this autumn. Copilot is moving to copilot.cloud.microsoft and Teams on the web to teams.cloud.microsoft. If something in your network blocks *.cloud.microsoft, October is when your users find out.

What’s changing

Copilot: m365.cloud.microsoft becomes copilot.cloud.microsoft

In message center post MC1462915 Microsoft says it started redirecting users from m365.cloud.microsoft to copilot.cloud.microsoft in early September, in organisations where the new address is reachable. Everyone else gets redirected in early October [1]. If the address is blocked, the redirect happens anyway, and “affected users may be unable to use Copilot in the web app, desktop app, and Microsoft Edge experience” [1].