Skip to content
Discussion options

You must be logged in to vote

Claude's suggestion did the trick:

curl -X PUT http://<device-ip>/api/v1/logs-udp-destination \
  -H "Content-Type: application/json" \
  -d '{"destination":"0.0.0.0"}'

However, how is this "standard" behaviour? Why flood the customers network with multicast syslog UDP packets. Also here Claude had a possible explanation:

  • Before v2.0.1, UDP logging sent to 239.255.255.250:514 (multicast) by default, but only on dev builds. Commit edf6682 made it opt-in for both dev and prod: with no destination set, the device stays silent.
  • The catch: the old firmware also saved that multicast address to NVS (udp_log_ns) on first boot. So a device that once ran a dev build before v2.0.1 still multicast…

Replies: 2 comments 2 replies

Comment options

You must be logged in to vote
1 reply
@jibrilsharafi
Comment options

Comment options

You must be logged in to vote
1 reply
@jibrilsharafi
Comment options

Answer selected by steiny2k
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants