Some words on this topic from the WebAdmin maintainer:
1. The Version 5 WebAdmin will never be as fast as the Version 4 one. Why? Well, version 4 used flat text files for configuration storage. This has the benefit of very fast read/write access, but once you want to read and write the configuration from more than one place, you start to get locking problems. Thats why we introduced a daemon called 'confd'. It is a managed configuration storage that also validates and cross-checks configuration data. Needless to say, it is much faster to read from a text file than to query confd (via XML-RPC). Since confd stores the basic config definitions like networks and services, it must be accessed on nearly each page of the WebAdmin. Check out /var/log/webadmin.log in the latest versions, there is some output regarding confd communication. We are currently working on making the communication faster.
2. I'm surprised to get so much flak for the pop-up menu. My design goal was to reduce clicks. In V4, you needed one click to open a menu, and another on to open the page. In V5, you only need one click, without a reload. Sure, you could pin the menus open in V4, but if you did that with most of them, you ended up scrolling a lot (mouse wheel syndrome).
3. The amount of configuration options has increased - again. This makes the interface more complex. I tried to pack as much information as possible in the tables, without cluttering things up too much. The filters should help you to navigate through the maze. Displaying less information would increase readability, but reduce usability for "advanced users". I'm seriously thinking about diversification into a "basic" and an "advanced mode". [[[:)]]]
4.Good, finally some tips. I think the concept of the new tables is not clear for everyone [[[:)]]]
Use the filters! They make finding stuff very easy. Also, you'll work on a limited set of entries, which helps with large tables.
You can edit stuff by clicking on it. If you can't click on it, you can't edit it.
You can edit multiple things at once, as many as you like. Clicking ONE of the open "Save" buttons will save all open edited entries. This also works across multiple lines.
When viewing logs (without live log), use the "Download" button on the right of the local log files table, and link .log files to a good text editor on your management machine (NOT notepad!). Logs can get real large, and most browsers handle multi-megabyte text files by crapping out. [[[:)]]]
Not sure what XML-RPC gives you that something like, oh, say, PostgreSQL wouldn't. Maybe you save some RAM or something. But damn, RAM is cheap compared to my hourly rate. as for browser crashes, I've never had so many since switching to 5, even on an Athlon 3000+. Seems to be the worst if you import a 4.021 config.
I'd be curious to see how many of us out there actually get a page when in Intrusion Protection >> Rules >> expand Miscellaneous WWW-specific rules >> then click Show All.
It also seems a bit asinine to force Astaro to Read through everything just filter out what you dont want. Again, why not just run SQL queries for what you do want to see in a web page.
We can make him faster, stronger, better - We have the technology!
Don't mis-understand me totally here though, between the things that needed fixing from 4 and the added functionality, 5 is the Premier FW OS. I just feel like I've given up two toes for a new pair of shoes.
Where's there's smoke there's fire, and it appears there's now a fire @ https://demo.astaro.com It seems to be producing the same Internal Server Error page that I get on my systems from time to time when the webadmin interface craps out only there's no refreshing this one to 're-login'.
Where's there's smoke there's fire, and it appears there's now a fire @ https://demo.astaro.com It seems to be producing the same Internal Server Error page that I get on my systems from time to time when the webadmin interface craps out only there's no refreshing this one to 're-login'.
