Skip to content

feat(onvif): Allow configuring the network interface hardware address - #32

Open
nilp0inter wants to merge 1 commit into
Shareed2k:mainfrom
nilp0inter:feat/onvif-hw-address
Open

nilp0inter wants to merge 1 commit into
Shareed2k:mainfrom
nilp0inter:feat/onvif-hw-address

Conversation

@nilp0inter

Copy link
Copy Markdown

Fixes #31

Context

When running multiple reolinkproxy instances across separate network interfaces, each instance has a distinct IP and MAC address. However, GetNetworkInterfaces previously returned a hardcoded hardware address (00:00:00:00:00:00), causing NVRs such as UniFi Protect to detect duplicate network interface identities during enrollment.

Changes

  • Added HWAddress field to ONVIFConfig and onvifConfig defaulting to "00:00:00:00:00:00".
  • Added --onvif-hw-address CLI flag bound to the REOLINK_ONVIF_HW_ADDRESS environment variable.
  • Emitted the configured HWAddress in GetNetworkInterfacesResponse.
  • Added unit tests for default and custom HwAddress in cmd/reolinkproxy/onvif_test.go.
  • Documented REOLINK_ONVIF_HW_ADDRESS and --onvif-hw-address in README.md.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Allow configuring the ONVIF network interface hardware address

1 participant