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

[Bear Giles]

The wifi is new because I was hoping to avoid running a 25' cat5 cable.  I
didn't touch the wired config until I saw it wasn't coming up after I strung
the cable so I could google on something larger than my netbook.

Rebooting the wifi hub and AP didn't help.

Curiouser and curiouser I can get a static address at 192.168.0.x (albeit
with some IOCTL errors) and ping another system in the same address space.
It barfs on a static address at 192.168.1.99.  I know nothing else has ever
used that IP address.

As for the rant - I'm all for making the system "mom-friendly" but it still
needs to maintainable by hand.  There's something wrong when someone has
been setting up networking (including local DHCP servers) for years but
can't even find the fracking config file on a linux system now.


On Fri, Jun 18, 2010 at 5:49 PM, David L. Anselmi <anselmi at anselmi.us>wrote:

> 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*.
>
> If you didn't change the Ubuntu system (just moved it to a different room),
> why are you mucking with
> its config?  Wouldn't it be more reasonable to check the network port etc
> (which I assume you've done)?
>
> Here's a true story: our office Internet connection went down.  The network
> admin called and asked
> me to check the network gear--all green and blinky.  So he asked me to
> trace all the cables and make
> sure there were no bad connections BEFORE HE ADMITTED HE WAS MUCKING WITH
> THE FIREWALL.  I suggested
> using a laptop and ping to determine whether the problem was inside or
> outside our building and
> determined that outside the firewall the Internet worked fine.  (Then a
> Cisco tech had to unscrew
> his "only allow IPsec traffic" rule.)
>
> > (*) 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.
>
> So it's a DHCP issue, and likely specific to the AP/Ubuntu combination.
>  Did you collect any data on
> the behavior of those DHCP transactions?
>
> Sorry, I'm thinking about the root cause and not your rant against Ubuntu.
>  Not very helpful I'm sure.
>
> Dave
> _______________________________________________
> 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/1a85797c/attachment.html>