Date: Wed, 5 Jun 2002 14:18:59 -0700 From: Norbert Papke <npapke@acm.org> To: "Matt Peterson" <matt@peterson.org> Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: wi question Message-ID: <20020605141859.6467fdc1.npapke@acm.org> In-Reply-To: <20020605133623.I82001@moaner.org> References: <20020605124344.384d172c.npapke@acm.org> <20020605133623.I82001@moaner.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 5 Jun 2002 13:36:23 -0700 "Matt Peterson" <matt@peterson.org> wrote: > This is because in an ad-hoc network, STA's must sync up with a BSSID. > Thus each time your W2K box reboots, this will be renegotiated. You > might want to run a cron job to ping your W2K box, and either up/down > the interface or -n "proven" should also re-sync them. I could also > be on crack. Thanks for your answer. Just to make sure I understand this correctly. Is this a problem with the W2K box in that it doesn't announce itself and renegotiate the BSSID on boot? Anyway, one of the symptoms I am seeing is that after a reboot of the W2K box, neither box can ping the other. I need to nudge the wi driver on the FreeBSD box before pings work. The cron job certainly is an option but it strikes me a kludge. But then again I don't know the 802.11b protocol. Cheers, -- Norbert Papke. npapke@acm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020605141859.6467fdc1.npapke>