You can configure the IPv6 stack by modifying the default ip6.cfg file found under sys:\etc. You can also use the rtadvd.cfg file in conjunction with the ip6.cfg file to make the node function as an advertising interface. This section describes the formats for the following configuration files:
The configuration of the IPv6 stack is possible through the ip6.cfg file, which is placed under sys:\etc. To configure the IPv6 stack, modify the default file provided with the stack.
[Interface All] Router Yes | No Autotunnel Yes | No 6to4 Yes | No [Interface Interface name] Addr v6_address_128_bit Prefixlen Prefix_length_of_Addr
mtu MTU_for_this_interface rsdelay Router_solicitation_delay_in_seconds rsinterval Delay_between_the_router_solicitation_in_seconds rstransmits Number_of_router_solicitations_transmitted autoconf Yes | No acceptra Yes | No acceptredirect Yes | No hoplimit Hop_limit_to_be_specified_in_the_outgoing_packet delayFirstProbeTime Neighbor_discovery_parameter baseReachableTime Neighbor_discovery_parameter retransTime Delay_between_successive_neighbor_solicitations sendRedirect Yes | No DadTransmits [1 - 3]
[Interface All] Router Yes Autotunnel No 6to4 No [Interface CE100B_1_EII] Addr 3ffe:501:ffff:100::1 Prefixlen 64 mtu 1280 rsdelay 1 rsinterval 4 rstransmits 3 autoconf Yes acceptra Yes acceptredirect Yes hoplimit 255 delayFirstProbeTime 5 baseReachableTime 30 retransTime 1 sendRedirect Yes DadTransmits 3
Table 3-1 For the Common Interface Record
Field Name |
Description |
Default Value |
---|---|---|
Router |
Router/Host functionality |
No (Host) |
Autotunnel |
Autotunnel enable/disable |
No (disable) |
6to4 |
6to4 tunnel enable/disable |
No (disable) |
Table 3-2 For the Interface-Specific Record
You can use the rtadvd.cfg file in conjunction with the ip6.cfg file to make the node function as an advertising interface. For the values in the rtadvd.cfg file to take effect, you need to set the Router field to Configuration File Format.
in the ip6.cfg file. Refer toYou need to set the following file formats to configure router advertisement (interface specific):
[Interface Interface_name]
RASendAdvertisements Yes | No
RAMaxInterval [4 - 1800]
RAMinInterval [3 - 0.75 * RAMaxInterval] seconds
RAManagedFlag Yes | No
RAOtherConfigFlag Yes | No
RALinkMTU [0 - LinkMTU]
RAReachableTime [0 - 3,600,000]
RARetransTimer Retransmit_time_in_milliseconds
RACurHopLimit Hop_limit
RADefaultLifeTime [0 | MaxRtrAdvInterval - 9000]
NOTE:This record can occur only once for an interface.
You need to set the following file formats to configure the Prefix list to be advertised for each interface:
[RAPrefixListIf Interface name]
Prefix Prefix_to_be_advertised
PrefixLen [64 - 128]
RAValidLifeTime Valid_life_time_of_the_Prefix_in_seconds
RAPreferredLifeTime Preferred_life_time_of_the_Prefix_in_seconds
RAAutonomousFlag Yes | No
RAOnLinkFlag Yes | No
RAReal_Fixed_TimeFlag Real | Fixed
NOTE:This record can occur multiple times for an interface, depending on the number of prefixes that are to be advertised.
[Interface DLKRTS_EII ] RASendAdvertisements Yes RAMaxInterval 20 RAMinInterval 3 RAManagedFlag Yes
RAOtherConfigFlag Yes
RALinkMTU 0
RAReachableTime 200
RARetransTimer 3
RACurHopLimit 255
RADefaultLifeTime 1800
[RAPrefixListIf DLKRTS_EII]
Prefix 3ffe:dad::0
PrefixLen 64
RAValidLifeTime 300
RAPreferredLifeTime 250
RAAutonomousFlag Yes
RAOnLinkFlag No
RAReal_Fixed_TimeFlag Real
[RAPrefixListIf DLKRTS_EII]
Prefix 3ffe:FEED::0
PrefixLen 64
RAValidLifeTime 50
RAPreferredLifeTime 30
RAAutonomousFlag Yes
RAOnLinkFlag No
RAReal_Fixed_TimeFlag Fixed
Table 3-3 For the Router Advertisement Record
Table 3-4 For the Prefix Description Record