Open julsemaan opened 6 years ago
In the case of a registration vlan in layer2 packetfence send the list of all members of a cluster as a gateway. In layer3, the gateway of the client is the layer3 interface of the remote registration network and the core switch do the routing. So for dns it make sense but for gateway i don't see the point.
I have users that actually put an ACL in the L2 registration VLAN so that would cause problem for them
Similarly to the active_active.dns_on_vip_only parameter, we would need the same for the gateway since its not pushing all the cluster members as possible gateways.
This can cause an issue if there are some ACLs in the registration VLAN containing the traffic on the VIP