mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 08:25:54 +02:00
[GH-ISSUE #564] [Bug]: Bad model when creating virtual printer #368
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
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-maziggy-1#368
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 @S3LL1G28 on GitHub (Mar 1, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/564
Originally assigned to: @maziggy on GitHub.
Bug Description
Hi ,
Big thanks for this wonderfull project ! !
I run a container image of bambuddy v0.2.1.1. I have followed your wiki to setup everything related to docker in networkmode: host.
I run on an lxc under promox with nested, keyctl.
My problem is when I create a virtual printer for my H2S i see x1c to H2S and asking about binding interface and have no choice of selecting interface.
I have created a second interface on this lxc which is on the same lan as my H2S.
I can get information about my real H2S for printer
Expected Behavior
Having a working virtual printer, with the capabilities to select network interface.
Steps to Reproduce
1- install a new bambuddy in networkmode host
2_ have a second physical interface
3- try to add a virtual printer after creating the real one
Printer Model
H2S
Bambuddy Version
0.2.2.1
Printer Firmware Version
01.01.02.00
Installation Method
Docker
Operating System
Linux (Ubuntu/Debian)
Relevant Logs / Support Package
Screenshots
Additional Context
No response
Checklist
@S3LL1G28 commented on GitHub (Mar 1, 2026):
bambuddy-support-20260301-165930.zip
@maziggy commented on GitHub (Mar 1, 2026):
Bambuddy cannot find any interface!
"network": {
"interface_count": 0,
"interfaces": []
},
Show me the output of "ifconfig" from your host OS and your LXC config.
@S3LL1G28 commented on GitHub (Mar 1, 2026):
my lxc conf:
I got other services on it but no port conflicts
edit: update github format
@maziggy commented on GitHub (Mar 1, 2026):
Sorry, I meant ifconfig from the container, Docker is running in.
Not sure if keyctl could be an issue. Never used it.
Fact is, Bambuddy does need to find the LXC container interfaces, but doesn't.
@S3LL1G28 commented on GitHub (Mar 1, 2026):
Sorry, if i misunderstood but ifconfig is not there.neither ip a
@S3LL1G28 commented on GitHub (Mar 1, 2026):
Just for your information i try on Kubernetes (even if it will not be used) and same error for virtual printer
@maziggy commented on GitHub (Mar 1, 2026):
cat /proc/net/dev in container?
@S3LL1G28 commented on GitHub (Mar 1, 2026):
@S3LL1G28 commented on GitHub (Mar 1, 2026):
I make some quick downgrade on kubernetes and found that 0.2.1b3 show me interface eth0
@maziggy commented on GitHub (Mar 1, 2026):
That's not going to work. Your container has no eth interface.
veth* interfaces are Docker/container virtual ethernet pairs. They're the point-to-point links between container network namespaces and Docker bridge networks. They're transient (created/destroyed with containers), have no meaningful routable IP from the host's perspective, and binding a Virtual Printer to one would be useless.
@S3LL1G28 commented on GitHub (Mar 1, 2026):
ok i will try to see how to change the name of interfaces => done and working with changing the name to eth1
But a bug persist independantly of interfaces. The virtual printer show x1c to H2s
@maziggy commented on GitHub (Mar 1, 2026):
What does "The virtual printer show x1c to H2s" mean? Show me a screenshot of the settings page.
@S3LL1G28 commented on GitHub (Mar 1, 2026):
after the name we can see x1c = H2s
@maziggy commented on GitHub (Mar 1, 2026):
Stop! You are running an old version of Bambuddy! Please update to latest version.
@S3LL1G28 commented on GitHub (Mar 1, 2026):
oh sure ! if it's that shame on me, i will check
@S3LL1G28 commented on GitHub (Mar 1, 2026):
docker compose ps bambuddy
NAME IMAGE COMMAND SERVICE CREATED STATUS PORTS
bambuddy ghcr.io/maziggy/bambuddy:0.2.1.1 "sh -c 'uvicorn back…" bambuddy 3 minutes ago Up About a minute (healthy)
I erase data too. and same problem
I was before in latest tag
@S3LL1G28 commented on GitHub (Mar 1, 2026):
I have tested something and have a bachup of a previous try. I have the right interface. So before update it was ok.
how can i see in sqlite3 the backup version ?
@maziggy commented on GitHub (Mar 1, 2026):
All good for the version I think.
H2S is what you selected under Target Printer?!
@S3LL1G28 commented on GitHub (Mar 1, 2026):
yes for sure, I have selected H2s
@S3LL1G28 commented on GitHub (Mar 1, 2026):
I try to find a software to read sqlite from the backup in case of
@maziggy commented on GitHub (Mar 1, 2026):
Yes, you added a proxy for X1C but selcted the H2D as a target!
@S3LL1G28 commented on GitHub (Mar 1, 2026):
no as you can see
@S3LL1G28 commented on GitHub (Mar 1, 2026):
tell me if you need i have now a tool to read sqlite db. i Open the one from backup to compare
@S3LL1G28 commented on GitHub (Mar 1, 2026):
in my old backup i see O1S , in the backup from a fresh version i see in table virtual printers: 3DPrinter-X1-Carbon
@maziggy commented on GitHub (Mar 1, 2026):
See....the workflow for adding a virtual printer is
So, when your card shows
X1C <-> H2S
its equal to
<**_name_**> <-> <your selected printer>So what happended? You entered X1C into the name field when creating the virtual printer.
@S3LL1G28 commented on GitHub (Mar 1, 2026):
I follow this logical sequence and if i put different name in name for example toto i have:
toto proxy x1c <->H2S.gil-yan.net
@maziggy commented on GitHub (Mar 1, 2026):
Ahhhhh.....wait!
Switch the VP mode and see what printer is selected for printer model. I think that's just a typo in frontend.
@S3LL1G28 commented on GitHub (Mar 1, 2026):
i don't understand you VP mode ?
@maziggy commented on GitHub (Mar 1, 2026):
The virtual printer settings card has four modes Archive, Queue, Review and Proxy. You are now in proxy mode. Switch to any other mode and check which printer is selected as target printer.
@S3LL1G28 commented on GitHub (Mar 1, 2026):
AH ok i understand by going into archiver th model is asked an when go to proxy mode it stay.
@maziggy commented on GitHub (Mar 1, 2026):
Which is correct, because the card is for the printer you specified when setting it up.
@S3LL1G28 commented on GitHub (Mar 1, 2026):
so it will be interesting to add a choice like archiver for the model . If others like me click directly they won't understand no ?
@maziggy commented on GitHub (Mar 1, 2026):
Sorry, don't know what you mean.