By atom2ueki
Jul 19 03:56:54 App-Docker kernel: [76610.517153] docker0: port 1(veth62a1f2c) entered disabled state
Jul 19 03:56:54 App-Docker kernel: [76610.541447] docker0: port 1(veth62a1f2c) entered disabled state
Jul 19 03:56:54 App-Docker kernel: [76610.542349] device veth62a1f2c left promiscuous mode
Jul 19 03:56:54 App-Docker kernel: [76610.542357] docker0: port 1(veth62a1f2c) entered disabled state
Jul 19 03:59:00 App-Docker kernel: [76736.443964] device veth0fb9910 entered promiscuous mode
Jul 19 03:59:00 App-Docker kernel: [76736.444224] IPv6: ADDRCONF(NETDEV_UP): veth0fb9910: link is not ready
Jul 19 03:59:00 App-Docker kernel: [76736.583446] IPv6: ADDRCONF(NETDEV_CHANGE): veth0fb9910: link becomes ready
Jul 19 03:59:00 App-Docker kernel: [76736.583478] docker0: port 1(veth0fb9910) entered forwarding state
Jul 19 03:59:00 App-Docker kernel: [76736.583483] docker0: port 1(veth0fb9910) entered forwarding state
Jul 19 03:59:15 App-Docker kernel: [76751.584064] docker0: port 1(veth0fb9910) entered forwarding state
Jul 19 04:02:17 App-Docker kernel: [76933.645427] docker0: port 1(veth0fb9910) entered disabled state
Jul 19 04:02:17 App-Docker kernel: [76933.669870] docker0: port 1(veth0fb9910) entered disabled state
Jul 19 04:02:17 App-Docker kernel: [76933.670768] device veth0fb9910 left promiscuous mode
Jul 19 04:02:17 App-Docker kernel: [76933.670776] docker0: port 1(veth0fb9910) entered disabled state
Jul 19 04:02:17 App-Docker kernel: [76933.683763] device veth9e31f0c entered promiscuous mode
Jul 19 04:02:17 App-Docker kernel: [76933.683869] IPv6: ADDRCONF(NETDEV_UP): veth9e31f0c: link is not ready
Jul 19 04:02:17 App-Docker kernel: [76933.683873] docker0: port 1(veth9e31f0c) entered forwarding state
Jul 19 04:02:17 App-Docker kernel: [76933.683877] docker0: port 1(veth9e31f0c) entered forwarding state
Jul 19 04:02:17 App-Docker kernel: [76933.987440] IPv6: ADDRCONF(NETDEV_CHANGE): veth9e31f0c: link becomes ready
Jul 19 04:02:32 App-Docker kernel: [76948.704082] docker0: port 1(veth9e31f0c) entered forwarding state
it seems my server run into promiscuous mode very frequently
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
There is a parameter you can set with ssh clients called KeepAliveInterval. In linux, you can edit either per account client (~/.ssh/config) or per installation (/etc/ssh/ssh_config) and set the value
Host * ServerAliveInterval 30
This howtogeek.com link has more info. Note: not sure how to set it with other clients, like PuTTY, as I haven’t needed it.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.