Bonding : Monitoring of 4965 wireless card
Hi, I want to make a bond with my wireless card. The ipw driver create two interfaces (wlan0 and wmaster0). When i switch the rf_kill button, ifplug detect wlan0 unplugged but not wmaster0. If i down wlan0 (while rf_kil ), bonding detect the inactivity when i up the interface. Have you some idea where is the problem? the driver or the miimon of the module? my module parameters mode=1 miimon=100 primary eth0 Thanks _ Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail http://mail.yahoo.fr -- 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
Re : Bonding : Monitoring of 4965 wireless card
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? Ps:(sorry i have trouble with my mail) - Message d'origine De : John W. Linville <[EMAIL PROTECTED]> À : [EMAIL PROTECTED] Cc : netdev@vger.kernel.org Envoyé le : Mercredi, 9 Janvier 2008, 18h02mn 05s Objet : Re: Bonding : Monitoring of 4965 wireless card On Wed, Jan 09, 2008 at 09:00:05AM +, [EMAIL PROTECTED] wrote: > Hi, > > I want to make a bond with my wireless card. The ipw driver create two > interfaces (wlan0 and wmaster0). When i switch the rf_kill button, > ifplug detect wlan0 unplugged but not wmaster0. If i down wlan0 (while > rf_kil ), bonding detect the inactivity when i up the interface. > > Have you some idea where is the problem? the driver or the miimon of > the module? > > my module parameters mode=1 miimon=100 primary eth0 I'm not sure I understand your description...what are you trying to do? How exactly is it failing? John -- John W. Linville [EMAIL PROTECTED] -- 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 _ Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail http://mail.yahoo.fr _ Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail http://mail.yahoo.fr -- 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
Re : Re : Bonding : Monitoring of 4965 wireless card
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 +, [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 -- John W. Linville [EMAIL PROTECTED] _ Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail http://mail.yahoo.fr -- 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
Re : Re : Re : Bonding : Monitoring of 4965 wireless card
I mean that instead of arp test an ip in lan or else, i want it to test 127.0.0.1 but in order to do this it must go out and re-enter and then use wlan0 to go out. - Message d'origine De : Jay Vosburgh <[EMAIL PROTECTED]> À : [EMAIL PROTECTED] Cc : John W. Linville <[EMAIL PROTECTED]>; netdev@vger.kernel.org Envoyé le : Mercredi, 9 Janvier 2008, 22h36mn 00s Objet : Re: Re : Re : Bonding : Monitoring of 4965 wireless card [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; The default for bonding is use_carrier=1, which makes bonding use the device driver's netif_carrier_on/off state for link detection. Bonding only checks via ethtool/mii if use_carrier=0. >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 ? What do you mean by "test localhost with arp, without pass through lo"? ARP monitoring issues probes (ARPs) to a remote destination to confirm that there is connectivity; I'm not sure what localhost has to do with it. In general, though, I have not tested bonding with wireless adapters, so I'm unfamiliar with how well it does or does not work. -J --- -Jay Vosburgh, IBM Linux Technology Center, [EMAIL PROTECTED] _ Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail http://mail.yahoo.fr -- 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
Re : Re : Re : Re : Bonding : Monitoring of 4965 wireless card
Yes it's what i'm looking for. I don't understand how to change the arp_ip_target with the gateway, arp_ip_target is a module option. - Message d'origine De : Jay Vosburgh <[EMAIL PROTECTED]> À : [EMAIL PROTECTED] Cc : netdev@vger.kernel.org Envoyé le : Jeudi, 10 Janvier 2008, 0h26mn 38s Objet : Re: Re : Re : Re : Bonding : Monitoring of 4965 wireless card [EMAIL PROTECTED] wrote: >I mean that instead of arp test an ip in lan or else, i want it to test 127.0.0.1 but in order to do this it must go out and re-enter and then use wlan0 to go out. In other words, what I think you're saying (and I'm not entirely sure here) is that you want probes to go to a remote node on the network, and back, without having to actually know the identity of the remote node (because, presumably, on a roaming type of wireless configuration, your gateway and whatnot can change from time to time). Is that what you're looking for? That isn't available now, but might be straightforward to plug into the address update system to keep the arp_ip_target up to date as the current gateway as the gateway changes. I haven't looked into the details of doing that, but in theory it sounds straightforward. -J --- -Jay Vosburgh, IBM Linux Technology Center, [EMAIL PROTECTED] > >- Message d'origine >De : Jay Vosburgh <[EMAIL PROTECTED]> >À : [EMAIL PROTECTED] >Cc : John W. Linville <[EMAIL PROTECTED]>; netdev@vger.kernel.org >Envoyé le : Mercredi, 9 Janvier 2008, 22h36mn 00s >Objet : Re: Re : Re : Bonding : Monitoring of 4965 wireless card > >[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; > >The default for bonding is use_carrier=1, which makes bonding >use the device driver's netif_carrier_on/off state for link detection. >Bonding only checks via ethtool/mii if use_carrier=0. > >>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 ? > >What do you mean by "test localhost with arp, without pass >through lo"? ARP monitoring issues probes (ARPs) to a remote >destination to confirm that there is connectivity; I'm not sure what >localhost has to do with it. > >In general, though, I have not tested bonding with wireless >adapters, so I'm unfamiliar with how well it does or does not work. > >-J > >--- >-Jay Vosburgh, IBM Linux Technology Center, [EMAIL PROTECTED] > > > > > > _ >Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail http://mail.yahoo.fr >-- >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 -- 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 _ Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail http://mail.yahoo.fr -- 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
Re : Re : Re : Re : Re : Bonding : Monitoring of 4965 wireless card
I try arp monitoring but it doesn't work! Test an ip, the interface must have an address, and the dhcpcd is launch by ifplugd if bond0 is linked ... so it goes around in circles. So i return to miimon, and i figured out that bond detect when wlan0 is associated and set it active interface. But when i switch rf_kill it don't react. So i try to deassociate and magic it detect interface off!! I presume it is a bug of the wlan driver which not re-initialise the info on the wlan. So i made a small script in acpi to provide that behavior. - Message d'origine De : Jay Vosburgh <[EMAIL PROTECTED]> À : [EMAIL PROTECTED] Cc : netdev@vger.kernel.org Envoyé le : Jeudi, 10 Janvier 2008, 21h59mn 20s Objet : Re: Re : Re : Re : Re : Bonding : Monitoring of 4965 wireless card [EMAIL PROTECTED] wrote: >Yes it's what i'm looking for. I don't understand how to change the arp_ip_target with the gateway, arp_ip_target is a module option. If you're running a relatively recent bonding driver (version 3.0.0 or later), the arp_ip_targets can be changed on the fly via sysfs, e.g., echo +10.0.0.1 > /sys/class/net/bond0/bonding/arp_ip_target echo -20.0.0.1 > /sys/class/net/bond0/bonding/arp_ip_target You can check out Documentation/networking/bonding.txt (in the kernel source code) for more details. -J --- -Jay Vosburgh, IBM Linux Technology Center, [EMAIL PROTECTED] >- Message d'origine >De : Jay Vosburgh <[EMAIL PROTECTED]> >À : [EMAIL PROTECTED] >Cc : netdev@vger.kernel.org >Envoyé le : Jeudi, 10 Janvier 2008, 0h26mn 38s >Objet : Re: Re : Re : Re : Bonding : Monitoring of 4965 wireless card > >[EMAIL PROTECTED] wrote: > >>I mean that instead of arp test an ip in lan or else, i want it to > test 127.0.0.1 but in order to do this it must go out and re-enter and > then use wlan0 to go out. > >In other words, what I think you're saying (and I'm not entirely >sure here) is that you want probes to go to a remote node on the >network, and back, without having to actually know the identity of the >remote node (because, presumably, on a roaming type of wireless >configuration, your gateway and whatnot can change from time to time). > >Is that what you're looking for? > >That isn't available now, but might be straightforward to plug >into the address update system to keep the arp_ip_target up to date as >the current gateway as the gateway changes. I haven't looked into the >details of doing that, but in theory it sounds straightforward. > >-J > >--- >-Jay Vosburgh, IBM Linux Technology Center, [EMAIL PROTECTED] -- 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 _ Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail http://mail.yahoo.fr -- 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
