Search
Results (709)
- Bug #16457 (Not a Bug): OpenVPN server does n ... hen set in /30 single public IP configuration
- Multi WAN , 2 node pfSense configuration. WAN ... for allowing OpenVPN traffic passes to CARP VIP, but returning back to client through other ... on in the platform or just a bug? Thanks
- Bug #16442 (New): if_pppoe fails to terminate when a virtual IP is added of type IP alias.
- So the background of this bug report, is me a ... eeds to happen is a process that removes any VIP's first before initiating PPP termination, t ... ne for a long time until manual intervention.
- Bug #16425 (Incomplete): After upgrading from ... ed unstable DNS response issues via the CARP VIP.
- After upgrading from pfSense CE 2.8.0 to 2.8. ... ed unstable DNS response issues via the CARP VIP. When using the VIP (192.168.0.254) as both the gateway and DNS ... ttl: 86400 prefetch: yes serve-expired: yes
- Bug #16422 (Not a Bug): DNS Resolver không phản hồi ổn định qua CARP VIP sau nâng cấp lên pfSense 2.8.1
- Sau khi nâng cấp từ pfSense CE 2.8.0 lên 2.8. ... gặp lỗi DNS không phản hồi ổn định qua CARP VIP. Khi dùng VIP làm gateway và DNS (192.168.0.254), truy cập ... 86400 prefetch: yes serve-expired: yes
- Bug #16385 (Duplicate): Dynamic DNS does not track the right IP when using GW groups and VIPs
- Hello, When we use GW group with CARP VIP selected in HA cluster , the IP selected by ... ting to differents GW groups with differents VIP) Right now we have 2 pfsense in HA with 3 wan and 7 public vip in IPv4 We did not check if it is the same ... 168.1.1 pf-b.wan1 : 192.168.1.2 wan1 carp vip 192.168.1.3 pf-a.wan2 : 192.168.2.1 pf-b.wan2 : 192.168.2.2 wan2 carp vip 192.168.2.3 *GW group GW_VPN is configure ... his. Kind regards, Arthur Besnard
- Revision 691852a2: Consider gateway group VIP preference with DDNS. Fix #16326
- Regression #16326 (Feedback): Dynamic DNS does not use preferred VIP in Gateway Group
- Since pfsense CE 2.8.0, Dynamic DNS only uses ... ic/197934/dynamic-dns-don-t-work-with-carp-ip
- Todo #16322 (Resolved): dpinger can use a CARP VIP as the source IP address
- find_interface_ip() in /etc/inc/interfaces.in ... the $interface_ip_arr_cache. If the CARP VIP is in /var/db/{$interface}_ip when calling find_interface_ip() with flush the VIP will still be used. I think it would make ... oticed as dpinger was monitoring on the CARP VIP instead of the interface address.
- Revision bb26a4ce: VIP corrections: Validate IPv4 for proxyarp and respect saved vip type
- Revision 5ff07bb5: Reference the correct VIP in input validation description. Fix #16272
- The $vip variable may not reference the $found_carp's VIP since there's no break in the loop. Fix it by keeping the ID once it's found.