trenzterra
New Around Here
I used to have three Aztech Powerline HomePlug AV adapters that I swapped out for three TP-Link Powerline adapters as I wanted to upgrade them to the faster AV2 standard. I heard that AV2 and AV were compatible with each other, so since I wanted an additional homeplug, I used one of the old Aztechs as my 4th homeplug.
However, I noticed that my router kept crashing after installing the 4th Homeplug. Thinking that it was the homeplug's fault, I replaced it with another TP-Link, but the problem persists!
Just some background, for my four TP-Link homeplugs, two of them are Wi-Fi enabled (the Nano HomePlug AV500), and two of them are the AV1000 TL-PA7020P Homeplug. The router is plugged directly into the AV1000 homeplug. At first, I thought it was some IP address conflict since the Wi-Fi enabled homeplugs will have their own IP address, so I made sure my router, modem and homeplugs are on different subnets. However, the problem still persists.
What I experience is this:
- When I turn on the 4th homeplug, my router will stop responding for a few minutes. WAN gets disconnected, and I cannot access my router page via either wired (directly to the router and not through the homeplug) or wireless.
- After a few minutes, I can finally access my router's page. WAN is sometimes restored, while sometimes I need to wait 5 mins for it to restore.
- However, if I were to turn off the 4th homeplug whenever my router hangs, my router immediately works normally again, and WAN is restored.
When I check the system logs, this is all I find:
I was always on Merlin's firmware on the latest version (378.55). I tried restoring to latest stock firmware and clearing NVRAM, but the issue persists. While the router 'hangs', the DHCP server still gives my wireless devices an IP address, and the blue LEDs on the router blink as per normal. It's just that I can't access the router interface nor surf the net.
I'm thus on my wits end... Is this a bug in the RT-N66U router? Or...? I've no idea how a homeplug can 'crash' my router. And it's funny how everything starts going awry only after the 4th is added in.
However, I noticed that my router kept crashing after installing the 4th Homeplug. Thinking that it was the homeplug's fault, I replaced it with another TP-Link, but the problem persists!
Just some background, for my four TP-Link homeplugs, two of them are Wi-Fi enabled (the Nano HomePlug AV500), and two of them are the AV1000 TL-PA7020P Homeplug. The router is plugged directly into the AV1000 homeplug. At first, I thought it was some IP address conflict since the Wi-Fi enabled homeplugs will have their own IP address, so I made sure my router, modem and homeplugs are on different subnets. However, the problem still persists.
What I experience is this:
- When I turn on the 4th homeplug, my router will stop responding for a few minutes. WAN gets disconnected, and I cannot access my router page via either wired (directly to the router and not through the homeplug) or wireless.
- After a few minutes, I can finally access my router's page. WAN is sometimes restored, while sometimes I need to wait 5 mins for it to restore.
- However, if I were to turn off the 4th homeplug whenever my router hangs, my router immediately works normally again, and WAN is restored.
When I check the system logs, this is all I find:
Code:
Sep 13 21:50:17 pppd[961]: Serial link appears to be disconnected.
Sep 13 21:50:20 WAN Connection: Fail to connect with some issues.
Sep 13 21:50:20 stop_nat_rules: apply the redirect_rules!
Sep 13 21:50:23 pppd[961]: Connection terminated.
Sep 13 21:50:23 pppd[961]: Modem hangup
Sep 13 21:50:34 nmbd[1026]: process_local_master_announce: Server LS-XL709 at IP 192.168.3.169 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election.
Sep 13 21:50:34 nmbd[1026]: [2015/09/13 21:50:34, 0] nmbd/nmbd_become_lmb.c:unbecome_local_master_success(149)
Sep 13 21:50:34 nmbd[1026]: Samba name server RT-N66U-5520 has stopped being a local master browser for workgroup WORKGROUP on subnet 192.168.3.1
Sep 13 21:50:52 nmbd[1026]: [2015/09/13 21:50:52, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(392)
Sep 13 21:50:52 nmbd[1026]: Samba name server RT-N66U-5520 is now a local master browser for workgroup WORKGROUP on subnet 192.168.3.1
Sep 13 21:51:08 pppd[961]: Timeout waiting for PADO packets
Sep 13 21:52:05 nmbd[1026]: [2015/09/13 21:52:05, 0] nmbd/nmbd_incomingrequests.c:process_name_release_request(118)
Sep 13 21:52:05 nmbd[1026]: process_name_release_request: Attempt to release name WORKGROUP<1d> from IP 192.168.3.169 on subnet 192.168.3.1 being rejected as it is one of our names.
Sep 13 21:52:23 pppd[961]: Timeout waiting for PADO packets
Sep 13 21:52:58 pppd[961]: Timeout waiting for PADS packets
Sep 13 21:53:33 pppd[961]: Timeout waiting for PADS packets
Sep 13 21:54:08 pppd[961]: Timeout waiting for PADS packets
Sep 13 21:54:43 pppd[961]: Timeout waiting for PADS packets
Sep 13 21:55:18 pppd[961]: Timeout waiting for PADS packets
Sep 13 21:55:53 pppd[961]: Timeout waiting for PADS packets
Sep 13 21:56:08 pppd[961]: Connected to 00:90:1a:a2:b8:90 via interface eth0
Sep 13 21:56:08 pppd[961]: Connect: ppp0 <--> eth0
Sep 13 21:56:09 pppd[961]: PAP authentication succeeded
Sep 13 21:56:09 pppd[961]: peer from calling number 00:90:1A:A2:B8:90 authorized
Sep 13 21:56:09 pppd[961]: local IP address 220.255.67.237
Sep 13 21:56:09 pppd[961]: remote IP address 116.15.210.1
Sep 13 21:56:09 pppd[961]: primary DNS address 165.21.100.88
Sep 13 21:56:09 pppd[961]: secondary DNS address 165.21.83.88
Sep 13 21:56:09 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Sep 13 21:56:09 wan: finish adding multi routes
Sep 13 21:56:09 rc_service: ip-up 1166:notify_rc stop_upnp
Sep 13 21:56:09 miniupnpd[1041]: received signal 15, good-bye
Sep 13 21:56:10 rc_service: ip-up 1166:notify_rc start_upnp
Sep 13 21:56:10 miniupnpd[1197]: HTTP listening on port 50437
Sep 13 21:56:10 miniupnpd[1197]: Listening for NAT-PMP traffic on port 5351
Sep 13 21:56:11 WAN Connection: WAN was restored.I was always on Merlin's firmware on the latest version (378.55). I tried restoring to latest stock firmware and clearing NVRAM, but the issue persists. While the router 'hangs', the DHCP server still gives my wireless devices an IP address, and the blue LEDs on the router blink as per normal. It's just that I can't access the router interface nor surf the net.
I'm thus on my wits end... Is this a bug in the RT-N66U router? Or...? I've no idea how a homeplug can 'crash' my router. And it's funny how everything starts going awry only after the 4th is added in.
Last edited:
