Menu
What's new
By:
Filters Better Search

[Release] Asuswrt-Merlin 380.61 is now available

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Hello,

I have the following problem with the new firmware (380.61_0) on ASUS RT-AC68U:
My printer (MFP HP LaserJet Pro M127fn) enters standby mode after a while and never returns. If I want to print something no longer receives the order and the only solution is to close and restart printer from on/off button.
I reinstalled the old firmware (380.59_0) and everything returned to normal. Now the printer wakes up from standby and print anytime.
I note that the settings are the same as both router firmware, that we have not made any new setting. I checked it several times. I made hardware reset before and after installing the new firmware.

Any ideas, please?
 
in WAN setting menu

the voices (PPPOE settings)
Enable WAN default= yes
Enable NAT default = yes
enable UPNP default = yes

?

Ugo
 
Asus RT-AC3100 380.61

Does this look normal to you guys.


Aug 27 11:16:34 kernel: net_ratelimit: 830 callbacks suppressed
Aug 27 11:16:34 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:34 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:34 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:34 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:34 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:34 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:34 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:34 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:34 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:34 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:39 kernel: net_ratelimit: 588 callbacks suppressed
Aug 27 11:16:39 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:39 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:39 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:39 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:39 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:39 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:39 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:39 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:39 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:39 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:44 kernel: net_ratelimit: 205 callbacks suppressed
Aug 27 11:16:44 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:44 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:44 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:44 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:44 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:44 kernel: TCP: time wait bucket table overflow

That just goes on and on and on... I cut it way short because you get the point!

Any input would be appreciated.
 
My_dogs_White said:
Asus RT-AC3100 380.61

Does this look normal to you guys.


Aug 27 11:16:34 kernel: net_ratelimit: 830 callbacks suppressed
Aug 27 11:16:34 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:34 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:34 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:34 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:34 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:34 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:34 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:34 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:34 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:34 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:39 kernel: net_ratelimit: 588 callbacks suppressed
Aug 27 11:16:39 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:39 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:39 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:39 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:39 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:39 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:39 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:39 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:39 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:39 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:44 kernel: net_ratelimit: 205 callbacks suppressed
Aug 27 11:16:44 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:44 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:44 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:44 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:44 kernel: TCP: time wait bucket table overflow
Aug 27 11:16:44 kernel: TCP: time wait bucket table overflow

That just goes on and on and on... I cut it way short because you get the point!

Any input would be appreciated.
Click to expand...
http://www.snbforums.com/threads/possible-issue.18244/

cat /proc/sys/net/ipv4/tcp_max_tw_buckets
 
MastaG said:
Thank you merlin, removing the .conf extension did the trick.
My iptv works again :)
Click to expand...

Be aware that you will have to change this back to igmpproxy.conf with 380.62.
 
My_dogs_White said:
I appreciate the link but it doesn't say how to fix the problem. For what it's worth I am not and have not used any torrent sites. As far as I know nothing should be attempting to access my network??
Click to expand...
Merlin's response gave you a possible resolution.

The Network Tools -> Netstat page might give you a hint
Click to expand...

Go there. :rolleyes:

Set method to netstat
Set option to tcp sockets
Resolve name set to the option that you prefer (I use no)
Click on Netstat button

This will show your tcp connections. By paying attention to the "time wait" entries you should be able to identify the source(s) of the tcp connections producing those syslog entries that you are concerned about. :)
 
DaveMishSr said:
Merlin's response gave you a possible resolution.



Go there. :rolleyes:

Set method to netstat
Set option to tcp sockets
Resolve name set to the option that you prefer (I use no)
Click on Netstat button

This will show your tcp connections. By paying attention to the "time wait" entries you should be able to identify the source(s) of the tcp connections producing those syslog entries that you are concerned about. :)
Click to expand...
Thanks for the response. I looked at the Netsat, mine was set to display all sockets. The box was empty and well... I didn't think to hit click on netsat button... doh! I'm not sure what it said because after too many hours messing with it I reverted back to 380.59. I was running that firmware 30 days plus without a single issue. I was rebooting the router because I thought it was due, not because it was acting up. Figured for now, it was the safest bet.

No, it appears it my macbook!

tcp 0 0 192.168.1.1:80 192.168.1.5:51631 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51545 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51556 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51569 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51592 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51534 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51598 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51550 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51549 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51560 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51552 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51563 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51553 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51599 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51578 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51573 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51540 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51617 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51600 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51536 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51547 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51551 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51524 TIME_WAIT
tcp 656 0 192.168.1.1:80 192.168.1.5:51641 ESTABLISHED
tcp 0 0 192.168.1.1:80 192.168.1.5:51595 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51611 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51608 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51586 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51596 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51622 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51585 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51579 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51568 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51580 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51590 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51558 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51605 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51559 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51535 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51630 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51610 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51541 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51618 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51584 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51561 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51621 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51614 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51544 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51575 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51628 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51574 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51555 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51530 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51581 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51523 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51594 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51528 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51539 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51570 TIME_WAIT
tcp 653 0 192.168.1.1:80 192.168.1.5:51643 ESTABLISHED
tcp 0 0 192.168.1.1:80 192.168.1.5:51543 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51571 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51638 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51616 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51529 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51606 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51588 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51562 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51548 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51632 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51531 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51626 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51601 TIME_WAIT
tcp 0 24687 192.168.1.1:80 192.168.1.5:51640 ESTABLISHED
tcp 0 0 192.168.1.1:80 192.168.1.5:51572 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51624 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51625 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51533 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51522 TIME_WAIT
tcp 658 0 192.168.1.1:80 192.168.1.5:51644 ESTABLISHED
tcp 0 0 192.168.1.1:80 192.168.1.5:51623 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51526 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51593 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51591 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51583 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51565 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51609 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51633 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51629 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51612 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51542 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51577 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51619 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51637 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51582 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51538 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51532 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51557 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51587 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51620 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51604 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51607 TIME_WAIT
tcp 654 0 192.168.1.1:80 192.168.1.5:51642 ESTABLISHED
tcp 0 0 192.168.1.1:80 192.168.1.5:51613 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51627 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51634 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51527 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51602 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51537 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51597 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51546 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51525 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51564 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51567 TIME_WAIT
tcp 0 3711 192.168.1.1:80 192.168.1.5:51639 FIN_WAIT1
tcp 0 0 192.168.1.1:80 192.168.1.5:51554 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51603 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51576 TIME_WAIT
tcp 0 0 192.168.1.1:80 192.168.1.5:51566 TIME_WAIT

