Kitz Forum
Computers & Hardware => Networking => Topic started by: vic0239 on January 21, 2016, 05:35:40 PM
-
I recently purchased a TP-Link TL-WR802N nano router to network attach a new CD player which is network enabled (ethernet). The WR802N is a tiny matchbox sized USB powered device which has a variety of configurable modes, I wanted it for its wireless client functionality. It was also much cheaper than the equivalent device offered by the CD player manufacturer.
However, I have been tearing my hair out over it as I have a problem that I can not get to the bottom of. Configured in client mode I can connect to my Wi-Fi network and attaching my Mac to the ethernet port on the WR802N I can access the Internet and ping every device on my network apart from my NAS where my media server resides! If I pull the ethernet cable and switch back to wireless the ping immediately works. I have swapped devices around, connecting the SPA to the time capsule for example and it remains pingable, but no matter where I connect the NAS I can’t ping it via the WR802N.
When it is connected to the CD player Internet radio stations are playable, but no media on the NAS. Attaching the CD player by ethernet cable is ok.
I have lost count of the number of times I have reset the @*&$ thing, but to no avail. What on earth can be causing this? Please, please can someone put me out of my misery? Please see diagram if that helps.
-
I've been using the previous version WR702N for similar purposes for quite some time. I have two.
Not sure if yours has exactly the same options but I've configured mine in Bridge mode to supply an Ethernet network to non-wireless devices by linking it wirelessly into my wireless router. I leave them in that configuration once set up.
I just plug the USB cable into a spare USB port on the device (for power) and connect the Ethernet cable and magically its as if it has a cable to the router.
-
I think Client mode on mine must be equivalent to your Bridge mode. It is described as 'Act as a "Wireless Adapter" to connect your wired devices (e.g. Blu-ray player, smart TV) to existing Wi-Fi', which is does apart from seeing the NAS. :(
-
Possibly, mine has AP, Router, Repeater and Bridge modes.
-
Note that in my setup using Bridge mode the device you are linking into the network then acquires its own IP address using DHCP (from my main router).
(The WR702N also has its own)
-
Mine has:
During Travel
Wireless Router(Default)
- Share internet connection from an Ethernet cable. For example: hotel room, small office, ...
Hotspot Router
- Share Internet connection anywhere public Wi-Fi exists. For example: hotel room, trade show, ...
At Home
Access Point
- Setup Wi-Fi on an existing wired network
Range Extender
- Extend the range of an existing Wi-Fi
Client
- Act as a "Wireless Adapter" to connect your wired devices (e.g. Blu-ray player, smart TV) to existing Wi-Fi
-
Note that in my setup using Bridge mode the device you are linking into the network then acquires its own IP address using DHCP.
(The WR702N also has its own)
I have DHCP disabled on the WR802N, the device gets its address from the Billion.
-
I've opened a ticket with TP-LINK, who knows they may come up with something. :fingers:
Thanks HPsauce for you views.
-
Sorry I can't be more help, mine seem fairly foolproof but yours is a newer version with some changes.
The "Client" option you describe is exactly how I use mine almost all of the time.
-
Is there a chance that the NAS is behind its own NAT, possibly would have to go through double NAT to see the wider Internet ? (Wild speculation when grasping for ideas.)
-
Not sure about the NAS, but everything is on the same subnet locally and a traceroute from a working address shows 1 hop. I've been looking at the ARP caches (rubs throbbing head) and the entry on the Mac is incomplete for the interface connected to the WR802N, but this may be ok as I guess it will complete the lookup? TP-LINK have asked for my network details claiming they will reproduce my setup to test.
-
Well, I have to say I am impressed. :o I received a beta firmware from TP-Link this morning which has fixed the problem. :) I can now ping the NAS from my Mac via the WR802N and the ARP cache entry for it is complete. More to the point my CD player can access the media server thereon.
-
That is good news. Well done TP-Link. :)
-
Well, I have to say I am impressed. :o I received a beta firmware from TP-Link this morning which has fixed the problem. :) I can now ping the NAS from my Mac via the WR802N and the ARP cache entry for it is complete. More to the point my CD player can access the media server thereon.
Sorry to ressurrect this old thread, but do you by any chance have the possibility to provide me with this firmware or tell me how you got tp-link to react to your inqiry? I have the same problem, I have no doubt the beta firmware will solve my problem, but so far tp-link support plays dead. Thank you!
-
Hi and welcome to the forum. :)
I just registered with the TP-Link support centre and raised a new problem ticket. http://ticket.tp-link.com/ (http://ticket.tp-link.com/)
However, you can get the beta from here - https://www.dropbox.com/s/ixzhcjvs4ufjb9b/wr802nv1_en_3_16_9_up%28160118%29.rar?dl=0 (https://www.dropbox.com/s/ixzhcjvs4ufjb9b/wr802nv1_en_3_16_9_up%28160118%29.rar?dl=0)
Hope it fixes your issue. :fingers:
-
Hey,
meanwhile TP-Link support also replied. Yes, this firmware indeed fixed the issue. In my case I had a Bizhub copier system connected to the network with the WR802N and printing worked, but scanning directly to the server via smb did not. With the new firmware, it now works. Puzzling, you could think they test stuff like this before releasing stuff... but that's what you get when you buy a $10 network adapter for a $3000 copier ;)
Thanks for your reply and for uploading the firmware.
-
Hello (from France) :)
I was sticked with a wr802N, trying to setup a "client mode" that would accept to work.
After 3 days, I finally reached that thread thanks to google :).
Hopefully the beta firmware is still available for download. I've upgrade my WR802N with that version, and without any modification in my configuration, all now works flawlessly.
A really great thanks to you for the share, and for the tests.
I'll now also raise a ticker to TP-LINK. In my opinion, they HAVE to release a firmware fixing the client mode.
Thanks to again to vic0239 and p0ddie for the tests and uploading the firmware.
[Moderator edit to fix the emoticons.]
-
Hello (from France) :)
Welcome to the Kitz forum.
Thank you for taking the time to register and post, confirming that the firmware also solves the problem you were experiencing. :)
-
Hello (from France) :)
Aucun problème!
Since my original post I have acquired a second device and performed a firmware update fully expecting this fix to be incorporated into the general release. Sadly as in your experience this is not the case, :no: but at least we have the beta. :)
-
Welcome to the Kitz forum.
Thank you for taking the time to register and post, confirming that the firmware also solves the problem you were experiencing. :)
No problem. Just had to google a little to answer correctly to the questions requested to register :-)
-
So, I raised a Ticket to Tp-Link about our problem.
After some tests and questions, the support answered me with a beta firmware, but not the same as the one "vic0239" shared with us.
I've test the beta firmware they send me, and it work as it should.
If you want to have a try, here is a link to the beta firmware I've receive : https://drive.google.com/open?id=0B9JVTol1WbbfUS1lRHRGT1FjX2c
I've try to convince the support to publish an official release with the client mode fix, but since beginning of January, nothing new on the Tp-Link support page.
Hope this could help someone.
Rirethy.
-
Thanks for sharing the newer firmware. :)
I wouldn't hold your breath waiting for an official release. I asked the same question over a year ago and despite receiving assurances it would be released, nothing came of it as we well know. At the time I asked for a technical explanation of the problem and received a response which, to me, looked like a bodge to get the MAC address of the NAS (in my case) propagated. Perhaps they don't want to include such a workaround in the released code.
3 February 2016
Hi
Sorry for this delay replay, this issue certainly will be fixed in a further official firmware, currently, you have to use this beta firmware. Sorry for bringing you trouble.
Best Regards
-------------------------------
XXXXX XX
Technical Support Engineer
TP-LINK TECHNOLOGIES CO, LTD.