U-verse Forums

Reply
Posted Apr 8, 2013
8:20:59 AM
View profile
NVG510 not bridgeable, no 2210 offered anymore

So, I have found all kinds of solutions to place the NVG510 into a "bridge mode" on the internet and old forums, but now as of 4/xx/2013 they say it can't be done anymore.  So I asked for a Motorola 2210, as that is what I used at my business location to set up passthrough mode so we could run our business our way.

 

 

My question,

     What is the replacement device so I can use my equipment behind the IP DSLAM gateway  NVG510 that was sent to me?

 

Kevin

So, I have found all kinds of solutions to place the NVG510 into a "bridge mode" on the internet and old forums, but now as of 4/xx/2013 they say it can't be done anymore.  So I asked for a Motorola 2210, as that is what I used at my business location to set up passthrough mode so we could run our business our way.

 

 

My question,

     What is the replacement device so I can use my equipment behind the IP DSLAM gateway  NVG510 that was sent to me?

 

Kevin

0
(0)
  • Rate this reply
View profile
Solved
Apr 15, 2013 4:52:59 AM
0
(0)
Teacher

On the NVG510:

1. Under “Home Network->Subnets & DHCP”: - Device IPv4 Address: 192.168.1.254 (this is the default)

- DHCPv4 Start Address: 192.168.1.1 - DHCPv4 End Address:  192.168.1.1 (This tells the NVG510 to only allocate one address to a device connected to it) "Which will be your router"

 

2. Under “Home Network->Wireless” - Wireless Operation: Off (Since you will be using your own WiFi router)

 

3. Under “Firewall->IP Passthrough” - Allocation Mode: Passthrough - Passthrough Mode: DHCPS-fixed - Passthrough Fixed MAC Address: <MAC address of the home router> (You can find your home router MAC address on the home router’s status page. Make sure to enter the WAN MAC address).

 

3. Under “Home Network->Configuration”, change IPv6 to “Off”, unless you know how to configure IPv6 to work with your router. This will save you some issues in the future.

 

On the Home Router

1. Make sure the home router allocates DHCP addresses on the LAN on a different range than 192.168.1.xxx. For example, 192.168.2.xxx will work (with a subnet mask of 255.255.255.0) or 10.0.0.1 will work (with a subnet mask of 255.255.0.0)2.

2. Tell the router to use a fixed WAN IP address (to not use DHCP to get an IP address from the NVG510). Then use the address from the NVG510 configuration page under “Broadband->Broadband IPv4 Address” as the WAN IP address, 255.255.0.0 as the subnet mask, the address under “Broadband->Gateway IPv4 Address” as the gateway address and the DNS server addresses from question #4 above as the primary and secondary addresses.

Accepted Solution

NVG510 not bridgeable, no 2210 offered anymore

4,275 views
9 replies
(0) Me too
(0) Me too
Post reply
Cancel
Submit
Replies
(9)
0
(0)
  • Rate this reply
View profile
Apr 8, 2013 11:45:13 AM
0
(0)
Guru
I'm not entirely sure where you got the information NVG510 not being bridgeable. It has an equivilant of IP Passthrough listed under firewall in the GUI (192.168.1.254).
I'm not entirely sure where you got the information NVG510 not being bridgeable. It has an equivilant of IP Passthrough listed under firewall in the GUI (192.168.1.254).

Re: NVG510 not bridgeable, no 2210 offered anymore

2 of 10 (4,254 Views)
0
(0)
  • Rate this reply
View profile
Apr 9, 2013 1:44:22 PM
0
(0)
Employee

bauwls wrote:
I'm not entirely sure where you got the information NVG510 not being bridgeable. It has an equivilant of IP Passthrough listed under firewall in the GUI (192.168.1.254).

That's what I was thinking, with the 2wire 2701HG-B (back in the DSL days) as long as I unchecked all the firewall detections and such (which will also work with the 3800, 3801, and 3600 as well) and put my device in DMZ+ mode any traffic I got went right to the DMZ+ 'd device.

 

Supposedly (and from what I have read) the NVG510 can do the same thing as long as you tell it to.

 


bauwls wrote:
I'm not entirely sure where you got the information NVG510 not being bridgeable. It has an equivilant of IP Passthrough listed under firewall in the GUI (192.168.1.254).

That's what I was thinking, with the 2wire 2701HG-B (back in the DSL days) as long as I unchecked all the firewall detections and such (which will also work with the 3800, 3801, and 3600 as well) and put my device in DMZ+ mode any traffic I got went right to the DMZ+ 'd device.

 

