lisfolks's profile

Mentor

 • 

40 Messages

Tuesday, October 4th, 2011 2:28 PM

NVG510 Bridge Mode???

Just switched from DSL (Motorola 2210) to UVerse (Motorola NVG510). I set the 2210 into bridge mode and ran my home network from an Apple Airport Extreme Base Station (AEBS). I have some complex configurations on my network and figured I'd be able to do the same thing with the NVG510. However, it seems the NVG510 uses different terminology than I am used to.

 

Under Firewall/IP Passthrough, I set:

Allocation Mode to 'Passthrough'

Passthrough Mode to 'DHCPS-Fixed'

Passthrough Fixed MAC Address to the AEBS' MAC address

And, I left the Lease at the default 10 minutes.

 

On the AEBS, under Internet/Internet Connection, I switched from 'PPPoE' to 'Ethernet'. I left the Ethernet WAN Port value at 'Automatic (Default)'. And Connection Sharing is set to 'Share a public IP address'.

 

This apparently is not enough, though. The AEBS reports that the "Wi-Fi base station does not have a valid IP address", and that there is a "Conflicting DHCP Range".

 

How do I turn off the DHCP on the NVG510? And, what are the correct settings to put the NVG510 into bridged mode?

Contributor

 • 

1 Message

12 years ago

I just got this working following your instructions.  I just got U-verse with the NVG510 gateway and was having a nighmare of a time getting my AEBS to route packets to my internally port-forwarded devices (I run several network services I expose via dynamic DNS).  The NVG510 kept blocking all the data until I applied your recommendations.

 

Thanks again! 🙂

Contributor

 • 

3 Messages

12 years ago

(see post I replied to below)

 

So what about this dynamic IP (the public internet IP) changing?  You say that it will not UNLESS there is an upgrade or something - which means it very well COULD change.

 

The reason this is concerning for me is because I will put a web server connected to my "home network" and another service will be http posting data to the database on that webserver.  I will use DDNS service like DynamicDNS or TurnKey to make sure my web domain address is always accurately pointing to the public IP address assigned by ATT - however - if that Public IP (Broadband) address changes - then my home router will not be able to receive the internet traffic anymore.  (According to the setup given here - which works great on my Linksys E2000 by the way...thanks!)

 

So how can I avoid any problems with this 'jerry rigged' bridge mode setup when the IP address (public/broadband) from ATT DOES change????  I would hate to lose ANY data that should be posting because it is live data that must be acted upon immediately upon being posted to my web server.

 

OH - and I want to avoid paying for a static IP address - the whole reason for using a DDNS service.

 

Thanks.

----------------------------------------------------------------------------------------------

A long post, but hopefully worth the reading:

 

I had some weird things happening the weekend after I set up my NVG510 as described above in the post starting:

"Okay, so here's what I've done that seems to be working at the moment...

 

- In the NVG510's setup, under Home Network, then Subnets & DHCP, I set the following:"

 

The Issue:

When family members were trying to access the Internet with multiple devices, things kept locking up. Say for example, the kids were trying to watch videos, one on an iPad, the other on an iPod Touch. The videos were buffering really slowly and kept locking up. So... back to the drawing board. Now, I have some interesting findings and a new setup.

 

The Research:

I researched IP-DSL and IP Passthrough a bit. It seems that IP-DSL, which U-verse is using, is actually using IP like a typical ethernet network. (Their prior DSL used ATM, which is a bit more complex technology.) The U-verse Residential Gateway (RG) is getting an IP address and gateway just like anything else you set up with IP and DHCP. The "Broadband IPv4 Address" on the Broadband Status tab is the public IP handed out to the RG. The "Gateway IPv4 Address" is the AT&T router managing the RG (typically called the "Default Gateway").

 

IP Passthrough is supposed to allow another device to receive the IP address of the RG. When IP Passthrough is turned on, then, the NVG510 is supposed to give its own public IP address to a specified LAN device. The instructions on the right-hand side of the IP Passthrough tab confirm this.

 

The Theoretical Setup

To set up the NVG510 correctly, then, for use with a home router (assuming you don't want to simply let your home router be a bridge, of course) -

 

Starting with the NVG510's default settings:

 

- Under Home Network, then Subnets & DHCP, I set the following:

Device IPv4 Address:

DHCPv4 Start Address:

DHCPv4 End Address:  

 

- Under Home Network, Wireless,

Wireless Operation: Off

 

- Under Firewall, IP Passthrough,

Allocation Mode: Passthrough

Passthrough Mode: DHCPS-fixed

Passthrough Fixed MAC Address:

 

On the AEBS, then:

 

- Under Internet, Internet Connection,

Connect Using: Ethernet

Connection Sharing: Share a Public IP Address

 

- Under Internet, TCP/IP,

Configure IPv4: DHCP

 

- Under Internet, DHCP, the DHCP values are set as normal, with an address range in a different subnet from the RG, though, in order to prevent double NAT messages. (For example, if the RG is 192.168.1.x, the AEBS is 192.168.2.x)

 

Restart the NVG510, then the AEBS.

 

Theoretically, the NVG510 should, using its own DHCP, give the AEBS its own public IP address (the "Broadband IPv4 Address"), a valid Subnet Mask, and the Default Gateway (Router) value equal to the "Gateway IPv4 Address".

 

In actuality, for some reason, the NVG510 only will give the AEBS its Gateway  and DNS values. The AEBS gets an internal IP address and a Subnet Mask of 255.255.255.255. I suspect a bug, er, "feature", in the NVG510's firmware...

 

The Actual Setup

The fix, then, is to set everything up as described above - except... in the AEBS, I changed the last step:

 

- Under Internet, TCP/IP,

Configure IPv4: Manually

IP Address:

Subnet Mask: 255.255.0.0 (Note that I'm not certain this is correct. The NVG510 doesn't show a subnet mask on its Broadband/Status tab, but the values I have showing would work with this mask.)

Router:

DNS:

 

Yay, It Works

No more lockups; everything is running smoothly with multiple devices accessing the Internet at the same time.

 

I'm going to mark this post as the answer, though hopefully I won't later get my hand slapped and told how I terribly messed things up - i.e., anybody trying anything I suggest in any post anywhere does so at their own risk, of course. I don't claim to be an expert - just yet another experimenter in the 'net world. Anybody with more expertise and good explanations is welcome to jump in!

Contributor

 • 

3 Messages

12 years ago

I just got this working following your instructions.  I just got U-verse with the NVG510 gateway and was having a nighmare of a time getting my AEBS to route packets to my internally port-forwarded devices (I run several network services I expose via dynamic DNS).  The NVG510 kept blocking all the data until I applied your recommendations.

 

I see your post is very directly related to the question I just asked.  Can you tell me your concerns with using this setup and also using Dynamic DNS services?

 

When the Broadband (public) IP address changes - this set up has your router HARD CODED to use the Broadband IP at the time you set it up.  But when the Broadband IP changes - then your connection will break until you go back into your home router and change to the new Broadband IP.

 

Then all the DDNS services will be for naught as they may be properly updated with the new IP (depending on how you're getting the communication of the new IP to these services) - but any in/out data from your home network will stop at the home router since the home router is now using an incorrect Internet IP address (wrong Broadband IP address)?

 

Please advise of any workarounds.

 

Thank you!

Tutor

 • 

12 Messages

12 years ago

I going to be addressing this issue once I get my NVG510 connected computer to be accessible from the public internet. So far, passthrough-NoDHCP-Staticly assigning Divice Address to my computer alows my computer to access the internet, but not the other way around.
I *think* the problem *you* guys are having is that the AEBS is not running the DynamicDNS software. If I am remembering correctly, I expect to have a PC running the DynamicDNS software and it would be connected to the NVG510 via a Networkcard/TCPIP configured Dynamic DNS (not static) and a second Networkcard/TCPIP configured something like 192.168.0.1. This PC would serve as the router for the network.

Tutor

 • 

12 Messages

12 years ago

Just revisited the NVG510 configuration and tried to duplicated teh above configuration.
No luck ping and RemoteDesktop still don't find the machine connected to it.

Mentor

 • 

40 Messages

12 years ago

drosengarden (and anyone else with concerns about the public IP address changing) - there is currently no workaround of which I am aware to have your router dynamically change with the NVG510.  Read on...

 

According to the instructions on the IP Passthrough page of the NVG510, and as I noted in my "theoretical setup" section, if you set a device's MAC address (presumably the non-NVG510 router) under the IP Passthrough page's DHCPS-Fixed section, the NVG510 is SUPPOSED to pass the public IP address, via DHCP, to the specified device. BUT, it doesn't. Thus, I believe there is a bug, er, "feature", in the NVG510's firmware preventing the DHCPS-Fixed function from working properly.

 

Until such time as that firmware issue is fixed, as long as you're using the solution of "hard coding" the NVG510's address into your router, your connection will be broken if that IP address changes.

 

A self-proclaimed AT&T employee posted earlier in this thread that the IP address should not change under normal circumstances. While I believe that poster (mine hasn't changed in the few months I've had the NVG510 so far), I would advise keeping a constant eye out for the connection's status if you have a critical application running via your U-verse connection.

 

Sorry, but we're talking about a DSL modem that DOESN'T even actually BRIDGE here, so until that's changed or someone finds a better way (I'm totally open to suggestions!), I would just be aware that this is an imperfect, but generally workable, solution.

Tutor

 • 

7 Messages

12 years ago

Hello I want to apply this using a d-link dir 827  After applying the settings to the NVG510 what port do I connect it to on the d-link, 1 of the 4 Lan prts or the Internet port that is normally used when connecting to a modem?

 

Thanks

Mentor

 • 

40 Messages

12 years ago

This solution used the Internet (WAN) port of the secondary router (AEBS, here, but D-Link for you, bwatching.

Contributor

 • 

1 Message

12 years ago

Hi there,

 

I did this set up using the actual setup steps.  It worked for me for about three weeks and now out of a sudden it stopped working.  I believe I have tried everything.  I even restored the NVG510 and the Airport extreme to factory settings and set everything up again using the steps outlined.  

 

Any thoughts, why it isn't working now.

 

Please help.

frustrated Uverse customer

Mentor

 • 

40 Messages

12 years ago

"I did this set up using the actual setup steps.  It worked for me for about three weeks and now out of a sudden it stopped working."

 

Yes, Adricas19, I actually had the same thing happen. Mine's been going along smoothly - then suddenly wouldn't work anymore, seemingly out of the blue.

 

It turns out that AT&T turned on the IPv6 functionality in the NVG510. I don't know what about that broke the system, but to fix it, I simply went into the NVG510's setup and turned off the IPv6. Then, everything went fine.

 

On the Home Network tab, click the Configure link.

Change the IPv6 dropdown to Off.

Click the Save button.

 

If the NVG510 prompts you to restart the device, click the link there; otherwise, go to the Device page, click the Restart Device link, and follow the directions there (a few more clicks, and you'll actually restart the NVG510 😉

 

The rest of your settings should stay the same as you had them from the solution earlier in this thread.

 

BTW, I spoke with an AT&T tech recently. He said that AT&T is now aware of at least a couple of problems with this modem (the DNS thing mentioned in this thread and an IP Diagnostics issue). They currently are planning to send out a firmware upgrade towards the end of this month (December 2011) to fix these issues. We'll see if that breaks anything else.... (not to be cynical or anything...)

Not finding what you're looking for?
New to AT&T Community?
New to the AT&T Community? Start by visiting the Community How-To.
New to the AT&T Community?
Visit the Community How-To.