The following networking bugs apply to the Solaris 10 release.
Sixty-four-bit programs that create PF_ROUTE sockets and parse the contents of RTM_IFINFO messages in the if_msghdr_t structure might work incorrectly unless they are recompiled.
In this Solaris release, IP forwarding is disabled by default. This setting applies to both IPv4 and IPv6 regardless of other system configurations. Systems with multiple IP interfaces that formerly forwarded IP packets by default no longer have this automatic feature. To enable IP forwarding in multihomed systems, administrators must manually perform additional configuration steps.
Workaround: The command routeadm enables IP forwarding. The configuration changes that are the result of routeadm usage persist across system reboots.
To enable IPv4 forwarding, type routeadm -e ipv4-forwarding .
To enable IPv6 forwarding, type routeadm -e ipv6-forwarding .
To apply the enabled IP-forwarding configuration to the currently running system, type routeadm -u.
For more information about IP forwarding, see the routeadm(1M) man page.
A zone can be configured so that the zone's IP address becomes part of an IP Network Multipathing (IPMP) group. The configuration process is documented in How to Extend IP Network Multipathing Functionality to Shared-IP Non-Global Zones in System Administration Guide: Oracle Solaris Containers-Resource Management and Oracle Solaris Zones.
If all the network interfaces in the IPMP group fail, a zone does not boot if it has an IP address that is part of the IPMP group.
The following example illustrates the result if you attempt to boot the zone.
# zoneadm -z my-zone boot zoneadm: zone 'my-zone': bge0:1: could not set default interface for multicast: Invalid argument zoneadm: zone 'my-zone': call to zoneadmd failed
Workaround: Repair at least one network interface in the group.
During system boot, multiple instances might not connect to their LAN Emulation (LANE) instance if more than eight LANE instances are on a single adapter. This bug does not appear at multiuser level.
Workaround: To reinitialize your SunATM network, perform the following steps:
Verify the problem by issuing a lanestat -a command.
Instances that are not connected have Virtual Circuit Identifier (VCI) values of 0 to the LAN Emulation Server (LES) and Broadcast and Unknown Address Server (BUS).
Stop and restart your SunATM network.
# /etc/init.d/sunatm stop # /etc/init.d/sunatm start
Reset netmasks or any other network setup for the SunATM interfaces.
If you configure multiple IP tunnels between two IP nodes, and enable ip_strict_dst_multihoming or other IP filters, packet loss might result.
Workaround: Choose one of the following:
First, configure a single tunnel between the two IP nodes. Add addresses to the tunnel by using the ifconfig command with the addif option.
Do not enable ip_strict_dst_multihoming on tunnels between two IP nodes.