Re: hostap recently broken

From: Sam Leffler (sam_at_errno.com)
Date: 07/26/05

  • Next message: Kirk Davis: "RE: 6-BETA1 iwi + wpa_supplicant fails, and sometimes silently re boots"
    Date: Tue, 26 Jul 2005 09:29:26 -0700
    To: Michal Mertl <mime@traveller.cz>
    
    

    Michal Mertl wrote:
    > Sam Leffler wrote:
    >
    >>Michal Mertl wrote:
    >>
    >>>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.
    >>
    >>I just tried with CURRENT (from last night). 5212 card setup with TKIP
    >>for PTK and GTK. ap operating in 11g. Powerbook running Tiger
    >>associated and operated fine. 29Mb/s for upstream tcp netperf (sta and
    >>ap in close proximity--rssi 41).
    >>
    >>I appreciate you testing stuff but please try to diagnose your problems
    >>a bit harder and then provide more useful info like the h/w revs and the
    >>exact steps you use to setup a non-working system.
    >
    >
    > Sorry, I had the exact same HW setup as before which I described in my
    > email about the problem with bridging.
    >
    > I've got several Atheros 5212 cards (mac 5.9 phy 4.3 radio 3.6) and also
    > IPW notebook all running CURRENT, the notebook and the client several
    > days old (from before 2005-07-22 16:00 UTC).
    >
    > The most basic setup - 'ifconfig ath0 192.168.0.1 mediaopt hostap ssid
    > aaa' on the AP and 'ifconfig ath0 192.168.0.2 ssid aaa' worked like a
    > charm before the date and not after. With the newer kernel on the AP the
    > cards associate and as I've just found I can communicate between the
    > stations on the AP. Ping to the AP doesn't work even when I get the MAC
    > address of the AP via ARP. Adhoc connection works.

    I am unclear still on what happens. I believe you are saying:

    ping 192.168.0.1

    from the station to the ap fails. If so what does 80211stats show on
    the ap when this happens (do releveant error stats go up)? If you do

    80211debug +input

    on the ap do you get any log msgs about discarded frames?

    You also seem to say the sta resolves the ip w/ arp. Is the same true
    for the ap (i.e. that it resolves the ip address of the sta)? I'm
    assuming you are NOT running firewall rules do not have crypto setup and
    have not fiddled with parameters like apbridge (you didn't provide
    ifconfig output for each side).

    I rarely test direct communication between sta+ap; usually I bridge to a
    wired net and communicate with stations on the wired net (it's always
    what I'm doing when I report netperf numbers). Does bridged
    communication to a sta on another network work?

            Sam

    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"


  • Next message: Kirk Davis: "RE: 6-BETA1 iwi + wpa_supplicant fails, and sometimes silently re boots"

    Relevant Pages

    • Re: Train Phobia
      ... communicate with them via voice radio. ... Fitting wireless access points to the approaches of stations, ... if they are the relatively expensive sort like, ... platform alteration is when they actually see the train rolling into ...
      (uk.railway)
    • Re: ATTN: AKC
      ... though both stations were in the same town, and both of their signals were ... yes, and from what I hear on my scanner, hams do it all the time. ... repeaters when they could communicate simplex instead. ...
      (rec.radio.cb)