• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Minimum hardware?

Scheduled Pinned Locked Moved Wireless
4 Posts 2 Posters 2.7k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • H
    Horu
    last edited by Nov 7, 2006, 2:57 PM

    I have an old laptop (Sony PII 500Mhz, 192MB RAM) with Proxim 8470 card. I installed PF 1.0.1 on the HD and it's working fine. When I configure the WAN i/f as an AP with WPA2/AES I can connect to it from my XP laptop but it drops the connection after 20 seconds and doesn't broadcast the SSID again for approx 2 minutes. I also tried iit from my phone and get the same result. Should this work OK on the hardware?

    1 Reply Last reply Reply Quote 0
    • H
      hoba
      last edited by Nov 7, 2006, 5:50 PM

      It should, however I don't know your wireless card. Anything obvious at status>systemlogs? Maybe you should first verify that the card works without using any kind of encryption.

      1 Reply Last reply Reply Quote 0
      • H
        Horu
        last edited by Nov 7, 2006, 10:21 PM

        The card is

        Card Name: Proxim Orinoco [WWW] 8470-WD
        Interface type(s): PCMCIA
        Power: 85 mW EIRP (b), 60 mW EIRP (g)
        Chipset: Atheros AR5212 (b/g)

        I have a few of them working fine on both PF and XP and they work fine with aireplay, kismet, etc. I just have the problem when in AP/WPA2/AES mode. I saw some other posts mention an Atheros bug, could that be the problem?

        The client connects to the AP for a few seconds then starts searching for it again, the system log on PF reports

        Nov 7 22:23:12 hostapd: ath0: STA 00:09:2d:2b:c2:11 IEEE 802.11: deassociated
        Nov 7 22:23:10 hostapd: ath0: STA 00:09:2d:2b:c2:11 IEEE 802.11: associated
        Nov 7 22:22:59 hostapd: ath0: STA 00:09:2d:2b:c2:11 IEEE 802.11: deassociated
        Nov 7 22:22:58 hostapd: ath0: STA 00:09:2d:2b:c2:11 IEEE 802.11: associated
        Nov 7 22:22:58 hostapd: ath0: STA 00:09:2d:2b:c2:11 IEEE 802.11: deassociated
        Nov 7 22:22:58 hostapd: ath0: STA 00:09:2d:2b:c2:11 IEEE 802.11: deauthenticated due to local deauth request
        Nov 7 22:22:55 hostapd: ath0: STA 00:09:2d:2b:c2:11 IEEE 802.11: associated
        Nov 7 22:22:55 hostapd: ath0: STA 00:09:2d:2b:c2:11 IEEE 802.11: deassociated
        Nov 7 22:22:55 hostapd: ath0: STA 00:09:2d:2b:c2:11 IEEE 802.11: deauthenticated due to local deauth request
        Nov 7 22:22:52 hostapd: ath0: STA 00:09:2d:2b:c2:11 IEEE 802.11: associated
        Nov 7 22:22:52 hostapd: ath0: STA 00:09:2d:2b:c2:11 IEEE 802.11: deassociated
        Nov 7 22:22:52 hostapd: ath0: STA 00:09:2d:2b:c2:11 IEEE 802.11: deauthenticated due to local deauth request
        Nov 7 22:22:49 hostapd: ath0: STA 00:09:2d:2b:c2:11 IEEE 802.11: associated
        Nov 7 22:22:17 hostapd: ath0: STA 00:09:2d:2b:c2:11 IEEE 802.11: deassociated
        Nov 7 22:22:16 hostapd: ath0: STA 00:09:2d:2b:c2:11 IEEE 802.11: associated
        Nov 7 22:22:16 hostapd: ath0: STA 00:09:2d:2b:c2:11 IEEE 802.11: deassociated
        Nov 7 22:22:16 hostapd: ath0: STA 00:09:2d:2b:c2:11 IEEE 802.11: deauthenticated due to local deauth request
        Nov 7 22:22:13 hostapd: ath0: STA 00:09:2d:2b:c2:11 IEEE 802.11: associated
        Nov 7 22:22:13 hostapd: ath0: STA 00:09:2d:2b:c2:11 IEEE 802.11: deassociated
        Nov 7 22:22:13 hostapd: ath0: STA 00:09:2d:2b:c2:11 IEEE 802.11: deauthenticated due to local deauth request
        Nov 7 22:22:10 hostapd: ath0: STA 00:09:2d:2b:c2:11 IEEE 802.11: associated
        Nov 7 22:22:10 hostapd: ath0: STA 00:09:2d:2b:c2:11 IEEE 802.11: deassociated
        Nov 7 22:22:10 hostapd: ath0: STA 00:09:2d:2b:c2:11 IEEE 802.11: deauthenticated due to local deauth request
        Nov 7 22:22:07 hostapd: ath0: STA 00:09:2d:2b:c2:11 IEEE 802.11: associated

        1 Reply Last reply Reply Quote 0
        • H
          hoba
          last edited by Nov 8, 2006, 2:43 AM

          Maybe your card doesn't support WPA2 under freebsd. We don't detect the capabilities of the card concerning wpa2 afaik. You'll find a config script (generated from your gui settings) for the wireless card in your /tmp folder. Try to ssh in to your system and run the script manually. Does it reject some of the options that the script tries to set?

          1 Reply Last reply Reply Quote 0
          4 out of 4
          • First post
            4/4
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
            This community forum collects and processes your personal information.
            consent.not_received