Error Log Messages

[AllonisDave]

My issue is that on a couple of my installations I am seeing lots of messages in the server log that look like this

[2023-03-02 18:57:52.582] W [SPICE-U10001:1612] STUN | stun_message.cpp:132 | Invalid magic cookie found: 02000A68
[2023-03-02 18:57:52.582] E [SPICE-U10001:1612] ICE | ice_port.cpp:629 | Could not parse STUN packet from <DatagramSocket: 0x55860fc3d0, #13, Bound, UDP, Nonblocking>
[2023-03-02 18:57:53.344] W [SPICE-U10001:1612] STUN | stun_message.cpp:132 | Invalid magic cookie found: 02000A18
[2023-03-02 18:57:53.344] E [SPICE-U10001:1612] ICE | ice_port.cpp:629 | Could not parse STUN packet from <DatagramSocket: 0x55860fc3d0, #13, Bound, UDP, Nonblocking>
[2023-03-02 18:57:55.310] W [SPICE-U10001:1612] STUN | stun_message.cpp:132 | Invalid magic cookie found: 02000A18
[2023-03-02 18:57:55.310] E [SPICE-U10001:1612] ICE | ice_port.cpp:629 | Could not parse STUN packet from <DatagramSocket: 0x55860fc3d0, #13, Bound, UDP, Nonblocking>
[2023-03-02 18:57:56.759] W [SPICE-U10001:1612] STUN | stun_message.cpp:132 | Invalid magic cookie found: 02000AE0
[2023-03-02 18:57:56.759] E [SPICE-U10001:1612] ICE | ice_port.cpp:629 | Could not parse STUN packet from <DatagramSocket: 0x55860fc3d0, #13, Bound, UDP, Nonblocking>

Can anyone explain what these messages really mean as they affect server performance? They start showing up a few seconds after the server starts and continue forever. I notice that if I isolate devices on the network I can slow down the frequency of the messages. So it sounds like there are devices on the network broadcasting packets OME does not like.

The messages imply STUN traffic. What ports should I monitor to try to find the problem sources?

If I move the server off the house network on to its own network the errors stop.

These servers are on networks with between 50 to 100 devices of a multitude of types. Any insight is appreciated.

Thanks, Dave...

[getroot]

This means that IceCandidate is receiving strange packets. Try monitoring the port bound to in the configuration file with a packet monitoring tool such as wireshark. It may also be helpful to check that there are no problems when changing the port.

<Bind>
  <Providers>
    <WebRTC>
      <Ice Candidates>
        <IceCandidate>*:10000-10004/udp</IceCandidate>

  ...
  <Publishers>
    <WebRTC>
      <Ice Candidates>
        <IceCandidate>*:10000-10004/udp</IceCandidate>

[AllonisDave]

Thanks for responding so quickly and pointing me in the right direction. The source of the errors packets are Ubiquity access points sending on port 10001. I changed the IceCandidate port range to 10002-10007 and all is good.

Is there anything special about the ports being used? Can they be any ports?

[getroot]

Yes, they can be any ports.