TL-WR802N not getting to wifi in client mode or getting an ip address
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I ordered a batch of about 20 nano-routers to connect to these machines that don't have wifis. I have a test machine at my desk that I have used to connect to then once i get a succesfully connection I ship them out to different places to connect them to the same type of device. I ordered another batch of 70 of them, I do the same steps that I have done and set them to client mode and then connect them to the ssid that they need to find. I noticed that before they work, it is all the whole batch thus far, that I need to get a successfully connection to the machine for these nano-routers to pull an ip address. If I connect them first to the device, they connect to the ssid but don't pull an ip address. I'm trying to figure out what is the difference between the ones that I first ordered and these second order of 70 that don't want to connect unless I get an existing connection to work on my device. Please advise me since I spent about $2000 on these nano-routers based off the performance of the first 20 batch that I got.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
As far as what may be different...
Are the routers a different version number?
Are they on the same firmware level?
If they are not getting the IP from the modem, it may be because the modem still thinks it is attached to the previous unit.
See https://community.tp-link.com/us/home/forum/topic/150603
- Copy Link
- Report Inappropriate Content
Both are v4 Both have the same firmware which is the 2004 something something The first 20 connected well with the same two devices. I can't connect to the modem or the switch real easily either. I went down this route as it was the easiest to walk an end user through the plug and play type connection which worked successfully with the first 20 I bought. I order the 70 from a different vendor which I'm starting to think it might be the batch. The devices that these newer routers are connecting to have never had them connecting to them. They connect to the AP with weird IPs ending in .0.1 when they're supposed to grab a different one, its not static but the IP range is not .0.1.
- Copy Link
- Report Inappropriate Content
Have you tried other modes, how do those perform?
Aside from the devices you want to attach to the 802N if you connected a computer instead does that work?
- Copy Link
- Report Inappropriate Content
I think I figured it out. The old one had a firmware of 170615 while the new one had a firmware of 2004. I rolled back the firmware and it connected to one of the devices without issue. I'm suspecting this a TP-Link issue with the firmware. I will need to test more of the bad batch that I got.
- Copy Link
- Report Inappropriate Content
This is the error from the firmware 2004:
1970-01-01 08:00:21 [5] DHCPD: Recv DISCOVER from F8:DC:7A:16:7A:C9 Tranaction ID 6a04f095
1970-01-01 08:00:21 [5] DHCPD: Send OFFER with ip 192.168.0.100
1970-01-01 08:00:21 [5] DHCPD: Recv REQUEST from F8:DC:7A:16:7A:C9 Tranaction ID 6a04f095
1970-01-01 08:00:21 [5] DHCPD: Send ACK to 192.168.0.100
1970-01-01 08:00:23 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:00:37 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:00:51 [5] DHCPD: Recv REQUEST from F8:DC:7A:16:7A:C9 Tranaction ID 6a04f095
1970-01-01 00:00:51 [5] DHCPD: Send ACK to 192.168.0.100
1970-01-01 00:00:52 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:01:06 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:01:21 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:01:22 [5] DHCPD: Recv REQUEST from F8:DC:7A:16:7A:C9 Tranaction ID 6a04f095
1970-01-01 00:01:22 [5] DHCPD: Send ACK to 192.168.0.100
1970-01-01 00:01:36 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:01:51 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:02:06 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:02:15 [5] DHCPD: Recv REQUEST from F8:DC:7A:16:7A:C9 Tranaction ID 6a04f095
1970-01-01 00:02:15 [5] DHCPD: Send ACK to 192.168.0.100
1970-01-01 00:02:21 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:02:37 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:02:44 [5] DHCPD: Recv REQUEST from F8:DC:7A:16:7A:C9 Tranaction ID 6a04f095
1970-01-01 00:02:44 [5] DHCPD: Send ACK to 192.168.0.100
1970-01-01 00:02:51 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:03:06 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:03:14 [5] DHCPD: Recv REQUEST from F8:DC:7A:16:7A:C9 Tranaction ID 6a04f095
1970-01-01 00:03:14 [5] DHCPD: Send ACK to 192.168.0.100
1970-01-01 00:03:21 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:03:36 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:03:45 [5] DHCPD: Recv REQUEST from F8:DC:7A:16:7A:C9 Tranaction ID 6a04f095
1970-01-01 00:03:45 [5] DHCPD: Send ACK to 192.168.0.100
1970-01-01 00:03:51 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:04:06 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:04:14 [5] DHCPD: Recv REQUEST from F8:DC:7A:16:7A:C9 Tranaction ID 6a04f095
1970-01-01 00:04:14 [5] DHCPD: Send ACK to 192.168.0.100
1970-01-01 00:04:21 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:04:36 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:04:44 [5] DHCPD: Recv REQUEST from F8:DC:7A:16:7A:C9 Tranaction ID 6a04f095
1970-01-01 00:04:44 [5] DHCPD: Send ACK to 192.168.0.100
1970-01-01 00:04:51 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:05:06 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:05:15 [5] DHCPD: Recv REQUEST from F8:DC:7A:16:7A:C9 Tranaction ID 6a04f095
1970-01-01 00:05:15 [5] DHCPD: Send ACK to 192.168.0.100
1970-01-01 00:05:21 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:05:36 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:05:51 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:06:06 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:06:21 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:06:22 [5] DHCPD: Recv DISCOVER from B0:5C:DA:EE:1A:C2 Tranaction ID 31f7c38c
1970-01-01 00:06:22 [5] DHCPD: Send OFFER with ip 192.168.0.101
1970-01-01 00:06:22 [5] DHCPD: Recv DISCOVER from B0:5C:DA:EE:1A:C2 Tranaction ID 65fcad83
1970-01-01 00:06:22 [5] DHCPD: Send OFFER with ip 192.168.0.101
1970-01-01 00:06:22 [5] DHCPD: Recv REQUEST from B0:5C:DA:EE:1A:C2 Tranaction ID 65fcad83
1970-01-01 00:06:22 [5] DHCPD: Send ACK to 192.168.0.101
1970-01-01 00:06:39 [5] DHCPD: Recv DISCOVER from 74:D8:3E:D1:9B:0B Tranaction ID 2a14a0cd
1970-01-01 00:06:39 [5] DHCPD: Send OFFER with ip 192.168.0.102
1970-01-01 00:06:39 [5] DHCPD: Recv REQUEST from 74:D8:3E:D1:9B:0B Tranaction ID 2a14a0cd
1970-01-01 00:06:40 [5] DHCPD: Send ACK to 192.168.0.102
1970-01-01 00:06:44 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:06:52 [5] DHCPD: Recv REQUEST from B0:5C:DA:EE:1A:C2 Tranaction ID 52cead2c
1970-01-01 00:06:52 [5] DHCPD: Send ACK to 192.168.0.101
1970-01-01 00:06:58 [5] DHCPD: Recv REQUEST from 74:D8:3E:D1:9B:0B Tranaction ID 3edb166a
1970-01-01 00:06:58 [5] DHCPD: Send ACK to 192.168.0.102
1970-01-01 00:07:01 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:07:19 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:07:22 [5] DHCPD: Recv REQUEST from B0:5C:DA:EE:1A:C2 Tranaction ID 56b05abc
1970-01-01 00:07:22 [5] DHCPD: Send ACK to 192.168.0.101
1970-01-01 00:07:23 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:07:40 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:07:48 [5] DHCPD: Recv REQUEST from 74:D8:3E:D1:9B:0B Tranaction ID dbbd9d88
1970-01-01 00:07:48 [5] DHCPD: Send ACK to 192.168.0.102
1970-01-01 00:07:52 [5] DHCPD: Recv REQUEST from B0:5C:DA:EE:1A:C2 Tranaction ID 78d15835
1970-01-01 00:07:52 [5] DHCPD: Send ACK to 192.168.0.101
1970-01-01 00:07:54 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:08:08 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:08:18 [5] DHCPD: Recv REQUEST from 74:D8:3E:D1:9B:0B Tranaction ID 3d7fb82e
1970-01-01 00:08:18 [5] DHCPD: Send ACK to 192.168.0.102
1970-01-01 00:08:21 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:08:22 [5] DHCPD: Recv REQUEST from B0:5C:DA:EE:1A:C2 Tranaction ID 49a587b8
1970-01-01 00:08:22 [5] DHCPD: Send ACK to 192.168.0.101
1970-01-01 00:08:37 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:08:48 [5] DHCPD: Recv REQUEST from 74:D8:3E:D1:9B:0B Tranaction ID d4883cf5
1970-01-01 00:08:48 [5] DHCPD: Send ACK to 192.168.0.102
1970-01-01 00:08:52 [5] DHCPD: Recv REQUEST from B0:5C:DA:EE:1A:C2 Tranaction ID ec889149
1970-01-01 00:08:52 [5] DHCPD: Send ACK to 192.168.0.101
1970-01-01 00:08:57 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:09:07 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:09:18 [5] DHCPD: Recv REQUEST from 74:D8:3E:D1:9B:0B Tranaction ID cfe5cca0
1970-01-01 00:09:18 [5] DHCPD: Send ACK to 192.168.0.102
1970-01-01 00:09:22 [5] DHCPD: Recv REQUEST from B0:5C:DA:EE:1A:C2 Tranaction ID b817f69e
1970-01-01 00:09:22 [5] DHCPD: Send ACK to 192.168.0.101
1970-01-01 00:09:24 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:09:37 [5] DHCPC: Discover DHCP service failed!
1970-01-01 00:09:49 [5] DHCPD: Recv REQUEST from 74:D8:3E:D1:9B:0B Tranaction ID 2c3de575
1970-01-01 00:09:49 [5] DHCPD: Send ACK to 192.168.0.102
1970-01-01 00:09:52 [5] DHCPD: Recv REQUEST from B0:5C:DA:EE:1A:C2 Tranaction ID f2e7d6ed
1970-01-01 00:09:52 [5] DHCPD: Send ACK to 192.168.0.101
1970-01-01 00:09:53 [5] DHCPC: Discover DHCP service failed!
On firmware 1705
I get no errors.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
I'm not sure what mode you configured on these, but I had the same problem as you. I was attempting to set my TL-WR802N wireless bridge up in "Client" mode so that I could connect a "headless" device that only has Ethernet, (no Wi-Fi) up to one of our WiFi networks.
I saw your post and rolled back the firmware on my unit as well. This revealed what the actual problem was, and the work-around:
The old WR802N firmware had a mode named "Hotspot Mode" which allowed you to connect it to a WiFi network, and then connect your Ethernet-only (non-WiFi) device to its Ethernet port (it has DHCP enabled, but if your WiFi has DHCP that should also work). This allowed me to connect to the WiFi, and the TP link wireless bridge then successfully got a DHCP address itself from my WiFi network, and everything worked great.
I made a backup of the config. I then updated the firmware to the latest available (V4_200421) and saw that the "Hotspot mode" had been renamed to "WISP" mode. The diagram for WISP mode in the TL-WR802N WiFi bridge manual is misleading because it only shows the WR802N connecting via WiFi to both the Public WiFi and the clients. However, this isn't the case because the Ethernet port on the WR802N also may be used to connect Ethernet-only (non-WiFi) equipment so that they can bridge through the unit to the Public Internet.
Hopefully this clears up a LOT of confusion for everyone.
Regards.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 3488
Replies: 7
Voters 0
No one has voted for it yet.