Powerline adaptors crashing ASUS RT-N66U

trenzterra

Arch-Supremacy Member
Joined
Sep 18, 2002
Messages
20,628
Reaction score
516
Hi guys, I'm having this weird problem where my powerline adaptors are crashing my RTN66U.

All along, I've 3 adapters that run with no issue. Recently, I decided to add one more, and that's where all the problem starts...

After pairing it to the network, I get random occasions where the router hangs. When I disconnect the homeplug, the router 'unhangs' itself. At first, I thought it's a homeplug issue, so I went out to buy another brand... HOwever, the issue persists. Kinda on my wits' end now... Using ASUS Merlin WRT latest version.

Anyone come across this issue before?

I get this on my error log:

Sep 12 11:21:57 kernel: vlan1: received packet with own address as source address
Sep 12 11:22:25 smbd[565]: [2015/09/12 11:22:25.464915, 0] smbd/sesssetup.c:1355(reply_sesssetup_and_X)
Sep 12 11:22:25 smbd[565]: reply_sesssetup_and_X: Rejecting attempt at SPNEGO session setup when it was not negotiated.
 

Ah-Pin-Kor

Great Supremacy Member
Joined
Apr 2, 2008
Messages
55,969
Reaction score
2,301
Are the 4 homeplugs all in the same network or separate 2 pairs?
 

trenzterra

Arch-Supremacy Member
Joined
Sep 18, 2002
Messages
20,628
Reaction score
516
Are the 4 homeplugs all in the same network or separate 2 pairs?

Same network. I tried troubleshooting and it seems the wireless part of the homeplug uses the same ip as my router. So I changed the ip on my router to another subnet... But it still happens! And I'm not sure if the router is hanging or something or the power line is just stopping me from accessing the router? because I don't get the error messages all the time.
 

Ah-Pin-Kor

Great Supremacy Member
Joined
Apr 2, 2008
Messages
55,969
Reaction score
2,301
What model is the homeplug with the wireless?
I assume the other 3 are just the normal wired-only ones.
 

trenzterra

Arch-Supremacy Member
Joined
Sep 18, 2002
Messages
20,628
Reaction score
516
Tplink nano av500. I have 2 of these and 2 of the wired ones. But funny thing is when I plug in the 4th one then I get the issue. Previously my 4th one was an aztech av200. At first I thought it was incompatibility issue so I changed to another tplink... But same problem


Could it be router issue? Shouldn't be right?
 

Ah-Pin-Kor

Great Supremacy Member
Joined
Apr 2, 2008
Messages
55,969
Reaction score
2,301
Just to understand your N66 "hang" problem.

I assume you have one LAN cable from the N66 connected to the homeplug network.
Once the router hangs, what are the symptoms?
Cannot access internet? Is the link light still on and the activity light flashing for that port on the router?
If you just disconnect that one cable from the router, will it recover by itself?
Is it only if you remove a particular homeplug or any one of the 4, that will cause the router to recover?
 

trenzterra

Arch-Supremacy Member
Joined
Sep 18, 2002
Messages
20,628
Reaction score
516
I cannot access Internet and cannot ping the router or access router page. My own com is not connected to the homeplug. Happens to all wired and wireless devices. But link light all those still on and blinking as per normal.

When I disconnect the cable from the main homeplug, it will suddenly work again. If I turn off the 4th homeplug it will also work again... The router will behave like nothing happened
 

Ah-Pin-Kor

Great Supremacy Member
Joined
Apr 2, 2008
Messages
55,969
Reaction score
2,301
I don't know whether the homeplug network cannot have a 4th node or is there some problem with the new homeplug itself (not likely since you said you tried aztech previously), so it's more likely the former, even though in theory, up to at least 8 nodes are possible.
Anyway, have you tried to update the firmware of all the homeplugs?
You may also want to see if you can work around the problem by using lesser homeplugs and use a small switch (if the devices are near enough to be cabled), or even using a wireless bridge, all depending on where the various client devices are (how far are they from each other and the router).
 

DiscMan

Senior Member
Joined
Mar 20, 2001
Messages
1,121
Reaction score
0
does it sounds like some more the router's IP is hijacked by the fourth homeplug?
 

trenzterra

