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

Introduce PEERROUTES directive #98

Open
deekej opened this issue May 9, 2017 · 0 comments
Open

Introduce PEERROUTES directive #98

deekej opened this issue May 9, 2017 · 0 comments
Assignees

Comments

@deekej
Copy link
Contributor

deekej commented May 9, 2017

Right now we are able to force network scripts not to obtain DNS servers from DHCP server (if configured in a specific way). However, we are not able to force network scripts not to obtain routes fro DHCP server.

We should start recognize a new directive PEERROUTES in the future, as NetworkManager does.

@deekej deekej self-assigned this May 9, 2017
@deekej deekej added this to the initscripts-10.0 milestone May 9, 2017
@deekej deekej removed this from the initscripts-10.0 milestone Jun 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant