PS4 LAG with test results!

[CiscoX]

try rebooting the router and test again, I am testing other options.

Hi,

Have you tried to connect your PS4 straight to you modem without using ASUS router? If it possible, just to see if you get the lag problem back.

How do you connect to your modem? Are you using PPPoE or you get IP automatically from your ISP?

 

[dfran1]

Hi,

Have you tried to connect your PS4 straight to you modem without using ASUS router? If it possible, just to see if you get the lag problem back.

How do you connect to your modem? Are you using PPPoE or you get IP automatically from your ISP?

Auto, from ISP, charter

I am getting no lag at the moment, it does not happen until ~20 hours, but with dd-wrt it does not happen at all. but I am still testing all suggestions here and want to thank all for them. Thank You!

 

[dfran1]

After every reboot, I have to go into WAN and hit apple to get internet access.

Is there any reason why this happens ?

 

[L&LD]

After every reboot, I have to go into WAN and hit apple to get internet access.

Is there any reason why this happens ?

I don't 'have to', but I want to hit apple too. But I have my reasons.

 

[RMerlin]

Thanks Merlin - any idea why UPNP is showing as not found on this test, but also by my PS3 - it is on in the 87u config.

I am running 378.51

Thanks

SSH into your router and check if the miniupnp daemon is still running:

ps w | grep miniupnp

If it is, then something is wrong with the way the PS4 tries to use UPNP (or the way that test tries UPNP).

Also check the System Log for any message related to UPNP and expired port mapping getting removed.

 

[RMerlin]

After every reboot, I have to go into WAN and hit apple to get internet access.

Is there any reason why this happens ?

Since you are with Charter, make sure that the DHCP frequency is set to "Normal" and not "Aggressive" on the WAN page. Their DHCP server is a bit paranoid when it comes to blacklisting clients requesting too many requests within a few minutes.

 

[Speedluvver]

SSH into your router and check if the miniupnp daemon is still running:

ps w | grep miniupnp

If it is, then something is wrong with the way the PS4 tries to use UPNP (or the way that test tries UPNP).

Also check the System Log for any message related to UPNP and expired port mapping getting removed.

I get the following in my log

Dec 1 00:01:03 qtn: bootcfg.tgz exists
Dec 1 00:01:03 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Dec 1 00:01:04 kernel: nf_conntrack_rtsp v0.6.21 loading
Dec 1 00:01:04 kernel: nf_nat_rtsp v0.6.21 loading
Dec 1 00:01:05 rc_service: ip-up 687:notify_rc start_upnp
Dec 1 00:01:05 rc_service: waitting "stop_upnp" via ip-up ...
Dec 1 00:01:07 miniupnpd[757]: HTTP listening on port 46737
Dec 1 00:01:07 miniupnpd[757]: Listening for NAT-PMP/PCP traffic on port 5351
Dec 1 00:01:07 ntp: start NTP update
Mar 16 12:39:16 rc_service: ntp 754:notify_rc restart_upnp
Mar 16 12:39:16 rc_service: ntp 754:notify_rc restart_diskmon
Mar 16 12:39:16 rc_service: waitting "restart_upnp" via ntp ...
Mar 16 12:39:16 miniupnpd[757]: shutting down MiniUPnPd
Mar 16 12:39:17 miniupnpd[772]: HTTP listening on port 58004
Mar 16 12:39:17 miniupnpd[772]: Listening for NAT-PMP/PCP traffic on port 5351
Mar 16 12:39:17 kernel: * Make sure sizeof(struct sw_struct)=160 is consistent
Mar 16 12:39:18 kernel: IDPfw: TrendMicro forward module ver-1.0.26
Mar 16 12:39:18 kernel: IDPfw: Apply module param dev_wan=ppp0
Mar 16 12:39:18 kernel: IDPfw: Apply module param sess_num=30000
Mar 16 12:39:18 kernel: IDPfw: Init chrdev /dev/idpfw with major 191
Mar 16 12:39:18 kernel: IDPfw: IDPfw is ready
Mar 16 12:39:18 kernel: sizeof forward param = 160
Mar 16 12:39:19 disk monitor: be idle
Mar 16 12:39:21 pppd[671]: System time change detected.
Mar 16 12:39:22 rc_service: ip-up 687:notify_rc start_firewall
Mar 16 12:39:22 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!

