PS4 LAG with test results!

[dfran1]

This is what I get in the port forwarding log before I hit apply
Thank You


Destination Proto. Port range Redirect to Local port Chain

!192.168.1.0 TCP 80 192.168.1.1 18017 PREROUTING

ALL UDP 53 192.168.1.1 18018 PREROUTING


rebooting the cable modem at the same time = same problem , have to hit apply in the WAN tab and same error above

NOTE: I think all my other problems were gone tho, it passed a 30 hour test.
just this one last problem. (I hope)

 

[john9527]

That's what I expected to see. The router got stuck during boot in a mode where it thinks the WAN is down. I think I can gen a a wan-start script that will fix the problem for you. Can you log into the router and post the output from the following

ls /tmp/nat* (that's a small letter 'L' for the first character)

NOTE to @RMerlin: There are two commits related to iptables-restore in my latest fork release that appears to fix this.

EDIT: Actually can tell you how to do it.....when you run that command you'll see two files. One will have a longer name than the other, like this /tmp/nat_rules_xxx_yyy
Take that name for below.

Make a file wan-start in the /jffs/scripts directory with the following contents

#!/bin/sh
iptables-restore /tmp/nat_rules_xxx_yyyy

Then make it executable with
chmod a+rx /jffs/scripts/wan-start

Make sure that the option to run scripts is enabled in the gui.

 

[dfran1]

/tmp/nat_rules /tmp/nat_rules_eth0_eth0

sorry but I never did this, dd-wrt has a nice place to put code but none on asus or merlins.

 

[john9527]

/tmp/nat_rules /tmp/nat_rules_eth0_eth0

sorry but I never did this, dd-wrt has a nice place to put code but none on asus or merlins.

Actually, we should make sure it works first....
After the boot when you have the problem..... log into the router and enter

iptables-restore /tmp/nat_rules_eth0_eth0

it should free things right up.

 

[dfran1]

after I hit the apply on the WAN page after reboot

admin@RT-AC87R-A2F8:/tmp/home/root# ls /tmp/nat*

/tmp/nat_rules /tmp/nat_rules_eth0_eth0

before I hit the apply on the WAN page after reboot

admin@RT-AC87R-A2F8:/tmp/home/root# ls /tmp/nat*

ls: /tmp/nat*: No such file or directory

So I can not run that command, Thank You!!!

 

[john9527]

Just enter this command

iptables-restore /tmp/nat_rules_eth0_eth0

 

[dfran1]

I did and I get this after reboot with the problem, it wont let me access that directory at that point.
maybe thats the problem

admin@RT-AC87R-A2F8:/tmp/home/root# iptables-restore /tmp/nat_rules_eth0_

eth0

Can't open /tmp/nat_rules_eth0_eth0: No such file or directory

Also I flashed to a merlin alfa tonight and still got the same problem, and the past month or 2 of merlins had this problem for me. but I think asus is good.

Merlin: I can not believe I am the only one with your versions on this problem (I think the asus ones work)? How could charter be causing it?

 

[baos]

Any chance you're using the latest from github? There is some lag being produced on that one. Could not decide why so I did not post. However rolling back fixed my issue.

 

[dfran1]

Any chance you're using the latest from github? There is some lag being produced on that one. Could not decide why so I did not post. However rolling back fixed my issue.

I am now using this
http://www.snbforums.com/threads/dd-wrt-for-rt-ac87r.22421/page-11#post-172913
seems extremely quick, I do not see any lag at all with it, in fact the gui is now super quick. (hopefully it lasts)

 

[john9527]

Can't open /tmp/nat_rules_eth0_eth0: No such file or directory

Well, that's interesting....haven't encountered that one.

Can you check the system log in the gui aright after boot and use your browser to search for
start_nat_rules
What do you find? there should be 2 or 3 hits.

 

[dfran1]

I cleared the log then rebooted and found only 1 and 1 more after WAN apply

Dec 31 19:01:01 wan: finish adding multi routes
Dec 31 19:01:01 rc_service: udhcpc 750:notify_rc stop_upnp
Dec 31 19:01:01 rc_service: waitting "restart_nasapps" via  ...
Dec 31 19:01:04 iTunes: daemon is stopped
Dec 31 19:01:04 FTP Server: daemon is stopped
Dec 31 19:01:04 qtn: bootcfg.tgz exists
Dec 31 19:01:05 Samba Server: smb daemon is stopped
Dec 31 19:01:05 kernel: gro disabled
Dec 31 19:01:05 Timemachine: daemon is stopped
Dec 31 19:01:05 kernel: gro enabled with interval 2
Dec 31 19:01:05 WAN Connection: WAN was restored.
Dec 31 19:01:05 start_nat_rules: apply the nat_rules(/tmp/nat_rules)!
Dec 31 19:01:06 Samba Server: daemon is started
Dec 31 19:01:08 rc_service: udhcpc 750:notify_rc start_upnp
Dec 31 19:01:10 miniupnpd[837]: HTTP listening on port 36149
Dec 31 19:01:10 miniupnpd[837]: Listening for NAT-PMP/PCP traffic on port 5351
Dec 31 19:01:11 ddns update: ez-ipupdate: starting...
Dec 31 19:01:11 ddns update: connected to members.dyndns.org (204.13.248.111) on port 80.
Dec 31 19:01:11 ddns update: members.dyndns.org says that your IP address has not changed since the last update
Dec 31 19:01:11 ddns update: asusddns_update: 0
Dec 31 19:01:12 ddns: ddns update ok
Dec 31 19:01:13 ntp: start NTP update

Mar 18 21:50:51 rc_service: ntp 843:notify_rc restart_upnp
Mar 18 21:50:51 miniupnpd[837]: shutting down MiniUPnPd
Mar 18 21:50:51 miniupnpd[856]: HTTP listening on port 33533
Mar 18 21:50:51 miniupnpd[856]: Listening for NAT-PMP/PCP traffic on port 5351
Mar 18 21:50:52 rc_service: ntp 843:notify_rc restart_diskmon
Mar 18 21:50:54 disk monitor: be idle
Mar 18 21:51:21 kernel: br0: received packet on eth1 with own address as source address
Mar 18 21:51:38 crond[659]: time disparity of 110990 minutes detected

after WAN apply

Mar 18 21:54:46 rc_service: httpd 657:notify_rc restart_wan_if 0
Mar 18 21:54:47 dnsmasq[651]: read /etc/hosts - 5 addresses
Mar 18 21:54:47 dnsmasq[651]: read /etc/hosts.dnsmasq - 4 addresses
Mar 18 21:54:47 dnsmasq-dhcp[651]: read /etc/ethers - 4 addresses
Mar 18 21:54:47 dnsmasq[651]: using nameserver 208.67.220.123#53 for domain local
Mar 18 21:54:47 dnsmasq[651]: using nameserver 208.67.222.123#53 for domain local
Mar 18 21:54:47 dnsmasq[651]: using nameserver 208.67.222.123#53
Mar 18 21:54:47 dnsmasq[651]: using nameserver 208.67.220.123#53
Mar 18 21:54:47 kernel: Attempt to kill tasklet from interrupt
Mar 18 21:54:47 pppoe-relay[738]: recv (receivePacket): Network is down
Mar 18 21:54:47 pppoe-relay[738]: recv (receivePacket): Network is down
Mar 18 21:54:47 kernel: br0: port 1(vlan1) entering forwarding state
Mar 18 21:54:47 kernel: device eth0 left promiscuous mode
Mar 18 21:54:47 kernel: device eth0 entered promiscuous mode
Mar 18 21:54:47 kernel: br0: port 1(vlan1) entering forwarding state
Mar 18 21:54:47 kernel: br0: port 1(vlan1) entering forwarding state
Mar 18 21:54:47 miniupnpd[856]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Mar 18 21:54:47 miniupnpd[856]: Failed to get IP for interface eth0
Mar 18 21:54:47 miniupnpd[856]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Mar 18 21:54:50 dnsmasq[651]: read /etc/hosts - 5 addresses
Mar 18 21:54:50 dnsmasq[651]: read /etc/hosts.dnsmasq - 4 addresses
Mar 18 21:54:50 dnsmasq-dhcp[651]: read /etc/ethers - 4 addresses
Mar 18 21:54:50 dnsmasq[651]: using nameserver 208.67.220.123#53 for domain local
Mar 18 21:54:50 dnsmasq[651]: using nameserver 208.67.222.123#53 for domain local
Mar 18 21:54:50 dnsmasq[651]: using nameserver 208.67.222.123#53
Mar 18 21:54:50 dnsmasq[651]: using nameserver 208.67.220.123#53
Mar 18 21:54:51 miniupnpd[856]: add_filter_rule() : chain FUPNP not found
Mar 18 21:54:51 miniupnpd[856]: Failed to add NAT-PMP 4500 udp->192.168.1.137:4500 'NAT-PMP 4500 udp'
Mar 18 21:54:51 rc_service: udhcpc 934:notify_rc start_firewall
Mar 18 21:54:51 dnsmasq[651]: read /etc/hosts - 5 addresses
Mar 18 21:54:51 dnsmasq[651]: read /etc/hosts.dnsmasq - 4 addresses
Mar 18 21:54:51 dnsmasq-dhcp[651]: read /etc/ethers - 4 addresses
Mar 18 21:54:51 dnsmasq[651]: using nameserver 208.67.220.123#53 for domain local
Mar 18 21:54:51 dnsmasq[651]: using nameserver 208.67.222.123#53 for domain local
Mar 18 21:54:51 dnsmasq[651]: using nameserver 208.67.222.123#53
Mar 18 21:54:51 dnsmasq[651]: using nameserver 208.67.220.123#53
Mar 18 21:54:51 miniupnpd[856]: add_filter_rule() : chain FUPNP not found
Mar 18 21:54:51 miniupnpd[856]: Failed to add NAT-PMP 4500 udp->192.168.1.137:4500 'NAT-PMP 4500 udp'
Mar 18 21:54:52 miniupnpd[856]: add_filter_rule() : chain FUPNP not found
Mar 18 21:54:52 miniupnpd[856]: Failed to add NAT-PMP 4500 udp->192.168.1.137:4500 'NAT-PMP 4500 udp'
Mar 18 21:54:52 wan: finish adding multi routes
Mar 18 21:54:52 rc_service: udhcpc 934:notify_rc stop_upnp
Mar 18 21:54:52 rc_service: waitting "start_firewall" via udhcpc ...
Mar 18 21:54:52 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Mar 18 21:54:53 kernel: nf_conntrack_rtsp v0.6.21 loading
Mar 18 21:54:53 kernel: nf_nat_rtsp v0.6.21 loading
Mar 18 21:54:54 miniupnpd[856]: shutting down MiniUPnPd

 

[baos]

I am now using this
http://www.snbforums.com/threads/dd-wrt-for-rt-ac87r.22421/page-11#post-172913
seems extremely quick, I do not see any lag at all with it, in fact the gui is now super quick. (hopefully it lasts)

There are reasons for using merlin over dd-wrt. That said, asus seems to be failing in the software area and if not for merlin their products probably wouldn't do as good. Even with his mods, no one seems able to meet the promised asus speeds and other brands are doing better(in real world tests). At best I've been able to bring an ea-n66 to half the promised speed of 400mbit in a remote location with no other networks around. it's an ac87r feeding it. At this point in time I'm very disappointed with asus for more than just the routers.

 

[john9527]

I cleared the log then rebooted and found only 1 and 1 more after WAN apply

Now I'm really confused....the before looks almost perfect but I don't see dnsmasq coming up (maybe you edited for clarity)...you can get to the internet as seen by you ddns update. After the WAN button is applied, things just break. Can you zip up your entire syslog and append it (if you don't want to post it, I'll send you a PM with my email address to send it to).

 

[dfran1]

Now I'm really confused....the before looks almost perfect but I don't see dnsmasq coming up (maybe you edited for clarity)...you can get to the internet as seen by you ddns update. After the WAN button is applied, things just break. Can you zip up your entire syslog and append it (if you don't want to post it, I'll send you a PM with my email address to send it to).

I sent you a PM

 

[john9527]

I sent you a PM

Got it...interesting....
When you first boot everything looks great....nice normal boot....ending with (the crond msg is usually what you see at the end of boot). Everything is up, the ddns update is successful, and upnp is up.

Dec 31 19:01:05 WAN Connection: WAN was restored.
Dec 31 19:01:05 start_nat_rules: apply the nat_rules(/tmp/nat_rules)!
Dec 31 19:01:06 Samba Server: daemon is started
Dec 31 19:01:08 rc_service: udhcpc 750:notify_rc start_upnp
Dec 31 19:01:10 miniupnpd[837]: HTTP listening on port 36149
Dec 31 19:01:10 miniupnpd[837]: Listening for NAT-PMP/PCP traffic on port 5351
Dec 31 19:01:11 ddns update: ez-ipupdate: starting...
Dec 31 19:01:11 ddns update: connected to members.dyndns.org (204.13.248.111) on port 80.
Dec 31 19:01:11 ddns update: members.dyndns.org says that your IP address has not changed since the last update
Dec 31 19:01:11 ddns update: asusddns_update: 0
Dec 31 19:01:12 ddns: ddns update ok
Dec 31 19:01:13 ntp: start NTP update
Dec 31 19:01:13 dhcp client: bound xxx.xxx.xxx.xxx via xxx.xxx.xxx.xxx during 22665 seconds.
Mar 18 21:50:51 rc_service: ntp 843:notify_rc restart_upnp
Mar 18 21:50:51 miniupnpd[837]: shutting down MiniUPnPd
Mar 18 21:50:51 miniupnpd[856]: HTTP listening on port 33533
Mar 18 21:50:51 miniupnpd[856]: Listening for NAT-PMP/PCP traffic on port 5351
Mar 18 21:50:52 rc_service: ntp 843:notify_rc restart_diskmon
Mar 18 21:50:54 disk monitor: be idle
Mar 18 21:51:21 kernel: br0: received packet on eth1 with own address as source address
Mar 18 21:51:38 crond[659]: time disparity of 110990 minutes detected

Then the very next entry, a little over 3 minutes later, you drop your WAN connection (and it really looks dropped)

Mar 18 21:54:46 rc_service: httpd 657:notify_rc restart_wan_if 0
Mar 18 21:54:47 dnsmasq[651]: read /etc/hosts - 5 addresses
Mar 18 21:54:47 dnsmasq[651]: read /etc/hosts.dnsmasq - 4 addresses
Mar 18 21:54:47 dnsmasq-dhcp[651]: read /etc/ethers - 4 addresses
Mar 18 21:54:47 dnsmasq[651]: using nameserver 208.67.220.123#53 for domain local
Mar 18 21:54:47 dnsmasq[651]: using nameserver 208.67.222.123#53 for domain local
Mar 18 21:54:47 dnsmasq[651]: using nameserver 208.67.222.123#53
Mar 18 21:54:47 dnsmasq[651]: using nameserver 208.67.220.123#53
Mar 18 21:54:47 kernel: Attempt to kill tasklet from interrupt
Mar 18 21:54:47 pppoe-relay[738]: recv (receivePacket): Network is down
Mar 18 21:54:47 pppoe-relay[738]: recv (receivePacket): Network is down
Mar 18 21:54:47 kernel: br0: port 1(vlan1) entering forwarding state
Mar 18 21:54:47 kernel: device eth0 left promiscuous mode
Mar 18 21:54:47 kernel: device eth0 entered promiscuous mode
Mar 18 21:54:47 kernel: br0: port 1(vlan1) entering forwarding state
Mar 18 21:54:47 kernel: br0: port 1(vlan1) entering forwarding state
Mar 18 21:54:47 miniupnpd[856]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Mar 18 21:54:47 miniupnpd[856]: Failed to get IP for interface eth0
Mar 18 21:54:47 miniupnpd[856]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping

This may sound silly, but if it were me the first thing I would do is replace the modem-router cable with a good quality Cat6 replacement.

 

[dfran1]

Got it...interesting....
When you first boot everything looks great....nice normal boot....ending with (the crond msg is usually what you see at the end of boot). Everything is up, the ddns update is successful, and upnp is up.


This may sound silly, but if it were me the first thing I would do is replace the modem-router cable with a good quality Cat6 replacement.

Now the monkey wrench
this does not happen with dd-wrt or I original firmware, just merlins (from what I recall), BUT i just tried 2 other cables, original is a shielded cat 6, a second shielded cat 6 and a 3rd non shielded cat6 all 2 feet tops and still the same problem.

 

[john9527]

Now the monkey wrench
this does not happen with dd-wrt or I original firmware, just merlins (from what I recall), BUT i just tried 2 other cables, original is a shielded cat 6, a second shielded cat 6 and a 3rd non shielded cat6 all 2 feet tops and still the same problem.

Ok...I had another thought.....when it comes up and you don't have access, try the same iptables command as before, but use the other file.

iptables-restore /tmp/nat_rules

and see if that frees things up (you may not generate the other file with eth0_eth0 unit you have a port forward in place)

EDIT: Shut down your browser and restart it after the command, since it can internally cache some bad info.

 

[RMerlin]

Mar 18 21:54:46 rc_service: httpd 657:notify_rc restart_wan_if 0
Mar 18 21:54:47 pppoe-relay[738]: recv (receivePacket): Network is down

Those lines are what strike me.

- The first line implies that the web server instructed the the router to take the WAN interface down.
- Why am I seeing pppoe-related services running when you are using a DHCP connection?

This sound as if you have a 3G/4G modem configured as a Dual WAN device.

 

[dfran1]

I went to the dual wan page and it is off and on wan, so I hit apply anyway and it did a reboot and no WAN again.

SO
I ran that line in telnet and
admin@RT-AC87R-A2F8:/tmp/home/root# iptables-restore /tmp/nat_rules

Can't open /tmp/nat_rules: No such file or directory

went back to wan page and hit apply to get internet back.

I pm'ed my latest log to john9527 and merlin.
Thank You!

 

[dfran1]

Hi,
I just sent john9527 and RMerlin my latest log.
what I did is install asus firmware on top of merlin's and I do not get WAN loss after reboot problems with asus firmware, just merlin's.
Can this be fixed?

EDIT:
I just installed another merlin version on top of the asus and back to hitting apply in the WAN page.