[CentOS] Re: Is there a way to save the routing table permanently?
rob.townley at gmail.com
Thu Aug 21 09:31:38 UTC 2008
On Wed, Aug 20, 2008 at 7:52 AM, Filipe Brandenburger
<filbranden at gmail.com>wrote:
> On Wed, Aug 20, 2008 at 01:22, Rob Townley <rob.townley at gmail.com> wrote:
> > two NICs each that would use two different gateways,
> If you are configuring default gateways on each interface, you are
> probably doing something wrong.
> The only reason why you would want to do that is to balance your
> outgoing traffic between the two NICs, and this is better accomplished
> with bonding interfaces.
Bonding would defeat my purpose for this. My registrar requires two dns
servers on two different IP addresses, but i only wanted to use one machine
for now. The machine has two NICs that connect out through the same cable
modem. One behind a soho firewall, one direct.
> > ifup would not process either route.ethX nor ethX.route
> > - at least not enough for it to show in route. Had to set
> > the routes in /etc/rc.local.
> I fail to see why SELinux would make any difference on that. Can you
> describe your issue better? What is the configuration you tried to set
> up, and why didn't it work? What version of CentOS are you using, 4 or
> 5? What is in /var/log/messages and /var/log/audit/audit.log when you
> try to bring the interface up?
The interfaces would come up, the point was that that system-config-network
would not keep the static information for the two NICs after a reboot. So
when the machine was rebooted, some part of IP, SM, GW, NS disappeared or
reverted back to DHCP even though it was explicitly set to static. I was
using CentOS 5.0 / 5.1 when i had most problems. No entries would have
appeared in the logs. I modified ifup-route to add logging to it directly
and believe it was never called. Maybe i will have to upgrade the machine
so i can run both the TUI and GUI more and monitor all files changed by
both. Further, i turned off NetworkManager to get much further in keeping
static ip setup.
Couldn't tell you much about why seLinux may have caused problems except
that maybe there were mdac labels on files that broke some part of
system-config-network keeping static routes and dns servers. I just
remember that uninstalling seLinux got me much much further on a different
machine when it came to static settings for multiple NICs. Much Further.
> CentOS mailing list
> CentOS at centos.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the CentOS