The Linux Administration group is for the discussion of technical issues technical issues that arise during the administration of Linux systems, including maintaining the operating system and supporting end-user applications.

Try getting a hold of the latest drivers for the NIC cards in question.
It sounds to me that you are wanting to use Active backup policy for
Bonding. In anycase, get a hold of the latest NIC drivers and compile
that to the kernel and get back to me.

I was able to get bonding to work, with Broadcom cards. Pull the
primary nic cable and the backup starts. That works fine. The real
problem happens when you attempt to access the server. Telnet, and SSH
work fine. But, when you use other produces like a web browser it will
not work.

From my research bonding has a number of issues with Broadcom NIC's and
third party products that use ports above 40. Such as http port 80,
webmin port 10000, and etc.

I did. I used webmin that normally uses port 10000 and set it to 38. I
was able to access. Then I did some research and found a university in
Colorado had the say issues with Broadcom card. That led to the BASPLNX
drive for what Broadcom calls teaming. I have yet to get it to work
properly.

It may depend on your configurations... Not knowing all the details of
what is going on with your issue, and just making a random guess... If
your web server is not working but telnet and ssh to the server I would
bet that in the /etc/sshd/sshd_config it is open. See below, and the Web
server Apache? is set to bind to an interface. Also in that I have not
set up MNIC teaming or bonding I have to assume that they each have a
different IP.t and ssh I I have