i am shure astaro team reads all posts, but i think they have not time to answer all posts. they invest the answer time in develop [;)]
Astaro-Report-Manager is an new feature to do a central reporting for asl-firewalls, e.g. you have to administrate a lot of, you can central see what happens. also you can correlate you data.
As I have said before, I have 7 ASL installations which all run perfectly stable. I run v5 @ home on a P3-600MHz 256MB ram... no problems... with content filtering, IDS, AV, and HA modes....
And no.. I would not eat sh..
[/ QUOTE ]
Hi,
Redman...why telling users of your p3 600GHZ/256MB with all features enabled works well....?
THANKS for let them think they are right, shouting out unstable and buggy with such minimum Hardware.
ASL 5.025 isnt very supportable with such Hardware you posted and all the features enabled, sorry.
Are you really running v5.023 + web/av enabled ?
I agree with you that V5 runs stable , i have many installations aswell and am lucky with that Product.
I only have one thing open,and that is the HTTP-Proxy "Bug" introduced in v5.023 with AV enabled...and thats very bad stuff because it affects each user of the firewall.
Cannot tell my !paying! Customers that they should disable WEB/AV scanning....cannot tell them that we have to make a new installation because of this issue.
Hope this issue will be resolved SOON.
OfficeDefender, I've been using Astaro for a LONG time and it seems to me that the companies attitude has changed around about the initial v5 release.
I'm sure Astaro have a development schedule, but there are simply a lot of issues that are causing a lot of paid up users hassle. My personal beef is the SSL encryption being now enforced on the SMTP authentication. Yes there's a workaround, and yes a solution has been promised. However new up2dates are overwriting the recommended fix, meaningwe have to go re-edit. (Not to mention warranty being voided by having to do this).
My corporate installations are running fine, a few niggly issues like the SMTP thing and spiking graphs. (Which has also been happening a long time).
OfficeDefender, you can't just temporarily shut off a feature that's causing problems without repercussions.
Users start asking what the hell is going on and sometimes things like that fly in the face of corporate IT policies. (Sorry guys I have to let porn sites through again coz the filter aint working right, just please don't sue us in the meantime for exposing you to porn).
My organisation isn't that bad (and I decide IT policy), but I know of sites for which those statements are VERY applicable.
As stated in my prior post, something changed with v5, the QC on releases seems a lot worse, (you yourself were getting fed up at one point). And yes it's better now, but some people are still having serious issues.
I'd say 95% of all these whines would go away if Astaro just kept us better informed.
You probably are chatting to them everyday and have inside knowledge, most people here only see what's written on the forum.
Can you tell me when Astaro are going to stop my systems whining to me daily about licensing issues and when we can stop having to custom configure our firewalls so that license counts don't skyrocket when we get portscanned?
Redman...why telling users of your p3 600GHZ/256MB with all features enabled works well....? THANKS for let them think they are right, shouting out unstable and buggy with such minimum Hardware. ASL 5.025 isnt very supportable with such Hardware you posted and all the features enabled, sorry. Are you really running v5.023 + web/av enabled ?
[/ QUOTE ]
Why? Because it is the truth..... however I also only have at most THREE users going though it. And YES I am running all features.
Why do you guys have to be so aggresive in your replies?
[ QUOTE ] Can you tell me when Astaro are going to stop my systems whining to me daily about licensing issues and when we can stop having to custom configure our firewalls so that license counts don't skyrocket when we get portscanned?
All of which are new "features"....
[/ QUOTE ]
Just ignore anything having to do with license counts. Pretend it doesn't exist and make no assumptions. Astaro is still working on this feature and it is not fully implemented or enforced at this time.
[ QUOTE ] OfficeDefender, I've been using Astaro for a LONG time and it seems to me that the companies attitude has changed around about the initial v5 release.
[/ QUOTE ]
Their attitude has not turned sour. It's no secret that the initial v5 release was problematic and caused a lot of knuckle-chewing for all of us. The reason this occurred, however, has little to do with any incompetence in the development and QC areas and a lot more to do with pressure to meet a timetable. I'm not going to go into the specifics, but what you've got to do is consider that Astaro is a company, not some dude coding in his basement, and like most businesses they have a rather complex set of constituents to satisfy. One thing I can tell you that I've heard from Astaro -- at all levels of contact -- is that the v5 debacle will NOT be repeated.
[ QUOTE ] My personal beef is the SSL encryption being now enforced on the SMTP authentication. Yes there's a workaround, and yes a solution has been promised. However new up2dates are overwriting the recommended fix, meaningwe have to go re-edit. (Not to mention warranty being voided by having to do this).
[/ QUOTE ]
This sounds more like a feature request rather than a bugfix. Feature requests take longer to go through the development food chain, bugfixes are given much higher priority. Why can't you deal with SSL encryption for SMTP authentication? Do your users' mail clients not support it or something?
[ QUOTE ] My main beefs are that: 1) They are not responding to threads here
[/ QUOTE ]
This isn't an official Astaro support forum. If you have a paid license, send an email to support@astaro.com or supportus@astaro.com.
[ QUOTE ] 2) Buggy up2dates and up2dates that do not install as described in the up2date release.
[/ QUOTE ]
This is a rare thing.
[ QUOTE ] 3) Licensing, my original thread was never answered satisfactorily. (How often will IP's remain counted before a refresh is done).
whats your problem? You got a free home use license, you got a free forum and you get regulary free information/updates/insider information?
Where do you get this from other vendors? Where is the user forum on the symantec site, where is the known-issue-list on the fortinet site, where are the home use licenses from checkpoint and so on...
I stopped posting here because of this continued weeping and crying "there are bugs, they do nothing, everything wrong, what they are doing?, they do not answer,....".
Where are the postings with a detailed bug description, with config, with hardware details, with topology details, with 5 step instruction to reproduce the bugs? Yes there are a few... (mostly not from the weeping-posters) - and these bugs become fixed or listed in the known-issue-list or (i'm sure) will be fixed.
If you paid for a license call the support and i promise you, they squeeze out all the information they need and you get qualified answer. Do you really expect an answer here for statements like "it does not work - help and fix it!"?
Sometimes i wonder if the "1000-and-more postings"-owner are working for a competitor or found a cheap solution to post there URL from their own business to increase the google ranking...
I waiting for the days astaro will shut down the board because of all this bull$%/[}-postings, condemnations, unproved allegations and statements like "I want" or "astaro must"....
OfficeDefender wrote: >Just ignore anything having to do with license counts. >Pretend it doesn't exist and make no assumptions. >Astaro is still working on this feature and it is not fully implemented or enforced at this time.
So why put it in? It does not make sense to me. If they need to test something like this, test it internally. Then, when it's ready to be FULLY tested, beta test it on volunteers and release to public after that.
I'm always ready to beta test Astaro on my HOME machine but lately it seems we've been live testing it in production environments.
Anyway, I've said my bit and that's enough for now. Wait and see what happens. I will only respond on this thread further if someone directly addresses me.
OfficeDefender: >It's no secret that the initial v5 release was problematic and caused a lot of knuckle-chewing for all of us. The reason this occurred, however, has little to do with any incompetence in the development and QC areas and a lot more to do with pressure to meet a timetable. ~~~~~~~~~~~~~~~~~~
Yeah I'd guessed that. I've worked for a software development company for 12 years and spotted the symtoms [:)]
I just hope they recover from it soon as it seems it's been a struggle.
Pushing a software feature set release to a specific release date is all very well and good, but you should never release before a certain stability and feature point is met, if the programmers are not happy with a release, they should be listened to.
OfficeDefender: >It's no secret that the initial v5 release was problematic and caused a lot of knuckle-chewing for all of us. The reason this occurred, however, has little to do with any incompetence in the development and QC areas and a lot more to do with pressure to meet a timetable. ~~~~~~~~~~~~~~~~~~
Yeah I'd guessed that. I've worked for a software development company for 12 years and spotted the symtoms [:)]
I just hope they recover from it soon as it seems it's been a struggle.
Pushing a software feature set release to a specific release date is all very well and good, but you should never release before a certain stability and feature point is met, if the programmers are not happy with a release, they should be listened to.
