For the dhcp mode, the WAN IP for NAT is assigned by DHCP from CMTS's CPE domain. No public LAN interface is created for this mode. For the static_and_routed mode, a public LAN interface is created using the setting from hitronGwMgmtPubLanIP and hitronGwMgmtPubLanNetmask. This public LAN IP is also used as the source IP for NAT traffic from the private LAN of this device. In this mode, the GW IP in the RIP message would be the CM's RF IP by default. To allow the traffic routing for this public LAN subnet, the rip daemon must be enabled and the hitronGwMgmtRIPCtrl OIDs must be setup appropriately. Also, if the GW IP in the RIP message is the RF interface, the hitronGwMgmtWanDnsServerTable should be setup appropriately since there is no DHCP's DNS information available in such setup. For the dhcp_and_routed mode, a public LAN interface is created using the setting from hitronGwMgmtPubLanIP and hitronGwMgmtPubLanNetmask. This public LAN IP would not be used as the source IP for NAT traffic. There is a extra DHCP WAN IP would be used for NAT traffic. To allow the traffic routing for this public LAN subnet, the rip daemon still needs to be be enabled and the hitronGwMgmtRIPCtrl OIDs must be setup appropriately. For the static-WAN-for-NAT mode, the WAN IP for NAT is assigned manually from CMTS's CPE IP domain. No public LAN interface is created for this mode. When the WAN is set to static-WAN-for-NAT mode, the hitronGwMgmtStaticWANIP, hitronGwMgmtStaticWANNetmask, hitronGwMgmtStaticWANGWIP and hitronGwMgmtWanDnsServerTable MUST all be configured with appropriate values. If they are not configured with hitronGwMgmtWANCtrlMode=4, the device would not work appropriatelt.