[lug] ubuntu networking: when it's bad, it's really, really bad

[Bear Giles]

I killed network manager and the wifi popped right up when I ran
wpa_supplicant manually.  So there's that - it's definitely not a problem
with the networking stack in general or the wifi hardware specifically.

The wired network still isn't picking up dhcp though.  Again I know the
networking stack and hardware is fine since I can establish a static ip
address and see another system on the network but it's just not seeing the
DHCP responses (or sending them) to the 192.168.1.x net.


On Fri, Jun 18, 2010 at 6:20 PM, Elyse M. Grasso
<emgrasso at data-raptors.com>wrote:

> On Friday, June 18, 2010 05:33:14 pm Bear Giles wrote:
> > Augh!  For the last few systems the Ubuntu networking 'has just worked'.
> >
> > But now, after literally doing nothing but moving a system from one room
> to
> > another(*) my networking is REALLY hosed.  The wired network isn't
> picking
> > up DHCP and the wireless networking is totally hosed as well.  I've gone
> > through Preferences > Network Configuration but all of the settings just
> go
> > *poof*.  I tried editing the files directly but the wired network isn't
> > getting picked up and as far as I can tell the wpa_supplicant
> configuration
> > is handled by unicorn farts.
> >
> > Seriously, that particular service is really getting on my nerves.  None
> of
> > the source files (in /etc/init.d, /etc/wpa_supplicant and
> > /etc/network/*.d/wpa_supplicant.sh) seem to refer to a configuration file
> > and when I try to kill the daemon so I can set up the networking manually
> > some process is respawning it.  But again nobody will admit to it, at
> least
> > via grepping the likely locations.
> >
> > Ideas?
> >
> > Bear
> >
> > (*) Well, strictly speaking, I went from a wired connection to the wifi
> hub
> > to a wired connection to an extension access point.  And I had to replace
> > the wifi hub since the old one was getting a little flaky.  But neither
> > should matter - several other systems are on that AP without incident and
> > DHCP is DHCP.
> The service that spawns wpa-supplicant  is NetworkManager, but I have found
> it
> tends to be cranky about syncing up with some routers. I cleaned it out
> completely and loaded wicd instead which seems happier with my router. (You
> need to be sure the Network management stuff is completely gone or you end
> up
> with two processes spawning wpa_supplicant, which is very bad.)
>
> --
> Elyse Grasso
>
> http://www.data-raptors.com Computers and Technology
> http://www.astraltrading.com Divination and Science Fiction
> http://www.data-raptors.com/global-cgi-
> bin/cgiwrap/emgrasso/blosxom.cgi WebLog
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: irc.hackingsociety.org port=6667 channel=#hackingsociety
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lug.boulder.co.us/pipermail/lug/attachments/20100618/4474e75f/attachment.html>