<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
iiNet IIRC.... Sysadmin stuff.<br>
<div class="moz-signature">
<meta http-equiv="Content-Type" content="text/html; ">
<div> <font face="Arial" size="2"><strong>Daniel Pearson<br>
</strong><font size="1">Flashware Solutions ABN 58 438 456 919</font></font></div>
<div> <font face="Arial"><font size="1">Mob: 0438 118 897 | Email: </font>
<a href="mailto:daniel@flashware.net"><font size="1">daniel@flashware.net</font></a></font></div>
<div> <font face="Arial" size="1"><br>
The information contained in this electronic transmission is
confidential. If you are not the intended recipient of this
transmission, use of this information is strictly prohibited. If you
have received this transmission in error, please contact Flashware
Solutions 0438 118 897.</font></div>
</div>
<br>
<br>
Chris Griffin wrote:
<blockquote
cite="midc38d95c20607070102u3f26011bq7be9afbd936e4c49@mail.gmail.com"
type="cite">Excellent, many thanks once again.
<br>
"graveyard shift", thankfully I have not had to do that for some years
now.
<br>
Where abouts and doing what?
<br>
<br>
Griff
<br>
<br>
On 7/7/06, Adrian Woodley <a class="moz-txt-link-rfc2396E" href="mailto:Adrian@screamingroot.org"><Adrian@screamingroot.org></a> wrote:
<br>
<blockquote type="cite">All things atheros/madwifi can be found on
madwifi.org
<br>
<br>
The list you're looking for is <a class="moz-txt-link-freetext" href="http://madwifi.org/wiki/Compatibility">http://madwifi.org/wiki/Compatibility</a>
<br>
<br>
Sorry about the delay - you've probably noticed from my posting times
<br>
that I'm working graveyard shift atm.
<br>
<br>
On Fri, 2006-07-07 at 12:01 +0800, Chris Griffin wrote:
<br>
> Hm, not exactly what I was hoping for. I guess I am a bit shocked
that
<br>
> our beloved Linux is so far behind in this area.
<br>
> It looks like the best alternative is to, as you suggest, put in a
<br>
> workaround and wait for the new drivers.
<br>
> In terms of the "atheros chipset", there was a site where one
could
<br>
> look up the network cards, what chipset they use and what the
Linux
<br>
> compatibility was.
<br>
> Do you remember the URL?
<br>
>
<br>
> Again, many thanks for the input.
<br>
>
<br>
> Regards,
<br>
> Chris G
<br>
>
<br>
> On 7/6/06, Adrian Woodley <a class="moz-txt-link-rfc2396E" href="mailto:Adrian@screamingroot.org"><Adrian@screamingroot.org></a> wrote:
<br>
> > Chris,
<br>
> >
<br>
> > If you absolutely need WPA/WPA2 today, and you don't have a
laptop, then
<br>
> > an atheros chipset would be the way to go. Unfortunately, I
can't
<br>
> > recommend any actual cards as I haven't bought a wifi card
for a couple
<br>
> > of years now.
<br>
> >
<br>
> > WPA/WPA2 is worth it in terms of ease of setup and use, as
well as
<br>
> > security. You could probably make do with WEP128, provided
you changed
<br>
> > your keys every day or so. Alternatively, you could run and
open access
<br>
> > point and firewall it off from the rest of your network and
allow
<br>
> > through only authenticated SSL services - imaps, smtp/TLS,
http proxy
<br>
> > over ssl, etc. You could also run a VPN over the top of a
firewalled,
<br>
> > open access point. This will provide you with security as
good as, if
<br>
> > not, better than WPA (plus you can use it for remote access
away from
<br>
> > home).
<br>
> >
<br>
> > If you can wait a bit (maybe 6 months?) there should be a new
wifi stack
<br>
> > in the kernel which will provide WPA/WPA2 support for most
wifi
<br>
> > chipsets.
<br>
> >
<br>
> > Adrian
<br>
> >
<br>
> > On Thu, 2006-07-06 at 19:47 +0800, Chris Griffin wrote:
<br>
> > > Hi Adrian,
<br>
> > >
<br>
> > > many thanks for the response. From what you have
indicated I would
<br>
> > > have thought the Prism2/2.5/3 the most likley but you
left it out of
<br>
> > > your summary, did I miss something?
<br>
> > > Given you say "Full feature set (AP and client,
WPA/WPA2/802.11X
<br>
> > > authenticator and supplicant)".
<br>
> > > Oh, I just noticed "* 802.11b only (AFAIK)", bother.
<br>
> > > Any idea of just what to buy, where to get it and how
much?
<br>
> > >
<br>
> > > Regards,
<br>
> > > Chris G
<br>
> > >
<br>
> > > On 7/6/06, Adrian Woodley
<a class="moz-txt-link-rfc2396E" href="mailto:Adrian@screamingroot.org"><Adrian@screamingroot.org></a> wrote:
<br>
> > > > Chris,
<br>
> > > >
<br>
> > > > Thats a bit of a hard choice. For WPA support it
pretty much comes down
<br>
> > > > to three chipsets:
<br>
> > > >
<br>
> > > > IPW2100/2200
<br>
> > > > * Intel chipset.
<br>
> > > > * 802.11a/g
<br>
> > > > * Good Linux support with out-of-tree kernel
drivers.
<br>
> > > > * Works well with wpa-supplicant.
<br>
> > > > * Monitor mode.
<br>
> > > > * Laptop only.
<br>
> > > >
<br>
> > > > Prism2/2.5/3
<br>
> > > > * Hostap driver.
<br>
> > > > * Full feature set (AP and client, WPA/WPA2/802.11X
authenticator and
<br>
> > > > supplicant)
<br>
> > > > * Monitor mode.
<br>
> > > > * 802.11b only (AFAIK)
<br>
> > > > * In in-tree kernel support.
<br>
> > > > * Not to be confused with Prism54g chipset.
<br>
> > > >
<br>
> > > > Atheros
<br>
> > > > * 802.11a/g
<br>
> > > > * Monitor mode.
<br>
> > > > * Supported by Madwifi drivers.
<br>
> > > > * Madwifi-ng has different API to standard Linux
Wifi Extensions - needs
<br>
> > > > to be carefully matched to wpa-supplicant version.
<br>
> > > >
<br>
> > > > So really, for 54g stuff you've got a choice
between Atheros/Madwifi and
<br>
> > > > IPW2100/2200, and even then IPW2100/2200 is only
supported in laptops
<br>
> > > > (mini-pci/pccard) AFAIK.
<br>
> > > >
<br>
> > > > I've had varying success with madwifi, using both
the original and "-ng"
<br>
> > > > versions. On the whole I've found its stability to
be lacking and
<br>
> > > > generally not as good as the Intel chipset.
<br>
> > > >
<br>
> > > > All that said, there are big changes going on in
the Linux Wifi stack
<br>
> > > > and all this will be changing soon. Software MAC
will be intergrated
<br>
> > > > into most drivers, meaning more chipsets will
support WPA/WPA2. This
<br>
> > > > will also mean a unified Wifi Extensions, so
systems like wpa-supplicant
<br>
> > > > and hostapd will be easier to maintain.
<br>
> > > >
<br>
> > > > Adrian
<br>
> > > >
<br>
> > > > On Wed, 2006-07-05 at 15:11 +0800, Chris Griffin
wrote:
<br>
> > > > > Sorry, I guess I assumed that if I was buying
new I would go for
<br>
> > > > > 802.11g. Mainly wanted to get away from WEP
due to inherent security
<br>
> > > > > issues.
<br>
> > > > >
<br>
> > > > >
<br>
> > > > > On 7/5/06, garry
<a class="moz-txt-link-rfc2396E" href="mailto:garbuck@westnet.com.au"><garbuck@westnet.com.au></a> wrote:
<br>
> > > > > >
<br>
> > > > > > Might be useful if you say which spec
card you want to buy.
<br>
> > > > > >
<br>
> > > > > > I still use the Enterasys 802.11b cards,
with Mandriva 2k6 they just work.
<br>
> > > > > >
<br>
> > > > > > HTH
<br>
> > > > > >
<br>
> > > > > > Garry
<br>
> > > > > >
<br>
> > > > > >
<br>
> > > > > >
<br>
> > > > > >
<br>
> > > > > > Chris Griffin wrote:
<br>
> > > > > >
<br>
> > > > > > > Greetings all,
<br>
> > > > > > >
<br>
> > > > > > > In light of the fact that such
things change at such a rapid rate, I
<br>
> > > > > > > am looking at upgrading my WiFi
cards and of course it is mandatory
<br>
> > > > > > > that they work flawlessly with Linux
(I run, mostly, Fedora). Could
<br>
> > > > > > > someone please give me some clues as
to what to get that, hopefully,
<br>
> > > > > > > will work out of the box?
<br>
> > > > > > >
<br>
> > > > > > > Regards,
<br>
> > > > > > > Chris Griffin
<br>
> > > > > > >
_______________________________________________
<br>
> > > > > > > PLUG discussion list:
<a class="moz-txt-link-abbreviated" href="mailto:plug@plug.org.au">plug@plug.org.au</a>
<br>
> > > > > > >
<a class="moz-txt-link-freetext" href="http://www.plug.org.au/mailman/listinfo/plug">http://www.plug.org.au/mailman/listinfo/plug</a>
<br>
> > > > > > > Committee e-mail:
<a class="moz-txt-link-abbreviated" href="mailto:committee@plug.linux.org.au">committee@plug.linux.org.au</a>
<br>
> > > > > > >
<br>
> > > > > >
<br>
> > > > > >
_______________________________________________
<br>
> > > > > > PLUG discussion list: <a class="moz-txt-link-abbreviated" href="mailto:plug@plug.org.au">plug@plug.org.au</a>
<br>
> > > > > >
<a class="moz-txt-link-freetext" href="http://www.plug.org.au/mailman/listinfo/plug">http://www.plug.org.au/mailman/listinfo/plug</a>
<br>
> > > > > > Committee e-mail:
<a class="moz-txt-link-abbreviated" href="mailto:committee@plug.linux.org.au">committee@plug.linux.org.au</a>
<br>
> > > > > >
<br>
> > > > >
_______________________________________________
<br>
> > > > > PLUG discussion list: <a class="moz-txt-link-abbreviated" href="mailto:plug@plug.org.au">plug@plug.org.au</a>
<br>
> > > > > <a class="moz-txt-link-freetext" href="http://www.plug.org.au/mailman/listinfo/plug">http://www.plug.org.au/mailman/listinfo/plug</a>
<br>
> > > > > Committee e-mail: <a class="moz-txt-link-abbreviated" href="mailto:committee@plug.linux.org.au">committee@plug.linux.org.au</a>
<br>
> > > >
<br>
> > > > _______________________________________________
<br>
> > > > PLUG discussion list: <a class="moz-txt-link-abbreviated" href="mailto:plug@plug.org.au">plug@plug.org.au</a>
<br>
> > > > <a class="moz-txt-link-freetext" href="http://www.plug.org.au/mailman/listinfo/plug">http://www.plug.org.au/mailman/listinfo/plug</a>
<br>
> > > > Committee e-mail: <a class="moz-txt-link-abbreviated" href="mailto:committee@plug.linux.org.au">committee@plug.linux.org.au</a>
<br>
> > > >
<br>
> > > _______________________________________________
<br>
> > > PLUG discussion list: <a class="moz-txt-link-abbreviated" href="mailto:plug@plug.org.au">plug@plug.org.au</a>
<br>
> > > <a class="moz-txt-link-freetext" href="http://www.plug.org.au/mailman/listinfo/plug">http://www.plug.org.au/mailman/listinfo/plug</a>
<br>
> > > Committee e-mail: <a class="moz-txt-link-abbreviated" href="mailto:committee@plug.linux.org.au">committee@plug.linux.org.au</a>
<br>
> >
<br>
> > _______________________________________________
<br>
> > PLUG discussion list: <a class="moz-txt-link-abbreviated" href="mailto:plug@plug.org.au">plug@plug.org.au</a>
<br>
> > <a class="moz-txt-link-freetext" href="http://www.plug.org.au/mailman/listinfo/plug">http://www.plug.org.au/mailman/listinfo/plug</a>
<br>
> > Committee e-mail: <a class="moz-txt-link-abbreviated" href="mailto:committee@plug.linux.org.au">committee@plug.linux.org.au</a>
<br>
> >
<br>
> _______________________________________________
<br>
> PLUG discussion list: <a class="moz-txt-link-abbreviated" href="mailto:plug@plug.org.au">plug@plug.org.au</a>
<br>
> <a class="moz-txt-link-freetext" href="http://www.plug.org.au/mailman/listinfo/plug">http://www.plug.org.au/mailman/listinfo/plug</a>
<br>
> Committee e-mail: <a class="moz-txt-link-abbreviated" href="mailto:committee@plug.linux.org.au">committee@plug.linux.org.au</a>
<br>
<br>
_______________________________________________
<br>
PLUG discussion list: <a class="moz-txt-link-abbreviated" href="mailto:plug@plug.org.au">plug@plug.org.au</a>
<br>
<a class="moz-txt-link-freetext" href="http://www.plug.org.au/mailman/listinfo/plug">http://www.plug.org.au/mailman/listinfo/plug</a>
<br>
Committee e-mail: <a class="moz-txt-link-abbreviated" href="mailto:committee@plug.linux.org.au">committee@plug.linux.org.au</a>
<br>
<br>
</blockquote>
_______________________________________________
<br>
PLUG discussion list: <a class="moz-txt-link-abbreviated" href="mailto:plug@plug.org.au">plug@plug.org.au</a>
<br>
<a class="moz-txt-link-freetext" href="http://www.plug.org.au/mailman/listinfo/plug">http://www.plug.org.au/mailman/listinfo/plug</a>
<br>
Committee e-mail: <a class="moz-txt-link-abbreviated" href="mailto:committee@plug.linux.org.au">committee@plug.linux.org.au</a>
<br>
<br>
</blockquote>
</body>
</html>