Motorola NVG510 User Manual download pdf (Page 2)

Some of the Differences

While there are quite a few differences overall between the two services, from the technology to the topology we will cover some of them which can in

one way or another more commonly impact you the customer.

• Various means of delivering the “last mile” of service. With your DSL service it is almost all ADSL technology. With AT&T U-verse there are various

means of connecting to the service. There are VDSL, Fiber and IP-DSL depending on where your home or office is located. Closer in and you are

more likely to get service via VDSL, in Apartments or other similar locations you may get service via Fiber, and if you are outside those areas but

within ADSL ranges you are more likely to be served by ADSL2+.

• Authenticationonto the network is different, there is no PPPoE authentication on the AT&T U-verse network.

• Due to the architecture of the AT&T U-verse platform, Bridge mode is not supported on the network nor on the RG. There will be separate sub-

sections dealing with how best to configure the RG for your particular need instead.

• Ping and Trace– by default AT&T U-verse RG’s are set to not respond to ICMP requests such as Ping and Trace. This is configurable through the user

interface. Also as the network utilizes MPLS your trace routes will often have lines which time out. This is not an indicator of trouble it is just that

that particular hop or node is not set to reply to ICMP requests. This is very much a common policy today as answering ICMP requests adds to CPU

utilization and can impact network performance when attacks are made via mass ICMP request attempts commonly referred to as Denial of Service

attacks.

• Use of 10.x.x.x IP addresses – the DHCP server in the RG is configured not to allow 10.x.x.x IP scope to be set as the DHCP IP addresses. You may

continue to use 10.x.x.x addresses on the LAN side of a 3

party routerbut the RG can not be configured to hand out 10.x.x.x. IP addresses.

• 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 our 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. (For those with a single Static IP there is no equivalent in U-verse

today.)

Also note that you will not be able to keep any existing Static IP addresses. They are a part of a larger block routed for DSL service.

• 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 common misconception is that using DMZplus / IP Passthrough (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.

These are some of the differences that are most likely to impact you in your migration.

Page 2

1 2 3 ... 40

Comments to this Manuals

No comments

Motorola NVG510 User Manual Page 2

Comments to this Manuals

Related products and manuals for Gateways/controllers Motorola NVG510