then a bunch of DHCP messages.. then

Mar 16 14:54:36 rc_service: httpd 589:notify_rc restart_wlcscan
Mar 16 14:54:47 wlcscan: start wlcscan scan
Mar 16 15:01:52 rc_service: httpd 589:notify_rc restart_wireless
Mar 16 15:01:55 kernel: UFFP entry not found
Mar 16 15:01:55 kernel: br0: port 2(eth1) entering forwarding state
Mar 16 15:01:55 kernel: device eth1 left promiscuous mode
Mar 16 15:01:55 kernel: br0: port 2(eth1) entering disabled state
Mar 16 15:01:55 kernel: br0: port 3(wl0.1) entering forwarding state
Mar 16 15:01:55 kernel: device wl0.1 left promiscuous mode
Mar 16 15:01:55 kernel: br0: port 3(wl0.1) entering disabled state
Mar 16 15:01:55 kernel: Hooks already unregistered
Mar 16 15:01:55 snooper: terminated with signal 15
Mar 16 15:01:55 kernel: Hooks already unregistered

Mar 16 15:01:59 kernel: wl_module_init: passivemode set to 0x0
Mar 16 15:01:59 kernel: wl_module_init: txworkq set to 0x1
Mar 16 15:01:59 kernel: eth1: Broadcom BCM4360 802.11 Wireless Controller 6.37.14.86 (r456083)

Mar 16 15:02:05 kernel: br0: received packet on vlan1 with own address as source address
Mar 16 15:02:05 kernel: br0: received packet on vlan1 with own address as source address
Mar 16 15:02:05 kernel: br0: received packet on vlan1 with own address as source address
Mar 16 15:02:07 kernel: br0: received packet on vlan1 with own address as source address
Mar 16 15:02:09 kernel: br0: received packet on vlan1 with own address as source address
Mar 16 15:02:11 kernel: device eth1 entered promiscuous mode
Mar 16 15:02:11 kernel: br0: topology change detected, propagating
Mar 16 15:02:11 kernel: br0: port 2(eth1) entering forwarding state
Mar 16 15:02:11 kernel: br0: port 2(eth1) entering forwarding state
Mar 16 15:02:15 kernel: br0: received packet on vlan1 with own address as source address
Mar 16 15:02:21 kernel: Interface wifi0 doesn't exist
Mar 16 15:02:21 kernel: device wl0.1 entered promiscuous mode
Mar 16 15:02:21 kernel: br0: topology change detected, propagating
Mar 16 15:02:21 kernel: br0: port 3(wl0.1) entering forwarding state
Mar 16 15:02:21 kernel: br0: port 3(wl0.1) entering forwarding state
Mar 16 15:02:21 snooper: started on vlan1/br0

I don't see UPNP restart - so maybe there is my issue.. but not sure why

Thanks

 

[got_milk]

I get the following in my log

