Traffic Graph for LAN and WAN showing outside IP Addresses
-
i tried on another machine same latest snap and that one shows so how can one machine show the ips and the other not, what could be wrong?
-
It works in the newest updated. But it isn't as simple to use as before.
I wish it would default to the previous configuration, and if you want to see external IPs then select that.
Listing a bzillion external IPs/hostnames coming and going isn't that visually helpful as it changes so fast.
-
I believe ermal is going to work on the In/Out sides of the display, so that the numbers for both local and remote IPs will match the In/Out convention of the graph.
The default for the table could easily be changed to "Filter: Local" - maybe people could give votes here for what they would prefer as the defaults? or a "Save" button could be put on the page that would save the current settings to the config and it would load those when it starts (more effort for that)? -
the table that shows in/out the ips just come and go too fast and if ur specifically monitoring a few local ips then they keep jumping up and down so y not simply keep the ip list static, meaning as soon as there is traffic from some ip, list it permanently and then just keep refreshing its in/out packets and suppose this ip stop communication for like 30 seconds then remove it from list
-
Does it make sense that external IPs/host names are displayed, especially when LAN interface is selected?
-
This same issue is present in PRERELEASE builds of 2.0.3 (see http://forum.pfsense.org/index.php/topic,58203.msg324782.html#msg324782). I note a few commits have been made to the master branch in response to this issue, although I'm not quite able to follow what is what. If any of these commits fix the original issue, can they be backported to RELENG_2_0 before 2.0.3 gets released?
-
I fixed so it accounts properly for the local subnet without showing the not local ips.
-
The "rate" utility is now back to the old behaviour, only showing local/internal IP addresses and is good for releasing 2.0.3. Whatever happens next, we need to be careful not to mess up the 2.0.n behaviour.
With no remote addresses returned by "rate", the "Filter: All/Local/Remote" box on the GUI is no longer useful/relevant.
I actually liked being able to see the external IP addresses. Combined with the option to display the FQDN (of IPs that have a reverse-lookup available) it often meant that I could quickly see what site a big BW user is downloading from. Of course it doesn't always work - if the IP has no reverse lookup then you have to do some work yourself on the raw IP if you want to get an idea what it is. The "Filter" option lets you suppress this output if you wish.
It would be easy enough to make "rate" take an extra parameter to make it spit out external IPs also. Then that could be invoked from the 2.1 code and not break the 2.0.n behaviour.
What do others think? Do you think having the external IP display option is useful? -
Why not let the user choose his preferred display mode by remembering the last chosen selection and using it by default until a different one is chosen.
-
Why not let the user choose his preferred display mode by remembering the last chosen selection and using it by default until a different one is chosen.
That requires a config write, which would not be ideal to do every time the user changes one of the dropdown selections. Adding a "Save Settings" button is probably the way to go.
-
Agreed…
