4/6/2024 0 Comments Tp link tl wdn4800 driver size![]() Total <= 2048, #channels <= 1, STA/AP BI must match ![]() Software interface modes (can always be added): * 5320 MHz (23.0 dBm) (passive scanning, no IBSS, radar detection) * 5300 MHz (23.0 dBm) (passive scanning, no IBSS, radar detection) * 5280 MHz (23.0 dBm) (passive scanning, no IBSS, radar detection) * 5260 MHz (23.0 dBm) (passive scanning, no IBSS, radar detection) HT TX/RX MCS rate indexes supported: 0-23 Minimum RX AMPDU time spacing: 8 usec (0x06) ![]() Maximum RX AMPDU length 65535 bytes (exponent: 0x003) Don’t forget to enable the hostapd service update-rc.d hostapd enable. :) Configurationįor people interested in my configuration files see below. I also believe that people are ignorant and simply bridge devices because they don’t understand routing and firewall rules…. This reduced broadcast traffic from my wired devices and helps keep the Wi-Fi channel a little quieter and improves performance slightly. I also chose to create a separate subnet for my Wi-Fi clients. Most of the time it will do in excess of 50 Mb/s of real world data throughput. My rMBP now gets link speed of 217 Mb/s which is still pretty good. As a result I had to fall back to 2.4 GHz channels and HT20. While the 450 Mbps bitrate of 5 GHz + HT40 + Short-GI was nice, it didn’t work with all my devices. Did I mention the card was only $45 and the Ubuntu 12.10 + development Linux 3.9 kernel just works after a little hostapd config? I paid 3x this for the EA6400 that barely worked (even though it was dual simultaneous band and had 802.11ac). My Nexus 4 has only 1 spatial stream, and negotiates a bitrate of 72 Mbps, which is the fastest the device can do. If I need speed faster then that I’ll use gigabit Ethernet. Speed tests show over 100 Mb/s actual data rate. When configured as a 5 GHz AP my rMBP connects to with a linksys of 450 Mbps. It features an Atheros AR9380 that can do 3 spatial streams, Short-GI, 2.4 GHz, 5 GHz, and HT40 (40 MHz channels). I settled on the TP-Link TL-WDN4800 card. This coupled with the idea that my desktop / server already runs my NAT, DNS, DHCP and this is a no brainer. Linux wireless is a lot more stable then it was several years ago, and host/software access points now work quite well. That’s too bad, I loved my old WRT54G and was hoping the EA6400 would be similar. I’m done with Linksys and will likely never buy a Linksys product if this is the route they are going. I did some tricks and got it to “kind of work” but not really. I don’t even have an optical drive reader or easy access to Windows. What if the Internet connection isn’t configured? Oh, use the included CD for Windows. Just Google “Linksys Smart Wi-Fi” and see what people have to say about the “502 Bad Gateway” error the router constantly threw me whenever I tried to use it as a bridging access point.Īpparently Smart Wi-Fi phones home to Linksys’s cloud to allow you to configure it from the web. Linksys created this “Smart Wi-Fi” feature that makes it a major pain to configure. I bought a Linksys EA6400 on sale thinking I could just replace my AP and be done. The PictionStation2 was then retired back to the drawer. I attempted to reconfigure it and fix it thinking it was my fault, but my attempts were in vain.Ī work project demanded Wi-Fi access for some testing at home and the PicoStation2 was making this more difficult. But, all my devices (Mac Book Retina Pro, Nexus 4, Lenovo Thinkpad, etc) all had issues with the AP just not working that well. The Linux SDK seemed cool (until I learned how /old/ the kernel actually was). I was impressed by the polish of the AirOS web interface. After my Linksys WRT54G died, the Picostation2 was put into action. The quad never got built, but I didn’t give up until after I bought a few pieces such as the Picostation2. The Picostation2 was supposed to be the high powered radio to control the who thing. I read alot of good things about Ubiquiti a while ago when I was planning to build a quad copter and do cool things with Linux + Pandaboard. No more consumer routers, the last thing I need is more stuff to configure. Add dnsmasq for simple DHCP, DNS and sometimes TFTP capabilities. My Linux desktop / server with an additional Intel PCIe NIC and Linux NAT capabilities make a pretty awesome combination. RIP WRT54G, you outlived your useful life while delivering above and beyond my expectations. I demoted by Linksys WRT54G running DD-WRT to just AP roles which lasted for a few more years before the hardware finally died. No longer am I restricted by buggy firmware, half implemented DHCP or DNS servers, NAT limitations, etc. I do most of my work at my apartment on my desktop, so why not make it my router and file server? Great question, great choice. A while ago I dumped my consumer NAT router in favor of using my desktop router.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |