Configuring Static IP
This Section will walk you through configuring the RG for use of a Static IP
block. As mentioned earlier but repeated here for convieniance is an overview
in differences between ADSL service handling of Static IP service and AT&T U-
verse
• Static IP delivery –
• with your DSL service the DSL modem was often set to bridge mode, one IP address was used at the Access
device on o
ur side as the Gateway IP address and minus the Network and Broadcast IP addresses the rest
were for users to configure on their equipment with the customer device being the next logical hop out
from the Access device.
• With AT&T U-verse
the RG is now our access device for this scenario. It has its own IP for its WAN which is
a sticky dynamically assigned IP. A Virtual port is then created on the LAN side for the Public / Static IP
block and like the DSL Access device uses one IP from the block as the Gateway. The remaining are handed
to the customer device.
• A reason this is different is that the Static IP block is routed to the WAN IP (dynamically assigned) of the RG
and mapped t
o the MAC address of the RG for anti-spoofing purposes.
• The common misconception is that using DMZplus / IP Passt
hrough (depending on device) will completely
remove the RG as the firewall and the Gateway. Neither of them are the case in general. Those modes
pass the sticky DHCP assigned IP of the RG WAN connection, which is separate from the Static IP block , to
the assigned device. Also there is always a portion of the RG’s firewall functionality that remains in place by
design for our U-verse services. This will be discussed in later sections of the document.
Page 16
Comments to this Manuals