Open GoogleCodeExporter opened 9 years ago
Issue 558 could perhaps be related, but my experience is with streaming rather
than hig cpu load. Other than that the symptom seem to be the same.
Original comment by bertilma...@gmail.com
on 5 Nov 2012 at 9:17
Same issue with audio streaming.
Issue isn't observed on original firmware.
Original comment by semik...@gmail.com
on 5 Nov 2012 at 4:59
Hi there,
exact same issue here: streaming video from a machine physically connected to
the router to a Mac mini connected via 5 GHz WiFi. After approx. 30 minutes,
the streaming stops (pinging the router gives "Host down", no packets come
back) but the network still seems to be connected. No log entry and it happens
every time ... CPU load is negligible.
Would be nice if this could be fixed. Great work though!
Cheers
Original comment by snake.pl...@gmail.com
on 15 Nov 2012 at 8:47
Reproduced with 3.0.3.26
Original comment by felicias...@gmail.com
on 20 Nov 2012 at 3:05
still no fix, same issue in 3.0.3.27
Original comment by bertilma...@gmail.com
on 29 Nov 2012 at 9:53
Issue 581 has been merged into this issue.
Original comment by d...@soulblader.com
on 4 Dec 2012 at 3:07
Merging Defect #592 with his one:
------------------------------------------
What steps will reproduce the problem?
1. Media files on physically connected server
2. Stream a media file over 5 GHz Wi-Fi to Mac mini client
3.
What is the expected output? What do you see instead?
Constant and reliable video stream. Instead, the stream stops after 30 to 60
minutes; the network still seems to be connected, however, no data can be
transmitted. I get is from a constant pinging in the background when the
problem occurs:
[rock-solid connection for almost an hour, then ...]
64 bytes from 10.0.0.1: icmp_seq=4524 ttl=64 time=0.850 ms
64 bytes from 10.0.0.1: icmp_seq=4525 ttl=64 time=1.309 ms
64 bytes from 10.0.0.1: icmp_seq=4526 ttl=64 time=1.484 ms
64 bytes from 10.0.0.1: icmp_seq=4527 ttl=64 time=1.137 ms
Request timeout for icmp_seq 4528
Request timeout for icmp_seq 4529
Request timeout for icmp_seq 4530
Request timeout for icmp_seq 4531
Request timeout for icmp_seq 4532
Request timeout for icmp_seq 4533
Request timeout for icmp_seq 4534
Request timeout for icmp_seq 4535
Request timeout for icmp_seq 4536
Request timeout for icmp_seq 4537
Request timeout for icmp_seq 4538
Request timeout for icmp_seq 4539
Request timeout for icmp_seq 4540
Request timeout for icmp_seq 4541
Request timeout for icmp_seq 4542
Request timeout for icmp_seq 4543
Request timeout for icmp_seq 4544
Request timeout for icmp_seq 4545
Request timeout for icmp_seq 4546
Request timeout for icmp_seq 4547
Request timeout for icmp_seq 4548
Request timeout for icmp_seq 4549
ping: sendto: No route to host
Request timeout for icmp_seq 4550
ping: sendto: Host is down
Request timeout for icmp_seq 4551
ping: sendto: Host is down
Request timeout for icmp_seq 4552
ping: sendto: Host is down
Request timeout for icmp_seq 4553
[at this point, even a network shutdown on the client side didn't help, had to
disable and re-enable the 5 GHz band on the router]
What version of the product are you using? On what operating system?
v3.0.3.0-026
Please describe the problem as detailed as it's possible.
If you have connection problem, then syslog file is required. (please do
attach it as a file)
Note that if there will be a poor problem description the issue status will
be changed to 'Invalid'!
Are there any logs I could provide? Connected to the router via ssh but
couldn't find anything but the syslog, which doesn't show anything useful in
this case ...
Original comment by snake.pl...@gmail.com
on 5 Dec 2012 at 6:59
i have similar this problem on 3.0.3.1-027 when streaming from usb harddrive.
however, disable and re-enable the wifi on client side will fix it.
Original comment by lapcc...@gmail.com
on 11 Dec 2012 at 9:21
Fix it? Don't think so. Its a workaround at best. The problem reappears so its
hardly an acceptable solution.
Original comment by bertilma...@gmail.com
on 11 Dec 2012 at 10:17
i just notice if streaming is from usb harddrive, no access to router after a
curtain time, ping to router ip will timeout but internet access remain fine.
turn off and on wifi and reconnect 5ghz will resume the service.
if streaming (or continus file access) from the internet, 5g will gone and i
need to connect via 2.4g to reset 5g (click apply on 5g config page) in order
to resume 5g wifi service.
Original comment by lapcc...@gmail.com
on 12 Dec 2012 at 6:28
where can i download previous version of this firmware? i only have problem
after update to 3.0.x
Original comment by lapcc...@gmail.com
on 12 Dec 2012 at 6:31
I just downgraded to v1.1.2.6 (old 2.6 kernel).
Had my first streaming crash on the 5 GHz WiFi after 5 minutes!
VERY disappointing ...
Original comment by markus.b...@googlemail.com
on 5 Jan 2013 at 6:47
Sad to hear that. I was considering downgrading as well...this MUST be high
priority. Our routers are seriously crippled. Ok it´s custom fw but
still...going back to stock fw would be SO disappointing.
Original comment by bertilma...@gmail.com
on 6 Jan 2013 at 8:36
Yes, but nobody seems to care. I almost regret donating money for this (apart
from this issue) very nice project. But there is no point for me using firmware
that doesn't allow me to use the 5 GHz WiFi for streaming (and that's basically
why I bought the router in the first place!) ...
Original comment by snake.pl...@gmail.com
on 6 Jan 2013 at 4:48
Installed stock fw again and 5Ghz i rock solid. Shame really but i needed a W I
R E L E S S router. This group needs to get it´s priorities right....
Original comment by bertilma...@gmail.com
on 14 Jan 2013 at 8:47
With stock firmware I remember having had frequent packing loss and connection
drops on the 2.4 GHZ WiFi. It's like having to choose between the devil and the
deep blue sea ...
Original comment by snake.pl...@gmail.com
on 14 Jan 2013 at 10:28
Back to stock fw, too. Still having issues with the 2.4 GHz there, but at least
I can use both bands ... Very sad!
Original comment by snake.pl...@gmail.com
on 16 Jan 2013 at 8:29
The 5GHz network remains unusable. After some minutes working it simply stops.
Original comment by egcarr...@gmail.com
on 7 Feb 2013 at 10:59
5g randomly disappear/crash on RT-N65U_3.0.3.3-041_full, just normal web
surfing not even streaming.
Original comment by lapcc...@gmail.com
on 14 Feb 2013 at 8:25
Switch to official firmware from ASUS, problem gone. 5GHz wi-fi now works
stable. I think that stable wireless working MOST important stuff than other
toys.
Original comment by tim.slep...@gmail.com
on 19 Feb 2013 at 2:21
i am running -040 on rt-n56u. does the same thing. drops 5ghz under high cpu
load. same thing on -042, if not worse. hard to switch back to asuswrt now that
padavan's outperform all other things. 1.1.2.6-018 is the last one to have
solid 5ghz.
Original comment by Wanttot...@gmail.com
on 28 Feb 2013 at 11:29
Not sure if this helps but the notes I've captured on this issue on
3.0.3.3-042_full
- nothing relevant is captured in the syslogs
- The issue occurs at different times for different clients. e.g. One client
experiences the 5ghz issue while others continue to function normally
Original comment by pemon...@gmail.com
on 28 Feb 2013 at 1:17
Check the first line of the changes of the new release:
Changes to firmware ver. 3.0.3.3-042:
----------------------------------------------------------
- Fixed SoC hangup on 5GHz Wireless interface down during data transfer.
- Fixed WAN-LAN spoofing issue on change WAN bridge mode or VLAN isolation.
- Fixed VLAN filter for partial untagged traffic.
- Fixed broken httpd login state after LAN IP address reconfig.
- Fixed 48 hours bug in Main_TrafficMonitor_last24.asp.
- Updated kernel-3.0.x to 3.0.68 from www.kernel.org.
- Updated openssl to v1.0.1e (vulnerability CVE-2013-0166).
- Updated miniupnpd to v1.8.20130207.
- Updated transmission to v2.77.
- Updated xUPnPd to rev382.
- Updated xl2tpd daemon from upstream.
- Increased max allowed Wireless clients up to 64 for each AP.
- Rolled back 5GHz Wireless driver to v2.4.3.6 (with backports and fixes).
- Added user-defined vid:pid slot to option.ko for support any UMTS and EVDO
modems.
- Added GreenAP feature for each AP. GreenAP goto 1T1R+20MHz mode if there is
no 11n clients.
- Added workaround for partial fix PPE UDP bug (drop UDP packets w/o checksum).
- Added NTP synchronization period control to WebGUI.
- Added DDNS update period control to WebGUI.
- Added PPPoE idle timeout feature.
- Added Ethernet ports info and Connections tracking info to WebGUI.
- Added force NVRAM clear on ASUS-WRT content detected (many params is
incompatible).
- Removed bogus Wireless bandwidth mode 40MHz Only (not used by Ralink/MTK WiFi
drivers).
- Removed port trigger dead feature.
Original comment by egcarr...@gmail.com
on 12 Mar 2013 at 3:54
Thanks egcarrano but I'm already running 3.0.3.3-042, the problem, or a very
similar is still occurring.
Additional to what I wrote previously I rolled back to the latest official Asus
firmware and have noted the exact same issue as when I was running padavan's
firmware. Hope that piece of information helps.
Original comment by pemon...@gmail.com
on 12 Mar 2013 at 7:02
Sorry... I was not clear... these are the changes of the new firmware
(3.0.3.3-045) when compared to the -042. This change has been introduced in the
new version, that was launched today!
Original comment by egcarr...@gmail.com
on 12 Mar 2013 at 7:37
Cheers, I'll get testing on this new release now
Original comment by pemon...@gmail.com
on 12 Mar 2013 at 9:29
I am using only the 5GHz network in the last two days and I am not having
problems.
Original comment by egcarr...@gmail.com
on 15 Mar 2013 at 3:36
unfortunately the problem is back.
Original comment by egcarr...@gmail.com
on 15 Mar 2013 at 9:43
The 5GHz network remains unusable. I am going back to the original firmware.
The new ASUSWRT is considerably better than the older versions. I dont know if
you have noticed that, but it has optware built-in. You just have to enable
telnet and you can install softwares using ipkg.
Original comment by egcarr...@gmail.com
on 18 Mar 2013 at 11:21
Original issue reported on code.google.com by
bertilma...@gmail.com
on 4 Nov 2012 at 5:30