(question) TP-Link TL-WR802N 300Mbps Wireless-N Nano Router
Anyone have this one? http://www.canadacomputers.com/product_info.php?cPath=27_1046_365&item_id=087761 http://www.tplink.ca/en/products/details/TL-WR802N.html If so, have you ever used its "Client Mode" and can you confirm that it works? I need small portable "wireless bridge", and the advertised "client mode" is what I need. But, last TP-Link I bought was N750 dual-band TL-WDR4300. It advertised "wireless bridge" and even their tech support said so. But, both lied. Shocking! I have Linksys WRT model with DD-WRT, and its client bridge works. But, it's a bit bulky to carry around. -- William
Hi William, First Question, do you care about double NAT? Scenario 1: Bridge (Single NAT from WIFI AP's upstream router). * The 'box' joins a wireless AP, and all packets, including broadcasts, DCHP, ARP, pass through transparently to the wired port on the 'box'. Scenario 2: Double NAT * The 'box' joins a wireless AP, get an address from the upstream router and then NATs that, creating and managing a separate network for the wired port. Internet Access would be still be 'normal', you would not get broadcast traffic, or addresses from the upstream router. Scenario 2 is a lot easier, and covers the majority of use cases. ---- Over the last five years I've been using the TL-MR3020 as a swiss army knife for old ball networking. I actually own several of them. I did use it's stock firmware as a wireless bridge (Scenario 1), evening doing a PXE network boot over it. Although that was 4 years ago. OpenWRT works on it very well, and I've even gone through the pain of bricking and recovering one. https://wiki.openwrt.org/toh/tp-link/tl-mr3020 http://www.canadacomputers.com/product_info.php?cPath=690&item_id=047186 You can still find some stock in Canada Computers. On the TL-WR802N, It's 'next model' name-sake of the venerable TL-WR702N*, minus the oh so useful USB Host port... -_-; It is completely different hardware though, not the same SoC and it looks like the openwrt community is still getting their heads around it. https://wiki.openwrt.org/toh/tp-link/tl-wr802n * TL-MR3020 is just a derivative of the TL-WR702N with hardware buttons, and an extra PCB antenna, and larger flash chip. So yeah, can't say anything about TL-WR802N other then it's half the price of the TL-MR3020. But the TL-MR3020 has worked well for me in the past. On 08/11/2016 11:52 PM, William Park via talk wrote:
Anyone have this one? http://www.canadacomputers.com/product_info.php?cPath=27_1046_365&item_id=087761 http://www.tplink.ca/en/products/details/TL-WR802N.html If so, have you ever used its "Client Mode" and can you confirm that it works?
I need small portable "wireless bridge", and the advertised "client mode" is what I need. But, last TP-Link I bought was N750 dual-band TL-WDR4300. It advertised "wireless bridge" and even their tech support said so. But, both lied. Shocking!
I have Linksys WRT model with DD-WRT, and its client bridge works. But, it's a bit bulky to carry around.
Thanks Scott. Scenerio 1 (bridge) is what I need. Basically, I have devices with ethernet port, and you normally plug into router or switch to get DHCP IP. Short distance, short cable, no problem. My problem starts with Long distance and long cable. I need something that will replace this long ethernet cable. If stock firmware can do "wireless client bridge", then I don't need OpenWRT or DD-WRT. Off to Canada Computer, I go... -- William On Fri, Aug 12, 2016 at 12:26:15AM -0400, Scott Sullivan via talk wrote:
Hi William,
First Question, do you care about double NAT?
Scenario 1: Bridge (Single NAT from WIFI AP's upstream router).
* The 'box' joins a wireless AP, and all packets, including broadcasts, DCHP, ARP, pass through transparently to the wired port on the 'box'.
Scenario 2: Double NAT
* The 'box' joins a wireless AP, get an address from the upstream router and then NATs that, creating and managing a separate network for the wired port. Internet Access would be still be 'normal', you would not get broadcast traffic, or addresses from the upstream router.
Scenario 2 is a lot easier, and covers the majority of use cases.
----
Over the last five years I've been using the TL-MR3020 as a swiss army knife for old ball networking. I actually own several of them.
I did use it's stock firmware as a wireless bridge (Scenario 1), evening doing a PXE network boot over it. Although that was 4 years ago.
OpenWRT works on it very well, and I've even gone through the pain of bricking and recovering one.
https://wiki.openwrt.org/toh/tp-link/tl-mr3020 http://www.canadacomputers.com/product_info.php?cPath=690&item_id=047186
You can still find some stock in Canada Computers.
On the TL-WR802N,
It's 'next model' name-sake of the venerable TL-WR702N*, minus the oh so useful USB Host port... -_-; It is completely different hardware though, not the same SoC and it looks like the openwrt community is still getting their heads around it.
https://wiki.openwrt.org/toh/tp-link/tl-wr802n
* TL-MR3020 is just a derivative of the TL-WR702N with hardware buttons, and an extra PCB antenna, and larger flash chip.
So yeah, can't say anything about TL-WR802N other then it's half the price of the TL-MR3020. But the TL-MR3020 has worked well for me in the past.
On 08/11/2016 11:52 PM, William Park via talk wrote:
Anyone have this one? http://www.canadacomputers.com/product_info.php?cPath=27_1046_365&item_id=087761 http://www.tplink.ca/en/products/details/TL-WR802N.html If so, have you ever used its "Client Mode" and can you confirm that it works?
I need small portable "wireless bridge", and the advertised "client mode" is what I need. But, last TP-Link I bought was N750 dual-band TL-WDR4300. It advertised "wireless bridge" and even their tech support said so. But, both lied. Shocking!
I have Linksys WRT model with DD-WRT, and its client bridge works. But, it's a bit bulky to carry around.
--- Talk Mailing List talk@gtalug.org https://gtalug.org/mailman/listinfo/talk
They are lying, again. I downloaded the user's manual. In the feature section, they mention "bridge". But, in the Client Mode chapter, they talk about DHCP, which mean it's NAT. -- William On Fri, Aug 12, 2016 at 01:15:57AM -0400, William Park via talk wrote:
Thanks Scott. Scenerio 1 (bridge) is what I need. Basically, I have devices with ethernet port, and you normally plug into router or switch to get DHCP IP. Short distance, short cable, no problem. My problem starts with Long distance and long cable. I need something that will replace this long ethernet cable.
If stock firmware can do "wireless client bridge", then I don't need OpenWRT or DD-WRT. Off to Canada Computer, I go... -- William
On Fri, Aug 12, 2016 at 12:26:15AM -0400, Scott Sullivan via talk wrote:
Hi William,
First Question, do you care about double NAT?
Scenario 1: Bridge (Single NAT from WIFI AP's upstream router).
* The 'box' joins a wireless AP, and all packets, including broadcasts, DCHP, ARP, pass through transparently to the wired port on the 'box'.
Scenario 2: Double NAT
* The 'box' joins a wireless AP, get an address from the upstream router and then NATs that, creating and managing a separate network for the wired port. Internet Access would be still be 'normal', you would not get broadcast traffic, or addresses from the upstream router.
Scenario 2 is a lot easier, and covers the majority of use cases.
----
Over the last five years I've been using the TL-MR3020 as a swiss army knife for old ball networking. I actually own several of them.
I did use it's stock firmware as a wireless bridge (Scenario 1), evening doing a PXE network boot over it. Although that was 4 years ago.
OpenWRT works on it very well, and I've even gone through the pain of bricking and recovering one.
https://wiki.openwrt.org/toh/tp-link/tl-mr3020 http://www.canadacomputers.com/product_info.php?cPath=690&item_id=047186
You can still find some stock in Canada Computers.
On the TL-WR802N,
It's 'next model' name-sake of the venerable TL-WR702N*, minus the oh so useful USB Host port... -_-; It is completely different hardware though, not the same SoC and it looks like the openwrt community is still getting their heads around it.
https://wiki.openwrt.org/toh/tp-link/tl-wr802n
* TL-MR3020 is just a derivative of the TL-WR702N with hardware buttons, and an extra PCB antenna, and larger flash chip.
So yeah, can't say anything about TL-WR802N other then it's half the price of the TL-MR3020. But the TL-MR3020 has worked well for me in the past.
On 08/11/2016 11:52 PM, William Park via talk wrote:
Anyone have this one? http://www.canadacomputers.com/product_info.php?cPath=27_1046_365&item_id=087761 http://www.tplink.ca/en/products/details/TL-WR802N.html If so, have you ever used its "Client Mode" and can you confirm that it works?
I need small portable "wireless bridge", and the advertised "client mode" is what I need. But, last TP-Link I bought was N750 dual-band TL-WDR4300. It advertised "wireless bridge" and even their tech support said so. But, both lied. Shocking!
I have Linksys WRT model with DD-WRT, and its client bridge works. But, it's a bit bulky to carry around.
--- Talk Mailing List talk@gtalug.org https://gtalug.org/mailman/listinfo/talk
Talk Mailing List talk@gtalug.org https://gtalug.org/mailman/listinfo/talk
On 08/12/2016 02:20 AM, William Park via talk wrote:
They are lying, again. I downloaded the user's manual. In the feature section, they mention "bridge". But, in the Client Mode chapter, they talk about DHCP, which mean it's NAT.
William, They are not lying. Wireless Bridge, and Client Mode are not the same thing at all. Wireless Bridge is Scenario 1. Client Mode is Scenario 2. Your searching on the wrong term, and Scenario 1 is Very Rare in Vendor Firmwares. I also repeat, I did my work 4 years ago, there have been a lot or revisions of the hardware and firmware in that time, and it's very possible that the feature was removed. Actually, forget manuals, let me give you screenshots. I just pulled my box of routers and one of my Spare TL-MR3020s that I've deliberately kept on the stock firmware. See Attached Screenshot. The setting is 'Enable WSD Bridge', and it pops out all the config options below it. You will in your SSID (or survey button, and select if from a list). Set Auth, and Password settings. And then reboot. Awh... and this is where 4 years my memory gets foggy. I was expecting my IP address to change, but it didn't. I then had to go manually disable DHCP on the the TL-MR3020 (which it will prompt to reboot for). After DHCP is disable, it stops winning the race condition, and you get the address from the hosting wifi AP. # Address from TL-MR3020 [scott@failfast ~]$ ifconfig enp0s20u3u1c2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.0.100 netmask 255.255.255.0 broadcast 192.168.0.255 After Disabling DHCP the TL-MR3020 rebooting, and myself re-connecting my laptop's Ethernet. # Address from SmartRG Router, over WSD client bridge. [scott@failfast ~]$ ifconfig enp0s20u3u1c2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.7 netmask 255.255.255.0 broadcast 192.168.1.255 FYI, this is a 3 year old router and build of the TP-Link's firmware. Firmware Version: 3.14.2 Build 120817 Rel.55520n Hardware Version: MR3020 v1 00000000 -- Scott Sullivan
Actually, forget manuals, let me give you screenshots. You might want to make it n only, instead of bgn. Having b in there can really slow things down. I don't know if that device supports gn or just n only. I have a TP-Link TL-WA901 and it does either bgn on n only. However, there's aren't many devices made in the past few years
On 08/12/2016 08:56 AM, Scott Sullivan via talk wrote: that don't support n, so no harm in going with n only.
On 08/11/2016 11:52 PM, William Park via talk wrote:
Anyone have this one? http://www.canadacomputers.com/product_info.php?cPath=27_1046_365&item_id=087761 http://www.tplink.ca/en/products/details/TL-WR802N.html If so, have you ever used its "Client Mode" and can you confirm that it works?
I need small portable "wireless bridge", and the advertised "client mode" is what I need. But, last TP-Link I bought was N750 dual-band TL-WDR4300. It advertised "wireless bridge" and even their tech support said so. But, both lied. Shocking!
I have Linksys WRT model with DD-WRT, and its client bridge works. But, it's a bit bulky to carry around.
You might try this. I have one and it has a variety of modes. http://www.ncix.com/products/?sku=DH888891640
On Fri, Aug 12, 2016 at 07:16:18AM -0400, James Knott via talk wrote:
On 08/11/2016 11:52 PM, William Park via talk wrote:
Anyone have this one? http://www.canadacomputers.com/product_info.php?cPath=27_1046_365&item_id=087761 http://www.tplink.ca/en/products/details/TL-WR802N.html If so, have you ever used its "Client Mode" and can you confirm that it works?
I need small portable "wireless bridge", and the advertised "client mode" is what I need. But, last TP-Link I bought was N750 dual-band TL-WDR4300. It advertised "wireless bridge" and even their tech support said so. But, both lied. Shocking!
I have Linksys WRT model with DD-WRT, and its client bridge works. But, it's a bit bulky to carry around.
You might try this. I have one and it has a variety of modes. http://www.ncix.com/products/?sku=DH888891640
I downloaded user's manual for this one also. It talks about DHCP in "Client Mode", which means it's client NAT, not bridge. -- William
I would +1 on Scott's suggestion of an MR3020. Openwrt installs quite nicely and Openwrt can do just about anything. On 08/12/2016 08:17 AM, William Park via talk wrote:
On Fri, Aug 12, 2016 at 07:16:18AM -0400, James Knott via talk wrote:
On 08/11/2016 11:52 PM, William Park via talk wrote:
Anyone have this one? http://www.canadacomputers.com/product_info.php?cPath=27_1046_365&item_id=087761 http://www.tplink.ca/en/products/details/TL-WR802N.html If so, have you ever used its "Client Mode" and can you confirm that it works?
I need small portable "wireless bridge", and the advertised "client mode" is what I need. But, last TP-Link I bought was N750 dual-band TL-WDR4300. It advertised "wireless bridge" and even their tech support said so. But, both lied. Shocking!
I have Linksys WRT model with DD-WRT, and its client bridge works. But, it's a bit bulky to carry around. You might try this. I have one and it has a variety of modes. http://www.ncix.com/products/?sku=DH888891640 I downloaded user's manual for this one also. It talks about DHCP in "Client Mode", which means it's client NAT, not bridge.
-- Alvin Starr || voice: (905)513-7688 Netvel Inc. || Cell: (416)806-0133 alvin@netvel.net ||
You could look at a GLi OpenWRT based mini router. They can probably be made to run in bridged mode. <http://www.gl-inet.com/> -- Scott
On 08/12/2016 08:17 AM, William Park via talk wrote:
I downloaded user's manual for this one also. It talks about DHCP in "Client Mode", which means it's client NAT, not bridge.
It has multiple modes, including "Wireless Client Mode". This is the Scenario 1 mentioned in another note that is what you said you wanted. In this mode, you connect one or more Ethernet devices via WiFi to an existing WiFi connection. The DHCP server is used only in Router Mode. The other mode is Access Point, where it's just a plain access point, providing WiFi to an existing Ethernet network. Further, this is designed as a portable device and comes with a nice case. It can be be powered either with an AC adapter or USB.
On 08/12/2016 09:09 AM, James Knott via talk wrote:
On 08/12/2016 08:17 AM, William Park via talk wrote:
I downloaded user's manual for this one also. It talks about DHCP in "Client Mode", which means it's client NAT, not bridge.
It has multiple modes, including "Wireless Client Mode". This is the Scenario 1 mentioned in another note that is what you said you wanted. In this mode, you connect one or more Ethernet devices via WiFi to an existing WiFi connection. The DHCP server is used only in Router Mode. The other mode is Access Point, where it's just a plain access point, providing WiFi to an existing Ethernet network. Further, this is designed as a portable device and comes with a nice case. It can be be powered either with an AC adapter or USB.
James, Client Mode is usually Scenario 2, where the portable router box (TL-MR3020 or TL-WR802N in these examples), is a client of the WIFI AP, and is NATing that connection like a traditional router. William, is correct in that 'client mode' is not what he's seeking, although he's not hit on the correct term yet. From what I understand so far, William can correct me, he wants Scenario 1, where its a transparent bridge. I've been re-acquainting myself with this all morning. While it can still be called confusingly 'bridged client mode', the specific term is a WDS client. https://en.wikipedia.org/wiki/Wireless_distribution_system From the OpenWRT documentation, this seems to require hardware support. https://wiki.openwrt.org/doc/recipes/bridgedclient https://wiki.openwrt.org/doc/recipes/atheroswds Atheros chip-sets (which the TL-MR3020 and TL-WR802N both are), do seem to have that support through the mac80211 drives. I've pulled out one of my TL-MR3020's running OpenWRT 15.05.1 (the latest stable). The LUCI webui does seem to configure it all nicely and correctly, when compared to the linked recipe above (second line). That said... I've not yet gotten this to work for me, yet. Still playing around with it though. /etc/config/wireless config wifi-device 'radio0' option type 'mac80211' option hwmode '11g' option path 'platform/ar933x_wmac' option htmode 'HT20' option disabled '0' option txpower '18' option country 'US' option channel '1' config wifi-iface option device 'radio0' option ssid 'Teksavvyc862' option mode 'sta' option wds '1' option network 'lan' option key '************' option encryption 'psk2' -- Scott Sullivan
On 08/12/2016 09:46 AM, Scott Sullivan via talk wrote:
From what I understand so far, William can correct me, he wants Scenario 1, where its a transparent bridge. I've been re-acquainting myself with this all morning.
While it can still be called confusingly 'bridged client mode', the specific term is a WDS client.
I've also wondered exactly what he wants. If he wants a WiFi "bridge", that is a device that extends WiFi range, then this device won't do it. My home access point, the TL-WA901ND will, as will my Asus wl-330ge portable access point. If he wants to connect an Ethernet device or network to existing WiFi, then the D-Link is fine
On Fri, Aug 12, 2016 at 09:59:53AM -0400, James Knott via talk wrote:
I've also wondered exactly what he wants. If he wants a WiFi "bridge", that is a device that extends WiFi range, then this device won't do it. My home access point, the TL-WA901ND will, as will my Asus wl-330ge portable access point. If he wants to connect an Ethernet device or network to existing WiFi, then the D-Link is fine
No a wifi bridge is not a range extender. It is a device to connect wired ethernet to wireless ethernet. -- Len Sorensen
On 08/16/2016 11:40 AM, Lennart Sorensen wrote:
On Fri, Aug 12, 2016 at 09:59:53AM -0400, James Knott via talk wrote:
I've also wondered exactly what he wants. If he wants a WiFi "bridge", that is a device that extends WiFi range, then this device won't do it. My home access point, the TL-WA901ND will, as will my Asus wl-330ge portable access point. If he wants to connect an Ethernet device or network to existing WiFi, then the D-Link is fine No a wifi bridge is not a range extender. It is a device to connect wired ethernet to wireless ethernet.
Sometimes those terms are not precise. Here's what my TP-Link access point says: Repeater - In Repeater mode, the AP with WDS enabled will relays data to an associated root AP. AP function is enabled meanwhile. The wireless repeater relays signal between its stations and the root AP for greater wireless range. Please input the MAC address of root AP in the field "MAC of AP". Universal Repeater - In Universal Repeater mode, the AP with WDS disabled will relays data to an associated root AP. AP function is enabled meanwhile. The wireless repeater relays signal between its stations and the root AP for greater wireless range. Please input the MAC address of root AP in the field "MAC of AP". Bridge with AP - This operation mode bridges the AP and up to 4 APs also in bridge mode to connect two or more wired LANs. Please input the MAC address of other APs in the field "MAC of AP1" to "MAC of AP4". AP function will also startup.
On Fri, Aug 12, 2016 at 09:46:10AM -0400, Scott Sullivan via talk wrote:
William, is correct in that 'client mode' is not what he's seeking, although he's not hit on the correct term yet.
From what I understand so far, William can correct me, he wants Scenario 1, where its a transparent bridge. I've been re-acquainting myself with this all morning.
Yes, scenario 1 is what I meant and want. Correct term (and operation) is "client bridge". Second router connects to the main router as client and gets DHCP IP from the main router, like any other connecting devices. Then, the second router bridges its wlan0 and eth0 (internally, creates br0 which contains wlan0 and eth0). Anyways, for the external device connecting to the second router, it appears as though it's connecting to the main router. It gets DHCP IP from the main router, it's on the same network as other devices connected (via cable or wifi) to the main router, etc. In other words, instead of long ethernet cable to the main router, it has short cable to the second router. This situation comes up a lot at work, and I'm sure everyone here has encounter this. You want to connect to a particular network and be in that network, but you can't roll out physical cable. -- William
On 08/12/2016 08:48 PM, William Park via talk wrote:
From what I understand so far, William can correct me, he wants Scenario 1,
where its a transparent bridge. I've been re-acquainting myself with this all morning. Yes, scenario 1 is what I meant and want. Correct term (and operation) is "client bridge". Second router connects to the main router as client and gets DHCP IP from the main router, like any other connecting devices. Then, the second router bridges its wlan0 and eth0 (internally, creates br0 which contains wlan0 and eth0).
Anyways, for the external device connecting to the second router, it appears as though it's connecting to the main router. It gets DHCP IP from the main router, it's on the same network as other devices connected (via cable or wifi) to the main router, etc. In other words, instead of long ethernet cable to the main router, it has short cable to the second router.
That is exactly what that D-Link will do in Client mode. It will connect one or more Ethernet devices via WiFi to the router.
On Fri, Aug 12, 2016 at 08:59:46PM -0400, James Knott via talk wrote:
That is exactly what that D-Link will do in Client mode. It will connect one or more Ethernet devices via WiFi to the router.
James, since you have this DAP-1350... Suppose Device-A is connected to your DAP, which is in "client mode" and is connected to a main router. The main router has another Device-B connected to it. - Does Device-A get its IP from DAP or the main router? - Can Device-B connect to Device-A? Usually, in NAT, Device-A can go out and connect to Device-B, but not the other way around. "client bridge" should act like 1-port ethernet switch connected to the main router via long cable. What I want, of course, is to replace this long cable with wifi. But, function and usage are the same. -- William
My apology... James is right. I got confused after reading TP-LINK TL-WR802N manual where it says "DHCP server". DAP-1350 manual says "DHCP" only. -- William On Fri, Aug 12, 2016 at 10:30:59PM -0400, William Park via talk wrote:
On Fri, Aug 12, 2016 at 08:59:46PM -0400, James Knott via talk wrote:
That is exactly what that D-Link will do in Client mode. It will connect one or more Ethernet devices via WiFi to the router.
James, since you have this DAP-1350...
Suppose Device-A is connected to your DAP, which is in "client mode" and is connected to a main router. The main router has another Device-B connected to it. - Does Device-A get its IP from DAP or the main router? - Can Device-B connect to Device-A? Usually, in NAT, Device-A can go out and connect to Device-B, but not the other way around.
"client bridge" should act like 1-port ethernet switch connected to the main router via long cable. What I want, of course, is to replace this long cable with wifi. But, function and usage are the same. -- William --- Talk Mailing List talk@gtalug.org https://gtalug.org/mailman/listinfo/talk
On 12 August 2016 at 20:48, William Park via talk <talk@gtalug.org> wrote:
Yes, scenario 1 is what I meant and want. Correct term (and operation) is "client bridge".
It looks like there isn't just one standard for connecting two routers via a wireless link and creating a single bridged network. Which protocol do you want to use? <https://wiki.openwrt.org/doc/howto/clientmode> -- Scott
On 08/11/2016 11:52 PM, William Park via talk wrote:
Anyone have this one? http://www.canadacomputers.com/product_info.php?cPath=27_1046_365&item_id=087761 http://www.tplink.ca/en/products/details/TL-WR802N.html If so, have you ever used its "Client Mode" and can you confirm that it works?
Frankly, This device costs so little, just buy it, try it and if it's unsuitable, return it. Your well with in your rights to return a product for it being 'unsuitable for intended purpose', Canada Computer won't bat an eyelash. -- Scott Sullivan
Depending on your intended use, there is also this: https://www.amazon.ca/dp/B01CVOLGOG/ref=pe_386430_202053160_TE_item TP-Link TL-WR810N 300 Mbps Wireless N Mini Router $35 It has a built-in power supply, 2 ethernet ports, and a USB port. It can operate in several modes: 1. Router 2. Hotspot 3. Range Extender 4. Client 5. Access Point Right now it is acting as a wireless client bridge (no NAT) for the MPB and a Grandstream VOIP ATA, while powering a USB fan. I got it mainly to run the VOIP phone off WiFi. -- Peter
Peter, Nice find. Looks like support has landed in Trunk (which will become the next stable release in the future) https://wiki.openwrt.org/toh/tp-link/tl-wr810n The USB port does support data. http://www.tp-link.com/en/products/details/TL-WR810N.html#overview And NewEgg has it on special for $25 dollars at the moment. http://www.newegg.ca/Product/Product.aspx?Item=N82E16833704290CVF ... and ordered one. Really, can't wait till trickle down brings 5Ghz to devices like these. I personally want to abandon the 2.4Ghz spectrum due to over crowding. There are only 4 AP's in the 5Ghz bands near my apartment, and there is no competition because of how wide the spectrum is. On 08/13/2016 12:57 AM, Peter Renzland via talk wrote:
Depending on your intended use, there is also this:
https://www.amazon.ca/dp/B01CVOLGOG/ref=pe_386430_202053160_TE_item TP-Link TL-WR810N 300 Mbps Wireless N Mini Router $35
It has a built-in power supply, 2 ethernet ports, and a USB port.
It can operate in several modes:
1. Router 2. Hotspot 3. Range Extender 4. Client 5. Access Point
Right now it is acting as a wireless client bridge (no NAT) for the MPB and a Grandstream VOIP ATA, while powering a USB fan.
I got it mainly to run the VOIP phone off WiFi.
-- Peter
--- Talk Mailing List talk@gtalug.org https://gtalug.org/mailman/listinfo/talk
On Thu, Aug 11, 2016 at 11:52:57PM -0400, William Park via talk wrote:
Anyone have this one? http://www.canadacomputers.com/product_info.php?cPath=27_1046_365&item_id=087761 http://www.tplink.ca/en/products/details/TL-WR802N.html If so, have you ever used its "Client Mode" and can you confirm that it works?
I need small portable "wireless bridge", and the advertised "client mode" is what I need. But, last TP-Link I bought was N750 dual-band TL-WDR4300. It advertised "wireless bridge" and even their tech support said so. But, both lied. Shocking!
I have Linksys WRT model with DD-WRT, and its client bridge works. But, it's a bit bulky to carry around.
Wireless bridging is actually quite tricky. Wifi expects connections to an AP to be for ONE mac address only. This makes doing bridging tricky if you expect more than one device to use the bridge. Doing a bridge for a single wired device to allow wifi is simple, just use the mac address of that device for the connection to the AP and it will work. However if you try to do multiple devices behind one bridge, now what? The AP will per the standard only allow traffic from one MAC for a given connection, so either the bridge has to do MAC address NAT (which is tricky to get right), or you could do the full layer 3 NAT instead and just handle it that way (which seems to be the common cheap solution since it actually works and does what most people want, and allow internet access from clients and nothing else). Now if you use WDS things get better, but unfortunately it isn't apparently quite an official standard so it might only work if all the wifi devices involved are from the same vendor. WDS can be used to setup a mesh network of repeaters, or it can be used for bridging and solves the MAC address issue by adding an extra field to store the MAC address of the sender in addition to the existing field for the MAC address of the wifi sender (which would be the bridge device). Various vendors have had proprietary WDS type things to allow two APs of the same model to work as a base station and a bridge together, and they use their own extensions to allow multiple MAC addresses behind one wifi connection to get through. This is the same thing that is preventing running a VM in bridged mode on a laptop with a wifi link. If you do full NAT you are fine, but if you are trying to run a VM as a server and make it accessible to the network you are out of luck. -- Len Sorensen
On 08/16/2016 11:38 AM, Lennart Sorensen via talk wrote:
This is the same thing that is preventing running a VM in bridged mode on a laptop with a wifi link. If you do full NAT you are fine, but if you are trying to run a VM as a server and make it accessible to the network you are out of luck.
FWIW, I run Windows 10 in a VirtualBox virtual machine on Linux, with my ThinkPad. I run the VM in bridge mode, not NAT. It gets it's own DHCP IPv4 address, along with SLAAC addresses on IPv6. I even have an assigned IPv4 address for it's MAC in my DHCP server. It all works well. This is with my TP-Link TL-WA901ND access point. It also works with my D-Link DAP-1350 and Asus WL-330gE portable access points. So, via WiFi, no matter which access point I use, Linux gets an address of 172.16.1.40 and the W10 VM gets 172.16.1.41, as configured in the DHCP server. I get full connectivity on both IPv4 and IPv6 through the single WiFi connection. BTW, those IP addresses are secret, so don't tell them to anyone else. ;-)
On Tue, Aug 16, 2016 at 12:15:52PM -0400, James Knott via talk wrote:
FWIW, I run Windows 10 in a VirtualBox virtual machine on Linux, with my ThinkPad. I run the VM in bridge mode, not NAT. It gets it's own DHCP IPv4 address, along with SLAAC addresses on IPv6. I even have an assigned IPv4 address for it's MAC in my DHCP server. It all works well. This is with my TP-Link TL-WA901ND access point. It also works with my D-Link DAP-1350 and Asus WL-330gE portable access points.
So, via WiFi, no matter which access point I use, Linux gets an address of 172.16.1.40 and the W10 VM gets 172.16.1.41, as configured in the DHCP server. I get full connectivity on both IPv4 and IPv6 through the single WiFi connection.
That's interesting. Does virtualbox use the same MAC as the host system, or it's own MAC? That would make a difference I would think. Which wifi adapter is in that machine? Certainly doing it in linux with brctl and kvm does not work. -- Len Sorensen
On 08/16/2016 12:21 PM, Lennart Sorensen wrote:
Does virtualbox use the same MAC as the host system, or it's own MAC? That would make a difference I would think.
Yes, it has it's own MAC. I wouldn't be able to configure the DHCP server for it otherwise.
Which wifi adapter is in that machine?
It's a "Realtek WLAN controller".
On Tue, Aug 16, 2016 at 12:25:48PM -0400, James Knott via talk wrote:
Yes, it has it's own MAC. I wouldn't be able to configure the DHCP server for it otherwise.
It could. DHCP servers are allowed to use more than one parameter, such as mac, hostname, etc. It could cause trouble with many dhcp servers though.
It's a "Realtek WLAN controller".
Interesting. I wonder how they made that work. Maybe I can find some info on it. -- Len Sorensen
On 08/16/2016 01:57 PM, Lennart Sorensen wrote:
It could. DHCP servers are allowed to use more than one parameter, such as mac, hostname, etc. It could cause trouble with many dhcp servers though.
I'm using the DHCP server in my pfSense firewall. The only identifier is the MAC address.
On 16 August 2016 at 15:35, James Knott via talk <talk@gtalug.org> wrote:
On 08/16/2016 01:57 PM, Lennart Sorensen wrote:
It could. DHCP servers are allowed to use more than one parameter, such as mac, hostname, etc. It could cause trouble with many dhcp servers though.
I'm using the DHCP server in my pfSense firewall. The only identifier is the MAC address.
I'm not sure what DHCP implementation that uses; it might be something less featureful than ISC DHCPD, maybe? Or perhaps the configuration tool doesn't manage everything supported in RFC 2132? When I tossed my Pine64 single board machine onto my LAN, when it negotiated with ISC DHCPD, I could see in my logs that it reported in as being "pine64". Presumably that's part of one of the further extensions (e.g. - transmitting more than merely the MAC address). -- When confronted by a difficult problem, solve it by reducing it to the question, "How would the Lone Ranger handle this?"
On Tue, Aug 16, 2016 at 12:21:47PM -0400, Lennart Sorensen via talk wrote:
On Tue, Aug 16, 2016 at 12:15:52PM -0400, James Knott via talk wrote:
FWIW, I run Windows 10 in a VirtualBox virtual machine on Linux, with my ThinkPad. I run the VM in bridge mode, not NAT. It gets it's own DHCP IPv4 address, along with SLAAC addresses on IPv6. I even have an assigned IPv4 address for it's MAC in my DHCP server. It all works well. This is with my TP-Link TL-WA901ND access point. It also works with my D-Link DAP-1350 and Asus WL-330gE portable access points.
So, via WiFi, no matter which access point I use, Linux gets an address of 172.16.1.40 and the W10 VM gets 172.16.1.41, as configured in the DHCP server. I get full connectivity on both IPv4 and IPv6 through the single WiFi connection.
That's interesting.
Does virtualbox use the same MAC as the host system, or it's own MAC? That would make a difference I would think.
VirtualBox uses different MAC for VMs, and those can be found in Network -> Adapter 1 -> Advanced -> MAC Address Just above that, there is Network -> Adapter 1 -> Name where you can choose host's real port(ie. wlan0 or eth1) to attach to.
Which wifi adapter is in that machine?
Certainly doing it in linux with brctl and kvm does not work.
Actually, I got "QEMU Bridge" working, but never used it much. You have to give different MAC to each image running; otherwise, they all run with the same default MAC. VirtualBox is just three mouse click! Network (click 1) -> Attached to -> Briged Adapter (click 2) -> Name -> wlan0 (click 3) -- William
participants (8)
-
Alvin Starr -
Christopher Browne -
James Knott -
Lennart Sorensen -
Peter Renzland -
Scott Allen -
Scott Sullivan -
William Park