I just wrote a tutorial on how I got mine working. It is a Broadcom
Corporation Dell Wireless 1390 WLAN Mini-PCI Card, though and not a
4318. It may be a different way of going about it ie a patch that is
necessary. If you want a write up on the tutorial let me know- I can
attach it on a rep
LOL. Yeah, I've gotten off what would have been some very expensive
tickets too. The only reason I could ever think of was because of the
cars I was driving at the time piqued the cops interest.
I once got pulled over for doing about 90 in town and having a huge blue
cloud of tire smoke behind
Try blacklisting ndiswrapper in /etc/modprobe.d/blacklist. I don't
think ndiswrapper being in one kernel should affect a different kernel,
but I'm no kernel expert. I know I've always had to reinstall
ndiswrapper after every kernel update that went from one kernel release
to another, i.e. 2.6.17
Hardware configurations sure makes a difference. I just loaded the
bcm43xx module and blacklisted ndiswrapper. My system became absolutely
unusable for accomplishing anything. The mouse cursor freezes
intermittently, windows not maximized jump around on the desktop, and
all the while cpu usage ne
Its not my AP only. My dad also uses it. He owns it. I may be able to
persuade him though.
:D
On Sat, Mar 03, 2007 at 03:27:49AM +0100, pinniped wrote:
>
> Hahaha ... the "Worthless Encryption Protocol" - don't ever use it, you'd
> only be fooling yourself. Even WPA-PSK isn't that much bett
Hahaha ... the "Worthless Encryption Protocol" - don't ever use it, you'd only be fooling
yourself. Even WPA-PSK isn't that much better - in fact you can implement much more secure
communications with absolutely no "wireless encryption" but that takes a little effort.
You should be using WPA
Mr Alk3 wrote:
I am using WEP encryption, but can set up WPA etc etc. I did notice
that when I was configuring the interface to connect to the WEP
encrypted AP that it wasn't finding any of the WEP access point in the
area.
I had a problem slightly similar to this about a year ago. I had
wpa_
I am using WEP encryption, but can set up WPA etc etc. I did notice
that when I was configuring the interface to connect to the WEP
encrypted AP that it wasn't finding any of the WEP access point in the
area. I might have to change my AP to use WPA as I am seeing that most
people are getting
Maybe I need to just set the MAC address when I configure it with
iwconfig? The router is our cable modem as well. It is a 2WIRE, but I
don't know what model. I am using the bcm43xx module on my 2.6.20
kernel. I also have a 2.6.18 kernel running with ndiswrapper. Could it
be a problem that
Hi!
Goodness, where did February go?? Wasn't I just wishing you a Happy
Valentine's Day a bit ago? LOL! Time flies when you're having fun, as they
say. :-)
Click Here for candle Drawing: http://www.barbaraw.scent-team.com (drawing jar
top right corner after you click the country icon).
I know there's a section on how to set up wireless stuff in the Debian docs but
I can't find it at the moment.
Anyway, if you use PSK-TKIP, look here for an example:
http://wiki.debian.org/Manual-Howto#head-6fdd87d329e68a583e5fde32c6b21e460e5541a5
If you use WPA-PSK (default on WinDos and ther
The access point on a wireless router is its MAC address. The only
reason I can see that yours might be considered invalid is due to what I
see as a conflict in configuration. The router reports that it has an
encryption key, but that the security mode is open. I find that pretty
strange.
What
I have my Broadcom wireless card half functional and it can be
configured. I just can seem to get it to connect to an AP. When I do
an 'iwconfig' I get this:
# iwconfig
lono wireless extensions.
eth0 no wireless extensions.
wlan0 IEEE 802.11b/g ESSID:"ByteMe" Nickname:"Br
13 matches
Mail list logo