Dec 1 00:01:03 qtn: bootcfg.tgz exists
Dec 1 00:01:03 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Dec 1 00:01:04 kernel: nf_conntrack_rtsp v0.6.21 loading
Dec 1 00:01:04 kernel: nf_nat_rtsp v0.6.21 loading
Dec 1 00:01:05 rc_service: ip-up 687:notify_rc start_upnp
Dec 1 00:01:05 rc_service: waitting "stop_upnp" via ip-up ...
Dec 1 00:01:07 miniupnpd[757]: HTTP listening on port 46737
Dec 1 00:01:07 miniupnpd[757]: Listening for NAT-PMP/PCP traffic on port 5351
Dec 1 00:01:07 ntp: start NTP update
Mar 16 12:39:16 rc_service: ntp 754:notify_rc restart_upnp
Mar 16 12:39:16 rc_service: ntp 754:notify_rc restart_diskmon
Mar 16 12:39:16 rc_service: waitting "restart_upnp" via ntp ...
Mar 16 12:39:16 miniupnpd[757]: shutting down MiniUPnPd
Mar 16 12:39:17 miniupnpd[772]: HTTP listening on port 58004
Mar 16 12:39:17 miniupnpd[772]: Listening for NAT-PMP/PCP traffic on port 5351
Mar 16 12:39:17 kernel: * Make sure sizeof(struct sw_struct)=160 is consistent
Mar 16 12:39:18 kernel: IDPfw: TrendMicro forward module ver-1.0.26
Mar 16 12:39:18 kernel: IDPfw: Apply module param dev_wan=ppp0
Mar 16 12:39:18 kernel: IDPfw: Apply module param sess_num=30000
Mar 16 12:39:18 kernel: IDPfw: Init chrdev /dev/idpfw with major 191
Mar 16 12:39:18 kernel: IDPfw: IDPfw is ready
Mar 16 12:39:18 kernel: sizeof forward param = 160
Mar 16 12:39:19 disk monitor: be idle
Mar 16 12:39:21 pppd[671]: System time change detected.
Mar 16 12:39:22 rc_service: ip-up 687:notify_rc start_firewall
Mar 16 12:39:22 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!

then a bunch of DHCP messages.. then

Mar 16 14:54:36 rc_service: httpd 589:notify_rc restart_wlcscan
Mar 16 14:54:47 wlcscan: start wlcscan scan
Mar 16 15:01:52 rc_service: httpd 589:notify_rc restart_wireless
Mar 16 15:01:55 kernel: UFFP entry not found
Mar 16 15:01:55 kernel: br0: port 2(eth1) entering forwarding state
Mar 16 15:01:55 kernel: device eth1 left promiscuous mode
Mar 16 15:01:55 kernel: br0: port 2(eth1) entering disabled state
Mar 16 15:01:55 kernel: br0: port 3(wl0.1) entering forwarding state
Mar 16 15:01:55 kernel: device wl0.1 left promiscuous mode
Mar 16 15:01:55 kernel: br0: port 3(wl0.1) entering disabled state
Mar 16 15:01:55 kernel: Hooks already unregistered
Mar 16 15:01:55 snooper: terminated with signal 15
Mar 16 15:01:55 kernel: Hooks already unregistered

Mar 16 15:01:59 kernel: wl_module_init: passivemode set to 0x0
Mar 16 15:01:59 kernel: wl_module_init: txworkq set to 0x1
Mar 16 15:01:59 kernel: eth1: Broadcom BCM4360 802.11 Wireless Controller 6.37.14.86 (r456083)

Mar 16 15:02:05 kernel: br0: received packet on vlan1 with own address as source address
Mar 16 15:02:05 kernel: br0: received packet on vlan1 with own address as source address
Mar 16 15:02:05 kernel: br0: received packet on vlan1 with own address as source address
Mar 16 15:02:07 kernel: br0: received packet on vlan1 with own address as source address
Mar 16 15:02:09 kernel: br0: received packet on vlan1 with own address as source address
Mar 16 15:02:11 kernel: device eth1 entered promiscuous mode
Mar 16 15:02:11 kernel: br0: topology change detected, propagating
Mar 16 15:02:11 kernel: br0: port 2(eth1) entering forwarding state
Mar 16 15:02:11 kernel: br0: port 2(eth1) entering forwarding state
Mar 16 15:02:15 kernel: br0: received packet on vlan1 with own address as source address
Mar 16 15:02:21 kernel: Interface wifi0 doesn't exist
Mar 16 15:02:21 kernel: device wl0.1 entered promiscuous mode
Mar 16 15:02:21 kernel: br0: topology change detected, propagating
Mar 16 15:02:21 kernel: br0: port 3(wl0.1) entering forwarding state
Mar 16 15:02:21 kernel: br0: port 3(wl0.1) entering forwarding state
Mar 16 15:02:21 snooper: started on vlan1/br0

