Rebuilding the routing tables

If the file system encounters a situation where it believes that the IPv4 routing information or the IPv4 home IP address information needs to be re-synchronized, it can issue the SIOCMSRBRTTABLE ioctl on the master socket. If the file system encounters a situation where it believes that the IPv6 routing information or the IPv6 home IP address information needs to be re-synchronized, it can issue the SIOCMSRBRT6TABLE ioctl on the master socket. If the IPv6 home IP address information needs to be re-synchronized, SIOCMSRBHOMEIF6 can also be used. These ioctls cause the prerouter to flush the information for the file system and rebuild it from scratch.

When the prerouter receives the SIOCMSRBRTTABLE ioctl (or SIOCMSRBRT6TABLE for IPV6) from the TP, it does the following:

For SIOCMSRBRTTABLE, if the TP returned a value of -1 for Iocn_NetConfLength on the initial SIOCGIFCONF (as described in Initializing an AF_INET (IPv4) transport driver), the prerouter only issues the SIOCGRTTABLE ioctl to rebuild its home, host, and network routing tables. Otherwise, the prerouter issues both the SIOCGIFCONF ioctl to rebuild its home interface table and the SIOCGRTTABLE ioctl to rebuild its host and network routing tables.
For SIOCMSRBRT6TABLE, if the TP returned a value of -1 for NchNumEntryRet on the initial SIOCGHOMEIF6 (as described in Initializing an AF_INET6 (IPv6) transport driver), the prerouter only issues the SIOCGRT6TABLE ioctl to rebuild its home, host, and network routing tables. Otherwise, the prerouter issues both the SIOCGHOMEIF6 ioctl to rebuild its home interface table and the SIOCGRT6TABLE ioctl to rebuild its host and network routing tables.

Note: If a user does a socket request during a rebuild, the user may or may not be able to connect with the file system. The routing table is in flux.