linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Karl Hiramoto <karl@hiramoto.org>
To: hostap@lists.shmoo.com,
	linux-wireless <linux-wireless@vger.kernel.org>,
	"ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>
Subject: Re: [ath9k-devel] hostapd not sending beacons, and no traffic.
Date: Fri, 22 May 2009 21:20:22 +0200	[thread overview]
Message-ID: <4A16FAF6.7030403@hiramoto.org> (raw)
In-Reply-To: <4A16C6DC.7070502@hiramoto.org>

If anyone can help me with this, I'd appreciate it.  I thin the issue may be with the TX, but I'm not sure where 
to look next. I'm willing to test any patches. 

Using wireless-testing from today, but the same occurs on 2.6.30-rc6

I simplified my test case and what fails still is copying from one 
interface to another when routing.   I  now have no bridges.

# ip addr
1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue
   link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
   inet 127.0.0.1/8 scope host lo
2: eth1: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
   link/ether 00:13:01:00:02:18 brd ff:ff:ff:ff:ff:ff
   inet 192.168.10.55/24 brd 192.168.10.255 scope global eth1
3: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
   link/ether 9e:b6:45:72:d7:98 brd ff:ff:ff:ff:ff:ff
4: wmaster0: <UP,10000> mtu 0 qdisc pfifo_fast qlen 1000
   link/ieee802.11 00:0e:8e:15:6e:16 brd 00:00:00:00:00:00
5: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
   link/ether 00:0e:8e:15:6e:16 brd ff:ff:ff:ff:ff:ff
6: wlan0_0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc cbq qlen 1000
   link/ether 00:0e:8e:15:6e:16 brd ff:ff:ff:ff:ff:ff
   inet 192.168.1.1/24 brd 192.168.1.255 scope global wlan0_0
8: mon.wlan0_0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast 
qlen 1000
   link/[803] 00:0e:8e:15:6e:16 brd ff:ff:ff:ff:ff:ff



# ip route
192.168.1.0/24 dev wlan0_0  proto kernel  scope link  src 192.168.1.1
192.168.10.0/24 dev eth1  proto kernel  scope link  src 192.168.10.55
127.0.0.0/8 dev lo  scope link
default via 192.168.10.254 dev eth1  proto static


Downloading a 40MB file from a http server on eth1 lan   to  wifi client 
on  access point  wlan0_0,     The connection at some point of the http 
file download fails.  Usually I can download at least 300KB of data before the error occurs. 


hostapd.conf:

interface=wlan0_0
driver=nl80211
logger_syslog=-1
logger_syslog_level=2
logger_stdout=0
logger_stdout_level=2
dump_file=/tmp/hostapd/hostapd.0.dump
ssid=karl
channel=1
hw_mode=g
auth_algs=1
macaddr_acl=0
accept_mac_file=/tmp/hostapd/hostapd.wlan0_0.accept
deny_mac_file=/tmp/hostapd/hostapd.wlan0_0.deny
ignore_broadcast_ssid=0
wpa=3
wpa_passphrase=hiramoto
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP CCMP
ieee8021x=0
eap_server=0


600KB of kernel log messages with modprobe ath9k debug=0xFFFFFFFF
at: http://karl.hiramoto.org/ath9k.txt


Thanks.
--
Karl

      parent reply	other threads:[~2009-05-22 19:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-22 11:24 hostapd not sending beacons, and no traffic Karl Hiramoto
2009-05-22 13:48 ` [ath9k-devel] " Karl Hiramoto
2009-05-22 15:38   ` Karl Hiramoto
2009-05-22 18:06     ` Karl Hiramoto
2009-05-22 19:20     ` Karl Hiramoto [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A16FAF6.7030403@hiramoto.org \
    --to=karl@hiramoto.org \
    --cc=ath9k-devel@lists.ath9k.org \
    --cc=hostap@lists.shmoo.com \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).