Re: wm DAD duplicate address

[Joerg Sonnenberger <joerg%bec.de@localhost>]

On Tue, Feb 21, 2017 at 12:25:00PM +0000, Patrick Welche wrote:
> wm1: flags=0x8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>         capabilities=7ff80<TSO4,IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx>
>         capabilities=7ff80<TCP4CSUM_Tx,UDP4CSUM_Rx,UDP4CSUM_Tx,TCP6CSUM_Rx>
>         capabilities=7ff80<TCP6CSUM_Tx,UDP6CSUM_Rx,UDP6CSUM_Tx,TSO6>
>         enabled=3f80<TSO4,IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx,TCP4CSUM_Tx>
>         enabled=3f80<UDP4CSUM_Rx,UDP4CSUM_Tx>
>         ec_capabilities=7<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU>
>         ec_enabled=0
>         address: 00:15:17:1a:48:1d
>         media: Ethernet autoselect (1000baseT full-duplex,flowcontrol,rxpause,txpause)
>         status: active
>         inet 10.0.0.35/24 broadcast 10.0.0.255 flags 0x0
>         inet 169.254.95.254/16 broadcast 169.254.255.255 flags 0x0
>         inet 10.100.0.62/24 broadcast 10.100.0.255 flags 0x0
>         inet6 fe80::323f:12f5:4624:c706%wm1/64 flags 0x0 scopeid 0x3
> 
> No 0.0.0.0 over there?

dhcpcd running? I think the DAD check should be explicitly disabled for
0.0.0.0.

Joerg