maziggy 3da0c18c4d Let a virtual printer be told which address to advertise ...

BambuStudio reads its FTP upload destination out of net.info[].ip in the
    MQTT status, and the bridge fills that field from the VP's bind address.
    On Docker bridge networking the two are different machines' worth of
    address: slicers reach Bambuddy on the host's LAN IP, the container binds
    something like 172.24.0.2, and that private address is what the slicer was
    handed -- so it opened an FTP connection to an address that does not exist
    on its network and the send stalled around 10%.

    VIRTUAL_PRINTER_ADVERTISE_ADDRESS supplies the address slicers actually
    use, taking precedence over the bind address and over the same-subnet host
    interface the bridge falls back to. The armed log line names its source, so
    (VIRTUAL_PRINTER_ADVERTISE_ADDRESS) against (bind_address) tells an
    operator whether the variable reached the container at all, and the
    not-armed diagnostic now names it as the remedy -- a bridge-network install
    that has not set it is exactly the one that cannot auto-resolve either, and
    until now saw only that nothing worked.

    An environment variable rather than a change to how the advertised address
    is resolved, which is the decision worth recording. The VP already has a
    "Network Interface Override" field, and reading it here is the smaller
    patch, but it feeds SSDP and the certificate SANs only: honouring it would
    silently move the upload destination on every install that has one set --
    the multi-NIC, VLAN and Tailscale setups, which are the ones most likely to
    have been arrived at by hand and least likely to survive being
    second-guessed. Unset, this changes nothing, and a test pins that.

    A value that is not a dotted-quad IPv4 is refused with one warning naming
    it and the previous address is used instead. That direction is deliberate:
    declining to rewrite would put the real printer's IP back in front of the
    slicer, which is the leak the rewrite exists to close, so a typo must not
    be able to reopen it. 0.0.0.0 counts as unset and whitespace is stripped,
    for values pasted into a compose file.

    Host and macvlan networking need none of this and stay what Virtual Printer
    is developed against. The variable removes one blocker; it does not make
    bridge mode equivalent. The wiki said in three places that the host address
    could not be discovered at all, which is no longer true, so those now
    describe the variable and keep the recommendation.

2026-08-26 10:14:27 +02:00

..

app

Let a virtual printer be told which address to advertise

2026-08-26 10:14:27 +02:00

tests

Let a virtual printer be told which address to advertise

2026-08-24 08:58:41 +02:00

__init__.py

…