Printer in different subnet of the same LAN

I have my Bambu X1C in a separate VLAN/subnet, dedicated for all Internet of Things devices. It is on purpose, to separate my computers from devices like printers, smart TVs, etc. However in this setup my printer is not discovered by Bambu Studio on my computer (no surprise).

Is there a way to define printer IP address in Bambu Studio, as LAN discovery will obviously not work between separated networks? or what other solution can I use? maybe like proxying mDNS protocol or something to make inter-vlan discovery possible?

Note: I have proper routing and full connectivity between both subnets. Connectivity is not my issue. Just discovery is not working.

2 Likes

I wish there was this option to put an IP, but not right now. Bambu Lab does networking through their ridiculous encrypted networking plugin. Instead you can enable SSDP multicast/broadcast across the two networks in the router for the discovery to work. It’s UDP 1990/2021

3 Likes

I will certainly give it a try. Thanks!

This is a big freature request by many, sure they are working on it. Stay tuned to release info i guess.

1 Like

If they would add possibility to specify local printer IP in Bambu Studio that would be the best and would solve all connectivity issues. So simple to do anyways. I’m so disappointed that it is not an option yet - obviously not all LANs are simple one VLAN / broadcast domain setup.

1 Like

See this gross workaround. It’s unsatisfying, but it does work.

2 Likes

I have my Bambu P1S on a IOT VLAN using Unifi equipment. I have a firewall rule which allows my default network to speak with my IOT without restriction (one way). No issues finding it. However my live video feed is choppy at best… Not sure if thats just the way it is or due to VLAN rules.

1 Like

I have my P1S on an IoT VLAN with same rule as you (default can speak to IoT). Discovery of other services work fine (printer, scanner, a few shelly devices, all on my IoT VLAN). But I can’t see my P1S from bambu studio or orca. I also use a completly unifi network with mDNS forwarding on (they now call it IoT Discovery)…

any clues?

Make sure your rules are in order. I had to move them up in the priority for them to work and grant access.

1 Like

I only have one rule: Block IoT to default network:

I then have the following multicast settings checked:
image

This works for my other devices on my IoT vlan like my HP printer, scanner, cameras, etc.

Is this what you have?

I have multicast on also.
I have another rule which allows default to IOT. But IOT out to LAN is blocked.

so basically you have the same setup as I do, and yours works and mine doesn’t :confused: I will try adding a rule about allowing LAN to IoT, but I think that works by default - for example I can ping the P1S on my IoT VLAN from the default LAN.

I was also struggling with this problem, bambustudio/orcaslicer didnt connect to P1S.
my linux machine is in LAN vlan and P1S in IOT vlan. strange is that windows machine in same vlan than linux worked without any configuration changes. also linux machine works in same (IOT) vlan worked.
I have opnsense so its bit different…
but this is what I did if it helps someone:
I added in to Opnsenses services UDP Broadcast Relay
Relay port: 2021, interfaces: IOT, LAN, Broadcast address:239.255.255.250
source address: P1S ip address.

1 Like

Hey guys, I have developed a solution for this problem.
With the help of many solutions and scripts from other forums, I have written a program which offers a kind of workaround.
I am relatively new to 3D printing myself, but I have encountered this problem before at our company.

The program I was referring to is available on GitHub:
Rdiger-36/StudioBridge

Had the same issue, only I use pfSense instead of OPNSense, but the ā€˜UDP Broadcast Relay’ package is available in pfSenses’s package manager as well. I’ve further disabled any sort of WAN access to the P1S and also restricted Bambu Studio to my IOT vlan only, so the setup is quite ā€˜offline’, or rather fully local, yet everything else works like a charm and I really have no need for the ā€˜cloud’ operation whatsoever…

1 Like

So the issue is that the printer communicates via UDP broadcast?

I have a similar setup, only that my router is a self-built OpenBSD box. I have the printer in my IOT vlan, and my laptop is in my ā€œPrivateā€ vlan. I don’t see any printer in the dropdown, and when I choose to ā€œBind with access codeā€, after putting in the IP address, code & serial number, the dialog just closes, and nothing happens.

How is this supposed to work? Should the printer be auto-discovered without the need to manually specify IP & code?

My laptop is running Ubuntu 24.04, if that would be important.

Haven’t yet tried with the laptop being in the same vlan. Gonna try out later. I really would like to use the printer without the cloud.

This is exactly what I would like to do. I have pfSense as well. Would you mind posting instructions on how you did this? I’d really appreciate it!

I presume you already have your computer(s) and your printer on different VLANs and you just want the printer to broadcast to a computer running Bambu Studio / Orca Slicer / whatever so that it’s discoverable.

I don’t remember exactly if these were exactly the same steps I did, but I presume it will get you somewhere :sweat_smile:

  1. Go to System / Package Manager / Available Packages, search for udpbroadcastrelay and install it.
  2. Go to Services / UDP Broadcast Relay and click on + Add
  3. Give it some descriptive name, under Network Interfaces select your your printer’s VLAN and VLAN(s) you want it to be ā€˜discoverable’ on
  4. For Destination UDP port to listen on enter 2021
  5. Don’t forget to enable the instance at the top, and enable the UDP Broadcast Relay on its main page as well

That will effectively ā€˜bridge’ your VLANs (or other interfaces if selected) for any UDP broadcast packages on port 2021, which is what your printer uses to announce its presence and that’s how Bambu Studio or Orca Slicer automagically find it (should start showing immediately under the printer selection on the Devices tab).

Keep in mind that you still need to make sure that your computer(s) VLAN can access the VLAN where your printer resides on, or at least your printer’s IP (i.e., create a Firewall rule for your computer(s) VLAN - Action: Pass, Protocol: Any, Source: <Computer_VLAN> subnets (or a specific computer on it), Destination: <Printer_VLAN> subnets (or a specific IP of your printer) and place it above any rule that might block your computer’s access to other subnets (or anything else for that matter)). You do not need to add any extra provisions for the VLAN on which your printer(s) reside.

Another thing to note - if you’re running a local firewall on your computers, make sure that you let in UDP broadcast traffic coming from your printer’s VLAN (or IP), otherwise it will still not show up in the Devices tab.

When the whole chain is set up properly, you will not even need to enter your printer’s IP or anything of the sort - it will show up in Bambu Studio / Orca Slicer and all you will need to do is enter the Access Code (which you’ll be able to see when you set your printer to a LAN-only mode).

3 Likes

Thanks so much! I’ve been messing with the printer, pfsense, and my Unifi AP for the last few hours. I’ll give this a shot and see how it goes😁

The printer uses UDP broadcast to announce its presence to the other devices on its network, that’s how Bambu Studio ā€˜finds’ it. I haven’t attempted it, but AFAIK it’s not mandatory - as long as your computer can access your printer’s VLAN you ought to be able to manually add your printer and use the access code just fine. Can you at least ping your printer from your computer?