LAN Only and Mac Ventura?

Can anyone confirm that LAN Only mode works when running BambuStudio on a Mac running Ventura 13.4 ?

I can get LAN Only mode to reliably work on a Windows 10 box but have thus far had no luck in getting it to show up on the mac. It would be nice to know if someone else has successfully gotten Lan Only mode to work on a MAC before I spend any more time troubleshooting this further.

Make sure your Mac is connected to your 2.4g network. The X1 only support 2.4g

Thanks … My IOT vlan is set to 2.4 since most IOT devices dont seem to support 5gHz …

I used the LAN only mode on my Mac for while. Initially I had problems but these were resolved once I changed to a static IP address for my P1P

Update:

After several days of troubleshooting I have finally been successful in getting the “Lan Only” option to work.

Along the way I discovered a few oddities that I thought I would pass along.

  1. The Ventura (13.4.1) Firewall does not work as expected (at least on my machine). What I found is that I have to reboot the machine after making Firewall changes. Specifically if I turn off the firewall or enable inbound connections to an application, neither will not take affect until the next reboot. This made my troubleshooting very difficult.

  2. BambuStudio apparently requires “Allow Inbound Connections” be enabled in the firewall. I have notified support of this and have asked for an explanation as to why this appears to be required as its counter to good security practices and is not normally required by MQTT applications. I confess this may just be an issue with my machine so Im holding off judgement until I hear back from support.

  3. There appears to be an odd issue with SSDP / mdns where I cannot discover the printer when on different vlan even though I have a rule that allows SSDP/mdns traffic to pass from vlan to lan. As I do not seem to have problems seeing other SSDP/mdns IOT devices this appears to be specific to Bambulab devices. Short term I have solved this issue by dual homing my Mac to ensure it have a direct connection to the printers VLAN.

The good news is that I have determined that you can successfully use the following features with no impact on your ablity to leverage “LAN Only” mode on the printer.

  1. VPN when configured correctly (Im using Mullvad with “Local network sharing” enabled)
  2. Network filtering when configured correctly (must allow BambuStudio access to mdns address 239.25.255.250)
  3. Apple Firewall / Options / Stealth Mode can be enabled
  4. Multhomed networks can be used
  5. Mixed mode wireless networks can be used ( 5 GHz & 2.5 Ghz sharing same SSDI/Password)

Should I solve the ssdp/msdn or “Allow Inbound Connections” mysteries I will update this discussion as appropriate

BambuStudio listens on *:2021 for broadcast announcements from printer(s). These are then used by BambuStudio to connect back to the printer(s). Unfortunately:

  1. there’s no way to manually configure a printer by IP address
  2. only one application at a time can bind to *:2021, so, e.g., running Orca and BambuStudio at the same time for LAN-only devices doesn’t work.
  3. your computer needs to be in the same broadcast domain as the printer, and allow unsolicited incoming traffic.*
  • Unless you spoof it using this sort of trickery. This DOES work; unfortunately, it doesn’t solve problem #2, and it’s not persistent, so if you reboot BambuStudio, one must re-spoof.

Honestly, it’s a lot of trouble and hackery to avoid adding a printer by IP address. Please, please just let us add by IP address. :weary:

2 Likes

Thanks, the hack works as described.

At the end of the day all that matters is BBL gives us the ability to add printers by IP address and not have to deal with network broadcast vagaries.

Its interesting that only my Mac requires gashtons discovery hack to get the printer to work across lan/vlan. All I had to do on my Windows 10 box was open up the firewall for BambuStudio.

Hm. Odd. I thought I had the same issue but in LAN-only mode but after rebooting the printer my device started showing up. On the Firewall side, I “allowed access” during the first install of the Bambu networking plugin. Basically, LAN mode is working perfectly fine across VLANs - I typically secure most IoT devices under a locked down network.

On the networking side, the usual issue with multicast DNS across VLANs is that your gateway/firewall needs to “hack” the packets and increase the TTL of any rebroadcast packets to ensure that they make it across the VLAN - this is often difficult if not impossible with consumer networking stuff. I’m running Unifi hardware that lets me do that transparently. Incidentally this is the same problem I’ve had with Chromecasts across VLANs. I used to use consumer grade stuff, and I’m not aware of any real solutions on most systems other than custom firmware + custom linux firewall configurations to make it work.

Hello Bambu Lab Community,

I’m reaching out with a concern regarding three specific LOG files I discovered in my Mac’s Apple Application folder. The names of these files are [tutk_log_avapi_41196], [tutk_log_iotc_41196], and [tutk_log_global_41196]. What’s intriguing is their creation date aligns with when I started using the Bambu PS1 22 and 21 dec. Upon opening them, I found a line stating “TUTK DDK set license key”. A quick internet search revealed that TUTK (ThroughTek Co.) is associated with cloud service recording and P2P IoT connectivity.

This discovery has raised my alarm, as I’m now concerned these files might be related to some form of malware or unauthorized monitoring. Can anyone in the community confirm if these logs are a standard part of Bambu’s installation? Any insights or clarifications would be greatly appreciated, as I want to ensure the security and privacy of my system.

Thank you for your attention to this matter.

I have finally found a solution, but it requires ideally a VM with multiple network interfaces. Some background. I have P1S in LAN Only Mode on a VLAN with No Internet Access. I have my clients I like to slice/monitor from on another VLAN that does have Internet access, etc so by default the SSDP discovery doesnt work for Bambu Studio/Orca Slicer.

I already have a Ubuntu Server VM running Avahi for mDNS reflector, so it has multiple interfaces on different vlans and i use that for the reflector.

I found a package on Github (GitHub - marjohn56/udpbroadcastrelay: UDP multicast/unicast relayer) and you can use it to relay the SSDP (UDP 2021 for LAN Only Mode in the case on BBL) to another interface.

I used the command: udpbroadcastrelay --id 1 --port 2021 --dev ens36 --dev ens35 -d -f. I made mine run as a service so it starts with the VM, but so far it’s been working great. Change the Dev ports to your network interfaces (1 interface on same network as Bambu, and 1 interface on same network as your clients).

1 Like

I made a PowerShell version of gashton’s ‘hack’. We needed it at work because we’re a Windows shop.

github withanhdammit BambuStudio_Launcher
(the forum won’t let me include links yet)