- Service Level Agreement (SLA).
- We likely did not configure DNS for the secondary WAN connection.
- Failure to correctly configure the monitor IP for the secondary WAN; failure to create firewall rules or to change outbound NAT rules to send traffic to the gateway group.
- We didn’t configure latency settings for the secondary WAN to allow for the greater amount of latency a satellite connection would have.
- (a) Because policy-based routing does not work with traffic that originates with pfSense, like DNS traffic. (b) Make the upstream DNS server the monitor IP, and pfSense will create an implicit static route to it.
- Enable State Killing on Gateway Failure.
- (a) Set both to Tier 1. (b) Set one to Tier 1 and one to Tier 2.
- (a) pfSense will think the gateway is up when it should be down. (b) The remote site’s administrator may interpret our pings an an attack and...
United States
Great Britain
India
Germany
France
Canada
Russia
Spain
Brazil
Australia
Singapore
Hungary
Ukraine
Luxembourg
Estonia
Lithuania
South Korea
Turkey
Switzerland
Colombia
Taiwan
Chile
Norway
Ecuador
Indonesia
New Zealand
Cyprus
Denmark
Finland
Poland
Malta
Czechia
Austria
Sweden
Italy
Egypt
Belgium
Portugal
Slovenia
Ireland
Romania
Greece
Argentina
Netherlands
Bulgaria
Latvia
South Africa
Malaysia
Japan
Slovakia
Philippines
Mexico
Thailand