EFW Support

Support => General Support => Topic started by: kikilinux on Tuesday 18 February 2014, 07:35:13 pm



Title: endian team just use endian community forum to improve appliance product
Post by: kikilinux on Tuesday 18 February 2014, 07:35:13 pm
Hi
I think the endian firewall team just use the community forum to improve appliance product.
New endian firewall version 3.0 still contains some bugs from previous version and they are not fixed yet.
Does these bugs exist in appliance version?! (I don't think so)
It seems Endian corporation has constructed this product very attractive (using a lot of features and simple web user interface) while most of the features do not work well.
And in the forum a lot of questions have been left without answer.

best


Title: Re: endian team just use endian community forum to improve appliance product
Post by: dda on Wednesday 19 February 2014, 07:48:13 am
Truthfully I don't think they support the product on this forum.  Remember this is a free product if you want support you might have to pay for it.  I come here hoping to assist others with problems and when I have a problem to be in turn assisted.


Title: Re: endian team just use endian community forum to improve appliance product
Post by: kikilinux on Wednesday 19 February 2014, 03:55:05 pm
I didn't say i want their support here
I just said I think they use this forum to fix appliance product.
do u think the appliance product has these bugs from old version to new version ?(I don't think so)
I know this is a free product but the ubuntu, clearOS, zentyal and other open source produsts are free too.
I have not seen a forum as inactive as this forum.
when somebody in this forum can repair a bug for example this bug (http://bugs.endian.com/view.php?id=4560) why this bug remains from old version of endian firewall to new version ?!!!

best


Title: Re: endian team just use endian community forum to improve appliance product
Post by: dda on Thursday 20 February 2014, 01:55:59 am
Well I don't get that problem.  I remember having it in ver 2.41 and got it resolved on this site.  I also used the fix on there to solve some other problem.