[Prism54-users] Re: channel bonding on 802.11g

[nitin bajaj]

Hi,
yes i realised my mistake and then built it from source. But i still face exactly the same problem. I have below the output i get when I run ifenslave with the verbose mode on.
 
 

bond0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 

UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0 

RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

lo Link encap:Local Loopback 

inet addr:127.0.0.1 Mask:255.0.0.0

UP LOOPBACK RUNNING MTU:16436 Metric:1

RX packets:6 errors:0 dropped:0 overruns:0 frame:0

TX packets:6 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0 

RX bytes:300 (300.0 b) TX bytes:300 (300.0 b)

ifenslave.c:v1.1.0 (December 1, 2003)

o Donald Becker (becker at cesdis.gsfc.nasa.gov).

o Detach support added on 2000/10/02 by Willy Tarreau (willy at meta-x.org).

o 2.4 kernel support added on 2001/02/16 by Chad N. Tindel

(ctindel at ieee dot org).

ABI ver is 2

current hardware address of master 'bond0' is 00:09:5b:c6:d1:fe, type 1

Interface 'eth0': flags set to 1002.

Interface 'eth0': address cleared

Master 'bond0': Error: SIOCBONDENSLAVE failed: Input/output error

Master 'bond0': hardware address set to 00:09:5b:c6:d1:fe.

Slave 'eth0': MTU set to 1500.

Master 'bond0', Slave 'eth0': Error: Enslave failed

ABI ver is 2

current hardware address of master 'bond0' is 00:09:5b:c6:d1:fe, type 1

Interface 'eth0': flags set to 1042.

Interface 'eth0': address cleared

Master 'bond0': Error: SIOCBONDENSLAVE failed: Input/output error

Master 'bond0': hardware address set to 00:09:5b:c6:d1:fe.

Slave 'eth0': MTU set to 1500.

Master 'bond0', Slave 'eth0': Error: Enslave failed

 

13 iwconfig eth0 essid barney key 1122334455

14 modprobe bonding

15 ifconfig bond0 up

16 ifconfig > /mnt/hda5/results

17 /mnt/hda5/a.out -v bond0 eth0 >>/mnt/hda5/results 

18 /mnt/hda5/a.out -v bond0 eth0 >>& /mnt/hda5/results 

19 /mnt/hda5/a.out -v bond0 eth0 2>> /mnt/hda5/results 

20 ifconfig eth0 up

21 /mnt/hda5/a.out -v bond0 eth0 2>> /mnt/hda5/results 

22 history >> /mnt/hda5/results


Margit Schubert-While <margitsw at t-online.de> wrote:
That's not going to work.
Bonding relies on changing the mac addresses on
the interfaces so that they are the same. Ooops, what's
your poor access point going to do with that ?!

You cannot just shove any ifenslave package onto any
kernel distro. It has to be compiled against kernel source
relative to the kernel that you are running.

The source for ifenslave is delivered with 2.4/2.6 kernels.
(In .../Documentation/networking)
So, for instance, if your kernel source is in
/usr/src/linux-2.4.26 :

cd /usr/src/linux-2.4.26/Documentation/networking

gcc -O -Wall -Wstrict-prototypes \
-I/usr/src/linux-2.4.26/include \
ifenslave.c -o ifenslave

cp ifenslave /sbin

Margit




		
---------------------------------
Do you Yahoo!?
vote.yahoo.com - Register online to vote today!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://prism54.org/pipermail/prism54-users/attachments/20040916/4ff873e9/attachment.html