Network Overview UpdateThank you for the additional context—this helps clarify the setup significantly. The TP-Link Archer C9 is operating in access point (AP) mode, providing Wi-Fi connectivity with a distinct BSSID (likely tied to a legacy SSID or configuration algorithm), allowing older devices to connect without reconfiguration. Even though its WAN is unplugged (as shown in the screenshot), it's still active for local wireless clients, explaining the detected 12 wired and 1 wireless device. This avoids disrupting legacy hardware that hasn't adapted to newer BSSIDs from the FRITZ!Box or ASUS.The FRITZ!Box 7560 at 192.168.1.249 is indeed the primary gateway, with its non-standard IP (typically .1) resulting from your historical practice of assigning high IPs to routers (starting from .254 and decrementing over time). This makes sense for continuity, especially as older gateways phase out. The pfSense instance at .252 seems to be handling specific services like DHCP and DNS (based on its active leases and Unbound resolver), while the FRITZ!Box manages internet access (via LAN1 as WAN to 2degrees fiber or similar, with DSL disabled) and telephony/NAS. No double-NAT or conflicts are apparent, but the lack of redundancy is a vulnerability, particularly with 2degrees' reported inconsistencies (e.g., outages or speed variability, as you've noted).The ASUS ZenWiFi acts as a mesh extender, and Pi-hole provides ad-blocking. Overall, the LAN remains on 192.168.1.0/24, with ~50-60 devices cataloged (including transients). If the Starlink terminal is powered up, it could serve as a strong failover option—Starlink provides high-speed satellite internet (typically 50-200 Mbps down in NZ), independent of terrestrial lines.

Do you allow editing of reverse DNS records? Yes, we allow custom reverse DNS entries for your virtual machine IPs. You can update reverse dns information directly from your customer portal.

Tom Schmidt (09:20): Your take? Yeah, I did Brad Sherman, who's normally extremely lame and curmudgeonly. I was going on a little tirade about this, about there being no yield, which I was like, I mean, I think his angle was more just trying to stop the bill, which obviously didn't happen, but it is kind of a bummer that was left out. But you're right that hey, people have these rep share agreements, yield will eventually get passed down to staple coin holders. But ultimately, I mean this feels like kind of the template of what the crypto industry has been asking for. Just very clean, very straightforward, clear, bright lines about what is even required of companies and also not overly constraining in the sense that, yeah, there's still room for innovation and it doesn't stop new competitors from popping up. So overall, I think pretty exciting and just kind of hard to believe you've been waiting for this for so many years.

Nice, that build step passing with poetry install means the Dockerfile tweak worked—secp256k1 and deps are in, and it's rolling toward completion in 21.8 seconds, which is solid for a redeploy. Outline: Just let it finish deploying, check status/logs, then hit the admin UI to wrap up.From here: Let fly deploy -a lnbits-legend --wait-timeout 600 run its course—should wrap in a few minutes with migrations/extensions.Check status: fly status -a lnbits-legend for healthy VMs.Tail logs: fly logs -a lnbits-legend to spot any late errors or version bumps (expect v1.2.1 or newer).Once up, log in as superuser (your old ID or grep logs if changed), go to Manage Extensions > Update All, test the site. Should be smooth sailing now.<grok:render type="render_inline_citation"></grok:render>