Escolar Documentos
Profissional Documentos
Cultura Documentos
In cases where the 2Wire HomePortal or OfficePortal is used with multiple broadband IP addresses, it is required that the HomePortal be properly configured to utilize these IP addresses with local network devices. This document describes the setup step to configure a 2Wire HomePortal for use with multiple broadband static IP address on the SBC ADSL network. Although the term "HomePortal" is used in this document, these instructions can also be used for setting up the 2Wire OfficePortal as well. There are some pre-requisites to using Multiple Broadband Addresses: The associated service providing the multiple IP addresses has been ordered and installed. The IP address and networking information has been identified for the subscribed service. The HomePortal is running version 3.5.5 or later of the 2Wire HomePortal system. The network devices are already configured for TCP/IP networking and are connected to the HomePortal LAN via one of the available interfaces (Ethernet, USB, HPNA or 802.11b Wireless.)
The configuration process can be divided into four logical steps. 1. Setup and configure the HomePortal for broadband access using the first IP address 2. Enable the Bridge Network function of the HomePortal and configure it with the appropriate subnet mask 3. Assign the broadband IP address(es) to the desired network devices 4. (Optional) Configure firewall rules to direct unsolicited traffic to the associated network devices
PPPoE Users
Go to http://homeportal/setup and use the PPPoE keycode (522P-22P4-6262-22AT-F2NV) to establish broadband connectivity with one IP address. Verify Internet connectivity by accessing public websites.
Page 1 of 6
Page 2 of 6
Note: On the OfficePortal, this information can also be set using the standard web pages in addition to those under the MDC.
Figure 1
Page 3 of 6
3. DHCP Fixed Public Network The network client is permanently assigned one of the broadband IP address. The address will not change until the HomePortal is reconfigured via the Address Allocation page. This will be the most common configuration for publicly accessible network devices. In all the above cases, the network device should be configured to enable their DHCP client. From this point on, the IP addresses for these LAN devices are managed by the HomePortal. In addition, a LAN device can be configured with a static IP address hard coded in the TCP/IP settings for that device. The IP address can be from either the DHCP Private Network addresses or from the DHCP Bridged Network addresses. When a DHCP Private Network address is statically assigned to a LAN device, the proper range must be used. The default range is 172.16.0.0, so the network device may statically use 172.16.1.1 through 172.16.1.32, inclusive. Devices assigned with these addresses act as if they were assigned an IP address in mode 1 above. When a DHCP Bridged Network address is statically assigned to a LAN device, the device assigned with this address acts as if they were assigned an IP address in mode 3 above. Use the IP address information as provided by the ISP. The HomePortal will automatically detect the usage of a broadband IP address on the LAN network and correctly route the return traffic to the appropriate LAN device. Once a broadband IP address has been detected by the HomePortal as being statically coded on the PC, its entry in the Address Allocation page will no longer be displayed. Note: The ability to use DHCP in assign WAN addresses to LAN devices is different from how some other routers operate. These other routers usually require that the address be hard coded on the LAN device.
Page 4 of 6
Figure 2
Page 5 of 6
Sample Configuration
In this sample configuration, the network consists of a public web server, a private web server, a public FTP server and a number of desktop devices. Only the public servers need be accessed from outside the network. The FTP server needs to be accessed from inside 1. Configure the HomePortal for Internet access. Enable the Bridge Network features with the proper subnet mask. 2. Use DHCP Private Network for all the desktop devices by default. These devices will use NAPT and share one of the broadband IP addresses. Addresses given out by the DHCP server in the HomePortal will range from 172.16.1.33 to 172.16.1.250. 3. Set the FTP server to one of the Fixed Bridged Network IP addresses. This will route all incoming traffic for the specific public IP address to the designated network device. In this case, the FTP server. Optionally if the FTP server machine does not have a DHCP client, the server could be configured with a public static IP address and the HomePortal will correctly route the traffic. If unsolicited inbound traffic is expected, the firewall must be configured to allow FTP traffic to pass. This is done from the Firewall Settings link of the MDC (http://homeportal/management).This can also be accomplished using the Firewall tab of the main GUI (http://homeportal). 4. Similar to the FTP example, set the public Web server to one of the Fixed Bridged Network IP addresses. This will route all traffic to the specific pubic IP address to the designated network client. The firewall must be configured (as described in step three above) to route inbound port 80 traffic to the server. 5. The private Web server should be set to a static private IP address, so that it is always accessible at the same address to the local desktop clients. For example, use 172.16.1.5 as the servers IP address.
Page 6 of 6