On Wed, Jan 09, 2008 at 09:17:06PM +0000, [EMAIL PROTECTED] wrote: > I ignore it, but it seems like it prevent bonding detect link of wlan0. I > enslave wlan0 and i already use use_carrier=1; > I use bond to have my etherenet ip in wifi at office, else the wireless > connection give temporary and you must pass through proxy then. > I'll try arp monitoring but this is annoying i c'ant test localhost. Is there > a way to test localhost with arp, without pass through lo ? > > > > ----- Message d'origine ---- > De : John W. Linville <[EMAIL PROTECTED]> > À : [EMAIL PROTECTED] > Envoyé le : Mercredi, 9 Janvier 2008, 21h24mn 10s > Objet : Re: Re : Bonding : Monitoring of 4965 wireless card > > On Wed, Jan 09, 2008 at 07:31:37PM +0000, [EMAIL PROTECTED] > wrote: > > I'm doing a bonding with my eth0(e1000 driver) and my wlan > > card(iwl4965). It work like i want, when i'm in wifi the dhcp give > > me my ethernet adress. When i unplug the cable, my wlan card become > > in charge of network. My problem is when i disconnect the wlan card, > > the bonding does not detect it correctly, and ifplugstatus show me > > wlan0 not connected and wmaster0 connected!! The bonding module does > > not say no active interface, it work like wlan is on. > > > > Am i clear? > > Yes, that is much more clear to me. > > What (if anything) are you doing to wmaster0? You should just > ignore it. > > FWIW, miimon is not going to work with a mac80211-based device at > this time. The miimon option relies on support for either miitool > or ethtool, and mac80211 device support neither of those. > > Hmmm...it looks like there is a use_carrier option for miimon. > Based on its description I would think it would work. Of course, > I think it is supposed to be the default and you don't seem to be > disabling it. So, I'm not sure what is happening. > > Are you enslaving wlan0? Or wmaster0? Make sure it is wlan0. > Also, please add use_carrier=1 to your bonding module options. > Does this change the behaviour? If not, please open a bug at either > bugzilla.redhat.com (if you are a Fedora, RHEL, or even CentOS user) > or bugzilla.kernel.org (otherwise). > > In the meantime, you might try using NetworkManger. Or you > might consider using ARP monitoring. The former probably is the > best solution if you are mobile (e.g. at a cafe or other hotspot) > while the latter might be appropriate if you are just plugging and > un-plugging within the same network (like at home or office). > > Hth! >
John's suggestion to consider using ARP monitoring is a good one. It is the preferred method to check for failover when link checking is not an option (which is the case with your current setup). -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
