I'm guessing bambu implementation returns the server socket's listen address, and they bind to 0.0.0.0. (Typography pet peeve, how do I disambiguate that dot?)
What's surprising is how this got shipped. Do the devs use some other client that has the WinSCP setting on by default, or is that feature only used by their slicer and their SDK does it by default?
One theory I have is they bound the server to the printer's address originally and it behaved properly, but then changed to 0.0.0.0 later.
> Typography pet peeve, how do I disambiguate that dot?
I have resorted to "0.0.0.0".
Reasonable.
I wish there was a common convention for logical grouping like we have in math when disambiguating operator precedence with parenthesis, but those are already taken for asides in regular prose. Maybe curly braces?
`0.0.0.0`.
Plus there's also ::/0 to bind to which will break/fix things as well.