[gentoo-user] [partially OT] USB wifi adapters that are supported out of the box?
brullo nulla
We are going to put a wireless network in a new building in my lab.
This is just a temporary/backup solution, so the boss had asked to buy
USB wifi adapters (instead of PCI receivers) that eventually can be
easily plugged and removed.
There are a couple of Linux machines (a Kubuntu 6.06 box and a Debian
Sarge box) that should be made working, but I also hope to have a
Gentoo box on it soon, so it's not totally off topic :)
Therefore, I'd like to know what USB adapters to buy that don't give
too much headaches in configuring and working. I tried googling a bit
but all what I found is confused and outdated (2004, 2005 at most)
information.
Thanks,
M.
--
gento...@gentoo.org mailing list
Neil Bothwick
> Therefore, I'd like to know what USB adapters to buy that don't give
> too much headaches in configuring and working. I tried googling a bit
> but all what I found is confused and outdated (2004, 2005 at most)
> information.
Edimax USB adaptors use the zd1211 driver, which is in the kernel now.
--
Neil Bothwick
Hello.. Incontinence Hotline.. Can you hold?
brullo nulla
> Edimax USB adaptors use the zd1211 driver, which is in the kernel now.
In the kernel "now" what does it means? from what kernel version?
I would need something supported even by a 2.6.12 kernel...
m.
--
gento...@gentoo.org mailing list
Neil Bothwick
> > Edimax USB adaptors use the zd1211 driver, which is in the kernel
> > now.
>
> In the kernel "now" what does it means? from what kernel version?
> I would need something supported even by a 2.6.12 kernel...
Now refers to the current kernel, 2.6.18. For earlier kernels, emerge
zd1211. I was using this with my iBook for almost a year, before the
bcm43xx drivers became available. The only problem I had with the Edimax
USB stick is that it snapped off when my grandson knocked the laptop onto
the floor :(
--
Neil Bothwick
All wight - Rho sritched mg kegtops awound?
Timothy A. Holmes
I have a gateway E4100 series computer acting as my snort box. It is
running 2006.1 and has the intel Pro1000 nic. The box was built from a
stage 4 install which I have 2 other identical machines running on.
The problem is that the network adapter seems to "fall asleep"
periodically. If I attempt to access the base webpage or ssh, I get no
response till I ping the box -- 8 pings later, it wakes up and acts
normally. For a while, then it starts over.
Checking /var/log/messages indicates no problems, it shows the crons
happily running, the snort startup etc. but nothing else. Can anyone
shed some light on the problem and a possible solution.
TIM
Timothy A. Holmes
IT Manager / Network Admin / Web Master / Computer Teacher
Medina Christian Academy
A Higher Standard...
Jeremiah 33:3
Jeremiah 29:11
Esther 4:14
--
gento...@gentoo.org mailing list
Hans-Werner Hilse
First: stop hijacking threads!
On Wed, 4 Oct 2006 15:21:58 -0400 "Timothy A. Holmes"
<tho...@mcaschool.net> wrote:
> The problem is that the network adapter seems to "fall asleep"
> periodically. If I attempt to access the base webpage or ssh, I get no
> response till I ping the box -- 8 pings later, it wakes up and acts
> normally. For a while, then it starts over.
Flaky switch? (Too) long or bad (non-standard) cabling? That was
usually the explanation when I was seeing such behaviour.
-hwh
--
gento...@gentoo.org mailing list
Timothy A. Holmes
Not sure what you mean about hijacking the thread, but I am sorry -- I
didn't mean to do anything wrong.
As far as the switch, its on a hub that is on the span port of a foundry
switch (the hub is used as a poormans network tap -- I have seen the
same type of failure on machines directly connected to a switch also)
The cable is a commercially manufactured cable that tests out correctly
- -its about 6 feet long
Hans-Werner Hilse
On Thu, 5 Oct 2006 08:23:38 -0400 "Timothy A. Holmes"
<tho...@mcaschool.net> wrote:
> > Flaky switch? (Too) long or bad (non-standard) cabling? That
> > was usually the explanation when I was seeing such behaviour.
> >
> Not sure what you mean about hijacking the thread, but I am sorry -- I
> didn't mean to do anything wrong.
No, you're only hurting yourself: Thread hijacking describes using the
"reply" facility of your email program to start a new thread (instead
of starting a new, fresh email, e.g. by clicking on the ML address).
Email agents that make use of information in the mail headers for
displaying threads will show your mail inside the structure of an
existing thread. Some people might not even find your message buried in
there. See the following link for knowing what I mean:
http://groups.google.com/group/linux.gentoo.user/browse_frm/thread/601571a0fced1a73/e17f8a0483af6690?tvc=1
> As far as the switch, its on a hub that is on the span port of a
> foundry switch (the hub is used as a poormans network tap -- I have
> seen the same type of failure on machines directly connected to a
> switch also)
>
> The cable is a commercially manufactured cable that tests out
> correctly
> - -its about 6 feet long
Did you try if it works with another cable, on another port of the
switch/hub? That would be proper exclusion of probable errors. You're
description tells me what you have, but not if it's working right now.
HTH,
Timothy A. Holmes
Hans:
Thanks for the explaination -- Outlook strikes again :(
I will change the way I do things
As far as the problem, I am going to try new hardware and see what
happens