No. This is not planned for future support.
Yes, this is possible. More about router settings.
The delay on the device, if the hardware meets our recommendations, does not exceed 30 µs (microseconds) or 0.03 ms (milliseconds). 'Ping' measurements start at 1 ms. Measuring such delays requires special software and equipment; in our lab, we use counters in nanoseconds supported by modern network cards.
SSG will send a response with the original packet tag if VLAN translation settings have not been applied.
SSG is a DPI device, similar to Cisco SCE. It operates as a bridge, without IP addressing, and is invisible on the network.
The delay when using it is no more than 30 microseconds (based on tests, 16 µs), which is virtually indistinguishable from a direct connection.
See detailed connection diagrams for SSG.
Yes, you can use LACP and LAG for traffic aggregation.
See detailed connection diagrams for SSG.
It depends on the task: if the platform connects as a DPI, then after the termination point; if BRAS, NAT functionality is required, then the SSG platform performs traffic termination directly.
Connection diagrams.
Apply the following settings in the /etc/sysctl.conf file:
net.core.netdev_max_backlog=10000 net.core.somaxconn=262144 net.ipv4.tcp_syncookies=1 net.ipv4.tcp_max_syn_backlog = 262144 net.ipv4.tcp_max_tw_buckets = 720000 net.ipv4.tcp_tw_recycle = 1 net.ipv4.tcp_timestamps = 1 net.ipv4.tcp_tw_reuse = 1 net.ipv4.tcp_fin_timeout = 30 net.ipv4.tcp_keepalive_time = 1800 net.ipv4.tcp_keepalive_probes = 7 net.ipv4.tcp_keepalive_intvl = 30 net.core.wmem_max = 33554432 net.core.rmem_max = 33554432 net.core.rmem_default = 8388608 net.core.wmem_default = 4194394 net.ipv4.tcp_rmem = 4096 8388608 16777216 net.ipv4.tcp_wmem = 4096 4194394 16777216
Example:
tcpdump. On the client's interface, mtu = 9000. neighbor 95.167.18.57 { traceoptions { file as12389.log size 1m files 3; } description "-= RT AS12389 Upload =-"; import [ bogus-reject MM-IN ]; export REJECT-ALL; peer-as 12389; tcp-mss 1460; } tcp-mss 1460;