Messages

gateway groups as failover.  what's weird is in 22.1 it would fail bac to the primary ip after ab out a minute.  i didn't have to do anything.  in 22.7 i now have to either forcibly disable the secondary wan or reboot the firewall for it to fal back.  if this non-going back to the primary is expected behavior..this is not the solution for me and my clients and will have to go back to another product.

we installed 22.1 back on the appliance and restored the config.  It now reverts back to primary within seconds as verified by ipchicken on a desktop behind the opnsense.  No need for a static route eithe.  I think 22.7 needs a ton of work at this point.

gateway groups as failover.  what's weird is in 22.1 it would fail bac to the primary ip after ab out a minute.  i didn't have to do anything.  in 22.7 i now have to either forcibly disable the secondary wan or reboot the firewall for it to fal back.  if this non-going back to the primary is expected behavior..this is not the solution for me and my clients and will have to go back to another product.

duh forgot the cidr notation..got it.

I think I found the issue.
Wan1 has a route set to the monitoring ip of 1.1.1.1 AND the ip of 8.8.8.8 3even though 8.8.8.8. is cearly seutp for monitoring on wan2.  Looks like a bug either in freebsd or the opnsense code.

trying to figure out why this is not working..:)

i'm not familiar with that..what parameters in the static route would i use?

so set a static route on each gateway to the monitoring ip addresses if i am reading this correctly....

no..it's probably your isp...

i'm not familiar with that..what parameters in the static route would i use?

I recently purchased an opnsense appliance for a client.  It appears 1500 dollars was not spent wisely.  it appears 22.7 is not supported on official hardware as their fix for any problem is to reinstall 22.1.  Right now the only email contact i can get to is sales....is there an actual support mailbox at the parent company?

everything worked correctly in the previous version.  only upon upgrading to 22.7 did it break.

so after further testing:

this is on official hardware the dec3850.
If we either pull the primary wan connection physically or disable it in the web gui failover to the secondary takes 5 seconds.  It used to be instant.  Another wrinkle is when the primary is restored it refuses to switch back,  Hitting save 0n an interface has no effect.  Disabling the secondary causes a 5 second loss of connectivity.  Otherwise a reboot is required.

in the previous release i could unplug one wan port and the system would fail over to number 2 without issue.  When the primary was restored it would fail back to the primary.  This is now NOT happening in the newest release.  This has apparently been a bug before..but now short of rebooting hte firewall it will not restore states back to the primary after a fail over to secondary.  any ideas?

I've done it with a sophos firewall where the vpn(via openvpn) instead of looking for an ip looks for a fgdn(aka firewall.dynamicdomain.tld).  Can opnsense be configured to act in this way?

a picture of your interfaces, interface assignments and firewall rules for each interface would be helpful.

i recently purchased a 3850 appliance and I was trying to go to the community edition but it keeps saying your subscription requires a token.  So far I have been told the only way to go back is to reinstall.  given the lack of a VGA port(use I know there's a console...but that's a bigger pita) can't I just switch repos(even if I have to do it in the root shell) and do it that way?