Motorola 800 Hgv B Manual

							
Configuring Mulitple Static IP Addresses
69
If you did not receive a subnet mask from your ISP, but were provided with a number of addresses has been, 
you can look up the associated subnet mask in the  table below. Because this information may have been 
identified in a number of different ways, it has  been presented here in a number of different ways.
Step 2: Allocate Public IP Addresses to the LAN Clients
This step requires that all network devices that you  wish to configure with a broadband IP address be turned 
on and connected to the 3700HGV-B. Devices should be conf igured to use their DHCP client for obtaining 
an IP address, although this is not an abs olute requirement as identified below.
Once the gateway is configured to use multiple br oadband IP addresses, network devices can be configured 
for one of three modes. Access the Address Allocation  page of the MDC to select the desired option (Figure 
2) for each LAN device. This information can also be set by clicking the 
EDIT ADDRESS ALLOCATION button on 
the Home Network - Advanced Settings page.
 Mode 1: DHCP Private Network. The network client is  given a private IP address on the private network 
(Default is the 192.168.1.0 network). This is the  normal mode of operation for all LAN devices by 
default (with or without the us e of multiple broadband addresses.)
 Mode 2: Public Fixed Network. The network client  is given one of the currently available broadband IP 
addresses. The address may change as the IP address l ease is renewed, but will always come from the 
pool of available broadband IP addresses.
 Mode 3: DHCP Fixed Address. The network cli ent is permanently assigned one of the broadband IP 
addresess. The address will not change until the gate way 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 devices should  be configured to enable their DHCP client. From this 
point on, the IP addresses for these LAN devices ar e managed by the 3700HGV-B. However, if DHCP is 
unavailable or its use undesirable, devices can be  configured (hard-coded) with a static IP address.
For devices in the Private Network (NAT), the proper  range must be used. The default range is 192.168.1.0, 
so the network device may statically use 192.168. 1.1 through 192.168.1.64, inclusive. Devices assigned 
with these addresses act as if they we re assigned an IP address (Mode 1 above).
To t a l  
Address 
Used by the 
Subnet CIDR
Number of 
Useable 
AddressesAddress 
Required for 
DSL Router Addresses 
Available for 
LAN 
Devices Subnet Mask to Use
8 /29 6 1 5 255.255.255.248
16 /28 14 1 13 255.255.255.240
32 /27 30 1 29 255.255.255.224
64 /26 62 1 61 255.255.255.192
128 /25 126 1 125 255.255.255.128
256 /24 254 1 253 255.255.255.0 
						

							
Configuring Mulitple Static IP Addresses
70
For devices using the Public Network addresses, simply configure the device to use the IP address (subnet 
mask and default gateway) as assigned by the ISP . The gateway will automatically detect the usage of a 
broadband IP address on the LAN network and correctly ro ute the return traffic to the appropriate LAN 
device. Once a broadband IP address has been detected by  the gateway as being statically coded on the 
device, its entr y in the Address Allo cation page will no longer be displayed.
Note: The ability to use DHCP in assigning WAN addres ses to LAN devices is different from how 
some other routers operate. T hese other routers usually requi re that the address be hard coded 
on the LAN device.
Upon successful configuration of the gateway, refresh t he IP address of the network device (this may require 
restar ting that device). It should now have the des ired public, or private, IP address assigned by the 
3700HGV-B. Confirm proper configuration by attempting to access the public Internet.
 
Figure 2
Step 3: Configure Firewall Rules
LAN devices using addresses from the Public Network ar e still protected by the gateway firewall. To allow 
unsolicited inbound traffic to any of these LAN devices,  you must modify the firewall settings specified for 
that device. That is, a LAN device can receive i nbound traffic associated with outbound traffic (e.g., web 
browsing) but needs to have a firewall ru le established to function as a server.
To change the firewall settings, access the Firewall - Settings page of the MDC or the Firewall Settings page 
of the standard web pages to configure the Hosted applications allowed for each device to be used with 
unsolicited traffic.
Note: This is different from how some other rout ers operate. These other routers automatically 
allow all traffic to pass through from the WAN to the LAN devices configured with WAN IP 
addresses.
The type of traffic to be received by the device det ermines the type of firewall configuration required:
 If the device only requires the public IP address then no rules need to be established.
 In some cases, all broadband traffic destined for a device is to be passed to that device. In this case,  the 3700HGV-B should be configured to 
Allow all applications for the specific device. 
 In other cases, only the traffic associated with a specific application (e.g., ftp server) is to be passed to  a device. In this case, the “hosted application”  feature of the 3700HGV-B will be used to configure 
