Vikram

We are seeing the same on our new setup with a mix of bare metal and VM nodes ``` Aug 7 18:10:15 node655 kernel: IPv4: martian source 172.16.64.2 from 172.16.248.0,...

Can it be due to two nic's on bare-metal?

@brb Yes, that is Weave Net IP addr range. What we have noticed is that the martian source warnings flood specifically if one or more node is unhealthy due to...

We did hit this issue again today morning and did cause an outage. Around 2:45 am PT there was a network outage for 4 mins, services recovered quickly as the...

@brb / @bboreham - Any leads on resolving this issue? These are ARP packets and did not get any lead by searching coreDNS related issues.

@murali-reddy - I do have some logs captured from that event except the weave report if that may help. Quick question, we are planning to have coreDNS listen on hostnetwork...

> On the contrary to your observation, 172.200.0.0/24 is not a RFC1918 private IP address I would expect that might cause problem. Good point. Yes, you are right, this was...

@bboreham Thanks! Yes, that jumped out for me too, but didn't have much information to say if that is expected or not. Here is the o/p of the ip addr...

@bboreham Do you think this issue may be related to #3620?

@bboreham - I am not sure if we have the same issue, is there a command that I can run to find out if there are same IP's assigned to...