Sponsored Content
Operating Systems Linux Red Hat Designating Default Gateway for multiple networks/adapters Post 302344769 by Padow on Monday 17th of August 2009 01:43:49 PM
Old 08-17-2009
Designating Default Gateway for multiple networks/adapters

Hi

I have 4 NIC's connected to my RHEL 5.3 server. Two on one subnet creating bond0, and two on a second subnet which create bond1. Both bonds are set to use DHCP to obtain IP addresses. Here is the config file for ifcfg-bond0:

Code:
DHCP_HOSTNAME=rrnltshckvmx001
DEVICE=bond0
BOOTPROTO=dhcp
DHCPCLASS=
ONBOOT=yes
USERCTL=no

Here are the lines added to /etc/modprobe.conf:

Code:
alias bond0 bonding
options bond0 mode=active-backup miimon=100 primary=eth0
alias bond1 bonding
options bond1 mode=active-backup miimon=100

This is working wonderfully, other than the default gateway is being configured for bond1, when I need it to be configured for the network connected to bond0 instead. Is there an option I can add to either one of these to denote it as the one that the default gateway should be configured for?

Will DHCP always configure the default route for the last configured adapter? If this is the case, I can just reverse the bond0 and bond1 names as a temporary fix, but I'd still like to know if there is a configuration option or a boot time command I could issue to ensure the proper gateway is configured at each boot.
Padow
 

4 More Discussions You Might Find Interesting

1. Linux

GNUGK-How to setup static gateway to gateway routing

Dear Sir I am a newbie in the world of IP telephony. I have been working with Asterisk PBX (SIP) and Cisco Call Manager (MGCP) but now I am learning on how to work GNUGK for H.323 Gatekeeper. I am having a problem, configuring static call routing on GNUGK in the section ... (0 Replies)
Discussion started by: mfondoum
0 Replies

2. Solaris

Multiple networks on same server

If I have 2 interfaces in a server on the same subnet/network does Solaris automatically choose to route packets destined for this network out the first interface. I.e if ce0 and ce1 were on same network ce0 would be chosen as it's first interface? (5 Replies)
Discussion started by: Actuator
5 Replies

3. Ubuntu

Routing trouble between multiple networks

Hi everyone, Hopefully there is someone here that can help me with the problem I got. At my office I have 1 ubuntu firewall/gateway and several networks. On the firewall/gateway I have three network cards, one for internet, one for network 192.168.100.0 and one for network 172.20.1.0 We... (0 Replies)
Discussion started by: thbor83
0 Replies

4. UNIX for Beginners Questions & Answers

Inconsistency between RedHat 6.5 global gateway and single gateway leads to loss of default gateway

Dear friends I use RedHat 6.5, which sets the gateway in the configuration file / etc / sysconfig / network as GATEWAY = 192.168.1.26, and the gateway in the configuration file / etc / sysconfig / network-scripts / ifcfg-eth11 as GATEWAY = 192.168.1.256. The two gateways are different.... (6 Replies)
Discussion started by: tanpeng
6 Replies
BOND2TEAM(1)						  Bonding to Team conversion tool					      BOND2TEAM(1)

NAME
bond2team -- Converts bonding configuration to team SYNOPSIS
bond2team [options] DESCRIPTION
bond2team is a tool to convert bonding options to team trying as much as possible to keep the original functionality. The resulting files are saved in a temporary directory using ifcfg style by default. In the case of converting an ifcfg file, it translates the bonding options to team, preserving all other options. In that case, it converts the respective slave ifcfg files to team port, pre- serving all their other options too. In case of converting from given bonding options in the command line, the tool can use the specified ports as team ports. OPTIONS
--master <interface> Specify the interface name or ifcfg file to convert. If the interface name is specified, the tool will look at /etc/sysconfig/network-scripts/ for the respective ifcfg file. --rename <interface> This is a convenient option to replace the original interface name by the specified name. For instance, if --master specifies bond0, it is possible to use --rename team0 to change the final interface name to team0. --ifcfg Set the output format to ifcfg config style. [default] --json Set the output format to JSON style. See teamd.conf(5) for further details. --bonding_opts '<bonding options>' Specify the bonding options to be converted instead of reading them from the ifcfg file. --port <interface> Set the specified interface as a team port. --configdir <directory> Change the ifcfg configuration path from /etc/sysconfig/network-scripts to the specified <directory>. --outputdir <directory> Set the output directory to <directory>. --stdout Print the result to the screen instead of writing to files. --debug Increase the debugging level. --quiet Disallow any messages to be printed to console. --version Print tool version to console and exit. --help Print help text to console and exit. --examples Print common usage examples to console and exit. EXAMPLES
To convert the current 'bond0' ifcfg configuration to team ifcfg: # bond2team --master bond0 To convert the current 'bond0' ifcfg configuration to team ifcfg renaming the interface name to 'team0'. Caution : firewall rules, alias interfaces, etc., that might be tied to the original interface name can break after the renaming because the tool will only change the ifcfg file, nothing else. # bond2team --master bond0 --rename team0 To convert given bonding parameters with ports without any ifcfg: # bond2team --bonding_opts 'mode=1 miimon=500 primary=eth1 primary_reselect=0' --port eth1 --port eth2 --port eth3 --port eth4 For more examples, see the option --examples. CAVEATS
The tool will not convert any other configuration which might be tied to the current setup. For instance, firewall rules, alias interfaces, bridges, and so on. AUTHOR
Flavio Leitner is the original author of the tool. Jiri Pirko is the original author and current maintainer of libteam. SEE ALSO
teamd(8), teamdctl(8), teamd.conf(5), teamnl(8) libteam 2013-07-18 BOND2TEAM(1)
All times are GMT -4. The time now is 07:14 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy