Closed gaoxingwang closed 1 year ago
Recent Developments:
The problem has been fixed.
Communicated with the kernel community and confirmed that the ipvlan module is defective. The up event in the kernel does not trigger the ipvlan status update. Submit a patch to add the up notification event to modify the ipvlan status.
Link to the kernel patch: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=57fb346cc7d0
Thank you for update. It's good to hear, that issue has been resolved.
Config bonding and ipvlan interface. After
ifdown bond0;ifup bond0
, ipvlan interface cannot recover correctly. It seems that ifdown-eth script deletes the slave interface byecho "-${DEVICE}" > /sys/class/net/${MASTER}/bonding/slaves 2>/dev/null
, and ipvlan interface will not recover from NO-CARRIER state. It does not happen when replacingifdown bond0;ifup bond0
byifconfig bond0 down;ifconfig bond0 up
.To reproduce the problem, perform the following steps:
Step 1: Configure bond0 and its slave by using the following file:
ifcfg-bond0 file:
config slave ifcfg-ens8 file:
restart network service:
Step 2: Run the following command to add ipvlan:
Step 3:
result: ipvlan came to be NO-CARRIER