How do I stop this? Oh no...
 
Last edited:
Nothing wrong with the performance of functioning of the router, so unless a clean log is really a 'necessity ' you don't need to roll back...
 
eddiez said:
Nothing wrong with the performance of functioning of the router, so unless a clean log is really a 'necessity ' you don't need to roll back...
Click to expand...
From what I read, (no expert, obviously) the time wait stuff I posted above is normal.. I was experiencing performance and function issues with the router. Destiny servers (Xbox One) were kicking me giving me the bore error code. I was also being randomly logged out of xbox live and being dropped from youtube with a network error message. The network was dropping for sure. I wasn't able to get things rolled back until later last night so only had limited time to test but so far all is back to normal. 380.59 is the sweet spot for me, so far.

Edit to add: I have two Asus routers on my network each with a different static ip. For what it's worth, the Rt-Ac3100 experienced issues while the Rt-Ac68U seems to be running fine on 380.61.
 
Last edited:
Is anyone else seeing missing data in the traffic monitor data table? Am I missing something or do I need to enable somewhere?

Edit: The statistic tab seems to be putting data together the right way.
 

Attachments

  • Traffic Monitor 1.PNG
    Traffic Monitor 1.PNG
    186.3 KB · Views: 499
  • Traffic Monitor 2.PNG
    Traffic Monitor 2.PNG
    315.6 KB · Views: 802
  • Traffic Monitor 3.PNG
    Traffic Monitor 3.PNG
    168.5 KB · Views: 762
Andrewski said:
Is anyone else seeing missing data in the traffic monitor data table? Am I missing something or do I need to enable somewhere?

Edit: The statistic tab seems to be putting data together the right way.
Click to expand...
The only way I was able to get traffic data in 380.61 was to set it up in 380.57 then upgrade to 380.61. I was able to create a folder on the USB but the data file would not be created and it would not read an old data file.

Sent from my P01M using Tapatalk
 
Don´t now why, since I updated to 380.61 my AC87U appears always in the left side of the finder, under de "Shared" section in Os X. I have no enabled server in the router.

Curiously, scanning the router it appears "Digital Audio Access Protocol (iTunes Music Sharing) service, but I can´t see nothing enabled.
 
Last edited:
You must log in or register to reply here.

Similar threads

RMerlin
Release Asuswrt-Merlin 3006.102.2 is now available for Wifi 7 devices
2 3 4
Replies
62
Views
7K
RMerlin
RMerlin
RMerlin
Release Asuswrt-Merlin 386.14 is now available for AC models
9 10 11
Replies
209
Views
32K
KGB7
K
RMerlin
  • Locked
Beta Asuswrt-Merlin 386.14 beta is now available
2
Replies
35
Views
9K
RMerlin
RMerlin
RMerlin
  • Locked
Release Asuswrt-Merlin 3004.388.8_2 is now available
22 23 24
Replies
469
Views
59K
aitor_mtb
A
RMerlin
Release Asuswrt-Merlin 3006.102.1 is now available for Wifi 7 devices
4 5 6
Replies
106
Views
17K
jksmurf
J
Similar threads
Thread starter Title Forum Replies Date
D Release GNUton [Official Fork] 388.8_2 Release Asuswrt-Merlin 31
D Release GNUTON- 388.7_1 release [Official FORK] Asuswrt-Merlin 4
H Suggestion/Idea: AI scan of release threads/forum Asuswrt-Merlin 5
RMerlin Release Asuswrt-Merlin 3004.388.8_4 is now available Asuswrt-Merlin 72
RMerlin Release Asuswrt-Merlin 3006.102.2 is now available for Wifi 7 devices Asuswrt-Merlin 62
B Unable to establish VPN connection to my PiVPN (ovpn) from my Asus RT-AC86U running Asuswrt-Merlin 386.14 Asuswrt-Merlin 1
F Several Questions Re:Asuswrt-Merlin Feature Implementation Asuswrt-Merlin 2
Yota How to enable port randomization in Asuswrt-Merlin? Asuswrt-Merlin 4
RMerlin Beta Asuswrt-Merlin 3006.102.2 Beta is now available for Wifi 7 devices Asuswrt-Merlin 70
J Does Asuswrt-Merlin support AiMesh over Wifi? Asuswrt-Merlin 4

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Members online

Total: 861 (members: 28, guests: 833)
Top