Trunking two network cards on Ubuntu Server 9.04

I'm trying to trunk two network cards together. I have three network cards in this server; eth0 is onboard, and eth1/eth2 is meant to be trunked. I have a test lab setup at the moment with almost an identical setup on a computer as the server has.

I found a website explaining how to do this and for the most part it makes sense but theres still a few unanswered questions. Here's a link: http://emcken.dk/weblog/archives/274-trunk-port-in-vmware-used-by-ubuntu-server-hardy.html

I followed this and here's what my config file looks like:
auto eth1.2
iface eth1.2 inet static
        address 192.168.1.6
        netmask 255.255.255.0

My question is how does the computer know that I would like to trunk eth1 & eth2 and leave eth0 out of it?
supanaturalAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

LunarNRGCommented:
I'm not 100% sure, but the instructions at the link you provided, seem to be doing the _inverse_ of what you actually want. In other words, instead of trunking(/bonding) two nics, they seem to be assigning another ip address to the same nic.

These instructions are a little old, but they should get you where you want to go ...
http://www.howtoforge.com/network_bonding_ubuntu_6.10



0
supanaturalAuthor Commented:
The problem is that that's ubuntu 6.04. I don't know if it has changed a lot since then. I'm running 9.04.

When I use the setup:
auto eth1.2
iface eth1.2 inet static
        address 192.168.1.6
        netmask 255.255.255.0
auto eth2.2
iface eth2.2 inet static
        address 192.168.1.6
        netmask 255.255.255.0

It doesn't work. It does work if I disable trunking on my switch which is weird.
0
LunarNRGCommented:
Actually the instructions are for ubuntu 6.10, and I doubt that bonding config has changed all that much. FWIW, I used these instructions to bond nics w/ a debian server just a few months ago.

Good Luck!
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

LunarNRGCommented:
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
supanaturalAuthor Commented:
I'm having a problem with these instructions. I posted the steps in the code snippet that I'm having a hard time with. In /etc/modprob.d, I have 5 files that start with the word blacklist and thats it.

Also, I'm running x64 architecture if that helps
1. Now append the following items to your aliases file:
 
pico /etc/modprob.d/aliases
 
2. Next, append the following items to your i386 file:
 
pico /etc/modprob.d/arch/i386

Open in new window

0
supanaturalAuthor Commented:
I like that article. I'm still having the same problem though with: /etc/modprobe.d/arch/i386

Here's all the files i see when I go to that folder:
root@Hypervisor2:/etc/modprobe.d# ls
blacklist-ath_pci.conf      
blacklist-firewire.conf
blacklist-watchdog.conf
blacklist.conf
blacklist-framebuffer.conf  

Open in new window

0
LunarNRGCommented:
I'm pretty sure you can just create a file in /etc/modprobe.d and include the directives alluded to in the instructions. I don't think the name of the file matters, but it should have the .conf extension, or so it seems.

See also, http://ubuntuforums.org/showthread.php?t=1147741
0
supanaturalAuthor Commented:
Cool, I have it working (sort of). When port trunking is disabled on my switch, it works, but when port trunking is enabled on my switch it stops working. Is that normal? Is there a way to test that I do infact have a 2gb line working?
0
LunarNRGCommented:
"""
When port trunking is disabled on my switch, it works, but when port trunking is enabled on my switch it stops working. Is that normal?
"""
I don't know. But, I'd kind of expect the opposite.

Can you elaborate on what you mean by "it stops working"? dead link?

If you post the make/model of your switch, we can have a look at the manual. While you're at it, post the result of 'cat /proc/net/bonding/bond0' (replace bond0 with the name you gave the bonded interface, if different).

"""
Is there a way to test that I do infact have a 2gb line working?
"""

I didn't need to bond for performance, so it's unfamiliar territory. But in this case, you may find these articles more your ... um, er ... 'speed', and suggest testing with the iperf package ... seems reasonable.

http://www.enterprisenetworkingplanet.com/nethub/article.php/3696561
http://www.enterprisenetworkingplanet.com/nethub/article.php/3697756


0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux Distributions

From novice to tech pro — start learning today.