bb-eco firewall status
Report whether the host firewall would block bb-eco's inbound UDP
Usage
bb-eco firewall status [options]
Options
| Option | Description |
|---|---|
--csv | Output in CSV format |
--json | Output in JSON format |
--timeout | Override default timeout in milliseconds |
--verbose | Enable verbose/debug output |
-?, -h, --help | Show help and usage information |
Examples
Check whether Windows Firewall will let firmware upgrades through (BOOTP/TFTP need inbound UDP on ports 67–69). A healthy install reports an allow rule covering the executable:
Firewall status: AllowedByRule (C:\Program Files\BB Eco\resources\bb-eco.exe)
With no rule in place, the output warns and says what to do next:
Firewall status: NoRule (C:\Users\jo\bb-eco\bb-eco.exe)
No rule exists. Run 'bb-eco firewall register' from an elevated prompt, or allow the app when the Windows Security Alert appears.
On machines where firewall notifications are suppressed (typical on Windows Server) the warning is stronger — inbound UDP is dropped silently and no prompt will ever appear, so firewall register is the only path.
On macOS and Linux the command reports that Windows Firewall inspection doesn't apply:
bb-eco firewall status
Firewall status: NotApplicable (/usr/local/bin/bb-eco)
The check is read-only — it never binds a socket, so it can't itself trigger a Windows Security Alert.
This page is auto-generated from the live CLI help text. Do not edit by hand — re-run node scripts/gen-cli-reference.mjs after changes. Example sections are maintained in docs/cli-examples/ in the bb-eco repo.