C:\Users\Hexo>ping 192.168.178.7 -n 20
Ping wird ausgeführt für 192.168.178.7 mit 32 Bytes Daten:
Antwort von 192.168.178.7: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit=4ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit<1ms TTL=64
C:\Users\Hexo>ping www.google.com -n 20
Ping wird ausgeführt für www.google.com [173.194.35.145] mit 32 Bytes Daten:
Antwort von 173.194.35.145: Bytes=32 Zeit=139ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=127ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Ping-Statistik für 173.194.35.145:
Pakete: Gesendet = 20, Empfangen = 20, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 50ms, Maximum = 139ms, Mittelwert = 58ms
C:\Users\Hexo>ping www.google.com -n 40
Ping wird ausgeführt für www.google.com [173.194.35.145] mit 32 Bytes Daten:
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=183ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=52ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=52ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=53ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=52ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=56ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=53ms TTL=57
Ping-Statistik für 173.194.35.145:
Pakete: Gesendet = 40, Empfangen = 40, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 50ms, Maximum = 183ms, Mittelwert = 54ms
Hey,
it´s seems, that i got also these dropbs in the wlan
The first ping was to my NAS System. Normaly i got a ping about <1 and since this fw i got some higher pings.
Also if i ping other server, you can see some very high ping.
I was using the latest beta without any problems.
After i made the update to the final version, i realise these drops.
I think the wlan isn´t running as good as it was as i use the beta.
I tried a hard rest but i still got the lags.
Can i switch without any problem back to the beta?
Edit: Some got a link to the beta? The links in the first post of this topic are dead
Greetz
Thanks but i tried Padavan´s Custom Firmware and everything is running perfekt!
I recently installed v. 3.0.0.4.260 but it hasn't been a good experience so far.
The new interface hangs any time I try navigating to a different section other than the initial screen.
It also hangs when trying to even log into the admin interface.
Has anyone else experienced this? And if so, how did you resolve it?
Thank you for any help you can provide.
Mine did this...press and hold the reset button on the router, once the router has restarted it should all work perfectly...atleast mine has, loving the firmware so far even better now the interface isnt buggy after the reset.
I recently installed v. 3.0.0.4.260 but it hasn't been a good experience so far.
The new interface hangs any time I try navigating to a different section other than the initial screen.
It also hangs when trying to even log into the admin interface.
Has anyone else experienced this? And if so, how did you resolve it?
Thank you for any help you can provide.
I have major wifi issues with the latest firmware (260)
I am looking to revert back to 206 but the links in the OP are dead.
Anyone can upload the Beta Version 3.0.0.4_206 to the forum and/or provide a working link?
Thanks so much!
Mickey
You are lucky I kept a back up of this , this has been the most stable firmware for me. I kept it in case I need it in the future, but so far I have been using padavan's firmware and my router doesn't slow down at all, its amazing fast. but I rather have stock firmware I feel safer using it.
https://www.dropbox.com/s/gb858i7r6kmd4nn/RT-N56U_3.0.0.4_206.trx
Thanks so much! You saved me. I am also using padavan's firmware but it has no QOS. I have VOIP so will see hoe pavadan is working...
Thanks again!
I tried to revert back to https://www.dropbox.com/s/gb858i7r6k....0.0.4_206.trx
But the router still shows 3.0.0.4.260. How do you guy downgrade? I am having wifi problem with 260 as well.
THANKs
use the rescue utility
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!