Note: this perhaps aint a CP issue but perhaps someone has experience dealing with the same issue.I know enabling VMAC would resolve the MAC change but we want to find the root cause of this issue. What could be the cause of the old gateway MAC address being stuck on the servers in VMWARE? The problem is not on a single server but many hosts all have the same issue and became unreachable. Dynamic ID Authentication is also supported in: Mobile Access Gateway version R80.10 and higher. So the fact is that for some reason their default gateway MAC address is still pointing to the old firewall. Endpoint Security VPN for macOS - version E83.20 and higher Check Point Mobile for Windows - version E80.65 and higher SecuRemote for Windows - version E80.65 and higher Notes: All other clients support only a single authentication option. Whenever we do a failover to activate the next member, the hosts are receiving the traffic but they still respond to the old (now STANDBY) gateway. We have a cluster R80.40 installed on VMWARE in ESX server and the three options are configured on all VLANS, forged transmit, promiscuous mode and mac learning on accept.Ĭurrently the VMAC is not enabled so after failover we depend on ARP(MAC) address update on the surrounding hosts.
0 kommentar(er)
