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

    Wifi Card TP-LINK TL-WDN4800 issues

    Scheduled Pinned Locked Moved Wireless
    7 Posts 4 Posters 2.1k 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.
    • M
      MrMatthew
      last edited by

      Hello,

      I have the wifi card TP-LINK TL-WDN4800 https://www.freebsd.org/releases/10.3R/hardware.html#wlan which is supported in the Freebsd 10.x versions. When I try to assing an interface the card is not being detected. when I log in and run pciconf -lv it shows the following

      none3@pci0:3:0:0:ย  class=0x028000 card=0x3112168c chip=0x0030168c rev=0x01 hdr=0x00
      Vendor = 'Qualcomm Atheros'
      device = 'AR93xx Wireless Network Adapter
      class = network

      I went looking online and found to add the following lines to /boot/loader.conf

      if_ath_load="YES"
      wlan_wep_load="YES"
      wlan_ccmp_load="YES"
      wlan_tkip_load="YES"

      but I still can not see/assign an interface to this device. Am I missing something?
      Any help is appreciated. Thank you.

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        They must have changed the chip used in that model ("name" brands are awful about that), the chip you have there is apparently not supported.

        We have all of the necessary options in the kernel.

        Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

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

          According to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207445 (same pciid) it works in 10 (ie - should be at least recognized).
          Maybe there is something useful in boot log?

          Need full pfSense in a cloud? PM for details!

          1 Reply Last reply Reply Quote 0
          • jimpJ
            jimp Rebel Alliance Developer Netgate
            last edited by

            The person reporting that bug said it worked on 11-CURRENT in January and was broken shortly after. No mention of 10.

            There isn't anything to do with it โ€“ hold onto it until pfSense 2.4-RELEASE in the next few months and see if it works once we are on a FreeBSD 11 base, but given that the bug is still open and unresolved I wouldn't hold out much hope.

            Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

            Need help fast? Netgate Global Support!

            Do not Chat/PM for help!

            1 Reply Last reply Reply Quote 0
            • B
              bobgoblin
              last edited by

              Ok. Thank you jimp. I will wait till 2.4 release.

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

                @jimp:

                The person reporting that bug said it worked on 11-CURRENT in January and was broken shortly after. No mention of 10.

                Oh, somehow missed that.

                In https://forum.pfsense.org/index.php?topic=70575.0#msg_387255 there is a report about it working in 10, but at same time - link to http://adrianchadd.blogspot.ru/2013/03/ar9380-support-on-freebsd-why-its-taken.html
                So, it should be at least detected in 2.3 as wifi card. Are you sure it really works? Maybe it should be pushed to PCI slot a little harder. :D

                Need full pfSense in a cloud? PM for details!

                1 Reply Last reply Reply Quote 0
                • jimpJ
                  jimp Rebel Alliance Developer Netgate
                  last edited by

                  In older versions of pfSense we had included a newer wireless stack, but it was crashing on 2.3 when we tried, so we had to roll back.

                  Waiting for 2.4 is one answer, getting a real AP is the better answer. There is nothing else to do.

                  Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

                  Need help fast? Netgate Global Support!

                  Do not Chat/PM for help!

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