Search
Results (314)
- Revision 5fda51cd: Check for lo0 when reconfiguring VIPs on sync. Fixes #7010
- Revision 80bc583c: Standardize and fix 'other' type VIP display on NAT pages. Fixes #6094
- Revision d2ce7d30: Fix 'Other' type VIP options. Ticket #6094
- While here, remove some defunct 'range' code that was never used.
- Revision 1c9bf396: Fix bug where CARP vip status is incorrent in the interface when more
- than one CARP vip is configured for an interface. (cherry pic ... mit 5116a8aa60ad87c0a47aafeca422cc323147ea14)
- Revision 5ad69855: Fix bug where CARP vip status is incorrent in the interface when more
- than one CARP vip is configured for an interface. (cherry pic ... mit 5116a8aa60ad87c0a47aafeca422cc323147ea14)
- Revision a227ecef: Merge pull request #3164 from fredronnv/master
- * 'master' of https://github.com/fredronnv/pfsense: Fix bug where CARP vip status is incorrent in the interface when more than one CARP vip is configured for an interface.
- Revision 2329b5a8: DHCPV6 only check VIPs in range if range valid
- If the user has input invalid values into ran ... to, then there is no point checking any IPv6 VIPs to see if they fall in the range. None of t ... mit 3707ffc4157408b498d3b84d64918d4e41b5a123)
- Revision 3707ffc4: DHCPV6 only check VIPs in range if range valid
- If the user has input invalid values into ran ... to, then there is no point checking any IPv6 VIPs to see if they fall in the range. None of t ... ecause the specified range is not even valid.
- Revision 5116a8aa: Fix bug where CARP vip status is incorrent in the interface when more
- than one CARP vip is configured for an interface.
- Revision f003f8db: Some small improvements to OpenVPN server handling when using CARP VIPs in Gateway Groups. Might help with issue #6607