Diagnostics ping increasing number
-
how hard would it be to tweek the diagnostics ping so it would go higher than 10 say 50 or 100 ?
-
Not hard but it's not a good idea. The page's return can take up to 1 second per attempt. 50 could take nearly 1 minute for the page to return. Anything beyond 10 isn't really reasonable for that type of page as they currently stand, there are a limited number of PHP processes, and long-running things like that can completely prevent the web interface from functioning. SSH is the answer for long-running commands.
-
i understand the time to return also the ssh is a bit of a pia with multiwan
not that it overly matters was just a thought, none of the isps trust anything from router although the router has always proved true, last problem was blamed on owning more than 1 apple product
-
ssh is a pia with multiwan? how is that ?
-
i understand the time to return also the ssh is a bit of a pia with multiwan
not that it overly matters was just a thought, none of the isps trust anything from router although the router has always proved true, last problem was blamed on owning more than 1 apple productIf you need more ping for your buck then perhaps you could use Diagnostics -> Command Prompt along with a good read of https://www.freebsd.org/cgi/man.cgi?query=ping&apropos=0&sektion=8&manpath=FreeBSD+10.2-stable&arch=default&format=html
Cheers
JonPS Note the -g -G -h options. Great for MTU testing. It would be nice if the Linux ping learned how to do ping sweeps sigh.
-
ssh is a pia with multiwan? how is that ?
I think he means the ping command is, as you need the '-S $source_IP'.
@Jon:
If you need more ping for your buck then perhaps you could use Diagnostics -> Command Prompt along with a good read of https://www.freebsd.org/cgi/man.cgi?query=ping&apropos=0&sektion=8&manpath=FreeBSD+10.2-stable&arch=default&format=html
Yeah but be really careful to not run a never-ending ping (or any other command) there, you'll have to get in SSH or console and kill it.