Skip to Content.
Sympa Menu

unclug - Re: [unclug] sudden wireless issues in Manning

unclug AT lists.ibiblio.org

Subject: UNC Linux Users Group

List archive

Chronological Thread  
  • From: Cristóbal Palmer <cmpalmer AT metalab.unc.edu>
  • To: UNC Linux Users Group <unclug AT lists.ibiblio.org>
  • Subject: Re: [unclug] sudden wireless issues in Manning
  • Date: Tue, 15 Jan 2008 22:44:28 -0500

On Tue, Jan 15, 2008 at 08:09:28PM -0500, Douglas A. Whitfield wrote:
>
> Please cut and past the Ping results:
> whitdoug@linux-laptop:~$ ping 152.2.221.116
> PING 152.2.221.116 (152.2.221.116) 56(84) bytes of data.
> From 169.254.5.184 icmp_seq=1 Destination Host Unreachable
> From 169.254.5.184 icmp_seq=2 Destination Host Unreachable


169.254.5.184 is a "link local" address. The 169.254/16 range is
reserved for situations where there's no DHCP server visible. There
are various implementations of "zeroconf", in your case Avahi:

http://en.wikipedia.org/wiki/Zeroconf

What updates did you pull recently? Kernel (uname -r)?

What's the output of 'ifconfig -a'?

What happens if you do the following (one command per line):

sudo su -l
/etc/init.d/NetworkManager stop
/etc/init.d/networking stop
ifconfig [your wireless interface] up
iwconfig [your wireless interface] essid UNC-1
iwconfig [your wireless interface] key [the UNC hex key]
dhclient [your wireless interface]

Do you get a valid lease? If you do, then your problem is with
NetworkManager or some other part of _your_ networking software stack,
and I recommend rolling back recent updates or otherwise reverting to
a known-good setup. If you don't get a lease, then there's more
troubleshooting to do.

Cheers,
--
Cristóbal Palmer
ibiblio.org systems administrator




Archive powered by MHonArc 2.6.24.

Top of Page