Search
Results (717)
- Revision e0c822a1: Use the appropriate parent interface with gateway groups using CARP VIPs.
- Ticket #4990
- Revision 2f1e2ad9: Use get_interface rather than find_interface here. It'll work for VIPs on gateway groups this way, and cache doesn't really matter here. Partial fix for Ticket #4990
- Revision dda80e76: Fix source address selection on Test Port to handle VIPs properly.
- Revision 2554dd64: Fix incorrect variable references for CARP VIPs. Fixes #5016
- Revision 4d843977: Fix incorrect variable references for CARP VIPs. Fixes #5016
- Bug #4990 (Resolved): Dynamic DNS Not Working With GW Group Using CARP VIP
- Under Dynamic DNS service, Interface to monitor is set to a Gateway Group that uses CARP VIPs for tier 1 and tier 2 I get the followin ... ne the public IP for interface - GWGROUP(wan_vip1). Probably interface is not a WAN interface. Cached IP always shows as "NA"
- Revision c617ffe7: Fix source address selection on Test Port to handle VIPs properly.
- Bug #4986 (Resolved): Selecting an IP Alias VIP for Test Port does not function
- On Diagnostics > Test Port, source address selection does not work when an IP Alias VIP is selected. A fix has been committed in ... 7a -- adding this for reference and feedback.
- Revision 6538d22f: Use an alternate method to find VIP targets that should be allowed for Captive Portal. Fixes #4903
- Revision 7fbe16f7: Use an alternate method to find VIP targets that should be allowed for Captive Portal. Fixes #4903