Supposedly (and from what I have read) the NVG510 can do the same thing as long as you tell it to.

 

*I am an AT&T employee and the postings on this site are my own and don’t necessarily represent AT&T’s position, strategies or opinions.

Re: NVG510 not bridgeable, no 2210 offered anymore

3 of 10 (4,224 Views)
0
(0)
  • Rate this reply
View profile
Solved
Apr 15, 2013 4:52:59 AM
0
(0)
Teacher

On the NVG510:

1. Under “Home Network->Subnets & DHCP”: - Device IPv4 Address: 192.168.1.254 (this is the default)

- DHCPv4 Start Address: 192.168.1.1 - DHCPv4 End Address:  192.168.1.1 (This tells the NVG510 to only allocate one address to a device connected to it) "Which will be your router"

 

2. Under “Home Network->Wireless” - Wireless Operation: Off (Since you will be using your own WiFi router)

 

3. Under “Firewall->IP Passthrough” - Allocation Mode: Passthrough - Passthrough Mode: DHCPS-fixed - Passthrough Fixed MAC Address: <MAC address of the home router> (You can find your home router MAC address on the home router’s status page. Make sure to enter the WAN MAC address).

 

3. Under “Home Network->Configuration”, change IPv6 to “Off”, unless you know how to configure IPv6 to work with your router. This will save you some issues in the future.

 

On the Home Router

1. Make sure the home router allocates DHCP addresses on the LAN on a different range than 192.168.1.xxx. For example, 192.168.2.xxx will work (with a subnet mask of 255.255.255.0) or 10.0.0.1 will work (with a subnet mask of 255.255.0.0)2.

2. Tell the router to use a fixed WAN IP address (to not use DHCP to get an IP address from the NVG510). Then use the address from the NVG510 configuration page under “Broadband->Broadband IPv4 Address” as the WAN IP address, 255.255.0.0 as the subnet mask, the address under “Broadband->Gateway IPv4 Address” as the gateway address and the DNS server addresses from question #4 above as the primary and secondary addresses.

On the NVG510:

1. Under “Home Network->Subnets & DHCP”: - Device IPv4 Address: 192.168.1.254 (this is the default)

- DHCPv4 Start Address: 192.168.1.1 - DHCPv4 End Address:  192.168.1.1 (This tells the NVG510 to only allocate one address to a device connected to it) "Which will be your router"

 

2. Under “Home Network->Wireless” - Wireless Operation: Off (Since you will be using your own WiFi router)

 

3. Under “Firewall->IP Passthrough” - Allocation Mode: Passthrough - Passthrough Mode: DHCPS-fixed - Passthrough Fixed MAC Address: <MAC address of the home router> (You can find your home router MAC address on the home router’s status page. Make sure to enter the WAN MAC address).

 

3. Under “Home Network->Configuration”, change IPv6 to “Off”, unless you know how to configure IPv6 to work with your router. This will save you some issues in the future.

 

On the Home Router

1. Make sure the home router allocates DHCP addresses on the LAN on a different range than 192.168.1.xxx. For example, 192.168.2.xxx will work (with a subnet mask of 255.255.255.0) or 10.0.0.1 will work (with a subnet mask of 255.255.0.0)2.

2. Tell the router to use a fixed WAN IP address (to not use DHCP to get an IP address from the NVG510). Then use the address from the NVG510 configuration page under “Broadband->Broadband IPv4 Address” as the WAN IP address, 255.255.0.0 as the subnet mask, the address under “Broadband->Gateway IPv4 Address” as the gateway address and the DNS server addresses from question #4 above as the primary and secondary addresses.

Re: NVG510 not bridgeable, no 2210 offered anymore

4 of 10 (4,171 Views)
Solution
0
(0)
  • Rate this reply
View profile
Apr 18, 2013 2:53:58 PM
0
(0)
Employee
Edited by David on Apr 18, 2013 at 2:56:35 PM

ron351 is on the right track however I would make one change otherwise you may find accessing the unit a bit hard in troubleshooting. Here is how I set my IP scheme up. Note I don't use the 192.168.x.x scheme as too many devices come to it as default. I also keep it as general practice as not using the device's access IP address as a assignable IP address.

 

how I set up the 2wire 2701HG-B I have.

 

Device IP address: 172.16.0.1 

subnet mask 255.255.255.248

dhcp range: 172.16.0.2 - 172.16.0.6

Directed broadcast IP is 172.16.0.7

network address: 172.16.0.0

prefix/CIDR: /29

 

