2DS continually tries to send packets to 0.0.0.0?

[tls]

The 2DS firmware appears to have some buggy behavior on the network. It's trying to send UDP packets to 0.0.0.0 -- and these are _not_ DHCP packets. I discovered this when wondering why my firewall was sending so many ICMP messages out the interface attached to the Envisalink:

15:59:11.626316 IP 192.168.102.2.2201 > 184.106.215.218.4021: UDP, length 208
15:59:11.668951 IP 184.106.215.218.4021 > 192.168.102.2.2201: UDP, length 48
15:59:13.112758 IP 192.168.102.2.2202 > 0.0.0.0.3061: UDP, length 32
15:59:13.112796 IP 192.168.102.1 > 192.168.102.2: ICMP 0.0.0.0 udp port 3061 unreachable, length 36
15:59:15.612937 IP 192.168.102.2.2202 > 0.0.0.0.3061: UDP, length 32
15:59:15.612956 IP 192.168.102.1 > 192.168.102.2: ICMP 0.0.0.0 udp port 3061 unreachable, length 36
15:59:19.113422 IP 192.168.102.2.2202 > 0.0.0.0.3061: UDP, length 32
15:59:19.113440 IP 192.168.102.1 > 192.168.102.2: ICMP 0.0.0.0 udp port 3061 unreachable, length 36
15:59:23.613825 IP 192.168.102.2.2202 > 0.0.0.0.3061: UDP, length 32
15:59:23.613846 IP 192.168.102.1 > 192.168.102.2: ICMP 0.0.0.0 udp port 3061 unreachable, length 36

The first two packets are normal traffic. But what's this business sending UDP messages to 0.0.0.0:3061? 0.0.0.0 is "this host, this network" -- it should not be used as a destination on the wire.

[GrandWizard]

It's a bug in 1.4.X, it is trying to contact a secondary server that isn't defined. It is fixed in the upcoming 1.5.X release.