I don't see UPNP restart - so maybe there is my issue.. but not sure why

Thanks

I see miniupnpd start up normally as per the boot process:

Dec 1 00:01:05 rc_service: ip-up 687:notify_rc start_upnp
Dec 1 00:01:05 rc_service: waitting "stop_upnp" via ip-up ...
Dec 1 00:01:07 miniupnpd[757]: HTTP listening on port 46737
Dec 1 00:01:07 miniupnpd[757]: Listening for NAT-PMP/PCP traffic on port 5351
...
Mar 16 12:39:16 rc_service: ntp 754:notify_rc restart_upnp
...
Mar 16 12:39:16 rc_service: waitting "restart_upnp" via ntp ...
Mar 16 12:39:16 miniupnpd[757]: shutting down MiniUPnPd
Mar 16 12:39:17 miniupnpd[772]: HTTP listening on port 58004
Mar 16 12:39:17 miniupnpd[772]: Listening for NAT-PMP/PCP traffic on port 5351

I don't see it shutting down again.

Did you check if the process was still running as @RMerlin suggested?

 

[Speedluvver]

I see miniupnpd start up normally as per the boot process:



I don't see it shutting down again.

Did you check if the process was still running as @RMerlin suggested?

I saw this... Dec 1 00:01:05 rc_service: waitting "stop_upnp" via ip-up ...

I ran that command - does this mean it is running ?

11760 admin 772 S miniupnpd -f /etc/upnp/config
11777 admin 1384 S grep miniupnp

 

[john9527]

I saw this... Dec 1 00:01:05 rc_service: waitting "stop_upnp" via ip-up ...

I ran that command - does this mean it is running ?

11760 admin 772 S miniupnpd -f /etc/upnp/config
11777 admin 1384 S grep miniupnp

Yes, that means it's running. One easy thing to check if you are running Windows clients, they will usually open up a upnp forward. Got to System Log - Port Forwarding and see if you have any forwards with a chain VUPNP.

 

[Speedluvver]

ok.. so the plot thickens - my NAS and a PC are using upnp - so it is working... PS3 and that test report its not 'available' - I don't think it is the PS3 unless others have the same result ?

 

[dfran1]

Since you are with Charter, make sure that the DHCP frequency is set to "Normal" and not "Aggressive" on the WAN page. Their DHCP server is a bit paranoid when it comes to blacklisting clients requesting too many requests within a few minutes.

Hi and thank you!!
I do have it set to normal and still after every reboot I have to hit apply on the WAN page (first one) or I get no internet access and all internet access wifi or lan just goes to the Asus firmware gui page.
Thanks for any help.

NOTE: so far I have been used dsring settings on my router and I am now getting an all time 3 seconds on my PS4 test WOW amazing... (all I have to say is my test does hold true 1000000000000%)
I will post all setting after a few days of testing, the only thing left so far is this reboot no WAN.

 

[got_milk]

(all I have to say is my test does hold true 1000000000000%)

As myself and others on this forum have said, the PS4 connection test is not a reliable measure or indicator of any particular issue (like I have said before, my PS4 routinely takes 10+ seconds to perform the connection test and I have no issues whatsoever). I'm glad that your issue is looking better but please let's not spread around the misinformation that a PS4 connection test is a measurable indicator of "lag". At worst there'll be others that see these postings, try it for themselves and blame a nonexistent "issue" on the router when there are a number of external influencers on that test, especially the highly inconsistent PlayStation Network.

I think the best course of test is actually playing games and check whether gameplay is smooth or not. Preferably on dedicated servers where poor P2P connections wouldn't play a role in introducing lag.

 

[dfran1]

As myself and others on this forum have said, the PS4 connection test is not a reliable measure or indicator of any particular issue (like I have said before, my PS4 routinely takes 10+ seconds to perform the connection test and I have no issues whatsoever). I'm glad that your issue is looking better but please let's not spread around the misinformation that a PS4 connection test is a measurable indicator of "lag". At worst there'll be others that see these postings, try it for themselves and blame a nonexistent "issue" on the router when there are a number of external influencers on that test, especially the highly inconsistent PlayStation Network.

