From: patnel972-linux@yahoo.fr
To: Jay Vosburgh <fubar@us.ibm.com>
Cc: netdev@vger.kernel.org
Subject: Re : Re : Re : Bonding : Monitoring of 4965 wireless card
Date: Wed, 9 Jan 2008 21:52:39 +0000 (GMT) [thread overview]
Message-ID: <416779.67064.qm@web25704.mail.ukl.yahoo.com> (raw)
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 <fubar@us.ibm.com>
À : patnel972-linux@yahoo.fr
Cc : John W. Linville <linville@tuxdriver.com>; netdev@vger.kernel.org
Envoyé le : Mercredi, 9 Janvier 2008, 22h36mn 00s
Objet : Re: Re : Re : Bonding : Monitoring of 4965 wireless card
patnel972-linux@yahoo.fr 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, fubar@us.ibm.com
_____________________________________________________________________________
Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail http://mail.yahoo.fr
next reply other threads:[~2008-01-09 21:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 21:52 patnel972-linux [this message]
2008-01-09 23:26 ` Re : Re : Re : Bonding : Monitoring of 4965 wireless card Jay Vosburgh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=416779.67064.qm@web25704.mail.ukl.yahoo.com \
--to=patnel972-linux@yahoo.fr \
--cc=fubar@us.ibm.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).