| Summary: | Adding better route handling to /etc/init.d/net.eth0 and an example to /etc/conf.d.net | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Mitchell <mns6070> |
| Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
| Status: | RESOLVED INVALID | ||
| Severity: | enhancement | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
the modified /etc/init.d/net.eth0 file
the modified /etc/conf.d/net file |
||
Created attachment 29852 [details]
the modified /etc/init.d/net.eth0 file
Created attachment 29853 [details]
the modified /etc/conf.d/net file
How does this affect routing in the system? I.e. what is the point of attaching the route directly to an interface instead of letting it float? Are there cases where you wouldn't want it to be directly associated with the interface? Presently /etc/conf.d/net lets you specify when this will occur and when it won't. I.e. you can put "-dev eth0" in your routes_eth0 variable. If I apply your patch then I decrease the flexibility of the system. So I'm closing this bug "invalid". Please re-open if you believe you have sufficient rationale for this change. |
I changed line 130 in the /etc/init.d/net.eth0 file to read "/sbin/route add ${routes_IFACE[i] -dev ${IFACE}". This way the static route is applied to interface that called it. I also added a line to /etc/conf.d/net demostrating how static routes can be easily added to an interface. Reproducible: Always Steps to Reproduce: