LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices

Reply
 
Search this Thread
Old 10-30-2008, 12:24 PM   #1
pauledwards03
Member
 
Registered: Dec 2006
Distribution: Slackware 12.1
Posts: 94

Rep: Reputation: 15
bonding two interfaces slackware 12.1


Does anyone know how to do this in slackware but without WPA and WEP instead? Slackware has no /etc/interfaces file.
 
Old 11-03-2008, 12:03 PM   #2
pauledwards03
Member
 
Registered: Dec 2006
Distribution: Slackware 12.1
Posts: 94

Original Poster
Rep: Reputation: 15
The goal is to be able to work while on the docking station through the wire, and be able to disconnect from the docking station and start using the wireless with no interruption. eth1 is a wireless interface using the ipw2200 module. eth0 is wired using e100. I recompiled my kernel to include bonding support and also recompiled my network drivers as modules.

I looked around online and found

http://www.linuxfoundation.org/en/Ne...l_with_bonding

I followed this and came up with the following configuration.

/etc/rc.d/rc.bond:

Code:
#!/bin/sh
 #
        case "$1" in
          'start')
            echo "start bond0"
            modprobe bonding mode=broadcast miimon=100
            ifconfig bond0 up
            ifconfig bond0 10.151.33.45 netmask 255.255.240.0 hw ether 00:16:3e:aa:aa:aa  up
	    ifenslave bond0 eth0
            ifenslave bond0 eth1
          ;;
          'stop')
            ifconfig bond0 down
            rmmod bonding
          ;;
          *)
            echo "Usage: $0 {start|stop}"
          ;;
        esac
Current ifconfig:

Code:
bond0     Link encap:Ethernet  HWaddr 00:16:3e:aa:aa:aa  
          inet addr:10.151.33.45  Bcast:10.151.47.255  Mask:255.255.240.0
          inet6 addr: fe80::216:3eff:feaa:aaaa/64 Scope:Link
          UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
          RX packets:3698 errors:0 dropped:6 overruns:0 frame:0
          TX packets:2824 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:2276400 (2.1 MiB)  TX bytes:303086 (295.9 KiB)

eth0      Link encap:Ethernet  HWaddr 00:16:3e:aa:aa:aa  
          inet addr:10.151.33.42  Bcast:10.151.47.255  Mask:255.255.240.0
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:2890 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1411 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:2197335 (2.0 MiB)  TX bytes:155203 (151.5 KiB)

eth1      Link encap:Ethernet  HWaddr 00:16:3e:aa:aa:aa  
          inet addr:10.151.33.41  Bcast:10.151.47.255  Mask:255.255.240.0
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:808 errors:0 dropped:6 overruns:0 frame:0
          TX packets:1413 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:79065 (77.2 KiB)  TX bytes:147883 (144.4 KiB)
          Interrupt:9 Base address:0x6000 Memory:e0206000-e0206fff 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:11 errors:0 dropped:0 overruns:0 frame:0
          TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:896 (896.0 B)  TX bytes:896 (896.0 B)
/proc/net/bonding/bond0:

Code:
Ethernet Channel Bonding Driver: v3.2.5 (March 21, 2008)

Bonding Mode: fault-tolerance (broadcast)
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0

Slave Interface: eth0
MII Status: up
Link Failure Count: 1
Permanent HW addr: 08:00:46:5f:e7:6e

Slave Interface: eth1
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:0e:35:ed:41:e6
mii-tool:

Code:
eth0: negotiated 100baseTx-FD flow-control, link ok
SIOCGMIIPHY on 'eth1' failed: Operation not supported
I get 50% packet loss using mode bonding mode balance-rr. I assume this is because it cycles through the interfaces and when it comes to using the wireless one it does not work. Using mode broadcast, I get no packet loss until the wire link goes down? Is this related to "SIOCGMIIPHY on 'eth1' failed: Operation not supported" and if so, how to resolve it? Thanks
 
Old 11-03-2008, 07:11 PM   #3
pauledwards03
Member
 
Registered: Dec 2006
Distribution: Slackware 12.1
Posts: 94

Original Poster
Rep: Reputation: 15
just some more info: when reversing the roles of the interfaces, the wireless link works fine in the bond but as soon as it goes down, the packets are lost. It does not switch over to using the wire.
 
Old 11-04-2008, 11:46 AM   #4
pauledwards03
Member
 
Registered: Dec 2006
Distribution: Slackware 12.1
Posts: 94

Original Poster
Rep: Reputation: 15
In case anyone does read this thread, I have some more information:

I tried to upgrade to kernel 2.6.27.4, still the same. Does ipw2200 just not support bonding? I am starting to think that is the case:

Code:
bash-3.1# ifenslave -c bond0 eth1
Master 'bond0', Slave 'eth1': Error: Change active failed
bash-3.1# ifenslave -c bond0 eth0
I can change active slave to eth0 without a problem.

Also, dmesg:
Code:
paul@/home/paul $ dmesg | grep bonding
bonding: Warning: either miimon or arp_interval and arp_ip_target module parameters must be specified, otherwise bonding will not detect link failures! see bonding.txt for details.
bonding: MII link monitoring set to 100 ms
bonding: bond0: enslaving eth0 as a backup interface with a down link.
bonding: bond0: Warning: failed to get speed and duplex from eth1, assumed to be 100Mb/sec and Full.
bonding: bond0: making interface eth1 the new active one.
bonding: bond0: first active interface up!
bonding: bond0: enslaving eth1 as an active interface with an up link.
bonding: bond0: link status definitely up for interface eth0.
bonding: bond0: making interface eth0 the new active one.
bonding: bond0: link status definitely down for interface eth1, disabling it
bonding: bond0: link status definitely up for interface eth1.
bonding: bond0: link status definitely down for interface eth0, disabling it
bonding: bond0: making interface eth1 the new active one.
bonding: bond0: link status definitely up for interface eth0.
bonding: bond0: making interface eth0 the new active one.
bonding: bond0: released all slaves
bonding: MII link monitoring set to 100 ms
bonding: Warning: eth0 primary device specified but has no effect in load balancing (round-robin) mode
bonding: bond0: enslaving eth0 as an active interface with a down link.
bonding: bond0: Warning: failed to get speed and duplex from eth1, assumed to be 100Mb/sec and Full.
bonding: bond0: enslaving eth1 as an active interface with an up link.
bonding: bond0: link status definitely up for interface eth0.
bonding: bond0: link status definitely down for interface eth1, disabling it
bonding: bond0: link status definitely up for interface eth1.
bonding: bond0: released all slaves
bonding: MII link monitoring set to 100 ms
bonding: Warning: eth0 primary device specified but has no effect in fault-tolerance (broadcast) mode
bonding: bond0: enslaving eth0 as an active interface with a down link.
bonding: bond0: Warning: failed to get speed and duplex from eth1, assumed to be 100Mb/sec and Full.
bonding: bond0: enslaving eth1 as an active interface with an up link.
bonding: bond0: link status definitely up for interface eth0.
bonding: bond0: link status definitely down for interface eth1, disabling it
bonding: bond0: link status definitely up for interface eth1.
bonding: bond0: link status definitely down for interface eth0, disabling it
bonding: bond0: link status definitely up for interface eth0.
bonding: bond0: link status definitely down for interface eth1, disabling it
bonding: bond0: link status definitely up for interface eth1.
bonding: bond0: link status definitely down for interface eth1, disabling it
bonding: bond0: link status definitely up for interface eth1.
bonding: bond0: link status definitely down for interface eth1, disabling it
bonding: bond0: link status definitely up for interface eth1.
bonding: bond0: link status definitely down for interface eth1, disabling it
bonding: bond0: link status definitely up for interface eth1.

Last edited by pauledwards03; 11-04-2008 at 01:33 PM. Reason: added dmesg output
 
  


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
problem with bonding slave interfaces zamri Linux - Networking 1 10-12-2006 08:48 PM
bonding in Slackware and firewall zamri Linux - Networking 2 05-05-2006 04:40 AM
Help with ethernet bonding on Slackware shubb Linux - Networking 0 12-02-2005 03:03 PM
Bonding Interfaces in Slackware 9.1 tim0707 Linux - Networking 2 07-26-2004 03:57 AM
ethernet channel bonding in slackware sublett Slackware 1 04-10-2003 11:43 PM


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

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration