09-23-2013 07:27:39 AM
ATT Friday forced an upgrade on us from a DSL Line to Uverse Internet.
Our prior LAN settings were simple enough and worked great with the ATT Motorola modem/router.
The Router Access was 18.104.22.168 (having been changed from the default 192.168.1.254)
Subnet mask 255.255.255.0
DHCP Start Address 22.214.171.124
DHCP End Address 126.96.36.199
In trying to change the new router's settings:
Home Network> Subnets & DHCP > Private LAN Subet > Device IPv4 Address
When the preferred address is entered (188.8.131.52) we encounter an error of "Address must be on network (184.108.40.206)"
Was hoping the setup would be as simple as the previous time? Any help?
Solved! Go to Solution.
09-23-2013 07:32:13 AM
It sounds like your subnet mask is not correct.
default for (what used to be) a Class C address is the familiar "255.255.255.0"
If, for some reason, you subnetted that address, or if the provider gave you a small block of addresses (if you tell us how many, we can tell you the correct subnet mask), the mask will be something like 255.255.255.248 or 255.255.255.240
09-23-2013 07:43:08 AM
you are right, I notice that the machine I am on that has been assigned an IP address using the DHCP shows the subnet mask as 255.255.255.240
The current settings on the NVG510 read:
Subnets & DHCP>
Device IPv4 Address: 192.168.1.254
Subnet Mask: 255.255.255.0
DHCPv4 Start Address: 192.168.1.64
DHCPv4 End Address: 192.168.1.253
again, I'd just like to alter the Device Address to 220.127.116.11 and change the start and end addresses.
09-23-2013 09:00:28 AM
09-23-2013 09:05:48 AM
09-23-2013 11:25:38 AM
Certainly appreciate all the help.
Here is as much detail as I can think of (not networking expert). Trying to get things back as close to OLD SETTINGS as possible (after DSL switched out for uVerse).
OLD SETTINGS (ATT DSL):
Netopia-3000, model 3347-02, software version 7.8.1r2
LAN IP Interface >
Enable Interface - checked
IP Address 18.104.22.168 (changed from default of 192.168.1.254)
IP Netmask 255.255.255.0
Restrictions - none
no advanced settings, no IP Subnets
DHCP Server >
Server mode - Server
Starting IP Address 22.214.171.124
Ending IP Address 126.96.36.199
Lease Period 01:00:00:00
WAN IP Interfaces
PPP over Ethernet vcc1
Enable Gateway option -checked
Interface Type PPP vcc1
WAN IP Interface (PPP over Ethernet vcc1) settings >
Enable Interface - checked
Address mapping (NAT) - checked
Restrictions - none
ISP Username xxxx
ISP Password xxxx
Connection Type - always on
Domain Name att.net
Primary DNS 188.8.131.52
Secondary DNS 184.108.40.206
NEW SETTINGS (ATT UVERSE, as per ATT installer departure from premisis)
Device and Broadband settings as per ATT installer & working.
|Device IPv4 Address||192.168.1.254|
|DHCPv4 Start Address||192.168.1.64|
|DHCPv4 End Address||192.168.1.253|
|DHCP Leases Available||197|
|DHCP Leases Allocated||6|
|DHCP Primary Pool||Public|
Configure > ports 1-4 all auto
Wireless - working
Mac Filters - none assigned
Private LAN Subnet
|Device IPv4 Address 192.168.1.254|
|Subnet Mask 255.255.255.0|
|DHCPv4 Start Address 192.168.1.64|
|DHCPv4 End Address 192.168.1.253|
Is it possible to replicate what we had previously "OLD SETTINGS" and have the DHCP server issuing IP addresses in the 195.10.10.xxx ranges? When trying to do so, error message is.
Address must be on network (192.168.1.0)
09-23-2013 01:27:14 PM
Not sure why it should matter why my private LAN settings are?
Because 195.10.10.x is not a private LAN. Those IP addresses belong to someone else, assigned to them by RIPE (IP addressing registry for Europe). If you were to try to pull up a web site hosted by the company that owns those IP addresses, you wouldn't be able to because your internal routing wouldn't properly route the request.
IP addressing is handled by international numbering authorities and is very specific in the way they're handed out. You can't just "pick" some addresses at random and use them. It doesn't matter if your network has been set up this way for years, that still doesn't make it any less wrong.
Unless you have hundreds of devices on static IP addresses, renumbering a network doesn't take very long. I have at least 10 devices on static IPs in my house (another 10-15 on DHCP), and renumbering would take me less than an hour.
RFC1918 specifies that you have 3 IP address ranges that are designated for private IP addressing that you can use however you see fit and can subnet however you see fit. AT&T allows you to use 2 of those 3 ranges:
192.168.0.0/16 is one block. Typically this is subnetted into class C-sized address space, like 192.168.1.0/24.
172.16.0.0/12 is the 2nd block. Same rules apply, usually it's subnetted into class C-sized address space.
As an example, you could use 192.168.245.0/24. This means that you would configure as follows:
Router (2Wire gateway): 192.168.245.254
Subnet masl: 255.255.255.0
Static IP addresses: 192.168.245.1 through 192.168.245.63
DHCP range: 192.168.245.64 through 192.168.245.253
For static IP devices, just pick an IP address in the static range. All of those devices also get 255.255.255.0 as their subnet mask and 192.168.245.254 as their gateway. For DNS, you can use the 2Wire gateway itself (192.168.245.254), or if you want you can use Google DNS (220.127.116.11 and 18.104.22.168) or OpenDNS (22.214.171.124 and 126.96.36.199).