1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Official Tomato v1.15.1297 released

Discussion in 'Tomato Firmware' started by FRiC, Jan 17, 2008.

  1. FRiC

    FRiC LI Guru Member

    A new version of Tomato firmware has been released.

    Changes are as follows:

    Tomato 1.15.1297
    • Downgraded busybox back to 1.2 for now. The upgrade seems to have caused a few problems with things like DHCP.
    If you're having problems with loosing Internet connection after a while and you're using DHCP, please try this version. Note: This is the same version used prior to Tomato 1.14. It's stable and from a user's viewpoint, you shouldn't see any change in functionality between the two.

    http://www.polarcloud.com/tomato_115


    --------------------------------------------------------------------------------------


    A new version of Tomato firmware has been released.

    Changes are as follows:

    Tomato 1.14.1288
    • Fixed possible cross-site vulnerability in web admin.
    • Fixed saving SSL certificate to nvram.
    • Fixed problem with NAT Loopback thanks to John M. It's now the default setting.
    • New favicon thanks to David V.
    • Microsoft MN-700 ID'd thanks to John F.
    • Network Label can now be entered for OpenDNS.
    • Upgraded Busybox to 1.9.0.
    • Upgrade L7 filters to l7-protocols-2008-01-16.


    --------------------------------------------------------------------------------------

    Download Mirror: http://www.linksysinfo.org/forums/downloads.php?do=file&id=3
     
  2. Toxic

    Toxic Administrator Staff Member

    Thanks for the update!
     
  3. Kiwi8

    Kiwi8 LI Guru Member

    Wowwow! So soon!
     
  4. mstombs

    mstombs Network Guru Member

    Wow - how long have CISCO-LINKSYS known about the cross-site vulnerability - and when are they going to fix it?

    With regards NAT Loopback: When disabled you cannot now access the router using its WAN IP address - unless you have explicitly enabled remote access - which is as I expect it to be. Haven't tested subtle difference between "all" and "forwarded only" - or seen any unexplained side-effects (dhcp, network browsing etc).
     
  5. srouquette

    srouquette Network Guru Member

    Tomato Adventure !!!
     
  6. jockel

    jockel LI Guru Member

    Hi,
    The 1.14 introduction says "Fixed problem with NAT Loopback thanks to John M. It's now the default setting."
    Please what is the default setting for NAT-Loopback? All, Forwarded only, disabled?
     
  7. Kiwi8

    Kiwi8 LI Guru Member

    Can anyone ask Jon to describe how he has fixed the above issue? I had downloaded the source code and searched for the comments that describe the above but to no avail. Hopefully by the explanation, everyone can help to view the code to ensure that the fix has no more vulnerabilities. :)
     
  8. mstombs

    mstombs Network Guru Member

    The default, which you should see in the web gui when you reset to defaults is "Forwarded only".
     
  9. LucasMoon

    LucasMoon Network Guru Member

    I had 1.13 and had issues of having the router to reboot every 20 minutes or more. Had wireless on but only for my son laptop. And still would reboot regardless even he was not at home with his laptop.
    So when back yesterday to 1.11 and no issues we have seen all evening.
    I hope in 1.14 is has stable than 1.11.

    Will test and report.

    Thank you and love your firmware very much.
     
  10. Touchy

    Touchy Network Guru Member

    Great work, just installed it and the WOL-Features works for me again. When I updated from 1.11 to 1.13 WOL didn´t work anymore.
     
  11. BassKozz

    BassKozz Network Guru Member

    Busybox 1.9.0 UNSTABLE

    According to Busybox.net:
    [​IMG]Should I be concerned?[​IMG]
     
  12. chadrew

    chadrew LI Guru Member

    Wow, those updates come so fast. I'm still on 1.11 and it's rock stable (37 days uptime), should I bother flashing this one?
     
  13. Kiwi8

    Kiwi8 LI Guru Member

    The most important part in this issue is the following:
    *Fixed possible cross-site vulnerability in web admin.

    So assuming Jon implemented it correctly, then it's not just a want, but a need to update to this version, unless u do not use UPnP.
     
  14. kzrssk

    kzrssk LI Guru Member

    I've had a weird problem in various versions where the webadmin will stop working, both local and remote. The only fix I've found is rebooting the router from SSH since I couldn't figure out how to restart just httpd. Anyone else get that?

    Other than that, 1.13 has been stable for me on my WHR-HP-G54. Before that I was running 1.11 , 1.10, and 1.07. Only 1.10 gave me problems, but I noticed that 1.11 rolled back some changes.

    Anyway, I'll probably flash this tonight and report feedback :)
     
  15. mstombs

    mstombs Network Guru Member

    You are confusing 2 vulnerabilities, cross-site is not the flash upnp one - although mechanism is similar - a single click on a web page making configuration changes in the router. I do not think Tomato upnp has the same issues as a UK ADSL BT home hub though - I don't think it is possible to change DNS servers or make outgoing diversions, for example.
     
  16. bhlonewolf

    bhlonewolf LI Guru Member

    Honestly why don't you just test? Looking in the code is fine, but "black box" testing is fine too. I gave an example in the original thread on this that you could alter some variables by doing the following:

    http://192.168.1.1/tomato.cgi?https_crt_cn=gotcha

    Log in to your router, change the address in that link if necessary, and give it a try. Go to the admin page and see if the CN name for the router was changed to "gotcha" ...
     
  17. Kiwi8

    Kiwi8 LI Guru Member

    Oh yah, I'm sorry for the confusion.
     
  18. Larix

    Larix LI Guru Member

    I have bricked my router. But why? I don't know. I have make the same procedure as everytime. ;( WRT54G v2.2.

    After debricking with TFTP I get it back.
     
  19. lwf-

    lwf- Network Guru Member

    Does the new favicon work? I don’t get any icon with Firefox or IE.
     
  20. srouquette

    srouquette Network Guru Member

    I have a tomato with firefox, it seems to work.
     
  21. dontbotherme

    dontbotherme Network Guru Member

  22. Trel

    Trel LI Guru Member

    Just curious, do people with the PPPoE issues in 1.13 have it fixed with this one?
     
  23. der_Kief

    der_Kief Super Moderator Staff Member Member

    Not really .... :frown:
     
  24. apelete

    apelete LI Guru Member

    Me neither.
    I cleared my browser cache after update to see the new favicon and don't get anything...
     
  25. mstombs

    mstombs Network Guru Member

    Favicons

    See what you are missing, from both Tomato and this site - from my Firefox toolbar!

    Also shows fine in Exploder
     

    Attached Files:

  26. apelete

    apelete LI Guru Member

    Thanks for the insight, got it working somehow, and identified the problem:

    In the identification tab, I have set router name and hostname to, let say, "example" and domain name to "net".
    If I try to access my router using "example.net" as the adress, I don't get the favicon.
    But if I try with just "example" as the adress in my browser, I get that damn slick new favicon.

    Never had that problem before, where do you think it comes from ?
     
  27. jsmiddleton4

    jsmiddleton4 Network Guru Member

    "I cleared my browser cache after update to see the new favicon and don't get anything..."

    After firwmare update rebooted router and new fat tomato shows fine.
     
  28. lwf-

    lwf- Network Guru Member

    Now I see it as well, but I had to kind of what you said apelete. When I just enter the IP-address like I usually do I get nothing. But then I entered “local” in the Domain Name field and I now get an icon at unknown.local but not at 192.168.1.1. This is a new bug, the icon worked with the IP-address before... or maybe its not a bug but something with my browser.
     
  29. wahur1

    wahur1 LI Guru Member

    Flased it, without any problem....

    I hope its better than 1.13..(1.13 was unstable for me :frown:)

    Even CIFS is working for me this time..:biggrin:
     
  30. StevenG

    StevenG LI Guru Member

    Going to upgrade from 1.11. Any reason to clear NVRAM or anything, or is a reboot sufficient? I'd hate to have to update all my settings...

    Thanks
     
  31. Kiwi8

    Kiwi8 LI Guru Member

    Well, in the faq, it was mentioned that any new Tomato firmware will update the settings to the new version if necessary, so by right there isn't a need to clear the NVRAM. So u may not need to clear NVRAM. But of course, if u do encounter issues that are isolated to the new version, u may try to clear the NVRAM and see if it solves the problem.
     
  32. kzrssk

    kzrssk LI Guru Member

    Doing this has solved problems for me in the past. In fact, I think it was when I upgraded from 1.11 to 1.13. After I cleared the NVRAM, everything was great.
     
  33. protoncek

    protoncek LI Guru Member

    Hi all!
    I just bought WRT54GL a few days ago and loaded tomato firmware 1.13. Yesterday i upgraded to 1.14 and i notice that log is not working. When i reboot only some 20 lines are written and that's it. Nothing more --no MARK line every hour, nothing. Going back to 1.13 all works fine again. I erased NVRAM, still same.
    Anybody else noticed this?
     
  34. DeCex

    DeCex LI Guru Member

    Yea, loggin stop working, worked before.
     
  35. protoncek

    protoncek LI Guru Member

    uiff---i'm glad it's not something in my router...i hope we'll see a new version soon. Thanks for info!
     
  36. Unetwork

    Unetwork LI Guru Member

    I also did a update and all went fine, now the only problem is that the wifi stopped working, also the light on the lynksys WRT54GL V1.1 is not flashing, stays dark.

    I tried every thing but there is no way I can get the wifi working.
    Is this a known bug, problem or am I just having this issue?

    Is there any thing I can try to see where the problem is?
    Thanks, Peter
     
  37. RonWessels

    RonWessels Network Guru Member

    Well, I've got a WRT54GSv2 running Tomato 1.14 and logging is working fine. Did you check the logging configuration to make sure that the settings are correct? Perhaps defaults changed: I explicitly changed the logging settings to get rid of those MARK log entries, so I'm not running default settings.
     
  38. wahur1

    wahur1 LI Guru Member

    How to clear the logs?
     
  39. UltUlt

    UltUlt LI Guru Member

    How'd you do that, ronwessels?
     
  40. mstombs

    mstombs Network Guru Member

    Logging (and wifi) all working here on a wrt54gsv1.1
     
  41. Unetwork

    Unetwork LI Guru Member

    Somebody?
    I returned back to the official software and righ away the wireless started to work again.
    Just a short opinion would be great!
    Peter
     
  42. LLigetfa

    LLigetfa LI Guru Member

    It's right on the Logs page.
     

    Attached Files:

  43. wahur1

    wahur1 LI Guru Member

    i think no one realized my post :(
     
  44. LLigetfa

    LLigetfa LI Guru Member

    Reboot the router.
     
  45. Toxic

    Toxic Administrator Staff Member

  46. valerima

    valerima LI Guru Member

    firmware 14

    I do have wrt54 gl 1.1. To v 14 upgraded Yesterday from version 11. Cleared NVRAM, also reseted settings at router. After that restored configuration which was saved before.
    wifi is working OK- both my kids have DELL laptops . Log is seen- what I did chose- I have chosen 25 lines- everything is working.
    Yesterday I have seen some uneasiness in traffic...But it is rather local problems, however I rebooter the router- now works about 19 hours with no evidently noticed problem.
     
  47. protoncek

    protoncek LI Guru Member

    i guess that clearing NVRAM will also clear the log---i did that and it was the same - MARK didn't appear, and also when i clicked for refreshing WAN connection it was refreshed, but nothing was written into log---all this is fine with v1.13. I also have WRT54GL V1.1
     
  48. cpgbg

    cpgbg LI Guru Member

    Problems with Tomato 1.14

    I have Buffalo WHR-HP-G54 and yesterday I have upgraded to Tomato 1.14.
    When I inspected the syslog, I found that there are no MARK lines at all. Also no lines about DHCP renew.
    With the previous version of the firmware the IP address was renewed in the middle of the lease time. Now it simply expires and I see these lines in the syslog every time the lease expires:

    Jan 21 10:20:59 buffalo daemon.info dnsmasq[979]: exiting on receipt of SIGTERM
    Jan 21 10:21:00 buffalo daemon.info dnsmasq[1136]: started, version 2.40 cachesize 150
    Jan 21 10:21:00 buffalo daemon.info dnsmasq[1136]: compile time options: no-IPv6 GNU-getopt no-RTC no-ISC-leasefile no-DBus no-I18N no-TFTP
    Jan 21 10:21:00 buffalo daemon.info dnsmasq[1136]: DHCP, IP range 192.168.1.100 -- 192.168.1.149, lease time 1d
    Jan 21 10:21:00 buffalo daemon.info dnsmasq[1136]: reading /etc/resolv.dnsmasq
    Jan 21 10:21:00 buffalo daemon.info dnsmasq[1136]: using nameserver 217.9.224.3#53
    Jan 21 10:21:00 buffalo daemon.info dnsmasq[1136]: using nameserver 217.9.224.2#53
    Jan 21 10:21:00 buffalo daemon.info dnsmasq[1136]: read /etc/hosts - 0 addresses
    Jan 21 10:21:00 buffalo daemon.info dnsmasq[1136]: read /etc/hosts.dnsmasq - 3 addresses

    I guess I have to rollback to v1.13, I hope that they will release v1.15 that fixes these issues soon.
     
  49. Unetwork

    Unetwork LI Guru Member

    Ok dear members just asked a simply, I guess, question about my wifi not working with this version, 1.13 was working for me.
    Now I tried everything to fix this problem but the light for the wireless stayed off and I could not see the wifi service on my laptop or Nokia N95.
    But no one seems to be interested to give me a reply on this, might be because of my newbie status here?
    Any-way I wish you all lots of luck, its still a wonderfull forum, just wished for a little help.
    rgds, Peter
     
  50. Kiwi8

    Kiwi8 LI Guru Member

    No, it's not that u are of newbie status, but perhaps there might be too many people asking this sort of question.

    Anyway, as I have always told others here, try to do a thorough NVRAM reset through the Tomato web interface, see if it helps revolving the problem. Most of the time it helps.
     
  51. valerima

    valerima LI Guru Member

    ....wifi is working OK- both my kids have DELL laptops....

    No problems with wi-fi at all. I just would like to suggest clean NVRAM and reset a router.
     
  52. Low-WRT

    Low-WRT LI Guru Member

    Why not stick with 1.13?
    Just b/c there's an update, it doesn't mean you have to update:wink:
     
  53. LLigetfa

    LLigetfa LI Guru Member

    If you want hand holding, you may be better off starting your own thread.
     
  54. Unetwork

    Unetwork LI Guru Member

    Thanks Kiwi8, and yep I did that but could not get te wireless working. As I posted before I am back to the original firmware again for the Linksys WRT54GL V1.1 and the wireless is working again.
    Do you happen to know if I am the only one with this problem?
     
  55. Kiwi8

    Kiwi8 LI Guru Member

    I forgot to mention, other than doing the thorough NVRAM reset, do try to power cycle the router too (ie turn off router, then turn it back on).
     
  56. LLigetfa

    LLigetfa LI Guru Member

    I don't trust the NVRAM reset in the GUI, preferring always to do the 30 second reset button hold.
     
  57. Unetwork

    Unetwork LI Guru Member

    Ok I can try to tell you what I did after the flash:
    Did the 30 seconds or more reset. closed firefox, and all PC's here.
    But no result.
     
  58. kzrssk

    kzrssk LI Guru Member

    No one else getting this at all?
     
  59. LLigetfa

    LLigetfa LI Guru Member

    If I had to guess (and I must), I'd say you're overloading the router with torrents at the time.
     
  60. szfong

    szfong Network Guru Member

    On one of my routers, a WRT54G v2.0, Tomato v1.14's Site Survey seems to have stopped working. On another router, a WHR-HP-G54, Site Survey also does not show any APs. They are both in AP+WDS mode. However, Tomato v1.13 & v1.11 shows about a dozen APs. This release seems to be a bit less stable than before. Is anyone else seeing this behavior?
     
  61. Int15

    Int15 Network Guru Member

    Hi,

    I seem to have the same issue as szfong. All of my 3 tomato routers (all WRTs) are showing empty lists in Wireless Survey. I know for a fact that there are other WiFi networks around (at least 6, depending on the router).

    Thanks,

    -Int15
     
  62. kzrssk

    kzrssk LI Guru Member

    I don't use BitTorrent, 'cept like once a month. Besides, it's set for 2048 connections, and my uTorrent's max global connections is set to 90.
     
  63. JensG

    JensG Network Guru Member

    What happens if you click "Refresh" when you are in Wireless Survey?

    On my router it doesn't run the survey like it used to when entering the Wireless Survey, but if I click "Refresh" it works OK.
     
  64. apelete

    apelete LI Guru Member

    Same here...
     
  65. JensG

    JensG Network Guru Member

    And I think that's the way it should be.
     
  66. protoncek

    protoncek LI Guru Member

    i also get blank survey - but if i hit refresh, all wireless around are found. This was the same with 1.13 firmware also. For now, only log is acting funny, and MARK entries are gone...
     
  67. AeN0

    AeN0 Network Guru Member

    Same problem with syslog. No MARK entries. But I guess It does not count as I'm using my own customized Tomato (based on 1.14) ...
     
  68. Int15

    Int15 Network Guru Member

    Humm, interesting. Refreshing brings the list up.Up until 1.13 the survey list was called right by clicking in the link in the NavBar.

    Also, my auto-refresh doesn't seem to kick in.

    -Int15
     
  69. cpgbg

    cpgbg LI Guru Member

    I think that the main problem is not the syslog itself, but some timers are not working. Not only MARK entries are missing, but the IP address is not renewed before the lease expires. After that the connection is reset and some services are restarted. During this time all packets are lost. The Connection Uptime is always reset to 00:00:00 when the lease expires. My ISP gives me lease time of 2-3 hours, so this is not OK for me.
    I have rolled back to v1.13 and everything is back to normal. I get -- MARK -- every hour and the lease is renewed in the middle of the lease time, so the connection stays up.
     
  70. szfong

    szfong Network Guru Member

    You may be right, when the Lease gets renewed, my uptime sometimes is set to 00:00:00. No wonder I have such lousy uptimes. I've also rolled back to v1.13.

    I've also tried refreshing the Site Survey on a WRT54G v2 I use for testing, it still shows no APs in the vicinity. v1.13 shows about a dozen.

    I'm sure we'll get a brand new release which fixes these issues VERY shortly. :)
     
  71. pharma

    pharma Network Guru Member

    No problem with Site Survey and 1.14 here! In a rural neighborhood it shows about 4 AP's. Clicking "Refresh" just added another (5 AP's). I think there might be a problem with "Auto Refresh" when you leave the page and then re-open the Site Survey page, however setting the page to Self-Refresh after a certain number of seconds does seem to work.

    Pharma
     
  72. mstombs

    mstombs Network Guru Member

    Problems With Tomato Version 1.14

    Just tested:

    Wireless Survey:- I think this is a new feature due to cross site vulnerability fix, running survey can disrupt clients, so only starts when you hit "refresh" after going to the page, won't auto start just by navigating to the page. Not a big issue for me!

    Logging:- Confirm "mark" doesn't work, also wan dhcp no longer logs, in fact now I have changed log configuration nothing new is being added at all

    udhcpc:- Confirm doesn't renew after half lease time, not helped by poor visibility in log, my cable lease time is 7 days so this would hit me eventually...

    Conclusion: Back to 1.13!

    Note: syslogd and udhcpc are both from the new busybox 1.9.0, didn't someone mention it was stilled flagged as "UNSTABLE"

    Edit: udhcpc and log marks works fine in 1.13 without changing setup. The option to disable dhcp logs is new in 1.14. Does a full hard reset clear these faults in 1.14 I didn't try?
     
  73. Unetwork

    Unetwork LI Guru Member

    I got the wifi working now only the light is not burning like normal it has 2 colours, yellow and white.
    I gues there are too many issues yet to be resolved in 1.14.

    And LLigetfa Reformed Router I am not here to ask for hand holding, just asked and made a ontopic comment on this topic.
    If you call yourself reformed you might like to join me a little? ;)
     
  74. BassKozz

    BassKozz Network Guru Member

    That would be me: Busybox 1.9.0 UNSTABLE ;)
     
  75. Macskeeball

    Macskeeball LI Guru Member

    That person's username is Lligetfa. The "Reformed Router" is not part of the username and is not chosen by the user. Rather, it is automatically assigned by this forum based on the number of posts the user has made, and changes as the user's postcount reaches certain milestones. Notice how the usernames and the titles are styled differently.

    So, for me, my username is Macskeeball and the title that is currently assigned to me by this forum based on my current post count is "Serious server."

    Does that make a little more sense now?
     
  76. LLigetfa

    LLigetfa LI Guru Member

    Reformed or not, I was just offering advice. Take it or leave it, it is afterall a public forum.

    This particular thread is like a crouded chat room, and as such does not lend itself to in-depth segways of particular issues. For one, the board does not flag to whom a reply is intended so as topics digress, they are difficult to follow. Also, a lot of posters may be hesitant to go into details in a crowded chat room.

    By starting your own thread, you create a venue for detailed on-topic discussion with less chance of the topic getting sidetracked.

    If you are offended by this, it is your problem.
     
  77. kevanj

    kevanj LI Guru Member

    Assuming a responder uses the Reply option within a post, and not the general topic reply button at the top of the topic page, responses made to a specific post can be seen in threaded mode by selecting that mode from the "Display Modes" dropdown at the top of each topic page....
     
  78. szfong

    szfong Network Guru Member

    Tomato v1.15 was just recently released, I hope it'll solve all the problems I was having with it. On a side note, wondering when Tomato will work on the WHR-G125 :)
     
  79. LLigetfa

    LLigetfa LI Guru Member

    Ah, two big assumptions that seldom come to fruition, but thanks for the clarification. I should not have placed the blame on the board.

    Anyway, looks like it's time to check out 1.15 now.
     
  80. DeCex

    DeCex LI Guru Member

    Any idea why Jon downgrade the Busybox to 1.2 version? Was that very stable version?

    - Ok, i shot him an email and got replied that BB 1.2 was used in the Tomato 1.13 version, i guess is cool then. You ROCK Jon
     
  81. szfong

    szfong Network Guru Member

    I though BusyBox v1.8.2 was the latest stable release, rather than v1.2.2. Anyhow, this version appears a bit more stable, so far, than the v1.14 release. Although, I still get "random reboots" on a couple routers deployed as hotspots.
     
  82. wahur1

    wahur1 LI Guru Member

    For me ver 1.14 is running smooth as silk....:biggrin:
     
  83. der_Kief

    der_Kief Super Moderator Staff Member Member

    Hi,

    for me there is no difference between 1.14 and 1.15. They both are stable on my GL1.1. But neither 1.14 or 1.15 solved my problems with PPPoE disconnects

    der_Kief
     
  84. MiseryQ

    MiseryQ Network Guru Member

    hmmm... I didn't know I had a "problem" until I read the new released and compared my uptime to my connection time.

    Thanks.
     
  85. cpgbg

    cpgbg LI Guru Member

    Running 1.15 since yesterday and everything seems to be fine. The problems with syslog and DHCP are gone.
     
  86. lwf-

    lwf- Network Guru Member

    I could see in my logs that I had lost connection three times today for the first time, so this was great timing. :)
     
  87. y2kboy23

    y2kboy23 Network Guru Member

    There is a problem with the Ping tool. When you use it, it won't show the individual packets, it just shows the summary at the end.
     
  88. damko

    damko Network Guru Member

    Hi, Tomato rocks :)

    I'm using 1.13 on GL 1.0 and FYI:
    Uptime 51 days, 01:16:17
    Connection Uptime 51 days, 01:17:58 (using PPPoE on 4M/512)
     
  89. LLigetfa

    LLigetfa LI Guru Member

    I thought this thread was about 1.14/1.15?
    I too would have uptime bragging rights if I didn't upgrade to 1.15 and didn't have powqer outages.

    Anyway 1.15 is as stable so far as 1.13 was.
     
  90. sded

    sded Network Guru Member

    1.15 did fix the DHCP problem in 1.14

    Had problems with losing the internet link between the WRT54Gv4 and NIC with 1.14. Modem in synch, IP assigned at router via DHCP, just not passed to NIC. Had to reboot the router to get it back. Problem appears solved in 1.15, at least in a couple of days observations.
     
  91. eRd12

    eRd12 LI Guru Member

    I have a bug I think... When I'm pinging any ip there is only this information without the information about every packet :cool:

    [​IMG]
     
  92. madsul

    madsul LI Guru Member

    Hi My 1.14 is as solid as a rock so far 12 days and counting
     
  93. Elbart

    Elbart LI Guru Member

    Why aren't you pinging on your normal pc?
     
  94. eRd12

    eRd12 LI Guru Member

    You asking me for that but why? It is normal I think that if I have this option in tomato so I want to use it. Besides if the provider is changing ttl for example it is fast way to check it, beacause you will check it on tomato and packets will back (with ttl=0) but on your computer connected to it the packet will die and then you know that ttl adjust should be set to +1. This is only example of using ping it tomato. In previous versions it was working well. Check on 1.15.
     
  95. LLigetfa

    LLigetfa LI Guru Member

    Ping in 1.15 for me returns only the summary info but I haven't tested in previous versions to compare.
     
  96. LLigetfa

    LLigetfa LI Guru Member

  97. mstombs

    mstombs Network Guru Member

    re ping - I'm sure its the same as ever for me on wrt54gs v1.1!

    Code:
    Tomato v1.15.1297
    
    BusyBox v1.2.2 (2008.01.28-00:18+0000) Built-in shell (ash)
    Enter 'help' for a list of built-in commands.
    
    # ping
    BusyBox v1.2.2 (2008.01.28-00:18+0000) multi-call binary
    
    Usage: ping [OPTION]... host
    
    Send ICMP ECHO_REQUEST packets to network hosts.
    
    Options:
            -c COUNT        Send only COUNT pings
            -s SIZE         Send SIZE data bytes in packets (default=56)
            -q              Quiet mode, only displays output at start
                            and when finished
    
    # ping -c 4 google.com
    PING google.com (64.233.187.99): 56 data bytes
    64 bytes from 64.233.187.99: icmp_seq=0 ttl=241 time=119.4 ms
    64 bytes from 64.233.187.99: icmp_seq=1 ttl=241 time=140.6 ms
    64 bytes from 64.233.187.99: icmp_seq=2 ttl=241 time=122.0 ms
    64 bytes from 64.233.187.99: icmp_seq=3 ttl=241 time=151.6 ms
    
    --- google.com ping statistics ---
    4 packets transmitted, 4 packets received, 0% packet loss
    round-trip min/avg/max = 119.4/133.4/151.6 ms
    but I never use the web gui tool...
     
  98. LLigetfa

    LLigetfa LI Guru Member

    I guess we are comparing apples to tomatoes? ;)
     
  99. LLigetfa

    LLigetfa LI Guru Member

    Further on this ping issue, I am finding that if pining by DNS name and it fails to resolve, there is not even a summary nor any error message.
     
  100. RonWessels

    RonWessels Network Guru Member

    I can confirm that the web "ping" interface changed behaviour between 1.14 and 1.15. With 1.15, only the summary information is displayed. My first thought was that the ping command changed the individual packet status from stdout to stderr and only stdout is being redirected. However, the command line behaviour of ping doesn't back that up. Further, since the web interface output of the ping command is obviously being processed in some way (the output text is different), there's something else going on.
     

Share This Page