Bug #5415
closed
pfSense attempts to display aliases on mouse over, which hangs the UI if there are significant numbers of IP addresses
0%
Description
Hi
If you hover over an alias on e.g. the dashboard within pfSense, pfSense attempts to display the IP addresses in the alias. That's fine for small numbers of IPs but if it's (say) a pfBlockerNG alias with 100,000s of IP addresses, it will hang the browser, presumably because there's a script that's trying to enumerate all the IPs to display them. Because the UI attempts to display the alias listing immediately on mouse over, you have to be very careful to steer around any aliases on the screen, otherwise it hangs the browser and you have to force close the browser and start again.
Suggested fixes:
• either put a delay in the mouse over before attempting to display - e.g. you have to hover the mouse for 2-3 seconds before it attempts to display the IPs; or
• truncate the display of IP addresses to (say) 50. More than that probably won't fit on the screen anyway.
Thanks.
Updated by Jim Pingle over 8 years ago
Which version of pfSense is this on? If it's 2.2.x, have you tried 2.3?
Updated by Andrew - over 8 years ago
Thanks for your reply.
It certainly does it on 2.2.4 and 2.2.5, most probably other 2.2.x versions. I haven't tried 2.3 as I'm running on the stable releases.
The easiest way to test it is to install the pfBlockerNG package (which puts the widget on the dashboard), set up a big alias (e.g. Bad peers - http://list.iblocklist.com/?list=cwworuawihqvocglcoss&fileformat=p2p&archiveformat=gz), and then hover over the alias name.
I suspect it's not limited to pfBlockerNG aliases or the dashboard. e.g. the same mouse over popups are on the Rules screen for the firewall. So, presumably, any long alias that a user sets up will have the same problem on those screens.
Updated by Anonymous over 8 years ago
My guess is that the pfBlocker widget will need to be updated for 2.3 and that would include a change to the jQuery autocomplete scheme. We should probably re-test when that conversion is done to see if the issue still exists.
Updated by Phillip Davis over 8 years ago
I did some code for RELENG_2_2 pfSense 2.2.5 just because it turned out to be quite easy. The sample code is guiconfig.inc in pull request https://github.com/pfsense/pfsense/pull/2061
Does something like that make life easier for really big aliases?
Of course as others have said above, that then needs to be engineered to work with 2.3...
Updated by Andrew - over 8 years ago
Thanks.
Phillip - the code you've linked to appears to limit the popup size to 200, which is along the lines of my second bullet - so that should work.
Steve - just to confirm, the issue does show up in the pfBlockerNG widget, but it's not limited to that. Any screen in pfSense that has the popups (e.g. the firewall rules screen) is susceptible to the issue if the alias is big enough.
Updated by Phillip Davis over 8 years ago
That code should limit it to 100 entries. The limit is easily changed - I just picked 100 for no particular reason.
Updated by Chris Buechler about 8 years ago
- Category set to Web Interface
- Status changed from New to Resolved
this was a 2.2.x issue that was resolved with Phil's PR in RELENG_2_2. Not an issue in 2.3