Search
Results (717)
- Bug #11793 (Closed): OpenVPN client starts when CARP VIP is in BACKUP status when bound to Virtual IP aliased to CARP VIP
- If an OpenVPN client is bound to a _virtual I ... if (($a_groups[$settings['interface']][0]['vip'] <> "") && (!in_array(get_carp_interface_status($a_groups[$settings['interface']][0]['vip']), array("MASTER", "")))) </code></pre> [ ... IP addresses failing over independently.
- Bug #11721 (Rejected): NAT redirecting traffic to incorrect interface address
- Good evening, To be clear upfront, this is ... ault NAT reflection mode is set for Pure NAT.
- Bug #11629 (Resolved): PPPoE WAN IP address different than expected when set static by ISP
- As per support ticket: #INC-77927 Hi, we'v ... om the router due to privacy, but can supply.
- Regression #11545 (Resolved): Primary interface address is not always used when VIPs are present
- If you have IP Aliases on a WAN interface tha ... 4. Restart IPSec service Tunnels now work.
- Revision 50ae67cd: Merge pull request #4487 from znerol-forks/feature/master/radvd-linklocal-vip
- Bug #11457 (Rejected): Client DNS doesn't resolve when using VIP in place of interface IP
- https://forum.netgate.com/topic/161056/client-dns-doesn-t-resolve-when-using-vip-in-place-of-interface-ip: "My inside interface is set to 192.168.1.1 and I created a VIP on .254. When I set a client device to use . ... m is when I set the client device to use the VIP as the DNS host. No responses come back. All ... tween .1 (inside interface) and .254 (inside VIP) for queries, .1 always works and .254 alway ... 168.88.41 - LAN IP, 192.168.88.44 - LAN CARP VIP it's better to hide all VIPs from the DNS Resolver "Network Interfaces" list
- Revision 01388d99: Add getVIPs() function for MVC
- Revision 4f630b14: Return correct Track IPv6 address if >1 VIP on interface. Issue #5999
- Revision 89c7e448: Return correct Track IPv6 address if >1 VIP on interface. Issue #5999
- Feature #11354 (Resolved): WireGuard should respond from the address used by peer
- When a WireGuard peer contacts the firewall, ... ve an address like 198.51.100.12, but a CARP VIP of 198.51.100.11. Remote peers should always contact the CARP VIP for proper failover, but when they do, packe ... le: HA node with 198.51.100.12 on interface, VIP of 198.51.100.11, and remote peer of 198.51. ... ndpoint, rather than using the original CARP VIP endpoint address which should move to a seco ... secondary node has MASTER status on the CARP VIP. The state would need to be manually cleared ... first, but doesn't work when failing over.