[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#604613: [mailer-daemon@googlemail.com: Delivery Status Notification (Failure)]

submitter 604613 Robert Wallner <robert@scinova.biz>
--- Begin Message ---
Delivery to the following recipient failed permanently:


Technical details of permanent failure: 
Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 550 550 5.1.1 <crk5070@psu.edu>... User unknown (state 13).

----- Original message -----

DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
Received: by with SMTP id wo2mr1703420igb.72.1342281319363;
        Sat, 14 Jul 2012 08:55:19 -0700 (PDT)
Return-Path: <jrnieder@gmail.com>
Received: from burratino (cl-1372.chi-02.us.sixxs.net. [2001:4978:f:55b::2])
        by mx.google.com with ESMTPS id z3sm4194902igc.7.2012.
        (version=SSLv3 cipher=OTHER);
        Sat, 14 Jul 2012 08:55:18 -0700 (PDT)
Date: Sat, 14 Jul 2012 10:55:11 -0500
From: Jonathan Nieder <jrnieder@gmail.com>
To: Robert Wallner <robert@scinova.biz>
Cc: 604613@bugs.debian.org, crk5070@psu.edu
Subject: Re: ath5k driver refuses to get an IP address from dhclient in
Message-ID: <[🔎] 20120714155511.GA22014@burratino>
References: <CAMhKhsQ6No51taAJGJd9wXKjVe7rWX2u9L41qxGDyu121AOC6g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAMhKhsQ6No51taAJGJd9wXKjVe7rWX2u9L41qxGDyu121AOC6g@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)


Robert Wallner wrote:

> I can confirm that it works for me on linux 3.2.0 from squeeze-backports,
> while failing on 2.6.32 from squeeze.

Thanks.  Can you spell it out more for me?  What kernel did you test
from squeeze (you can get the installed kernel version with

	dpkg-query -W linux-image-$(uname -r)

and the version number of the running kernel is in parentheses in

	cat /proc/version

output)?  What authentication scheme are you using (WEP, WPA, or
something else)?  What is your wireless chip and other hardware
configuration (full "dmesg" output from booting and reproducing the
problem would be helpful).  Can you reproduce it using iproute and iw,
like so:

	ip link set wlan0 up
	iw dev wlan0 scan
	iw dev wlan0 connect -w <ssid> key d:0:<key>
	dhclient wlan0

Does installing the crda package from wheezy (I haven't checked if it
can be installed in squeeze without too much surgery) or upstream make
things any better or worse?  If you have time to try it, could you
bisect through the pre-compiled kernels in-between listed at
http://snapshot.debian.org/package/linux-2.6/ to find which one fixes
the bug?  Does an iw event log retrieved as described at [1] reveal
anything interesting?

Hope that helps,

[1] http://linuxwireless.org/en/users/Documentation/Reporting_bugs

--- End Message ---

Reply to: