Logo United Kingdom

Register | Login 

TP-Link TL-WDN4800 Wireless N Dual Band (PCIe, 450Mbps)

Network 802.11n, Network card, PCIe, TP-Link, WiFi

TP-Link TL-WDN4800 Wireless N Dual Band (PCIe, 450Mbps)
Linux compatibility: Only the Linux compatibility is rated on this page, not the general quality of the product. If you use this product with Linux, please rate it and share your experience in the comment area of this page (bottom) to support other Linux users.
13 votes, average: 4.4 out of 513 votes, average: 4.4 out of 513 votes, average: 4.4 out of 513 votes, average: 4.4 out of 513 votes, average: 4.4 out of 5
  ( 4.4 with 13 ratings)

Price: £ 24.00 (on stock)
(without shipping costs) Prices provided by Amazon do not include shipping costs that might be due depending on product and Amazon Marketplace supplier.

 Buy from

Price trend
TP-Link TL-WDN4800 Wireless N Dual Band 
Minimum: £ 16.99 
Maximum: £ 36.28  
Updated: 10/04/2016 02:50

Review of Linux Compatibility

The PCI-Express card TP-Link TL-WDN4800 has the PCI ID 168c:0030. The card bases on the Atheros chipset AR9380 and is recognized by the Linux kernel (e.g. Ubuntu 12.10) in the following way:

20:00.0 Network controller: Atheros Communications Inc. AR9300 Wireless LAN adaptor (rev 01)
Subsystem: Atheros Communications Inc. Device [168c:3112]

The card is fully supported by the kernel module ath9k. If an older version of the driver is used the connection can show a very low bandwidth. In this case it is necessary to disable the hardware encryption of the WiFi chipset to allow a higher data throughput. To achieve this the Kernel module ath9k has to be loaded with an additional option, which can be set in the file /etc/modprobe.d/ath9k.conf:

options ath9k nohwcrypt=1

The kernel module ath9k is loawird als Treiber automatisch geladen:

ath: EEPROM regdomain: 0x21
ath: EEPROM indicates we should expect a direct regpair map
ath: Country alpha2 being used: AU
ath: Regpair used: 0x21
ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control'
ath: EEPROM regdomain: 0x809c
ath: EEPROM indicates we should expect a country code
ath: doing EEPROM country->regdmn map search
 ath: country maps to regdmn code: 0x52
ath: Country alpha2 being used: CN
ath: Regpair used: 0x52
ieee80211 phy1: Selected rate control algorithm 'ath9k_rate_control'

Manufacturer spezifications can be found at:

Similar Linux Hardware

scroll left scroll right


13 Responses to “TP-Link TL-WDN4800 Wireless N Dual Band (PCIe, 450Mbps)”

  • Cory Hilliard says:

    Worked flawlessly out of the box. Using Fedora 23 / Cinnamon DE
    uname -r = 4.4.8-300.fc23.x86_64

  • fallen00sniper says:

    ubuntu 14.04.1 works out of box for a few hours and the just 3 seconds after connecting to the access point it will only allow ping, no browsing.

    wish they would make a linux driver, using ndiswrapper and forced to use the windows xp driver :(

    apparently ubuntu uses ath9k and it doesn’t seem all to compatible.

    54mbps solid connection with ndiswrapper though, so better than what i had before i guess.

    • fallen00sniper says:

      I got it to work with a Windows 8.1 driver, just noticed i should read, going to try the nohwcrypt=1 with the ath9k driver and see if it works properly with a native driver, the rest of you seem to have had no issue.

    • AMD_Fan says:

      It’s surprising that ping does work but web browsing not. I would have guessed that this is some configuration error instead of a driver problem.
      Is DNS and routing working correctly on the console?

      You should definitely try the nohwcrypt option with the ath9k driver, since this one often solves problems with the driver.

    • fallen00sniper says:

      It didn’t, I’m back to using ndiswrapper.

      I’m thinking ipv6 may be a issue, it doesn’t seem to be using ipv6 it works fine now, just not at top speed, which is why I bought the card to begin with.

    • fallen00sniper says:

      figured the problem out extensive googling, my wireless modem had a semi-hidden wps section and it needs to be disabled for this card to be happy.

      found the idea on a hackintosh forum, they also recommended setting the encryption to tkip only, but it works fine with tkip/aes enabled (which 11n needs apparently to work, i got 11g only with just tkip), just the wps garbage was causing it to connect and never have internet access beyond ping.

      since i was having the same issue with windows 7 as i was xubuntu 14.04.1 and i lost my install, i’ll have to conclude that it should work extremely great with the out of box driver installed and not need to use the ndiswrapper to get a stable connection.

      also if anyone ends up here, the atheros driver for the ar9380 is updated recently and is basically what this card is and the tp-link tech support is well, not very good at giving ideas of what to do except say ‘the signal is too weak’ um it worked fine yesterday, ‘try re-installing the driver’ did that many times, maybe i should change the slot, disable ipv6… and silence. be nice if they said more to help instead of useless ideas.

      so in shot disable wps on your router or wireless modem and this card is really sweet.

      if your having a issue close to the access point, not sure what to tell you, i only had a issue at about 75 to 100 feet.

  • Gabe says:

    Worked out of the box on Fedora 20.

  • Terje says:

    Works fine in Linux Mint 17. Plug’n'Play

  • Peter says:

    I use the TP-LINK TL-WDN4800 with Fedora 20, and it works out of the box perfectly

  • Márcio says:

    Very useful information! Tanks

  • Claas says:

    Works out of the Box with Ubuntu 13.10 as described above.

    • Douglas says:

      This may explain the mixed responses. With the exact same hardware, it worked fine under Fedora 23, but had serious issues with Ubuntu 14.10. Precisely, it received and sent signals, but didn’t communicate. (It detected SSIDs, was able broadcast an SSID (which could seen using wifi-radar from another machine), but, using any rational method, was unable to make a successful connection.)

      I’m still working on a rational diagnosis, but best guess: There’s a simple fix for Ubuntu which I haven’t found yet. Anyway: The big question was, “Does it work immediately ‘out of the box’ with no issues?”

      Since I started testing with Ubuntu, I went through many, many frustrating hoops getting this far. SO that answer is “No.” Had I started testing with Fedora, I would have said, “Yes.”

      Finally: Sometimes. Not always.

    • Lubuntu 15.10 says:

      Lubuntu 15.10 32 bit. Been working then suddenly kernel 4.2.2-30 (or 27??) then it stopped working. It has to be a Linux issue.

Start new Discussion

Please use the comment section to submit corrections to the article as well as relevant excerpts of lspci, lsusb, lshw, dmesg e.t.c. Furthermore, use the section for the exchange of experiences with this hardware component or search for configuration help from other owners of this hardware.

Email address will not be published.

Rate Linux compatibility

Use the following HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Allowed file types: txt, jpg, png, gif, maximum file size: 2MB.