Messages

allow me to restate...the lack of support from Deciso during US business hours...hence the move to another vendor for business clients.

(original text: lack of support hours available from Deciso in the US...hence the move to another vendor for business clients.)

The summary is, I am going with a different product in the future. 

for today's software...yes...unfortunately release is no longer the actual release.

read my previous post.  if you cannot understand why from that...i cannot assist any further..:)

[hardware]

Actually for a 5k server from Dell you get minimum 3 year on-site hardware support.  I wound up reinstalling 22.1 to solve the failover issue that led to this post.  Lesson learned.

A: I was talking about workstations not servers

B: That is a perfect example of how any company and even products within a company offer different types of support

C: Reread your sentence. Did you notice, that you used the word hardware? If you understand the difference between hardware and software support, you really have learned your lesson.

D: 3y onsite is not even true for all Dell servers. T150 offers only 13 months. Also take a look at the Dell "help me choose" page for support: https://www.dell.com/en-us/shop/help-me-choose/cp/supportforenterprise
Now take a look at "Product coverage". Can you see how you only get Hardware support at Basic Warranty and you have to upgrade to ProSupport to get software coverage?

5k was the threshold mentioned..5k is how is responded.  5k workstaiton gets you a minimum of 3 year NBD oonsite as well. you are arguing with a long time dell partner here.  quit while you are behind. 

i understand now the software is effectively unsupported now without additional cost.  Read my other posts as to my disappointment in this regression.

not thanks.  my clients..either home or business are not used by me to beta test my vendors products.  I now know the release policy of OpNSense..lesson learned..:)

Please either lock or delete this thread

I know how it works now....not too long ago release meant release...not it's kinda done but the users are the final beta test which has infested the rest of the software community.  Firewalls and other critical infrastructure..imo...should hold themselves to a higher standard and open source ones used to hold themselves to even higher ones.  You know what they say about assumptions...Assumptions always bite you in the ass.

we asked for an rma..the reply was..please do not send the machine back..it's not a hardware problem.  If you will honor the rma i'll message you the order number, allow you to research it.  If you will then offer the RMa option, i'll present this to my partner.

you are welcome.  My lack of feedback is because i am not running 22.7 in a failover environment now as i cannot afford to be testing the software in said environment as the client will not put up with that.  22.1 works as the use case calls for..and as the thread shows..22.7 doesn't(Edited..not in it's current release form)..a.  I DO have 22.7 running here with a single wan and that, of course, works perfectly.  My statement of..you should not have to cycle the interface goes all the way back to my first post about this...if i had the ability to test this further..i would.  I don't..so i won't. OPnsense is a good product..but this one issue burned me badly when alll other times it worked perfectly.  Normally i upgrade here..beat on it..and deploy7.  I tested it here in a similar..but not exact environment..then upgraded to 22.7 on the 3850 on the client firewall only to have OPnSense fall flat..and continue to do so.  In order to fix it..a reinstall to 22.1 was required.  Due to the lack of a vga port that machine wilt stay on 22.1...probably forever until I can guarantee failover works as it should.  At this point what is probably going to happen is i will have to replace that firewall..at my expense..with a pfsense box that i KNOW does failover correctly.  I wanted to move to opnsense for my critical business clients due to PFSense's well stated intentions of going closed source and paid only...it looks like for non-critical applications i will continue to use opnsense...but for other applications it's either pfsense or something else.  This regression has caused me to look like an idiot to my partner AND also to the client we spent many hours trying to get rid of a sonicwall firewall to replace it with this 3850.  I am now contemplating having to buy the hardware from my partner and eat several hours of time to get the sonicwall working or replace the 3850 with a PFSense machine with TAC.

I am not saying opnsense is a bad product but this failover issue left me looking like a complete idiot.  I have never had a firewall upgrade blow up this badly..in full view of both my partner and a major client..at the same time. 

I appreciate the entire opnsense teams time and efforts...and i know this will be resolved eventually.  This is going to cost me a good deal of money both in having to either replace the hardware with something else...OR eating many hours of time trying to convince the partner and client this is a viable solution for their needs. 

I actually hae two custom Opnsense firewalls i am configuring for a different client who does not have a failover requirement...and will happily deploy those firewalls(on custom hardware).  I will continue to run Opnsense here at my office as well.  Opnsense is a solid product but this incident has made me change my use cases for the product.

i hope that provides the context you are looking for franco. 

(Edit: noticed the patch...great job..just cannot test it at the client as reinstalling from the serial console is really a pain..if it had a vga port...Once .3 is released i'll test here at my office in my multi-wan setup and then if it works right..we MIGHT decide to upgrade the 3850....)

Nope..had to use the serial display and reinstall from USB.  This will be the last official opnsense I purchase due to lack of vga port.

That should not be necessary in terms of cycling the interface. 

Actually for a 5k server from Dell you get minimum 3 year on-site hardware support.  I wound up reinstalling 22.1 to solve the failover issue that led to this post.  Lesson learned.   

care to share the script?

so it seems 22.7 needs some work.  it's either a bsd issue, a middleware issue or a combination of the two.  This unfortunately means we will be leaving a brand new opnsense firewall at 22.1 forever...when and IF this issue gets fixed we might try going forward.  It's also strange that is generates a nearly 5 second outage going either way in 22.7 when it's nearly instant on 22.1.