Arch-Supremacy Member
Joined
Sep 18, 2002
Messages
20,628
Reaction score
516
After changing the IP addresses of my modem, router and homeplugs to different subnet, the problem is less severe.

However, I'm still getting random WAN disconnects and router unresponsiveness for about 1 minute from time to time...

This is my router log when it happens:

Sep 13 15:01:27 pppd[938]: No response to 10 echo-requests
Sep 13 15:01:27 pppd[938]: Serial link appears to be disconnected.
Sep 13 15:01:27 pppd[938]: Connect time 833.0 minutes.
Sep 13 15:01:27 pppd[938]: Sent 118529777 bytes, received 2286334950 bytes.
Sep 13 15:01:27 miniupnpd[1010]: Failed to get IP for interface ppp0
Sep 13 15:01:27 miniupnpd[1010]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Sep 13 15:01:27 dnsmasq[1019]: read /etc/hosts - 5 addresses
Sep 13 15:01:27 dnsmasq[1019]: using nameserver 192.168.0.1#53 for domain local
Sep 13 15:01:27 dnsmasq[1019]: using nameserver 192.168.0.1#53 for domain Home
Sep 13 15:01:27 dnsmasq[1019]: using nameserver 192.168.0.1#53 for domain local
Sep 13 15:01:27 dnsmasq[1019]: using nameserver 192.168.0.1#53 for domain Home
Sep 13 15:01:27 dnsmasq[1019]: using nameserver 192.168.0.1#53
Sep 13 15:01:27 dnsmasq[1019]: using nameserver 192.168.0.1#53
Sep 13 15:01:29 WAN Connection: Fail to connect with some issues.
Sep 13 15:01:29 stop_nat_rules: apply the redirect_rules!
Sep 13 15:01:33 pppd[938]: Connection terminated.
Sep 13 15:01:33 pppd[938]: Sent PADT
Sep 13 15:01:33 pppd[938]: Modem hangup
Sep 13 15:01:50 pppd[938]: PPP session is 10773 (0x2a15)
Sep 13 15:01:50 pppd[938]: Connected to 00:90:1a:a2:b8:90 via interface eth0
Sep 13 15:01:50 pppd[938]: Using interface ppp0
Sep 13 15:01:50 pppd[938]: Connect: ppp0 <--> eth0
Sep 13 15:01:50 pppd[938]: PAP authentication succeeded
Sep 13 15:01:50 pppd[938]: peer from calling number 00:90:1A:A2:B8:90 authorized
Sep 13 15:01:51 miniupnpd[1010]: Failed to get IP for interface ppp0
Sep 13 15:01:51 miniupnpd[1010]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Sep 13 15:01:51 miniupnpd[1010]: Failed to get IP for interface ppp0
Sep 13 15:01:51 miniupnpd[1010]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Sep 13 15:01:51 miniupnpd[1010]: Failed to get IP for interface ppp0
Sep 13 15:01:51 miniupnpd[1010]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Sep 13 15:01:51 pppd[938]: local IP address 119.74.128.132
Sep 13 15:01:51 pppd[938]: remote IP address 116.15.210.1
Sep 13 15:01:51 pppd[938]: primary DNS address 165.21.100.88
Sep 13 15:01:51 pppd[938]: secondary DNS address 165.21.83.88
Sep 13 15:01:51 rc_service: ip-up 1386:notify_rc start_firewall
Sep 13 15:01:51 dnsmasq[1019]: read /etc/hosts - 5 addresses
Sep 13 15:01:51 dnsmasq[1019]: using nameserver 192.168.0.1#53 for domain local
Sep 13 15:01:51 dnsmasq[1019]: using nameserver 192.168.0.1#53 for domain Home
Sep 13 15:01:51 dnsmasq[1019]: using nameserver 192.168.0.1#53 for domain local
Sep 13 15:01:51 dnsmasq[1019]: using nameserver 192.168.0.1#53 for domain Home
Sep 13 15:01:51 dnsmasq[1019]: using nameserver 165.21.83.88#53 for domain local
Sep 13 15:01:51 dnsmasq[1019]: using nameserver 165.21.100.88#53 for domain local
Sep 13 15:01:51 dnsmasq[1019]: using nameserver 165.21.100.88#53
Sep 13 15:01:51 dnsmasq[1019]: using nameserver 165.21.83.88#53
Sep 13 15:01:51 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Sep 13 15:01:51 wan: finish adding multi routes
Sep 13 15:01:51 rc_service: ip-up 1386:notify_rc stop_upnp
Sep 13 15:01:51 rc_service: waitting "start_firewall" via ip-up ...
Sep 13 15:01:52 miniupnpd[1010]: shutting down MiniUPnPd
Sep 13 15:01:53 rc_service: httpd 807:notify_rc start_autodet
Sep 13 15:01:53 rc_service: ip-up 1386:notify_rc start_upnp
Sep 13 15:01:53 miniupnpd[1422]: HTTP listening on port 48105
Sep 13 15:01:53 miniupnpd[1422]: Listening for NAT-PMP/PCP traffic on port 5351
Sep 13 15:01:54 WAN Connection: WAN was restored.

