About Host and Network Interface Settings : About base interfaces
  
About base interfaces
You view and modify settings for the appliance primary and auxiliary interfaces under Networking > Networking: Base Interfaces.
When you initially ran the Configuration wizard, you set required settings for the base interfaces for the SteelHead. Only use the controls in this page if you require modifications or additional configuration:
• Primary Interface—On the appliance, the primary interface is the port you connect to the LAN switch. The primary interface is the appliance management interface. You connect to the primary interface to use the web UI or the CLI.
• Auxiliary Interface—On the appliance, the auxiliary interface is an optional port you can use to connect the appliance to a non-Riverbed network management device. The IP address for the auxiliary interface must be on a subnet different from the primary interface subnet.
• Main Routing Table—Displays a summary of the main routing table for the appliance. If necessary, you can add static routes that might be required for out-of-path deployments or particular device management subnets.
IPv6 supported features
IPv6 unsupported features
IPv6 supported features
RiOS supports IPv6 traffic with packet-mode optimization and supports autodiscovery and fixed-target rules. By using autodiscovery or fixed-target in-path rules, RiOS can apply transport and application streamlining techniques (similarly as it does for TCP connections over IPv4) to improve the user experience as the transition to IPv6 continues.
IPv6 is enabled by default. The support for IPv6 is twofold:
• Managing appliances—Support for management access using IPv6 IP addresses on primary and auxiliary interfaces.
• Optimizing IPv6 traffic—RiOS appliances can optimize IPv6 traffic.
This table lists IPv6 support by feature and notes any limits and special considerations.
RiOS IPv6 support includes
RiOS version
Notes
Enhanced autodiscovery of SteelHeads.
9.5 and later for IPv6-only (single-stack) networks
8.5 and later for IPv4 only or dual-stack IPv4 and IPv6 networks
Starting with RiOS 9.5, enhanced autodiscovery is supported for SteelHeads in networks that run IPv6 only (IPv6 single-stack).
SteelHeads running RiOS 8.5 to 9.2 require IPv4 for the TCP inner connections between the peer SteelHeads.
IPv6 support for the SteelHead communication channel with the SteelCentral Controller for SteelHead, appliance manageability (for example, NTP servers, logging, hosts, DNS, Web/FTP proxy, email, and management interfaces) policy pages, and Interceptor Cluster pages (for example, in-path rules and load balancing).
9.5 and later
 
Encrypted Outlook Anywhere latency optimization.
8.6 and later
 
MAPI, eMAPI latency optimization.
8.6 and later
Authentication is over IPv4.
Authentication over IPv6.
8.6 and later
 
Latency optimization of signed-SMB, CIFS/SMB1, SMB2, and SMB3 using IPv6 endpoint addressing.
8.5.2 and later
The authentication stack continues to require IPv4 endpoint addressing.
Conformance with Request for Comments (RFCs) 1981, 2460, 2464, 2710, 3590, 4007, 4291, 4443, 4861, 4862, 4943, 5095, and 5156.
8.5 and later
 
TCP IPv6 traffic interception between source and destination, bandwidth optimization.
8.5 and later
 
Ability to automatically discover fixed-target and pass-through in-path rules, along with ability to deny and reject IPv6 TCP traffic as configured in the in-path rules.
8.5 and later
RiOS doesn’t support the neural framing modes Always, TCP Hints, and Dynamic.
RiOS doesn’t support the Oracle forms and Oracle forms over SSL pre-optimization policies.
HTTP and HTTPS latency optimization for IPv6 TCP traffic.
8.5 and later
 
Ability to configure serial clusters.
8.5 and later
 
Interception of IPv6 traffic for in-path, virtual in-path, and server-side out-of-path configurations.
8.5 and later
WCCPv6 support is not available. Virtual in-path support is PBR. Interceptor deployments are supported in RiOS 9.5 and Interceptor 6.0.
Intercepting and passing through IPv4 and/or IPv6 traffic, depending on the in-path rules.
8.5 and later
 
Ability to detect asymmetric routes for IPv6 TCP traffic; enables connection forwarding of IPv6 TCP traffic in asymmetric conditions.
8.5 and later
The connection-forwarding control channel between the neighbors is strictly IPv4. You must configure IPv4 addresses on the SteelHead appliances' in-path interfaces when using a connection-forwarding control channel.
Ability to configure IPv4 and IPv6 addresses on every in-path interface and intercepting and optimizing IPv4 and IPv6 traffic.
8.5 and later
 
Ability to configure one IPv6 address configuration for every in-path interface.
RiOS intercepts and optimizes traffic matching the scope of the IPv6 address configured on the in-path interface. Not applicable for a link-local address configured on the in-path interface.
8.5 and later
RiOS passes through IPv6 TCP traffic not matching the scope of the IPv6 address configured on the in-path interface.
Ability to configure IPv6 addresses on any in-path interface.
8.5 and later
RiOS 8.5 - RiOS 9.2: IPv6 TCP inner connections only in fixed target cases.
Enhanced autodiscovery of SteelHead appliances for IPv6 TCP traffic.
8.5 and later
RiOS 8.5 - RiOS 9.2: TCP inner connections between the peer SteelHead appliances is IPv4 only. RiOS 9.5 allows for IPv6 TCP inner connections between peers.
Simplified routing for IPv6 TCP traffic.
8.5 and later
 
Connection forwarding for IPv6 traffic in multi-interface mode.
8.5 and later
The control connection between neighbors is still IPv4 only.
When multiple interface support in the Networking > Network Integration: Connection Forwarding page is not enabled, IPv6 traffic is passed through.
Ability to configure peering rules for IPv6 traffic.
8.5
The peer client-side SteelHead IP address is IPv4 only.
Ability to configure IPv6 addresses in Single Ended Interception (SEI) rules under Optimization > Network Services: Transport Settings.
8.5 and later
 
Global and automatic kickoff for pass-through TCP IPv6 traffic.
8.5 and later
 
Ability to configure asymmetric VLANs for IPv6 TCP traffic.
8.5 and later
 
 
IPv6 unsupported features
These features are not IPv6 compatible:
• Transparency
• NetFlow
• Path selection
• QoS
• Host labels
• IPsec
• Automatic address assignment through DHCPv6
• Multicast listener discovery
• IPv6 stateless address autoconfiguration
• WCCP using anything other than IPv4 outer connections