NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
steveoelliott
Dec 24, 2015Luminary
device eth0 entered promiscuous mode
Hi all, I noticed something strange in my logs today, it never appears to have happened (certainly since March) before. Dec 17 09:15:57 despair kernel: device eth0 entered promiscuous mode ...
mdgm-ntgr
Jan 06, 2016NETGEAR Employee Retired
This probably relates to the IP address conflict detection deamon (ipwatchd).
Have you got your DHCP server (e.g. router) to reserve an I.P. address for the MAC address of the NIC in your NAS? If not, perhaps try that and see if it helps.
steveoelliott
Jan 06, 2016Luminary
Hi,
Thanks for the reply.
No I haven't I assign them statically and exclude them from the range on the DHCP server.
This has always been the case.
Both units have entered and left promiscuous mode at the same time, although it's been on both units since 22nd December:
Dec 17 09:15:57 chaos kernel: device eth0 entered promiscuous mode
Dec 17 09:16:02 chaos kernel: device eth0 left promiscuous mode
Dec 22 14:58:26 chaos kernel: device eth0 entered promiscuous mode
Why would this suddenly change?
- mdgm-ntgrJan 07, 2016NETGEAR Employee Retired
Not sure what would cause this then.
Did you experience any problems at that time? Is having it in promiscuous mode causing problems for you? - steveoelliottJan 07, 2016Luminary
No issues at all at the time or now... However, being in promiscuous mode elevates the CPU since the CPU processes EVERYTHING the NIC hears.
Also being an engineer, I never like something which I cannot explain or know the cause of. Otherwise things have a tendancy to rear their head later...
I'm sure others must have seen this but perhaps completely unaware.
I have just reloaded the secondary CHAOS and currently it is not running in promiscuous mode. So whilst the trigger occured at the same time, it seems it's no longer there. However, as you see on the 17th both devices entered and left this mode at the same time and went back to this mode on 22nd.
So strange....
- steveoelliottJan 27, 2016Luminary
Hi all,
Whilst a reboot solved the issue, I then saw the following appear again:
Jan 20 17:36:35 chaos kernel: device eth0 entered promiscuous mode
Jan 20 17:36:39 chaos kernel: device eth0 left promiscuous mode
Jan 20 17:37:20 chaos kernel: device eth0 entered promiscuous mode
Jan 20 17:37:24 chaos kernel: device eth0 left promiscuous modeThis occured on both NAS's connected to the same network at the same time. Still no idea what may have caused this...
Thanks...
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!