Search
Results (711)
- 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
- Revision 65b5efa7: Add config function init_config_arr()
- This function initializes a set of nested key ... xample: init_config_arr(array('virtualip', 'vip')); This will create $config['virtualip']['vip] as an array.
- 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 ...
- Bug #8690 (Closed): PHP unable to init zend modules 2017 vs 2013
- yikes. so much PHP @2.4.4 from this mornin ... oronto] PHP Warning: Illegal string offset 'vip' in /usr/local/pkg/pfblockerng/pfblockerng.i ... oronto] PHP Warning: Illegal string offset 'vip' in /usr/local/pkg/pfblockerng/pfblockerng.i ... e 46 No FreeBSD crash data found.
- Bug #8653 (Resolved): Spurious HA XMLRPC Sync Error after move to PHP7
- After moving to PHP7, an HA pair logs an XMLR ... , wol sections) from XMLRPC client. </pre>
- Bug #8586 (Resolved): Gateway Group trigger level
- Hi to all, i think there is a problem using ... ( [0] => WAN_UMTSGW|1|_vip5a60be577ad2b [1] => WAN_VSATGW|2|_vip5a4bc724a886d ) ... ( [0] => WAN_VSATGW|2|_vip5a4bc724a886d ) ... } </pre>
- Revision 45c44edb: Correct the gateway check when deleting a VIP. Fixes #4438
- Now it checks to see if there are other VIPs in the same subnet left, and only prevents deleting the last VIP by which a gateway could be reached. (cherr ... mit 480c21f44c42dd84f7ca0e0db62a7a731ed0278e)