Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email firstname.lastname@example.org
From: Jean Tourrilhes (jtbougret.hpl.hp.com)
Date: Tue May 08 2001 - 19:05:55 CDT
On Wed, May 09, 2001 at 09:45:18AM +1000, Robert Scholten wrote:
> > By the way... Have you upgraded the firmware on your AP ? And
> > maybe doing a bit of AP filtering may help...
> Sorry Jean - we're not using an AP, hence trying to use the ad-hoc mode.
> We have several wireless clients at one end, talking to a linux router,
> which then connects to the internet via another linux router 23km away.
> No AP. It all worked very very well with proprietary ad-hoc mode and
> wvlan_cs and the old firmware. I'm thinking about reverting back to that,
> and kernel 2.2.14-5.0, but will persevere a little longer.
> Thanks, and again, I really do appreciate all your valuable work.
Sorry, I'm doing too many stuff, so not keeping enough
context... That's why it's good to refresh my memory.
I don't remember why exactly you did upgrade driver. Might
have been the Tx Timeouts. You are right about demo mode, it's simpler
than IBSS mode (no ad-hoc beacons), so less likely to fail.
On the other hand, you are not required to use IBSS mode, why
don't you give the good old Ad-Hoc demo mode with orinoco_cs.c a try ?
It still works fine (tested yesterday). Just check on my Orinoco web
page how to enable it...
Also, you can still use wvlan_cs with kernel 2.4. It's also
documented on my Wavelan-IEEE web pages. However, I would be surprised
to see wvlan_cs working better than orinoco_cs.
I also tested orinoco_cs will all firmware I could put my hand
on, and it works (in my setup, as old as 1.16). On the other hand, I
don't know if the Cabletron tools allow to revert to an older