Hi Ceszmi
In general terms, you'd still use one interface for ingress (client side) and one interface for egress (server side) and simply use VLANs on your ESX vSwitches.
In our labs this is what we do, with an ingress VLAN connected to the ingress interface on the VM and the egress VLAN connected to the egress interface. Managing the traffic from a VLAN perspective on your vswitches then simply becomes a matter of standard software defined networking, which the networking team should be able to do as a matter of course.
As long as the traffic coming from your upstream device (firewall, edge router, etc) is tagged correctly and the downstream device(s) are set to accept the correct egress VLAN tags all should be good.
------------------------------
Stefan Pynappels
Escalation Engineer
Imperva
------------------------------
Original Message:
Sent: 11-20-2019 03:04
From: cezmi çal
Subject: Running Virtual Appliance as Bridge Mode on ESX
Hi everyone,
If we want to deploy virtual appliance as bridge mode on ESX, how should we configure virtual switches and port groups on ESX to pass traffic through the gateway without latency or other network issues?
#DatabaseActivityMonitoring
#On-PremisesWAF(formerlySecuresphere)
#AllImperva
------------------------------
cezmi çal
technical expert
Barikat Cyber Security
------------------------------