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

    Fresh install gives no wireless

    Scheduled Pinned Locked Moved 1.2.1-RC Snapshot Feedback and Problems-RETIRED
    15 Posts 10 Posters 9.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.
    • T
      thinair
      last edited by

      I have the same problem, but I installed the upgrade.  I'm using an atheros PCMCIA card.  Same no carrier status.

      Nelson Papel

      1 Reply Last reply Reply Quote 0
      • C
        cheekymonkey
        last edited by

        same here (wrap with cm9 running pfSense-20080711-0208), but on bootup I saw

        "ieee80211_load_module: load the wlan_scan_ap module by hand for now." quite a few times

        google says "Short answer is the scanning support is now broken out into separate modules that you must either load or specify in your kernel config file. wlan_scan_sta for sta mode operation. wlan_sta_ap for ap mode operation."
        but as I cant compile a kernel it doesnt mean much to me

        1 Reply Last reply Reply Quote 0
        • D
          David_W
          last edited by

          You probably don't need to build a kernel - probably all it needs is a line for each module you need to load in /boot/loader.conf.

          1 Reply Last reply Reply Quote 0
          • T
            thinair
            last edited by

            This is all I saw in the logs regarding the interface:

            Jul 11 00:06:27 kernel: ath0: unable to reset hardware; hal status 0
            Jul 11 00:06:27 kernel: ath0: unable to reset hardware; hal status 0
            Jul 11 00:06:27 kernel: ath0: ath_chan_set: unable to reset channel 6 (2437 Mhz, flags 0x490 hal flags 0x150)
            Jul 11 00:05:53 kernel: ath0: mac 5.9 phy 4.3 radio 4.6
            Jul 11 00:05:53 kernel: ath0: Ethernet address: 00:0f:3d:68:8d:31
            Jul 11 00:05:53 kernel: ath0: using obsoleted if_watchdog interface
            Jul 11 00:05:53 kernel: ath0: [ITHREAD]
            Jul 11 00:05:53 kernel: ath0: <atheros 5212="">mem 0x88000000-0x8800ffff irq 11 at device 0.0 on cardbus0

            edit: upon reading the logs, I set the wireless channel from 'auto' to channel 1 and the wireless works again with an 'associated' status.</atheros>

            Nelson Papel

            1 Reply Last reply Reply Quote 0
            • C
              cheekymonkey
              last edited by

              Still doesn't make mine work
              On my box or an upgrade file (20080710-0010) if I check /boot/kernel I cant see anything like wlan_scan_ap  or  wlan_scan_sta

              But I just built a freeBSD 7.0 vmware image and checking /boot/kernel I see the following.

              -r-xr-xr-x root/wheel    7543 2008-02-25 05:16 /boot/kernel/wlan_scan_ap.ko
              -r-xr-xr-x root/wheel    47319 2008-02-25 05:16 /boot/kernel/wlan_scan_ap.ko.symbols
              -r-xr-xr-x root/wheel    18060 2008-02-25 05:16 /boot/kernel/wlan_scan_sta.ko
              -r-xr-xr-x root/wheel    56865 2008-02-25 05:16 /boot/kernel/wlan_scan_sta.ko.symbols
              -r-xr-xr-x root/wheel    13863 2008-02-25 05:16 /boot/kernel/wlan_tkip.ko
              -r-xr-xr-x root/wheel    54171 2008-02-25 05:16 /boot/kernel/wlan_tkip.ko.symbols
              -r-xr-xr-x root/wheel    8914 2008-02-25 05:16 /boot/kernel/wlan_wep.ko
              -r-xr-xr-x root/wheel    45589 2008-02-25 05:16 /boot/kernel/wlan_wep.ko.symbols
              -r-xr-xr-x root/wheel    4049 2008-02-25 05:16 /boot/kernel/wlan_xauth.ko
              -r-xr-xr-x root/wheel    40075 2008-02-25 05:16 /boot/kernel/wlan_xauth.ko.symbols

              along with some tkip , wep and xauth stuff.

              thinair, what are snapshot are you running, and was it an upgrade or full install, embedded or ISO build?

              1 Reply Last reply Reply Quote 0
              • T
                thinair
                last edited by

                I upgraded to 1.2.1-20080706-0037 from 1.2 stable, full version.
                Since then I have upgraded through 20080707-2021, 20080709-0101, 20080710-0010, and now 20080711-0140.

                Nelson Papel

                1 Reply Last reply Reply Quote 0
                • S
                  singerie
                  last edited by

                  @thinair:

                  Jul 11 00:06:27 kernel: ath0: unable to reset hardware; hal status 0

                  I have the same issue

                  1 Reply Last reply Reply Quote 0
                  • D
                    DeCex
                    last edited by

                    Almost same issue;
                    -pfSense-Full-Update-1.2.1-TESTING-SNAPSHOT-20080711-0140
                    -Netgear WG311T PCI card on pfSense

                    After i manually changed the channel it got associated and registered the Turbo function, but when try to connect from a client it dont work. Downgrade to 1.2 stable for now and use 54mbit module, that worked for me.

                    I think Im gonna wait till everything gets stable since im very noob  ::)

                    1 Reply Last reply Reply Quote 0
                    • S
                      singerie
                      last edited by

                      @DeCex:

                      Almost same issue;
                      -pfSense-Full-Update-1.2.1-TESTING-SNAPSHOT-20080711-0140
                      -Netgear WG311T PCI card on pfSense

                      After i manually changed the channel it got associated and registered the Turbo function, but when try to connect from a client it dont work. Downgrade to 1.2 stable for now and use 54mbit module, that worked for me.

                      I think Im gonna wait till everything gets stable since im very noob  ::)

                      I will try to change manually the channel, and see if it work. also, I have a super G card, so i can check the turbo :)

                      1 Reply Last reply Reply Quote 0
                      • C
                        cheekymonkey
                        last edited by

                        Still no luck with the latest snapshots of both this and 1.3, signing off testing until for now until someone else can replicate this problem.

                        1 Reply Last reply Reply Quote 0
                        • A
                          adrianhensler
                          last edited by

                          I tried a wireless nic (first time to try this with pfSense; previously using wrt54g externally for wireless; works great).

                          It seems to allow the laptop to connect okay for the first 10 seconds; but it seems to not be bridging correctly with the LAN or else I have a setting done incorrectly - it seems to be that the wpa2 authenticates but then the card doesn't get an IP so it drops after 10 seconds. That's ust me thinking I understand what is going on.   I can see in the logs that it connects ok but I never see any logs entries in the dhcp log.

                          In my case I think it might be user error; I only mention what I am seeing in case it helps someone else identify a problem.

                          edit

                          To try to be at least a tiny bit helpful; this is what I see on the system log:

                          JJul 14 23:50:02 hostapd: ral0: STA 00:19:7d:d4:44:fe IEEE 802.11: deassociated
                          Jul 14 23:49:17 hostapd: ral0: STA 00:19:7d:d4:44:fe WPA: group key handshake completed (WPA)
                          Jul 14 23:49:17 hostapd: ral0: STA 00:19:7d:d4:44:fe WPA: pairwise key handshake completed (WPA)
                          Jul 14 23:49:17 hostapd: ral0: STA 00:19:7d:d4:44:fe IEEE 802.11: associated

                          Not sure why it just drops - as I say; it doesn't seem to try to talk to dhcp according to the logs.I do see this:

                          Jul 14 23:59:19 OPT1 0.0.0.0:68 255.255.255.255:67 UDP

                          But then nothing on the dhcp logs.

                          My rule on the wireless NIC (opt1):

                          Proto  	Source  	Port  	Destination  	Port  	Gateway  	Schedule  	Description  	
                          	* 	* 	* 	* 	* 	* 	  	allow any wireless 
                          

                          Any pointers welcome - I'm still happy to this this is user error.

                          1 Reply Last reply Reply Quote 0
                          • H
                            hansru
                            last edited by

                            For me as well
                            Alix configuration with Full install on Microdrive. Perfect working WiFi, after upgrade no wifi, downgrading tot RC 1.2 and Wifi works again.

                            Regards,
                            Hans

                            1 Reply Last reply Reply Quote 0
                            • First post
                              Last post
                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.