mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 05:35:30 +02:00
[GH-ISSUE #445] [Bug]: Virtual Printer Proxy Mode Bambulab connects to port 3002 #274
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#274
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 @kaiminator on GitHub (Feb 18, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/445
Originally assigned to: @maziggy on GitHub.
Bug Description
I am running Bambuddy in k8s and exposed the ports via nodeport.
The ports 990,8883 and 3000 are reachable from DesktopPC via nodeip:nodeport - tested with nmap
`Starting Nmap 7.80 ( https://nmap.org ) at 2026-02-18 20:17
Nmap scan report for 10.10.200.30
Host is up (0.00045s latency).
PORT STATE SERVICE
990/tcp open ftps
3000/tcp open ppp
8883/tcp open secure-mqtt`
I want to use virtual printer in proxy mode and override interface ip to nodeip. I also added the bbl_ca.crt certificate to the bambustudio chain in printer.cer
When i wanted to connect Bambustudio to Bambuddy with add printer via access code and give nodeip 10.10.200.30 and real printer access code i got an connection error.
In Bambuddy app i installed for debugging reason tcpdump and i see connections from desktop pc - but the destination port is 3002 not 3000.
listening on any, link-type LINUX_SLL2 (Linux cooked v2), snapshot length 262144 bytes 19:36:47.925042 eth0 In IP 10.10.10.100.36478 > 10.10.200.30.3002: Flags [S], seq 2773118642, win 65535, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0 19:36:47.925081 eth0 Out IP 10.10.200.30.3002 > 10.10.10.100.36478: Flags [R.], seq 0, ack 2773118643, win 0, length 0 19:36:48.438209 eth0 In IP 10.10.10.100.36478 > 10.10.200.30.3002: Flags [S], seq 2773118642, win 65535, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0 19:36:48.438264 eth0 Out IP 10.10.200.30.3002 > 10.10.10.100.36478: Flags [R.], seq 0, ack 1, win 0, length 0 19:36:48.952920 eth0 In IP 10.10.10.100.36478 > 10.10.200.30.3002: Flags [S], seq 2773118642, win 65535, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0 19:36:48.952961 eth0 Out IP 10.10.200.30.3002 > 10.10.10.100.36478: Flags [R.], seq 0, ack 1, win 0, length 0 19:36:49.467579 eth0 In IP 10.10.10.100.36478 > 10.10.200.30.3002: Flags [S], seq 2773118642, win 65535, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0 19:36:49.467619 eth0 Out IP 10.10.200.30.3002 > 10.10.10.100.36478: Flags [R.], seq 0, ack 1, win 0, length 0 19:36:49.981990 eth0 In IP 10.10.10.100.36478 > 10.10.200.30.3002: Flags [S], seq 2773118642, win 65535, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0 19:36:49.982047 eth0 Out IP 10.10.200.30.3002 > 10.10.10.100.36478: Flags [R.], seq 0, ack 1, win 0, length 0 19:36:51.990558 eth0 In IP 10.10.10.100.36479 > 10.10.200.30.3002: Flags [S], seq 686099842, win 65535, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0 19:36:51.990622 eth0 Out IP 10.10.200.30.3002 > 10.10.10.100.36479: Flags [R.], seq 0, ack 686099843, win 0, length 0 19:36:52.492833 eth0 In IP 10.10.10.100.36479 > 10.10.200.30.3002: Flags [S], seq 686099842, win 65535, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0 19:36:52.492867 eth0 Out IP 10.10.200.30.3002 > 10.10.10.100.36479: Flags [R.], seq 0, ack 1, win 0, length 0 19:36:52.994717 eth0 In IP 10.10.10.100.36479 > 10.10.200.30.3002: Flags [S], seq 686099842, win 65535, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0 19:36:52.994755 eth0 Out IP 10.10.200.30.3002 > 10.10.10.100.36479: Flags [R.], seq 0, ack 1, win 0, length 0 19:36:53.498532 eth0 In IP 10.10.10.100.36479 > 10.10.200.30.3002: Flags [S], seq 686099842, win 65535, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0 19:36:53.498588 eth0 Out IP 10.10.200.30.3002 > 10.10.10.100.36479: Flags [R.], seq 0, ack 1, win 0, length 0 19:36:54.013792 eth0 In IP 10.10.10.100.36479 > 10.10.200.30.3002: Flags [S], seq 686099842, win 65535, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0 19:36:54.013827 eth0 Out IP 10.10.200.30.3002 > 10.10.10.100.36479: Flags [R.], seq 0, ack 1, win 0, length 0 19:36:56.021815 eth0 In IP 10.10.10.100.36481 > 10.10.200.30.3002: Flags [S], seq 1714751013, win 65535, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0 19:36:56.021874 eth0 Out IP 10.10.200.30.3002 > 10.10.10.100.36481: Flags [R.], seq 0, ack 1714751014, win 0, length 0 19:36:56.535803 eth0 In IP 10.10.10.100.36481 > 10.10.200.30.3002: Flags [S], seq 1714751013, win 65535, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0 19:36:56.535842 eth0 Out IP 10.10.200.30.3002 > 10.10.10.100.36481: Flags [R.], seq 0, ack 1, win 0, length 0 19:36:57.051386 eth0 In IP 10.10.10.100.36481 > 10.10.200.30.3002: Flags [S], seq 1714751013, win 65535, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0 19:36:57.051434 eth0 Out IP 10.10.200.30.3002 > 10.10.10.100.36481: Flags [R.], seq 0, ack 1, win 0, length 0 19:36:57.554182 eth0 In IP 10.10.10.100.36481 > 10.10.200.30.3002: Flags [S], seq 1714751013, win 65535, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0 19:36:57.554242 eth0 Out IP 10.10.200.30.3002 > 10.10.10.100.36481: Flags [R.], seq 0, ack 1, win 0, length 0 19:36:58.069047 eth0 In IP 10.10.10.100.36481 > 10.10.200.30.3002: Flags [S], seq 1714751013, win 65535, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0 19:36:58.069101 eth0 Out IP 10.10.200.30.3002 > 10.10.10.100.36481: Flags [R.], seq 0, ack 1, win 0, length 0Expected Behavior
connection from Bambustudio to Bambuddy via port 3000
Steps to Reproduce
Printer Model
A1
Bambuddy Version
0.2.0
Printer Firmware Version
01.07.02.00
Installation Method
Other
Operating System
Other
Relevant Logs / Support Package
Screenshots
No response
Additional Context
bambuddy-support-20260218-203239.zip
Checklist
@maziggy commented on GitHub (Feb 19, 2026):
The additional connection on port 3000 was introduced with the latest(?) release of Bambu Studio. Obviuously we need to add a port range instead of only port 3000. Perhaps it's advertised by SSDP?
Anyway...I'm currently working on improving the virtual printer function so that it supports multiple printers. Will check for the new port requirements and add it to the new version.
Please wait a few days until I'm finished. Will let you know. Thanks.
@kaiminator commented on GitHub (Feb 19, 2026):
your are welcome - as a workaround i tried to manage to get a connection between bambuddy and bambustudio by port foward the node local port from 3002 to 3000 via iptables
sudo iptables -t nat -A PREROUTING -p tcp --dport 3002 -j REDIRECT --to-ports 3000in this case the nodeport 3002 is open and localy redirect it to port 3000 - the traffic from Bambustudio now reaches Bambuddy, but never connects
if you need further informations don't hesitate to get in contact with me
2026-02-19 11:15:29,089 INFO [backend.app.services.virtual_printer.tcp_proxy] Bind proxy: client connected from 10.10.10.100:11339
2026-02-19 11:15:29,089 INFO [backend.app.services.virtual_printer.manager] Proxy Bind: connected: 10.10.10.100:11339
2026-02-19 11:15:29,092 INFO [backend.app.services.virtual_printer.tcp_proxy] Bind proxy: connected to printer 10.10.10.34:3000
2026-02-19 11:15:29,123 INFO [backend.app.services.virtual_printer.tcp_proxy] Bind proxy: client 10.10.10.100:11339 disconnected
2026-02-19 11:15:29,124 INFO [backend.app.services.virtual_printer.manager] Proxy Bind: disconnected: 10.10.10.100:11339
2026-02-19 11:15:31,131 INFO [backend.app.services.virtual_printer.tcp_proxy] Bind proxy: client connected from 10.10.10.100:11340
2026-02-19 11:15:31,131 INFO [backend.app.services.virtual_printer.manager] Proxy Bind: connected: 10.10.10.100:11340
2026-02-19 11:15:31,134 INFO [backend.app.services.virtual_printer.tcp_proxy] Bind proxy: connected to printer 10.10.10.34:3000
2026-02-19 11:15:31,142 INFO [backend.app.services.virtual_printer.tcp_proxy] Bind proxy: client 10.10.10.100:11340 disconnected
2026-02-19 11:15:31,142 INFO [backend.app.services.virtual_printer.manager] Proxy Bind: disconnected: 10.10.10.100:11340
2026-02-19 11:15:33,151 INFO [backend.app.services.virtual_printer.tcp_proxy] Bind proxy: client connected from 10.10.10.100:11341
2026-02-19 11:15:33,151 INFO [backend.app.services.virtual_printer.manager] Proxy Bind: connected: 10.10.10.100:11341
2026-02-19 11:15:33,154 INFO [backend.app.services.virtual_printer.tcp_proxy] Bind proxy: connected to printer 10.10.10.34:3000
2026-02-19 11:15:33,161 INFO [backend.app.services.virtual_printer.tcp_proxy] Bind proxy: client 10.10.10.100:11341 disconnected
2026-02-19 11:15:33,161 INFO [backend.app.services.virtual_printer.manager] Proxy Bind: disconnected: 10.10.10.100:11341
@maziggy commented on GitHub (Feb 19, 2026):
As said, please wait for the next beta release. There are major changes.
@maziggy commented on GitHub (Feb 19, 2026):
Please try again with latest beta release 0.2.1b.
@kaiminator commented on GitHub (Feb 19, 2026):
tested 0.2.1.b and bambustudio is now connecting to virtual proxy port
2026-02-19 15:49:35,958 INFO [backend.app.services.virtual_printer.manager] [VP Bambuddy] Proxy MQTT: connected: 10.10.10.100:62613
2026-02-19 15:49:36,753 INFO [backend.app.services.virtual_printer.tcp_proxy] MQTT proxy: connected to printer 10.10.10.34:8883