NM bug? Ad-hoc network

Andrew Farris flyindragon1 at aol.com
Thu Aug 13 18:38:28 UTC 2009

On Thu, 2009-08-13 at 13:19 -0500, Chris Mohler wrote:
> On Thu, Aug 13, 2009 at 9:39 AM, Chris Jones<jonesc at hep.phy.cam.ac.uk> wrote:
> > You should be careful to not blame NM for problems that are actually
> > caused by poor wireless card drivers. In my experience most problems
> > people blame on NM are actually not NM's fault but elsewhere.
> >
> >  From memory the NM devs are (rightly in my view) quite strict on not
> > polluting their code with workarounds and nasty hacks for poorly
> > behaving drivers. Their view is fix the problems at source.
> >
> > I'm not necessarily saying this is what is happening here, just you
> > should probably do some investigating first to try and find out where
> > the real problem is, before posting bug reports.
> Good advice.  I did try two separate interfaces (Intel built-in and ZD
> external) first, but I should dig around some more before pinning it
> on NM.
> Anyone on the list been able to create an ad-hoc wifi network through
> the NM applet (without installing dnsmasq)?

Both my laptop and desktop already had dnsmasq-base installed by
default, so i was able to create ad-hoc wireless networks just fine out
of box.

however, i did note that I had issues connecting to the ad-hoc networks
I created. I can create/see them just fine, but I simply cant connect to

Anybody else?

Beware of a dark-haired man with a loud tie.

More information about the ubuntu-users mailing list