Search
Results (402)
- Bug #9435 (Resolved): Dynamic DNS Update events do not occur after certain failover event cases
- This test was done on a lab HA pair behind a ... lover group FAILOVER WAN_GW Tier 1 WAN CARP VIP WAN2_GW Tier 2 WAN2 CARP VIP Dynamic DNS on HE.NET bound to the FAILOV ... are rare enough this isn't hit more often.
- Bug #9384 (Confirmed): devd putting "$" before variable contents when using single quotes
- On 2.5.0 snapshots, when @check_reload_status ... _status 357 Linkup starting $vmx3 </pre>
- Bug #9358 (Closed): Lost default gateway after recover from failover with CARP VIP and HA
- The same issue #8465 is back on 2.4.4-RELEASE ... .0.2/30 lan: 16X.XXX.100.252/24 Carp: wan vip: 16X.XXX.198.154/30 lan vip: 16X.XXX.100.254/24 Default Gateway of node ... carp" and "persistent carp maintenance mode"
- Feature #9224 (Rejected): Cannot configure STATICALLY-allocated IPv6 addresses on pfSense
- Hello, *On current version of pfSe ... pport. Best regards, Răzvan
- Bug #8815 (New): IP addresses are removed fro ... nk is lost and either IPv4 or IPv6 is dynamic
- When an interface loses link the IPv4 addresses, including VIPs, can disappear from the interface. If the l ... ear. The highest impact is from HA/CARP. The VIPs disappear from the interface, so the OS doe ... check_reload_status: Reloading filter </pre>
- Bug #8814 (Rejected): After changing WAN CARP VIP Outbound NAT rules don't import new value but stay with old one and need to be changed manually
- I created HA cluster on 2.4.3_p1 and after changing WAN CARP VIP Outbound NAT rules don't import new value. S ... ually, everything started to work. WAN CARP VIP is '172.21.41.252' igb0: flags=8943<UP,BROA ... 29.0/24 to any -> 172.21.41.13 port 1024:6553
- Bug #8768 (Resolved): IP Aliases with CARP VIP parent need reinitialized after interface event
- IP Aliases with CARP VIP parent need reinitialized after interface ev ... https://github.com/pfsense/pfsense/pull/3967
- Bug #8741 (Resolved): IP Alias and CARP VIP subnet remains set to /128 for IPv4 address
- Visit Firewall > Virtual IPs, click +Add, cli ... ress, click IP Alias, click Save. A IP Alias VIP is created for the IPv4 address with the sub ... Password and confirm it, click Save. A CARP VIP is created for the IPv4 address with the subnet set to /128.
- Bug #8728 (Resolved): Can not create VIP after deleting existed one
- I deleted VIP and tried to create new one on latest and got the error: <pre> Warning: Illegal string offset 'vip' in /usr/local/www/firewall_virtual_ip_edit.php on line 39 Warning: Illegal string offset 'vip' in /usr/local/www/firewall_virtual_ip_edit. ... .php:42 Stack trace: #0 {main} thrown </pre>
- Bug #8693 (Duplicate): Filter rules error after deleting VIP
- On 2.4.2 and 2.4.3p1 I ran into a rules.debug ... g it fail to load rules. I deleted 2 Carp vips which resulted in the following rule errors ... ming from filter.inc where it is parsing the vips. For the actual real interface we check all ... </pre> However, we then add rules for the vips, and there is no validation on the vip address there. <pre> if (ip_in_subnet($vip['ip'], "{$ifcfg['sa']}/{$ifcfg['sn']}")) { ... ']} route-to ( {$ifcfg['if']} {$gw} ) from {$vip['ip']} to !{$ifcfg['sa']}/{$ifcfg['sn']} tra ... [spoofcheck] => yes [bridge] => [vips] => Array ( [0] => Ar ... re> global $config; print_r(get_configured_vip_list()); print_r(link_interface_to_vips('opt1')); include("/etc/inc/filter.inc"); ... Iflist); </pre> I see that the configured ...