From owner-freebsd-current@FreeBSD.ORG  Mon Jul 25 20:12:17 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: freebsd-current@freebsd.org
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 2391016A420
	for <freebsd-current@freebsd.org>; Mon, 25 Jul 2005 20:12:17 +0000 (GMT)
	(envelope-from mime@traveller.cz)
Received: from ss.eunet.cz (ss.eunet.cz [193.85.228.13])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5C6E243D58
	for <freebsd-current@freebsd.org>; Mon, 25 Jul 2005 20:12:15 +0000 (GMT)
	(envelope-from mime@traveller.cz)
Received: from localhost.i.cz (ss.eunet.cz [193.85.228.13])
	by ss.eunet.cz (8.13.1/8.13.1) with ESMTP id j6PKC2D7035812;
	Mon, 25 Jul 2005 22:12:02 +0200 (CEST)
	(envelope-from mime@traveller.cz)
From: Michal Mertl <mime@traveller.cz>
To: freebsd-current@freebsd.org
Content-Type: text/plain
Date: Mon, 25 Jul 2005 22:11:58 +0200
Message-Id: <1122322318.1042.12.camel@genius1.i.cz>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port 
Content-Transfer-Encoding: 7bit
Cc: Sam Leffler <sam@errno.com>
Subject: hostap recently broken
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jul 2005 20:12:17 -0000

Hello,

I've just found out that something very recently broke hostap on FreeBSD
CURRENT. The client associates and gets the MAC address of the AP. When
I run tcpdump on the AP I see the pings from the client getting in but
the AP doesn't reply. The ARP protocol works but nothing else does.

Source checked on 2005-07-22 16:00 UTC works fine.

The AP card is atheros but just reverting the last changes to the driver
doesn't help.

Michal