My Windows 10 PC is connected via wired ethernet to my ISP modem. My A1 Mini is connected via WiFi to the same modem. The PC has the IP address 192.168.2.1, the printer has the IP address 192.168.12.125. The printer is LAN only mode. I can ping the printer’s IP from the PC, but the printer does not show up in Bambu Studio. I suspect the problem is that they are on different sub-nets. Is there any way to get the PC to connect to the printer?
Change printer IP address to 192.168.2.125
same, i VLAN my network and printers do not live on the same subnet as PCs; is there no way to manually specify the known IP address of the printer?
Don’t use DHCP in your printer network setup, then change IP address.
Same address as your computer only last part after dot must be different.
You can use an IP scanner to see which IP addresses are used or not.
for those of us with multiple subnets, that’ll just knock the printer offline outright without some way to specify a route directly on the printer, so manual IP assignment wouldn’t be useful in this scenario
This. I believe it takes special firewall rules to route traffic like that.
my forum account is new enough that i don’t have edit permissions to my own posts yet, but yeah, after moving the printer to the same subnet as my PCs it showed up in bambu studio immediately.
for folks without more enterprise-y network experience, what’s happening is that bambu studio is only looking at the 255 possible addresses in the immediate /24 subnet range for your active network connection, so if your computer is 192.168.0.10 for example, bambu studio will only find addresses between 192.168.0.1 through 0.255, and it’ll never find the printer with the IP of 192.168.10.10 even though you have an explicit route on your computer specifying that the other subnet is just one hop away through your router.
the best possible fix for this would be the addition of a manual IP entry in the devices panel - i definitely understand the desire for user-friendliness and “magic” but when a cloud outage knocks out practically the entirety of the print world like this morning, there has to be a workable fallback and without a way to tell bambu studio “no, i know what i’m doing and my printer isn’t where you’re looking” then this problem will continue to rear its ugly head
oh hey, looks like it’s in the works? can’t include links yet but go to Ability to enter IP of Printer(s) · Issue #2232 · bambulab/BambuStudio · GitHub
1 Like
What about “Bind IP to MAC” if your Internet router serves DHCP you can bind an IP number to your printer’s MAC address.
the issue isn’t the printer’s IP address, it’s that a discover packet isn’t going to hop subnets regardless if a route exists via switch ACL or firewall rule. studio will never find the printer automatically with it on a different VLAN/subnet, but since the manual IP input field is coming down the line, the issue is moot once that version of studio releases.
I came up with a solution that works for me. I programmed a Raspberry Pi 3 to be a bridged wireless acess point. The printer is now on the same subnet at my PC and LAN only mode works. When the cloud service is restored, the same connection should allow the printer to work with the cloud.
See this article on Github:
Using a Raspberry Pi 3 as a Wireless Access Point and Bridge