Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consult about route contention #456

Open
gaoxingwang opened this issue Jun 19, 2023 · 0 comments
Open

Consult about route contention #456

gaoxingwang opened this issue Jun 19, 2023 · 0 comments
Labels

Comments

@gaoxingwang
Copy link

When I use the following configuration, restart the network service.

Configuration content:
/etc/sysconfig/network-scripts/ifcfg-eth2

STARTMODE='onboot'
BOOTPROTO='static'
IPADDR='192.9.201.21'
NETMASK='255.255.0.0'
MTU='1450'
DEVICE="eth2"

/etc/sysconfig/network-scripts/route-eth2

ADDRESS0=192.9.0.0
NETMASK0=255.255.0.0
GATEWAY0=192.9.201.200

ADDRESS1=10.10.1.0
NETMASK1=255.255.255.0
GATEWAY1=192.9.201.200

ADDRESS2=12.10.110.0
NETMASK2=255.255.255.0
GATEWAY2=192.9.201.200

Before the commit a71dcfd , routes corresponding to gateway 1 and gateway 2 can be added, but the route corresponding to gateway 0 fails to be added, and error message like :"RTNETLINK answers: File exists".

After the patch is merged, the route corresponding to gateway0 can replace the default route added by the kernel. As a result, the other two routes cannot be added, and the error message is displayed: Error: Nexthop has invalid gateway.

The patch aims to solve the race problem between routes and works successfully.But the failure to add gateway1 and gateway2 directly affects my network. In this case, users should not use the configuration like this? Or do we have a better solution?

@jamacku jamacku added the bug label Jun 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants