Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| en:dpi:bras_bng:bras_l2_vlan_term:ttl:start [2023/10/13 14:27] – ↷ Links adapted because of a move operation elena.krasnobryzh | en:dpi:bras_bng:bras_l2_vlan_term:ttl:start [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== TTL ====== | ||
| - | {{indexmenu_n> | ||
| - | By default, Stingray Service Gateway in L2 BRAS mode does not change TTL packets, that is, it is transparent for utilities, such as traceroute. This is not always convenient: for example, the subscriber will not see his subscriber gateway in the output of the traceroute command. | ||
| - | |||
| - | In SSG 10.1 an additional parameter '' | ||
| - | |||
| - | < | ||
| - | # Transparent (1) or not (0) SSG in L2 BRAS mode | ||
| - |     # In transparent mode, L2 BRAS does not control the TTL of the packet, it does not send ICMP Time Exceeded when the TTL is exhausted,  | ||
| - | # therefore, for example, the traceroute utility will not recognize the subscriber gateway when tracing. | ||
| - | # In non-transparent mode (0) L2 BRAS corrects the TTL of the packet and sends ICMP Time Exceeded when exhausted. | ||
| - | # Default value: 1 (L2 BRAS is transparent) | ||
| - | # This parameter works only in the DPDK version of SSG | ||
| - | bras_transparency=1 | ||
| - | </ | ||
| - | |||
| - | In the case of '' | ||
| - | |||
| - | For IPv6, a virtual IPv6 address is always used [[en: | ||
| - | |||
| - | <note tip>In the [[dpi: | ||