ADC SG-1 Manuel D’Utilisation
A-26
ROUTE
GROUP
route:remote-filter-redirect-gw
This vendor specific sub-attribute defines the remote redirection gateway for redirecting the packets that did not
pass the defined filters. It also works dynamically and allows changing the user-redirected gateway on the fly. Upon
receipt of this sub-attribute the system tunnels the user data to the remote Redirection Gateway using the IP in IP
tunnel protocol. When a redundant RDS is configured the system uses it, if the first prioritized RDS is not
responding.
pass the defined filters. It also works dynamically and allows changing the user-redirected gateway on the fly. Upon
receipt of this sub-attribute the system tunnels the user data to the remote Redirection Gateway using the IP in IP
tunnel protocol. When a redundant RDS is configured the system uses it, if the first prioritized RDS is not
responding.
General:
Format:
adc-avpair = "route:remote-filter-redirect-gw=<gateway IP address>[,<redundant
gateway IP address]>",
Example:
adc-avpair = "route:remote-filter-redirect-gw=192.168.1.23,192.168.1.24",
route:next-hop
This sub-attribute defines the next-hop router to be used for the user connection upstream traffic. It may be activated
dynamically, enabling the change of the next-hop router of a connected user on the fly.
dynamically, enabling the change of the next-hop router of a connected user on the fly.
General:
Format:
adc-avpair = "route:next-hop=<Next-hopIP address>",
Example:
adc-avpair = "route:next-hop=192.168.1.23",
route:nip-pipe-next-hop
The route:nip-pipe-next-hop attribute defines the next-hop router to be used for the traffic destined to a native IP
user. The system when receiving this attribute directs the traffic through the native IP PIP to the defined next-hop.
The attribute may be sent in Access-Accept message and operated during the session lifetime and it overwrites the
current native IP pipe next-hop of the user session. It may be included once in access accept messages, and the
user. The system when receiving this attribute directs the traffic through the native IP PIP to the defined next-hop.
The attribute may be sent in Access-Accept message and operated during the session lifetime and it overwrites the
current native IP pipe next-hop of the user session. It may be included once in access accept messages, and the
Operation Mode:
Access-Accept message
Service-Accept message
Service-Accept message
Vendor-type:
70
Vendor-length =
2 + name length + (7-15)
Operation Mode:
Access-Accept message
Service-Accept message
Service-Accept message
Vendor-type:
71
Vendor-length =
2 + name length + (7-15)