[TAG] Answer blog
fahadsaeed11 at hotmail.com
Sat Feb 11 17:33:15 MSK 2006
I would have to agree with Kapil here.Yes the configuration process is
sometimes extremely difficulty.As Benjamin potrayed it ...it seems pretty
easy and in theory it is .But when done practically it is not that
The main problem is that the drivers available are for differernt
chipsets.The vendors do not care abt the chipsets and change the chipsets
without changing the product ID.It happened in our case with WMP11 if i am
Obviously once you get the correct sets of drivers, kernel and chipsets it
The lab setup that we did in UET LAHORE required the cards to work in ad-hoc
mode.We used madwifi drivers .Now as you may know that there is beacon
problem in the madwifi drivers.and the ad-hoc mode it self does not work
reliably.The mode that we implemented was Ad-hoc mode Cluster Head
Routing.In simple words it meant that one of the PC's were configured to be
in Master mode and there were bunch of PCs around.It would have been really
cool if we could get it work in 'pure ad-hoc' mode nevertheless it served
the LAB purposes.
>From: "Benjamin A. Okopnik" <ben at linuxgazette.net>
>To: fahad saeed <fahadsaeed11 at hotmail.com>, tag at lists.linuxgazette.net
>Subject: Re: [TAG] Answer blog
>Date: Fri, 10 Feb 2006 15:03:21 -0500
>On Fri, Feb 10, 2006 at 11:26:59AM -0800, Kapil Hari Paranjape wrote:
> > Just to be completely clear. I have not managed to get two laptops
> > to communicate with each other using ad-hoc mode. Both sides say the
> > (wireless) link is up, but I couldn't get them to send IP packets to
> > each other. I have only managed to get an IP link when there is a
> > common access point (hub).
>That's something I'd really like to learn to do myself. I've thought
>about it on occasion, and it always seemed like a doable thing - but I
>never got any further than that, so a description of the actual setup
>would be a really cool thing.
>When I read about those $100 laptops that Negroponte et al are cranking
>out, I pictured a continent-wide wireless fabric of laptops stretching
>across, say, Africa - with some sort of a clever NAT and
>bandwidth-metering setup on each machine where any host within reach of
>an AP becomes a "relay station" accessible to everyone on that WAN.
>Yeah, it would be dead slow if there were only a few hosts within reach
>of APs... but the capabilities of that kind of system would be awesome.
> > The problem is that getting wireless cards to work with Linux has
> > been such a complicated issue in the past that most HOWTO's spend a
> > lot of time in explaining how to download and compile the relevant
> > kernel modules and load firmware. The authors are probably exhausted
> > by the time they got to the details of setting up networking :)
>I must say that, in this case, "the Devil is not as bad as he's
>painted". In my experience of wireless cards under Linux has consisted
>1) Find the source on the Net and download it;
>2) Unpack the archive in /usr/src/modules;
>3) 'make; make install' the module and add it to the list in
>Oh, and run 'make; make install' every time you recompile the kernel.
>Not what I'd call terribly difficult.
>* Ben Okopnik * Editor-in-Chief, Linux Gazette * http://linuxgazette.net *
Express yourself instantly with MSN Messenger! Download today it's FREE!
More information about the TAG