I think the best course of test is actually playing games and check whether gameplay is smooth or not. Preferably on dedicated servers where poor P2P connections wouldn't play a role in introducing lag.

PLEASE I am not getting into another useless debate on this with you, I tried to avoid your first post, I do not care what you think on my test at all (sorry no criticism meant), BUT it holds true, maybe not to you but certainly to me.
I have tested it enough, over 4-5 seconds and I also have ingame lag.
I am not going to answer you again on this. You are not in my environment, You don't have my ISP, ect.........

Please be more useful, like trying to figure out why I need to hit the apply button on every reboot in the WAN of merlins firmware.

 

[john9527]

like trying to figure out why I need to hit the apply button on every reboot in the WAN of merlins firmware.

When you first come up and don't have access....what is shown in the System Log - Port Forwarding tab? Are there any forwards?

 

[dfran1]

When you first come up and don't have access....what is shown in the System Log - Port Forwarding tab? Are there any forwards?

in the log I get this
WAN Connection: ISP's DHCP did not function properly.
and I am not sure on the port forwarding.
I have to clear log and reboot on anything else.



Mar 16 17:44:41 miniupnpd[836]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Mar 16 17:44:41 miniupnpd[836]: Failed to get IP for interface eth0
Mar 16 17:44:41 miniupnpd[836]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Mar 16 17:44:43 dnsmasq[644]: read /etc/hosts - 5 addresses
Mar 16 17:44:43 dnsmasq[644]: read /etc/hosts.dnsmasq - 4 addresses
Mar 16 17:44:43 dnsmasq-dhcp[644]: read /etc/ethers - 4 addresses
Mar 16 17:44:44 miniupnpd[836]: add_filter_rule() : chain FUPNP not found
Mar 16 17:44:44 miniupnpd[836]: Failed to add NAT-PMP 4500 udp->192.168.1.137:4500 'NAT-PMP 4500 udp'
Mar 16 17:44:44 miniupnpd[836]: add_filter_rule() : chain FUPNP not found
Mar 16 17:44:44 miniupnpd[836]: Failed to add NAT-PMP 4500 udp->192.168.1.137:4500 'NAT-PMP 4500 udp'
Mar 16 17:44:44 rc_service: udhcpc 906:notify_rc start_firewall

 

[got_milk]

Are you rebooting just the router? Or the modem itself? If just the router, try rebooting the modem as well (do the modem first, let it finish booting, then do the router).

 

[john9527]

....what is shown in the System Log - Port Forwarding tab? Are there any forwards?

I'm asking about clicking the tab at the top for Port Forwarding and what is listed there.

 

[dfran1]

Are you rebooting just the router? Or the modem itself? If just the router, try rebooting the modem as well (do the modem first, let it finish booting, then do the router).

I will try tomorrow, I want to see if I make 24 hours with everything else good
THANK YOU!

I'm asking about clicking the tab at the top for Port Forwarding and what is listed there.

right now a lot (but its working so unimportant), but you want to know after I reboot what is listed, will test tomorrow after I reboot, again after 24 hour mark and post back, but got milk may have a good idea, but it still does not do it with official firmware (I think) nor dd-wrt (fact).
THANK YOU!!

 

[Speedluvver]

PLEASE I am not getting into another useless debate on this with you, I tried to avoid your first post, I do not care what you think on my test at all (sorry no criticism meant), BUT it holds true, maybe not to you but certainly to me.
I have tested it enough, over 4-5 seconds and I also have ingame lag.
I am not going to answer you again on this. You are not in my environment, You don't have my ISP, ect.........

Please be more useful, like trying to figure out why I need to hit the apply button on every reboot in the WAN of merlins firmware.

Just to back up dFran1 here - I also get the same - if the connection test takes longer, then I get in game lag - to add to this, of me, upnp is running on the router, yet PS3 says its not available