You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the first tomato release if we run a traceroute or ping via the Tools GUI nothing is displayed until the command launched is fully completed. For ping (if failed) it can take 10sec+ where traceroute in the very worst scenario can take even longer.
I think it would be good if the command output is updated on the page as it happens (e.g. line by line)
Comments (2)
rs232 reporter
I would personally also expand the parameter that can be passed to each ping / traceroute.
E.g. for ping
Modify the default Ping count to from 5 to 3
add these fields:
Swift mode [X]
So on/off appends -A to the command (on by default)
timeout [___] (default 5 to allow DNS resolution)
numeric = which essentially adds -W $N
for traceroute I would add:
IP only [X] (default off)
So on/off. On would appends -n
Bypass routing [X] (default off)
So on/off. On would appends -r
Use ICPM [X] off = udp (default off)
On would append -I
Probes per hop [___] (default 1)
numeric = which essentially adds -q $N
Ms send wait [___] (default 1)
numeric = adds -z $N
2024-02-15
Hogwild
I too could use this enhancement.
2024-12-03
The text was updated successfully, but these errors were encountered:
Ref. https://bitbucket.org/pedro311/freshtomato-arm/issues/217/improvements-for-tools-ping-and-tools
rs232 created an issue 2022-04-08
Since the first tomato release if we run a traceroute or ping via the Tools GUI nothing is displayed until the command launched is fully completed. For ping (if failed) it can take 10sec+ where traceroute in the very worst scenario can take even longer.
I think it would be good if the command output is updated on the page as it happens (e.g. line by line)
Comments (2)
The text was updated successfully, but these errors were encountered: