LinuxQuestions.org
Latest LQ Deal: Complete CCNA, CCNP & Red Hat Certification Training Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Fedora
User Name
Password
Fedora This forum is for the discussion of the Fedora Project.

Notices


Reply
  Search this Thread
Old 07-16-2007, 12:00 PM   #1
joshv
LQ Newbie
 
Registered: Apr 2007
Posts: 8

Rep: Reputation: 0
FC7 Bonding and VLANs oh boy!


Could use some help here - I have scoured the NET and can't find anyone else stupid enough to try the configuration I am working on, so I'll bleed here for a while.

I am trying to configure Fedora Core 7 (FC7) with Vmware Server (free) version 1.0.3. The tricky part is that I am trying to bond eth0 and eth1 - which have VLAN's over the trunk (let's say VLAN 111 and VLAN 113).

All was well, found a few tips around and managed to get bond0 up with interfaces for bond0.111 and bond0.113. Ping tests were good and I was very happy. Until I installed VMWare and found out that they have a long standing bug preventing it from using interface names over 8 characters. So it was truncating bond0.111 to bond0.11 and that just won't work because it turns it into a different VLAN.


So, now I am trying to rename bond0 to b0 - allowing me to shorten the interface names to something the folks at VMWare see fit to deal with. I ended up rebuilding the FC7 install completely because I couldn't figure out how to make bond0 disappear and it seemed to be conflicting with b0. The bond appears to be working now, but I can't get the VLAN interfaces to start automatically.

I'll post my different network related file configurations below:

/etc/sysconfig/network:
IPV6INIT=no
NETWORKING_IPV6=no
NETWORKING=yes

/etc/modprobe.conf:
alias b0 bonding
install b0 /sbin/modprobe bonding -o b0 miimon=100 mode=0
alias net-pf-10 off

/etc/sysconfig/network-scripts/ifcfg-eth0:
DEVICE=eth0
BOOTPROTO=none
MASTER=b0
ONBOOT=yes
USERCTL=no
SLAVE=yes
TYPE=Ethernet

/etc/sysconfig/network-scripts/ifcfg-eth1:
DEVICE=eth1
BOOTPROTO=none
ONBOOT=yes
MASTER=b0
USERCTL=no
SLAVE=yes
TYPE=Ethernet

/etc/sysconfig/network-scripts/ifcfg-b0:
ONBOOT=yes
DEVICE=b0
TYPE=Bonding
BOOTPROTO=none
USERCTL=no

/etc/sysconfig/network-scripts/ifcfg-b0.111:
DEVICE=b0.111
BOOTPROTO=none
NETWORK=10.1.11.0
NETMASK=255.255.255.0
IPADDR=10.1.11.20
GATEWAY=10.1.11.1
ONBOOT=yes
VLAN=yes
TYPE=Ethernet

/etc/sysconfig/network-scripts/ifcfg-b0.113:
ONBOOT=yes
DEVICE=b0.113
BOOTPROTO=none
VLAN=yes
TYPE=Ethernet


The error I receive after a "service network restart" is:

Bringing up loopback interface: OK
Bringing up interface b0: OK
Bringing up interface b0.111: Device b0.111 does not seem to be present, delaying initialization: FAILED
Bringing up interface b0.113: Device b0.111 does not seem to be present, delaying initialization: FAILED


Now, if after boot I do a "vconfig add b0 111" and "vconfig add b0 113" everything works fine until the next reboot. I guess I could put these commands in the rc.local, but it really screws with VMWare to have the interfaces down when you start the VMWare server service.

I am hoping someone out there has some ideas, places to look, or has seen this behavior before from FC.

Any help at all is appreciated. TIA!

BTW, why hasn't someone written a GUI for FC that configures bonding and VLAN's yet? Or am I just missing something here?


-Josh
 
Old 07-18-2007, 09:50 AM   #2
lord-fu
Member
 
Registered: Apr 2005
Location: Ohio
Distribution: Slackware && freeBSD
Posts: 676

Rep: Reputation: 30
Hi vmware-server will not allow you to use VLAN's you need ESX for that.
Did you find a way to work around that?

I have never done bonding, vlans yes, but does it not show as a device somewhere (/etc/sysconfig/network/devices /etc/sysconfig/network-scripts)? I see your out put above of devices, did deleting the file not allow the removal?

Sorry I could not be of more help.

Last edited by lord-fu; 07-18-2007 at 09:56 AM.
 
Old 07-19-2007, 09:16 AM   #3
joshv
LQ Newbie
 
Registered: Apr 2007
Posts: 8

