Search
Results (403)
- 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
- Regression #16326 (Resolved): 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
- Bug #16322 (Resolved): Gateway monitoring daemon can unexpectedly 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.
- Bug #16272 (Resolved): Input validation text for deleting an IP Alias VIP within a CARP VIP subnet may reference incorrect VIP
- Input validation exists that prevents the del ... subnet. To reproduce: # Create the CARP VIP 198.51.100.1/24 with description "Test CARP VIP" # Create the IP Alias VIP 198.51.100.2/25 with description "Test IP Alias VIP" # Apply changes then delete the IP Alias VIP. The input validation text says: @This en ... a CARP IP with the description Test IP Alias VIP@ The input validation should instead reference "Test CARP VIP".
- Bug #16235 (Resolved): Using IPv4 VIPs on PPPoE interfaces with ``if_pppoe`` causes looping
- Originally reported on the forum: https://forum.netgate.com/topic/197369 IPv4 VIPs are added by rc.newwanip via link_interface_to_vips() and each VIP triggers an ADDR_ADD event. These events tri ... alls rc.newwanip and hence results in a loop.
- Bug #16221 (Not a Bug): Other interfaces are ... uses DHCP resulting in split-brain operation
- Expected behavior: When you unplug an int ... The behavior is the same on both versions.
- Feature #16174 (New): CARP VIP support for ``if_pppoe``
- With the mpd5 PPPOE implementation it is poss ... not intentional/supported) to create a CARP VIP on the PPPOE parent interface, and then assign the CARP VIP rather than the interface itself as the pare ... ter switching to if_pppoe selecting the CARP VIP prevents the interface from starting correct ... ace itself. This prevents automatic failover.
- Bug #16131 (New): DHCP Relay not working when CARP Status VIP is other than None
- Hello, I have an IPSec tunnel between a PF ... 0.5. The thing is, if I select a CARP Status VIP in the DHCP Relay menu, the packets get forw ... ort 67 or port 68 -e -vv). When CARP Status VIP is set to None, everything works as expected ... at one wasn't working either :D Thank you!
- Bug #15676 (Resolved): OpenVPN not rendering alises in "IPv4 Local network" setting.
- When using network aliases in "IPV4 Local net ... ific issue, hence I'm opening this one.