Can we PLEASE quiet down "vmnet-natd"?!

[kennycrudup]

My syslogs are getting spammed by vmnet-natd on average every 30 seconds. Is there a reason this output should be displayed (and not say, subject to a "debug" flag)? It's by far the most verbose repeating message in my logs

----

Mar 1 15:31:44 xps-9320 vmnet-natd: RTM_NEWADDR: index:9, addr:192.168.126.36
Mar 1 15:31:44 xps-9320 vmnet-natd: RTM_NEWADDR: index:7, addr:192.168.126.189
Mar 1 15:32:12 xps-9320 vmnet-natd: RTM_NEWADDR: index:9, addr:192.168.126.36
Mar 1 15:32:12 xps-9320 vmnet-natd: RTM_NEWADDR: index:7, addr:192.168.126.189
Mar 1 15:33:11 xps-9320 vmnet-natd: RTM_NEWADDR: index:9, addr:192.168.126.36
Mar 1 15:33:11 xps-9320 vmnet-natd: RTM_NEWADDR: index:9, addr:192.168.126.36
Mar 1 15:33:11 xps-9320 vmnet-natd: RTM_NEWADDR: index:7, addr:192.168.126.189
Mar 1 15:33:44 xps-9320 vmnet-natd: RTM_NEWADDR: index:9, addr:192.168.126.36
Mar 1 15:33:44 xps-9320 vmnet-natd: RTM_NEWADDR: index:7, addr:192.168.126.189
Mar 1 15:34:04 xps-9320 vmnet-natd: RTM_NEWADDR: index:9, addr:192.168.126.36
Mar 1 15:34:05 xps-9320 vmnet-natd: RTM_NEWADDR: index:7, addr:192.168.126.189
Mar 1 15:34:46 xps-9320 vmnet-natd: RTM_NEWADDR: index:9, addr:192.168.126.36
Mar 1 15:34:46 xps-9320 vmnet-natd: RTM_NEWADDR: index:7, addr:192.168.126.189
Mar 1 15:35:07 xps-9320 vmnet-natd: RTM_NEWADDR: index:9, addr:192.168.126.36
Mar 1 15:35:07 xps-9320 vmnet-natd: RTM_NEWADDR: index:7, addr:192.168.126.189
Mar 1 15:36:05 xps-9320 vmnet-natd: RTM_NEWADDR: index:9, addr:192.168.126.36

---

$ gunzip --force --stdout /var/log/syslog* | fgrep -I vmnet-natd | wc -l
728

[NateNateNAte]

Yeah, that's been a problem in many different forum posts over the last few years. It screams that the virtual network is constantly switching VM addresses and resetting over and over.  There has yet to be a formal or final solution.  I've seen some that remove and re-add the virtual network interface - but that was aimed at reducing the CPU load of the running vmnet-natd service...There have been tickets submitted to VMware on this topic but I haven't seen any response there either.  

Most of the above was with Fusion.  Are you experiencing this in Fusion or somewhere else?

[kennycrudup]

> Are you experiencing this in Fusion or somewhere else?

Workstation Pro, and in every version I've had for at least a decade now.

I've had to resort to killing off "vmnet-natd" if I'm not NATing my HV instance, but seriously this should be a debug-level log print; problem solved.