ДП
Но эти чудо опции никто даже наизусть не знает
Size: a a a
2016 December 26
TM
Только опционально если
ДП
Вот 82 все знают
ДП
А есть тоже самое но для в6
ДП
Но номер другой
VG
там и запоминать не надо, option_interface_id
VG
правда формат не стандартизирован. и разное железо туда может пихать разное. от текстового имени интерфейса, до айдишников
TM
У option82 тоже сразных коммутаторов разный формат
G
Using AAA RADIUS Server to Obtain IPv6 Prefixes for NDRA
When the BNG needs to obtain a prefix for NDRA, it uses the values in one of the following RADIUS attributes that it receives in Access-Accept messages from the RADIUS server:
Framed-IPv6-Prefix—The attribute contains an IPv6 prefix that the BNG can send to the CPE in router advertisement messages.
Framed-IPv6-Pool—The attribute contains the name of an NDRA pool configured on the BNG from which the BNG can select a prefix to include in router advertisements.
When the BNG needs to obtain a prefix for NDRA, it uses the values in one of the following RADIUS attributes that it receives in Access-Accept messages from the RADIUS server:
Framed-IPv6-Prefix—The attribute contains an IPv6 prefix that the BNG can send to the CPE in router advertisement messages.
Framed-IPv6-Pool—The attribute contains the name of an NDRA pool configured on the BNG from which the BNG can select a prefix to include in router advertisements.
VG
prefix - для wan интерфейса
TM
Это как я понял когда BNG будет шлюзом для всех клиентов
VG
pool - для lan во внутрь
VG
хотя. про пул вру скорее всего
G
Link-local address assignment for local connectivity to the BNG
Global address assignment for global connectivity
The process is as follows:
During IPv6CP negotiation to establish the PPPoE link between the BNG and the CPE, an interface identifier is negotiated for the CPE.
The CPE creates a link-local address by appending the interface identifier with the IPv6 link-local prefix (FE80::).
Note: When the interface ID is 0, such as for Windows 7 clients, PPP uses the subscriber’s session ID in place of the interface ID.
The CPE now has IPv6 connectivity to the BNG, and it can use NDRA to obtain its global IPv6 address.
The CPE sends a router solicitation message to the BNG.
The BNG responds with a router advertisement message that includes an IPv6 prefix with a length of .
This prefix can come directly from a local NDRA address pool configured on the BNG.
If you are using AAA, a RADIUS server can specify the prefix in the Framed-Ipv6-Prefix attribute, or it can specify an NDRA pool on the BNG from which the prefix is assigned in the Framed-Ipv6-Pool attribute.
When the CPE receives the 64-bit prefix, it appends its interface ID to the supplied prefix to form a globally routable 128-bit address.
The CPE verifies that the global address is unique by sending a neighbor solicitation message destined to the new address. If there is a reply, the address is a duplicate. The process stops and requires operator intervention.
Global address assignment for global connectivity
The process is as follows:
During IPv6CP negotiation to establish the PPPoE link between the BNG and the CPE, an interface identifier is negotiated for the CPE.
The CPE creates a link-local address by appending the interface identifier with the IPv6 link-local prefix (FE80::).
Note: When the interface ID is 0, such as for Windows 7 clients, PPP uses the subscriber’s session ID in place of the interface ID.
The CPE now has IPv6 connectivity to the BNG, and it can use NDRA to obtain its global IPv6 address.
The CPE sends a router solicitation message to the BNG.
The BNG responds with a router advertisement message that includes an IPv6 prefix with a length of .
This prefix can come directly from a local NDRA address pool configured on the BNG.
If you are using AAA, a RADIUS server can specify the prefix in the Framed-Ipv6-Prefix attribute, or it can specify an NDRA pool on the BNG from which the prefix is assigned in the Framed-Ipv6-Pool attribute.
When the CPE receives the 64-bit prefix, it appends its interface ID to the supplied prefix to form a globally routable 128-bit address.
The CPE verifies that the global address is unique by sending a neighbor solicitation message destined to the new address. If there is a reply, the address is a duplicate. The process stops and requires operator intervention.