Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
en:dpi:dpi_components:platform:faq:net_points:start [2021/07/26 15:12] – edrudichgmailcom | en:dpi:dpi_components:platform:faq:net_points:start [2024/07/29 12:41] (current) – removed elena.krasnobryzh | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== 3 Networking ====== | ||
- | {{indexmenu_n> | ||
- | ===== Does STP transparently pass? ===== | ||
- | Yes. | ||
- | |||
- | ===== Will your solution design allow the following implementation scheme: the server has one 10G network interface. Is it possible to pass traffic through the SSG by organizing two VLANs on this interface (input and output)? ===== | ||
- | No. No future support is planned. | ||
- | |||
- | ===== Can your system arrange a BGP link with a border to export prefixes, which traffic needs to be routed to the SSG? ===== | ||
- | Yes, it can. [[en: | ||
- | |||
- | ===== We connected an internal LAN to try it out, the ping time did not change. Is there supposed to be a delay? ===== | ||
- | If the equipment complies with our recommendations, | ||
- | |||
- | ===== If you implement mirroring, and traffic with different tags will come to in_dev=dna1: | ||
- | The SSG sends a response with the original packet tag if no [[en: | ||
- | |||
- | ===== What is the Stingray Service Gateway? A router, a NAT, a transparent proxy? Or is it transparent to network devices? ===== | ||
- | Stingray Service Gateway is a DPI device, analogous to the Cisco SCE. It works as a bridge, without assigning IP addresses, meaning it is not visible in the network. | ||
- | Latency is not more than 30 microseconds (according to tests it is 16 microseconds), | ||
- | [[en: | ||
- | |||
- | ===== How is aggregated traffic sent? Can ports be grouped via LACP? ===== | ||
- | Yes, you can use LACP, LAGG for traffic aggregation.\\ | ||
- | [[en: |