which traffic to send to the device.
Note: The 2Wire firewall only allows traffic for a public network IP address to be directed to a 
local LAN device with the same public network IP  address. That is, except for traffic sent to the 
single broadband IP address assigned to the router  and shared through NAPT, traffic sent to other 
specific broadband IP addresses associated with  the connection cannot be directed to local LAN 
devices that may be using private IP addresses. 
						

							
Configuring Mulitple Static IP Addresses
71
Sample Configuration
In the sample network below, the customer has subscribed to ser vice with an 8 IP address subnet (i.e., 5 
usable broadband IP addresses). The customer wants to  host dedicated VPN and web servers in addition to 
having PCs with private IP addresses. The subnet  assigned to the customer is 208.35.230.192/29. The 
sample network is shown in Figure *.
Figure *. Sample Network
Following are the steps required to config ure the gateway for this configuration. 
						

							
Configuring Mulitple Static IP Addresses
72
First, configure the gateway to suppor t “Public Network” static IP addressing using the ser vice provider 
assigned IP addresses of 208.35.206.198 for the  gateway and a subnet mask of 255.255.255.248 as 
shown in Figure xxx. Click 
SAVE to ensure the changes are saved.
Figure xx
Second, assign static IP addresses to the Network  Ser vers from the available. This can be done by hard 
coding these on the network interface for t hese ser vers or via the gateway using DHCP . The later is shown in 
this example.
Check that the gateway-connected network interface for eac h server is configured as a DHCP client (i.e. to 
“Obtain an IP address automatically”). 
						

							
Configuring Mulitple Static IP Addresses
73
Edit the addresses assigned to each device as shown below. Assign an available static IP address to each 
ser ver, selecting the “DHCP Fixed” option from the lis t box next to each ser ver name. For this example, 
select the following options:
Click 
SAVE after making your selections in order  to ensure the addresses are properly assigned.
After this step, restar t each server so that  it is issued the desired static IP address.
Finally, configure the gateway to allow the appropriate broadband traffic to flow to the network ser vers.
In this example, all broadband traffic destined for the VP N ser ver will be allowed. Allowing all inbound traffic 
disables the inbound port blocking feat ure of the gateway firewall. However, stateful packet inspection will 
still occur as the traffic passes through the gatewa y providing continued protection against Denial of 
Ser vice and other common Internet attacks. Device IP Address
VPNSRV DHCP Fixed 208.35.230.193
WEBSRV DHCP Fixed 208.35.230.194 
						

							
Configuring Mulitple Static IP Addresses
74
In the case of the Web Ser ver, the “hosted application” feature of the 3700HGV-B will be used. This feature 
provides a quick and easy way to allow specific types  of unsolicited traffic through the 3700HGV-B firewall. 
For the web ser ver, this includes traffic on TCP port 80 (http).
Select the computer to which you would like to have a ll data sent. In this example, the computer selected is 
VPNSRV.
Select 
Allow all applications and click DONE. Doing so will allow all inbound data destined for the selected 
ser ver to pass through the firewall. 
						

							
Configuring Mulitple Static IP Addresses
75
To allow all traffic for the web ser ver, configure the gateway to allow the specific type of the associated 
inbound por ts to flow to the ser ver. In this example, the computer WEBSRV is selected as the destination 
for the web ser ver traffic.
Select the 
Allow individual application(s) option.
Select the appropriate application fr om the application list, click the 
ADD buttton, and then click the DONE 
button. In this example, the application type is “Web Ser ver.”
When the configuration has been completed, you shoul d confirm your firewall settings on the gateway. 
						

							
76
LEDs
LED overview
The 2Wire Gateway has numerous indicator lights that can be used to diagnose installation and connection 
problems. The following table describes  how to interpret the indicator lights.
Power LED
Solid green The gateway is powered on.
Off The gateway is not receiving power.
Flashing red Power-On Self-Tes t (POST) is in progress.
Solid red POST failure (not bootable), or a gateway malfunction  occurred.
Local Ethernet, Wireless, 
USB - PC, or MoCA LEDs
Solid green  The device has established a link.
Off The device is not connected.
Broadband LED
Solid green Broadband connection established via DSL or  Ethernet.
Off No physical signal detected.
Flashing green Attempting broadband connection.
Flashing red No broadband signal (E thernet or DSL) detected on 
line.
Flashing green and red The gateway has been unable to establish a  broadband connection for more than three 
consecutive minutes. 
						

							
LEDs
77
Service LED 
Solid green IP connected (The residential gateway has a WAN IP  address from IPCP or DHCP and the broadband 
connection is up, or a static IP address is configured, 
PPP negotiation has successfully completed - if used - 
and the broadband connection is up).
Off The gateway is not receiving power. The gateway is in bridged mode.
Broadband connection is not established.
Flashing green Attempting to connect via PPP .
Attempting to establish IEEE 802.1X authentication.
Attempting to obtain DHCP information (for non-PPP 
connections).
Solid red The gateway could not establish an IP connection (for  example, no DHCP response, no PPPoE response, 
PPPoE authentication failed, no IP address from 
IPCP). 
						

							
78
Glossary
ATA (Analog Telephone Adapter). IP device (often Ethernet) with one or more ports for connecting analog 
telephones.
Balun.  A circuit that allows signals to flow smoothly  between Twisted Pair and Coax (term derived from 
BALanced / UNbalanced transmission medium).
Coax Splitter.  Used to divide RF signals over Coax allowing more devices to be connected.
Diplexer.  A bi-directional frequency specific splitter that will aid in VDSL and Video (MoCA, RF) deliver y over 
the same Coax wiring; two different types will be used for Splitters and RG locations.
DSL Splitter.  Used to separate the VDSL signals from the TDM voice service installed in the NID.
Jumpers.  Shor t cables that connects outlets to  CPE, CPE to CPE, or CPE to devices.
SIP (Session Initiated Protocol).  VoIP signaling method used to set up and complete VoIP calls.