mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 13:45:32 +02:00
[GH-ISSUE #734] [Bug]: Naming of virtual printers #490
Labels
No labels
A1
automated
automated
bug
bug
Closed due to inactivity
contrib
dependencies
dependencies
duplicate
enhancement
feedback
hold
invalid
Notes
P1S
pull-request
security
security
ThumbsUp
user-report
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/bambuddy#490
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Utility9298 on GitHub (Mar 17, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/734
Originally assigned to: @maziggy on GitHub.
Bug Description
Using virtual printers in proxy mode. The naming scheme of the printers (which are shown in BambuStudio) do not match the virtual printer name. I do not know if this is a misconfiguration or a bug, but since the X1C is called "BambuLab Drucker" maybe it is an information from the physical printer itself?
Expected Behavior
Show the name of the virtual printers in BambuStudio.
Steps to Reproduce
Printer Model
X1 Carbon
Bambuddy Version
v0.2.2
Printer Firmware Version
01.11.02.00
Installation Method
Docker
Operating System
Linux (Ubuntu/Debian)
Relevant Logs / Support Package
bambuddy-support-20260317-145528.zip
Screenshots
Additional Context
No response
Checklist
@maziggy commented on GitHub (Mar 17, 2026):
How is your network topology? Proxy mode is used for connecting to printers which are located on another LAN than your slicer. Can it be, that your slicer is on the same LAN the printers are also connected to?
@Utility9298 commented on GitHub (Mar 17, 2026):
I have to VLANs:
The clients with BambuStudio are on the Office - VLAN, the physical printers are on the IOT - VLAN.
Bambuddy is running on a virtual Debian machine (Proxmox) inside docker (network mode: host) and has two network adapters: one network adapter in office vlan and one in the IOT vlan. The network adapter on the office VLAN has several IP adresses (each one for one virtual printer)
@maziggy commented on GitHub (Mar 17, 2026):
Mhhhh.....I'm quite sure that your slicer is seeing SSDP packets directly from the printer.
Do the following:
What printers do you see?
@Utility9298 commented on GitHub (Mar 17, 2026):
I did pull the plug on the A1 and the P2S. Bambuddy proxy is still enabled.
I do still see all 4 printers:
One thing that comes to my mind:
I had to open ports on the firewall from the office network to the IOT network. But traffic from IOT to the office is not allowed.
We were able to connect to the virtual printer in proxy mode, but when sending files to the printer (or start printing directly) BambuStudio always showed a pop up and suggested the phyiscal printer IPs. On the Firewall I saw that clients try do send directly files to the physical printer (that's why I did open the ports). Otherwhise we were not able to print.
Shall I disable the IOT adress on the BamBuddy server and add the printers manually via IP adresses?
@maziggy commented on GitHub (Mar 17, 2026):
The problem is, if the slicer can "see" your printer on the network. Then it received duplicate SSDP packets for the same printer - one directly from the printer and one from Bambuddy. That's somehting Bambu Sutdio cannot handle. Somehow it always preferers the direct path.
@Utility9298 commented on GitHub (Mar 17, 2026):
I did disable all rules on the firewall so that there is no traffic from Office to the IOT vlan.
Following behaviour:
I can see the virtual printers in bambu studio (proxy mode) and can connect to them. As soon as I try to send a file to the virtual printer, I do receive an error message in BambuStudio and can see blocked traffic on the firewall:
It's like proxy mode does not really do his job. Instead Bambu Studio switches from the virtual IP adress to the physical IP Adress of the printer. And this fails because the firewall does not allows the traffic. But I do not understand where the BambuStudio gets aware of the pysical IP adress of the printer. That should be impossible, unless BamBuddy gives the IP to BambuStudio.
@maziggy commented on GitHub (Mar 17, 2026):
The screenshot shows the send file dialogue. This is not correct for VP proxy mode.
@Utility9298 commented on GitHub (Mar 18, 2026):
Mistery solved: When a printer is connected to the bambu cloud (via bambu handy), it is possible to set a new name of the printer. That's exactly the same name that is shown in BambuStudio on the virtual printer via ssdp.
So far I did not find any other method to set the printer name.