Netstumbler .40 closes card -

We have a Dell laptop WinXP with the 1300 wireless mini-pci card
which uses the Broadcom chipset...
Netstumbler has been a problem on this chipset,
as sometimes it would work - and sometimes not -
The latest version (0.40) seems to be rock solid.
BUT - something has changed,
in that Netstumbler seems to close or break
the connection between the card and the protocol stack.
After closing NS, the wireless physical connection can
still be seen, but the TCP/IP functionality is gone...
This did not happen with the previous version.
It comes back after a few minutes, but not sure how or why ?

In article <pAFjc.14$(E-Mail Removed)>,
(E-Mail Removed) says...
> We have a Dell laptop WinXP with the 1300 wireless mini-pci card
> which uses the Broadcom chipset...
> Netstumbler has been a problem on this chipset,
> as sometimes it would work - and sometimes not -
> The latest version (0.40) seems to be rock solid.
> BUT - something has changed,
> in that Netstumbler seems to close or break
> the connection between the card and the protocol stack.
> After closing NS, the wireless physical connection can
> still be seen, but the TCP/IP functionality is gone...
> This did not happen with the previous version.
> It comes back after a few minutes, but not sure how or why ?
>
>
>
>
This also happens on my Linksys WPC11 2.5 card on a Compaq Presario 2700
laptop.

--

Ben E. Brady
http://www.clariondeveloper.com/webmailcloak.htm
FREE! Encrypt email addresses on your web site!
Keep spam bots from sending you spam!
http://www.firewallreporting.com
Personal firewall log analysis tools for
ZoneAlarm, BlackICE, WinRoute Pro and Windows XP
Take stock of your firewall settings and take action against intruders.
http://www.videoprofessorscam.com
Don't get stung by this scam!

> In article <pAFjc.14$(E-Mail Removed)>,
> (E-Mail Removed) says...
>
>>> We have a Dell laptop WinXP with the 1300 wireless mini-pci card
>>> which uses the Broadcom chipset...
>>> Netstumbler has been a problem on this chipset,
>>> as sometimes it would work - and sometimes not -
>>> The latest version (0.40) seems to be rock solid.
>>> BUT - something has changed,
>>> in that Netstumbler seems to close or break
>>> the connection between the card and the protocol stack.
>>> After closing NS, the wireless physical connection can
>>> still be seen, but the TCP/IP functionality is gone...
>>> This did not happen with the previous version.
>>> It comes back after a few minutes, but not sure how or why ?
>>>
>>>
>>>
>>>
>
> This also happens on my Linksys WPC11 2.5 card on a Compaq Presario 2700
> laptop.
>
> -- Ben E. Brady http://www.clariondeveloper.com/webmailcloak.htm FREE! Encrypt email addresses on your web site! Keep spam bots from sending you spam! http://www.firewallreporting.com Personal firewall log analysis tools for ZoneAlarm, BlackICE, WinRoute Pro and Windows XP Take stock of your firewall settings and take action against intruders. http://www.videoprofessorscam.com Don't get stung by this scam!


Check the chipset that netstumbler run on. I believe it only runs on
prism chipset.

(E-Mail Removed) (Phil Schuman) wrote in
newsAFjc.14$(E-Mail Removed):

> We have a Dell laptop WinXP with the 1300 wireless mini-pci card
> which uses the Broadcom chipset...
> Netstumbler has been a problem on this chipset,
> as sometimes it would work - and sometimes not -
> The latest version (0.40) seems to be rock solid.
> BUT - something has changed,
> in that Netstumbler seems to close or break
> the connection between the card and the protocol stack.
> After closing NS, the wireless physical connection can
> still be seen, but the TCP/IP functionality is gone...
> This did not happen with the previous version.
> It comes back after a few minutes, but not sure how or why ?

The "README" file for the new version says this:

"When NetStumbler is in "auto reconfigure" mode (the default), it
will occasionally disconnect you from your network. This enables it
to perform its scans accurately, and is not a bug. "

http://stumbler.net/readme/readme_0_4_0.html

Would that explain what you're seeing?

--
Bert Hyman | St. Paul, MN | (E-Mail Removed)