Skip to content

Network Firewall

Marko@VMHOMELAB edited this page Jun 13, 2026 · 1 revision

Network & Firewall

Printer integrations fail most often because of routing, firewall, or VLAN rules. Check the network path before changing application settings.

Recommended network model

  • Printbuddy host can reach all printer IPs.
  • Printers have stable DHCP reservations.
  • DNS names resolve consistently, or IP addresses are used.
  • Printer API/camera ports are allowed between VLANs if segmented.

Docker networking

On Linux, the default compose file uses:

network_mode: host

This is helpful for:

  • Bambu discovery and local services.
  • Camera streams.
  • Virtual-printer ports.
  • Printer callbacks or services that expect LAN-style access.

On Docker Desktop for macOS/Windows, host networking is not supported in the same way. Use the commented ports: section in the compose file and add printers manually by IP.

Common ports

Actual ports depend on printer and provider, but common examples include:

  • Printbuddy web UI: 8000 by default.
  • Moonraker: 7125 by default.
  • Bambu/virtual-printer workflows: multiple LAN service ports depending on mode.
  • Cameras: depends on MJPEG/RTSP/snapshot provider.

Basic checks

From the Printbuddy host:

curl -I http://<printer-ip>:7125/server/info
curl -I http://<camera-url>

Use the exact URL that Printbuddy is configured to use.

Clone this wiki locally