Original Poster
Rep: Reputation: 0
VLAN's do work in VMWare Free Server on FC. You can setup NAT or Bridged (which is basically like a virtual switch in ESX) networking to any interface on FC (/etc/sysconfig/network-scripts). In fact, if you notice in my config above b0.113 (VLAN 113) is present and it doesn't have an IP address assigned (neither DHCP nor static). So the host can't actually see VLAN 113 but I am bridging it to a "Virtual network" which works fine for the VM's. In the VM, I can only send it one VLAN per NIC - but that suits my needs. Actually I think that is a limitation in ESX as well if I am not mistaken (they didn't used to support trunking at the VM NIC level).

My only problem with the Free Server is that the Interface names can not be longer than 8 characters. Which then lends itself to a problem with FC apparently not being happy about having a bond called anything but "bond0".

On your question about ability to delete....yes, I thought deleting the files in /etc/sysconfig/network-scripts and a reboot would have done the trick, and maybe it did. However a couple of utilities still said "bond0" was present so I rebuilt the OS. Strangely enough, the VMWare Server vmware-config.pl still sees "bond0" as an available interface even now - but I have never typed "bond0" into the configs on this box (post rebuild). So, something in the FC code is making that assumption (I see it in the gui network configs for FC as well) when I build the bond - and it is wrong (IMHHO).
 
Old 07-19-2007, 10:16 AM   #4
lord-fu
Member
 
Registered: Apr 2005
Location: Ohio
Distribution: Slackware && freeBSD
Posts: 676

Rep: Reputation: 30
Hi, I am experienced with vmware server and somewhat experienced with F6 and vlans. However I have never done bonding. Thats why I asked becasue we have setup similar here in our test lab where I have tried(about 5hrs worth) before on trying to get a vlan'ed interface eth1.1 for example to bridge(v switch) to vmnet0 for example, and it would never work. And upon researching this I came to find out that vmware server free version does not support vlan'ed interfaces. Well if you got it to work , kudos on that end.

As for bond0 still showing up post rebuild, unless you have already set that up on FC after the build the only reason I could think of is that you are still using the same make file possibly for the vmware install? Does a make clean work in this case? Sorry I cannot be of more help.
[edit] tried a make clean, don't know what I was thinking sorry...Are you using the same un-tarred folder for the install, could you try to extract a new vmware-server-distrib dir. Again sorry I cant be of more help.[/edit]

Last edited by lord-fu; 07-19-2007 at 10:22 AM.
 
Old 07-19-2007, 10:55 AM   #5
joshv
LQ Newbie
 
Registered: Apr 2007
Posts: 8

Original Poster
Rep: Reputation: 0
Yes, I am using the Boot ISO for network based install for FC7 (from Fedora). I am not rebuilding the kernel. No recompile - everything I need comes out of the box.
 
Old 07-19-2007, 11:01 AM   #6
joshv
LQ Newbie
 
Registered: Apr 2007
Posts: 8

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by lord-fu
Hi, I am experienced with vmware server and somewhat experienced with F6 and vlans. However I have never done bonding. Thats why I asked becasue we have setup similar here in our test lab where I have tried(about 5hrs worth) before on trying to get a vlan'ed interface eth1.1 for example to bridge(v switch) to vmnet0 for example, and it would never work. And upon researching this I came to find out that vmware server free version does not support vlan'ed interfaces. Well if you got it to work , kudos on that end.[/edit]

If you ever want to try it again....my configs are in this thread for 2 bonded trunks (eth0 and eth1 to b0). I can then setup whatever VLAN I want as an interface (e.g. b0.111) and bridge that to vmnetX. Works fine. Don't even have to give the FC interface an IP, just make sure it is ONBOOT=yes, BOOTPROTO=none.

My workaround for this entire thing is to add to the /etc/rc.local:

vconfig add b0 111
vconfig add b0 113
ifup b0.111
ifup b0.113

Which seems to be working fine except for the errors at boot mentioned above.
 
Old 07-19-2007, 11:47 AM   #7
joshv
LQ Newbie
 
Registered: Apr 2007
Posts: 8

Original Poster
Rep: Reputation: 0
Incidenly, the "vconfig" statement I am putting in the /etc/rc.local is exactly the same thing that VLAN=yes if the ifcfg file is supposed to do as I understood things. Maybe I should submit a bug to the Fedora guys.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
SNAT between VLANS garnser Linux - Networking 4 03-05-2007 09:09 AM
VLANS communications metallica1973 Linux - Networking 6 09-10-2006 04:17 PM
Switches and VLANS metallica1973 Linux - Networking 2 04-26-2006 06:12 PM
VLANs understanding twantrd General 3 12-13-2005 03:44 AM
Arpwatch across VLANS? TotalDefiance Linux - Software 0 09-15-2005 10:19 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Fedora

All times are GMT -5. The time now is 04:03 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration