On Mon, Oct 31, 2005 at 08:28:44AM -0500, Robin Mordasiewicz wrote:
> Ok, but what about the rules,
> ie. When issueing the following commands I understand how I can use the
> route-device file, but which file do edit to deal with the "ip rule add"
> line ?
>
> /sbin/ip rule delete from ${IPADDR} lookup ${TABLE}
> /sbin/ip rule add from ${IPADDR} table ${TABLE} priority ${PRIORITY}
If you are willing to do some packaging work, you might want to look
at /etc/net, which has been developed for the ALTLinux distribution:
http://etcnet.org/
/etc/net represents a new approach to Linux network configuration
tasks. Inspired by the limitations of traditional configuration
subsystems, /etc/net provides builtin support for:
* configuration profiles
* interface name management
* removable devices
* full iproute2 command set
* interface dependencies resolution
* QoS configuration framework
* firewall support
/etc/net provides support for the following interface types:
* Ethernet
* WiFi (WEP)
* IPv4/IPv6 tunnels
* PSK IPSec tunnels
* VLAN
* PLIP
* Ethernet bonding and bridging
* traffic equalizer
* usbnet
* PPP (PPtP, PPPoE)
* DVB (SkyStar-2, Pent@NET, Pent@VALUE)
Due to its modular design, support for new interface types can be added
without overall design changes. /etc/net consists of core scripts (stable)
and GUI configurator (development). Both parts are licensed under GPL.
To get this packaged properly under Fedora, you'll want to hack up the
initscripts package spec file to split off the networking parts into a
subpackage (call it netscripts or whatever) and then package up etcnet as a
replacement. I filed an RFE for subpackage separation a while ago,
but Buill Nottingham nixed the idea:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145787
Regards,
Bill Rugolsky
> --
> fedora-list mailing list
> fedora-list@xxxxxxxxxx
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
