首页 > 代码库 > 云主机配置Docker Bridge，在重新颠倒配置，重启网卡，导致物理网卡不正常工作
云主机配置Docker Bridge，在重新颠倒配置，重启网卡，导致物理网卡不正常工作
1，物理机配置,eth0,eth1 配置bonding，bonding 作为bridge 物理网卡，在生成bond0 作为物理机管理口
2，虚拟机配置，eth1 作为bridge 虚拟网卡br500, eth0 配置正常网卡IP
3, 因eth0 为WEB 段， eth1 为DB 段，需颠倒配置，重启网卡，出现以下问题
4，相关错误日志：
an 3 14:46:41 localhost kernel: device vnet0 entered promiscuous mode Jan 3 14:46:41 localhost kernel: br100: port 2(vnet0) entering forwarding state Jan 3 14:46:41 localhost kernel: device vnet1 entered promiscuous mode Jan 3 14:46:41 localhost kernel: br101: port 2(vnet1) entering forwarding state Jan 3 14:46:56 localhost kernel: __ratelimit: 23 callbacks suppressed Jan 3 14:46:56 localhost kernel: kvm: 27962: cpu0 unhandled wrmsr: 0x391 data 2000000f Jan 3 14:46:56 localhost kernel: kvm: 27962: cpu2 unhandled wrmsr: 0x391 data 2000000f Jan 3 14:46:56 localhost kernel: br100: port 2(vnet0) entering forwarding state Jan 3 14:46:56 localhost kernel: br101: port 2(vnet1) entering forwarding state Jan 3 14:50:02 localhost kernel: __ratelimit: 91391 callbacks suppressed Jan 3 14:50:02 localhost kernel: vnet0: received packet with own address as source address Jan 3 14:50:02 localhost kernel: vnet0: received packet with own address as source address Jan 3 14:50:02 localhost kernel: vnet0: received packet with own address as source address Jan 3 14:50:02 localhost kernel: vnet0: received packet with own address as source address Jan 3 14:50:02 localhost kernel: vnet0: received packet with own address as source address Jan 3 14:50:02 localhost kernel: vnet0: received packet with own address as source address Jan 3 14:50:02 localhost kernel: vnet0: received packet with own address as source address Jan 3 14:50:02 localhost kernel: vnet0: received packet with own address as source address Jan 3 14:50:02 localhost kernel: vnet0: received packet with own address as source address Jan 3 14:50:02 localhost kernel: vnet0: received packet with own address as source address
解决办法： 1，在重启网卡之前，需要删除老的bridge 配置 ifconfig br500 down brctl delbr br500 ifdown eth1 systemctl stop network.service systemctl start network.service 2, 直接重启云主机
本文出自 “欢迎评论，欢迎点赞” 博客，请务必保留此出处http://swq499809608.blog.51cto.com/797714/1598870
云主机配置Docker Bridge，在重新颠倒配置，重启网卡，导致物理网卡不正常工作
声明：以上内容来自用户投稿及互联网公开渠道收集整理发布，本网站不拥有所有权，未作人工编辑处理，也不承担相关法律责任，若内容有误或涉及侵权可进行投诉： 投诉/举报 工作人员会在5个工作日内联系你，一经查实，本站将立刻删除涉嫌侵权内容。