Is it time for a new router? New modem? or?
 

AshSim

Master Member
Joined
May 11, 2015
Messages
4,228
Reaction score
0
I don't know whether the homeplug network cannot have a 4th node or is there some problem with the new homeplug itself (not likely since you said you tried aztech previously), so it's more likely the former, even though in theory, up to at least 8 nodes are possible.
Anyway, have you tried to update the firmware of all the homeplugs?
You may also want to see if you can work around the problem by using lesser homeplugs and use a small switch (if the devices are near enough to be cabled), or even using a wireless bridge, all depending on where the various client devices are (how far are they from each other and the router).


Ya, I think lesser homeplugs may work? Or maybe, don't plug high-consuming electrical appliances together lor...
 

ASUS@SG

Suspended
Joined
Jul 26, 2011
Messages
7,580
Reaction score
8
Dear AshSim,

One of your homeplug using same router power source from 13A socket?

Best regard,
JK
 

upgrade

Senior Member
Joined
Apr 16, 2008
Messages
1,304
Reaction score
2
I have been using homeplugs for a few years now, upgrading as better speed came along:

1) 6 pcs TL-PA251 200AV
2) 6 pcs TL-PA551 500AV + TL-WPA4220 500AV (Wifi)
3) 4 pcs PL1800EP 1800AV2
with 1 pc in living room and 1 pc each in 3 bedrooms connected to routers in the bedrooms (total 4 routers). Routers in bedrooms used to be the old WRT54G workhorse, but now using ASUS RT-N56U and 2 Belkin cannot remember the different models.

I can tell you that the problem is not with the homeplugs.

From your log posting, I note you are using ST DNS so I believe you are using ST.

a) I keep my router at the ST default 192.168.1.254.
b) I set ST router DHCP to the range 192.168.1.100 to 192.168.1.200
c) I disable DHCP in all bedroom routers.
d) I set bedroom routers and homeplug Wifi IPs within the 192.168.1.1 to 192.168.1.9 range.
e) All bedroom routers are connected LAN port to homeplug.

You will notice I use all homeplug with pass-through. The ST router/ONT/mioSTB and TV all plugged into an extension socket, in turn this plug into pass-through homeplug (to filter out electrical noise interference) in the living room.

Similarly, the same in the bedroom - everything into extension socket then into homeplug pass-through for the same noise filter reason.

No problem at all.

Edit to add:
You can use up to 8 homeplugs, so 4 is not a problem.

.
 
Last edited:

upgrade

Senior Member
Joined
Apr 16, 2008
Messages
1,304
Reaction score
2
I am not expert in this but this seems like the router connection to ST problem:

"Sep 13 15:01:27 miniupnpd[1010]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping"

I did a simple search, did not go into detail, and seems someone out there have the same problem with RT-N66U and Merlin 374.43:

http://www.snbforums.com/threads/st...s-on-rt-n66u-resulting-in-dns-problems.18268/

Also maybe same right here at home but with RT-AC66U and Merlin:
http://forums.hardwarezone.com.sg/i...rk-knight-rises-3845510-113.html#post84075651

Not sure whether same as your situation. If so, maybe some clue for you.

.
 
Last edited:
Important Forum Advisory Note
This forum is moderated by volunteer moderators who will react only to members' feedback on posts. Moderators are not employees or representatives of HWZ Forums. Forum members and moderators are responsible for their own posts. Please refer to our Community Guidelines and Standards and Terms and Conditions for more information.
Top