restart network service will lost routing tables

[miaoshixuan]

I use vxlan backend and set DirectRouting true.when I run service network restart , routing table added by flanneld will lose

Expected Behavior

all routing tables should recover

Current Behavior

routing talble added by flannel will lose

Possible Solution

Steps to Reproduce (for bugs)

1. deploy flannel using vxlan backend and set DirectRouting true
2. restart network service

Context

Your Environment

• Flannel version: v0.10.0
• Backend used (e.g. vxlan or udp): vxlan DirectRouting=true
• Etcd version: 3.2.15
• Kubernetes version (if used): 1.11.2
• Operating System and version: centos 7.4
• Link to your project (optional):

[lihezhong93]

Flannel doesn't monitor the state of host network. You should restart flannel if you restart network

[yuchunyun]

There is automatic checking of routing tables and completion when the backend type is A host-gw. when vxlan default,network interface flannel.1 added, restarting the network will not affect the routing table of this interface.But if Directrouting turned on, the routing table will lost after restart network,I think this situation also needs to be checked like host-gw

[pravin-singhal]

@zhangxiangui40542 any update on this issue - I too have the same issue - flannel routes get lost when used with vxlan with direct routing.

[apakhomov]

It is not only network service restart problem. After interface is suddenly reset/disconnected (any maintenance on host/network, or network "flapped") direct routes are being lost and one is to monitor and maintain this situation manually.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.