Now for the NVG510 (assuming I had one- won't be IPDSL till later this year. )

 

Here is the IP range if using 192.168.1.254 as the device IP. I probably won't use this as again a security issue with me.


Device IP: 192.168.1.254

Subnet mask: 255.255.255.248

Network address: 192.168.1.248

DHCP range: 192.168.1.249-192.168.1.253

Directed broadcast (for wake on lan): 192.168.1.255

prefix/CIDR: /29

 

 

Again- I like staying away from 192.168.x.x for security and configuration reasons. What I will probably use..

 

Device IP: 172.16.0.254

Subnet mask: 255.255.255.248

Network address: 172.16.0.248

DHCP range: 172.16.0.249-172.16.0.253

Directed broadcast (for wake on lan): 172.16.0.255

prefix/CIDR: /29

 

 

 

Now you can do a as ron351 posted/suggested with /30 (2 host addresses) I wouldn't but that doesn't mean you can. Only problem with this I forsee is if you are troubleshooting your network you may have to disconnect your network to troubleshoot, or change your /30 (2 host addresses) to /29 (6 host addresses).

 

 

What I will do as I like the 172.16.0.x IP range:

 

Device IP: 172.16.0.254

Subnet mask: 255.255.255.252

Network address: 172.16.0.252

DHCP- 1 IP range: 172.16.0.253

Directed broadcast (for wake on lan): 172.16.0.255

Prefix/CIDR: /30

 

 

for the device's default IP range here is what it would be.

 

Device IP: 192.168.1.254

Subnet mask: 255.255.255.252

Network address: 192.168.1.252

DHCP-1 address: 192.168.1.253

Directed broadcast (for wake on lan): 192.168.1.255

Prefix/CIDR: /30

 

note: I don't like using 192.168.1.254 as an assignable IP address, again, keep it simple and stupid applies here.

 

 

 

 

ron351 is on the right track however I would make one change otherwise you may find accessing the unit a bit hard in troubleshooting. Here is how I set my IP scheme up. Note I don't use the 192.168.x.x scheme as too many devices come to it as default. I also keep it as general practice as not using the device's access IP address as a assignable IP address.

 

how I set up the 2wire 2701HG-B I have.

 

Device IP address: 172.16.0.1 

subnet mask 255.255.255.248

dhcp range: 172.16.0.2 - 172.16.0.6

Directed broadcast IP is 172.16.0.7

network address: 172.16.0.0

prefix/CIDR: /29

 

Now for the NVG510 (assuming I had one- won't be IPDSL till later this year. )

 

Here is the IP range if using 192.168.1.254 as the device IP. I probably won't use this as again a security issue with me.


Device IP: 192.168.1.254

Subnet mask: 255.255.255.248

Network address: 192.168.1.248

DHCP range: 192.168.1.249-192.168.1.253

Directed broadcast (for wake on lan): 192.168.1.255

prefix/CIDR: /29

 

 

Again- I like staying away from 192.168.x.x for security and configuration reasons. What I will probably use..

 

Device IP: 172.16.0.254

Subnet mask: 255.255.255.248

Network address: 172.16.0.248

DHCP range: 172.16.0.249-172.16.0.253

Directed broadcast (for wake on lan): 172.16.0.255

prefix/CIDR: /29

 

 

 

Now you can do a as ron351 posted/suggested with /30 (2 host addresses) I wouldn't but that doesn't mean you can. Only problem with this I forsee is if you are troubleshooting your network you may have to disconnect your network to troubleshoot, or change your /30 (2 host addresses) to /29 (6 host addresses).

 

 

What I will do as I like the 172.16.0.x IP range:

 

Device IP: 172.16.0.254

Subnet mask: 255.255.255.252

Network address: 172.16.0.252

DHCP- 1 IP range: 172.16.0.253

Directed broadcast (for wake on lan): 172.16.0.255

Prefix/CIDR: /30

 

 

for the device's default IP range here is what it would be.

 

Device IP: 192.168.1.254

Subnet mask: 255.255.255.252

Network address: 192.168.1.252

DHCP-1 address: 192.168.1.253

Directed broadcast (for wake on lan): 192.168.1.255

Prefix/CIDR: /30

 

note: I don't like using 192.168.1.254 as an assignable IP address, again, keep it simple and stupid applies here.

 

 

 

 

*I am an AT&T employee and the postings on this site are my own and don’t necessarily represent AT&T’s position, strategies or opinions.

Re: NVG510 not bridgeable, no 2210 offered anymore

[ Edited ]
5 of 10 (4,136 Views)
0
(0)
  • Rate this reply
View profile
Apr 26, 2013 11:29:54 AM
0
(0)
Contributor

No offense but I called and talked to tech support and they said it cant be done.  I have tried all of these options as well as many of my own and I cannot get to the Cisco router behind the NVG510.

 

On a side note I was sold 6MB service but can only receive 2.75MB, I was sold that I could use my own equipment, was told it had to be the RG from the installer.  I was also sold no other changes and I now have the phone that shuts off when the power turns off and I can not go back to a hard phone line.  I have had the RG lose connections and have all green lights on the front, only to have to power the unit off and back on to get my service restored.  I have had another tech come out and say that I am too far from the main location and that I should not have been sold UVerse at all as I am at the limit.  Lots of problems.

 

How do business customers get past these roadblocks?

 

I also tried to get business equipment and I was told no. 

No offense but I called and talked to tech support and they said it cant be done.  I have tried all of these options as well as many of my own and I cannot get to the Cisco router behind the NVG510.

 

On a side note I was sold 6MB service but can only receive 2.75MB, I was sold that I could use my own equipment, was told it had to be the RG from the installer.  I was also sold no other changes and I now have the phone that shuts off when the power turns off and I can not go back to a hard phone line.  I have had the RG lose connections and have all green lights on the front, only to have to power the unit off and back on to get my service restored.  I have had another tech come out and say that I am too far from the main location and that I should not have been sold UVerse at all as I am at the limit.  Lots of problems.

 

How do business customers get past these roadblocks?

 

I also tried to get business equipment and I was told no. 

Re: NVG510 not bridgeable, no 2210 offered anymore

6 of 10 (4,076 Views)
0
(0)
  • Rate this reply
View profile
May 8, 2014 3:46:20 PM
0
(0)
Contributor
Edited by Lacrocivious on May 8, 2014 at 3:47:24 PM

ron351--

 

Your solution is brilliant and apparently eliminates the filthy double NAT hack. It works perfectly. Thank you very much!

 

I cannot understand why this technique is not included in the box along with the NVG510. Or perhaps I simply don't want to understand.

 

Nor can I understand why, after spending nearly two full days slogging through essentially useless, largely clueless, and perhaps debilitatingly restricted AT&T 'tech support' -- I use that term charitably -- I was not only unable to get any AT&T representative to divulge anything even remotely similar to the simple technique you present here, I  was repeatedly told in several different ways that it was not possible.

 

One is left with the very strong impression that AT&T wishes to deliberately restrict the options and funcitionality available to its end users to the maximum extent they find possible. One might suspect that they find the concept of a customer who only wants to pay for access to the Intertubes and nothing else to be abhorrent.

 

In any event, I thank you again for your excellent instruction of how to achieve something that should be available as a simple and clearly presented option in the 'gateway' firmware.

 

ron351--

 

Your solution is brilliant and apparently eliminates the filthy double NAT hack. It works perfectly. Thank you very much!

 

I cannot understand why this technique is not included in the box along with the NVG510. Or perhaps I simply don't want to understand.

 

Nor can I understand why, after spending nearly two full days slogging through essentially useless, largely clueless, and perhaps debilitatingly restricted AT&T 'tech support' -- I use that term charitably -- I was not only unable to get any AT&T representative to divulge anything even remotely similar to the simple technique you present here, I  was repeatedly told in several different ways that it was not possible.

 

One is left with the very strong impression that AT&T wishes to deliberately restrict the options and funcitionality available to its end users to the maximum extent they find possible. One might suspect that they find the concept of a customer who only wants to pay for access to the Intertubes and nothing else to be abhorrent.

 

In any event, I thank you again for your excellent instruction of how to achieve something that should be available as a simple and clearly presented option in the 'gateway' firmware.

 

Re: NVG510 not bridgeable, no 2210 offered anymore

[ Edited ]
7 of 10 (3,373 Views)
0
(0)
  • Rate this reply
View profile
May 8, 2014 4:11:01 PM
0
(0)
Teacher

Lacrocivious Thanks it works just fine for me with no issues at all.

Took a little searching and trial and error but this way you can also log into the NVG510 on the 192.168.1.254 ip address to work in the modem/router and also log into the connected router like 192.189.3.1 or what ever it is set to.

ATT really needs to work on this router as it renders useless to me except t use it as a connectiong to Uverse and passthrough to the secondary router.

Besides I wasted a day trying to open ports in the NVG510 and ATT said you should be able to but I think they block them and simply want you to get a static IP address and pay more.

I even had to show the tech they sent out how to do it as he called his boss and his boss said you can't do that with a 2nd router.

Well I did, you did and we prove them wrong and also saved some money on a static IP address.

Glad it worked for you

Ron

Lacrocivious Thanks it works just fine for me with no issues at all.

Took a little searching and trial and error but this way you can also log into the NVG510 on the 192.168.1.254 ip address to work in the modem/router and also log into the connected router like 192.189.3.1 or what ever it is set to.

ATT really needs to work on this router as it renders useless to me except t use it as a connectiong to Uverse and passthrough to the secondary router.

Besides I wasted a day trying to open ports in the NVG510 and ATT said you should be able to but I think they block them and simply want you to get a static IP address and pay more.

I even had to show the tech they sent out how to do it as he called his boss and his boss said you can't do that with a 2nd router.

Well I did, you did and we prove them wrong and also saved some money on a static IP address.

Glad it worked for you

Ron

Re: NVG510 not bridgeable, no 2210 offered anymore

8 of 10 (3,368 Views)
0
(0)
  • Rate this reply
View profile
May 8, 2014 9:20:16 PM
0
(0)
Contributor
Edited by Lacrocivious on May 8, 2014 at 9:26:50 PM

David's suggestions about using alternative non-routable IP address ranges are well founded and worthy of consideration, for all the reasons he mentions.

 

In my own case, I traded my well worn foil hat for convenience, and changed the NVG510's network to 192.168.0.0 so that I would not have to reconfigure my internal 192.168.1.0, 192.168.2.0, or 192.168.3.0 LAN subnets. Thus, the NVG510 is 192.168.0.254, the single DHCP address it assigns is 192.168.0.253, and so far as my internal subnets are concerned, their gateway IP remains 192.168.(x).1 where 'x' is 1, 2, or 3.

 

As you point out, I can now access the NVG510 via any node on the e.g., 192.168.1.0 network by simply entering 192.168.0.254 in a browser address bar.

 

This setup even works with IRC DCC, which is notoriously finicky, perhaps because it handshakes 'backwards' in terms of who opens ports where. If this is not proof that the disgustingly unspeakable kludge known as double NAT has been eliminated, I don't know what is.

David's suggestions about using alternative non-routable IP address ranges are well founded and worthy of consideration, for all the reasons he mentions.

 

In my own case, I traded my well worn foil hat for convenience, and changed the NVG510's network to 192.168.0.0 so that I would not have to reconfigure my internal 192.168.1.0, 192.168.2.0, or 192.168.3.0 LAN subnets. Thus, the NVG510 is 192.168.0.254, the single DHCP address it assigns is 192.168.0.253, and so far as my internal subnets are concerned, their gateway IP remains 192.168.(x).1 where 'x' is 1, 2, or 3.

 

As you point out, I can now access the NVG510 via any node on the e.g., 192.168.1.0 network by simply entering 192.168.0.254 in a browser address bar.

 

This setup even works with IRC DCC, which is notoriously finicky, perhaps because it handshakes 'backwards' in terms of who opens ports where. If this is not proof that the disgustingly unspeakable kludge known as double NAT has been eliminated, I don't know what is.

Re: NVG510 not bridgeable, no 2210 offered anymore

[ Edited ]
9 of 10 (3,341 Views)
0
(0)
  • Rate this reply
View profile
May 8, 2014 9:58:43 PM
0
(0)
Teacher
Edited by ron351 on May 8, 2014 at 10:13:39 PM

Only thing David has a 2wire I have NVG510 modem/router and don't think I can change the IP 192.168.1.254 I would have to look again, but believe there wasn't a option to change that.

Just looked and can change the 192.168.1.254 I have so much connected to the setup I have now, I would fear a disaster if something didnt go right. I have about 12 to 13 devices running on my setup and 1 slipup I would dread.

I will have to understand what exactly is the change David talks about to see if it will work for me and all my devices

The NVG510 I assume he changes that to the 192.168.1.254 to 192.168.1.0 and the external router to what he had which I can't see because I am editing my last post.

capture1.jpg

 

Only thing David has a 2wire I have NVG510 modem/router and don't think I can change the IP 192.168.1.254 I would have to look again, but believe there wasn't a option to change that.

Just looked and can change the 192.168.1.254 I have so much connected to the setup I have now, I would fear a disaster if something didnt go right. I have about 12 to 13 devices running on my setup and 1 slipup I would dread.

I will have to understand what exactly is the change David talks about to see if it will work for me and all my devices

The NVG510 I assume he changes that to the 192.168.1.254 to 192.168.1.0 and the external router to what he had which I can't see because I am editing my last post.

capture1.jpg

 

Re: NVG510 not bridgeable, no 2210 offered anymore

[ Edited ]
10 of 10 (3,333 Views)
Share this post
Share this post