Goto this page unless you're wanting to do some soldering onto your modem This page is only here now for historical reasons
Motorola NVG510 Reverse Engineering Information
This information is still a work in progress, and if it doesn't work, fries your modem, or kills your dog. Don't blame me just because you listened to a random blog on the internet. USE AT YOUR OWN RISK
Rooting It with the WebUI: There is a way to root the modem without opening it up and soldering on it. See http://lastyearswishes.com/blog/view/4fcff51b4aa5d8385420c706 If you don't want to solder onto your modem, use this. In fact, unless you plan on opening the device up or doing some real hacking, everything should be located there. Again goto http://lastyearswishes.com/blog/view/4fcff51b4aa5d8385420c706
Update: A true bridge mode I believe has been found. Scroll to the bottom for more
Big Update: A way to the root shell has been found. At the serial console shell, all that must be entered is
! and it'll take you there.
Hopefully, you reached this web page because you are like me. Tired of the shitty NVG510 modem that you can't do anything about because of AT&T. Well, if you have a bit of electronics know how, and are comfortable with a command line, you can make your modem actually pretty decent. I happened to have an extra one of these things(though both work on my U-Verse account) so I decided what better way to put it to use, than to tear it apart. That said, I'm fairly surprised I didn't fry it in some way. You might not be that lucky. Be prepared to buy a new one if things don't work out.
The FCC manual should be the first step in understanding the operation of the NVG510. It can be found at this website
To get access to the described console in the manual however, I'm 99% sure that you must open it up. I've yet to find anything that would allow me to enable the console on an unopened modem.
To open it up, on the underside there are 4 rubber/felt pads. Remove those and under two of them there will be screws. Remove the screws and it should open up fairly easily.
The Serial Port
Now take a look at the circuit board. As you can see, there is plenty of things to modify. There are plug-ins for an external wifi antennae as well as a possible JTAG connector that is unpopulated. You should now look for 4 unpopulated pins labeled "J10". This is a 3.3V/TTL serial port. The square hole is Ground, the hole next to it is 3.3V. The hole next to power is TX and next to that is RX.
Those four holes ended up being fairly difficult to desolder for me. The RX and TX luckily are quite easy to desolder and insert pin headers into, and luckily is all you need. I also soldered a wire into GND, though not properly. Soldering the GND wire is very difficult because it's connected to a fairly large ground plane and I couldn't get it hot enough for all of the solder to melt at one time, so I just (improperly) added some solder to the top of it and stuck in a wire. It's worth it to try reading from the serial port now.
To hook this up to you computer you'll need a proper 3.3V serial cable. Computers natively use 5V serial ports, so they must be level shifted. Also, if you're going to hand-make this cable, you'll need to use an isolator. Or, if you'll feeling extra ambitious, (like I was) you can connect a grounded supply up to it. I managed this by using a PC power supply. I connected GND to the negative terminal, and 12V(yellow) to the positive terminal.. I soldered wires straight to the PCB, but a barrel jack that fits would have been a lot more proper.
Also, the way I accomplished the serial port bit is just use an FPGA I had lying around. My FPGA has a USB-Serial FTDI built in, so all I had to do was make a quick VHDL design like so:
ExtTX <= PCRX; PCTX <= ExtRX;
And then it did all the heavy lifting, and my FPGA works off of 3.3V already, so it did the level shifting for me.
Now, at first I had a problem in that I never received data from the serial port. I ended up finding a 10K pull up resistor on both RX and TX that I had to remove and then create a solder bridge over. If you're having problems getting any data from the modem, desoldering is worth a try. They are just right of the 4 pins, and are easy to trace out to make sure you got the right two. They are extremely tiny though. Remember, flux is your friend.
The serial port on the modem uses 57600bps, 8-bit data, and 1 stop bit. That information I got from wikidevi
So I simply did
$ screen /dev/ttyUSB1 $ sudo stty -F /dev/ttyUSB1 57600 cs8 -cstopb
Where ttyUSB1 is the USB serial port provided by my FPGA FTDI.
Now, you should be able to turn on the modem and see it's boot log and dmesg. After that press enter into the console and it should pop up something like
This console is actually fairly simple and easy to use, and breaks out everything that you can configure on the modem. But, it is not the console described in the FCC manual.
This is the help text:
Axis/124578433> help help [command] : Get help. history : Show command history. get OBJ.ITEM : Get the value of OBJ.ITEM (ITEM is a parameter or status). ### Hint: run 'info OBJ.params' or 'info OBJ.status' to get a list of the OBJ's parameters and status. set OBJ.ITEM VALUE : Set the value of OBJ.ITEM to VALUE. info INFO [ARGS ...] : Get the INFO information (expert mode). new OBJ [NAME] : Create an object with an (optional) name (requires an 'apply') del OBJ : Delete an object (requires an 'apply') aget OBJ.ITEM ATTR : Get the OBJ.ITEM's ATTR attribute. aset OBJ.ITEM ATTR VALUE : Set the OBJ.ITEM's ATTR attribute to VALUE. name OBJ [NAME] : Get or set the OBJ's "name" (specify a new name to set it). names [OBJ] : Recursively show all object names. validate [OBJ] : Validate OBJ, or the entire database if no OBJ specified. apply : Apply changes to the database (changes are NOT saved). revert : Revert the database by discarding your changes. save : Save the database (rewrites config.xml). defaults : Reset the system back to the factory defaults (deletes config.xml). dump [OBJ [LEVELS]] : Dumps the OBJ's parameters, or the entire database. Use the optional LEVELS parameter to limit the depth of the database tree. sdump [OBJ [LEVELS]] : Dumps the OBJ's status, or the entire database. tdump [TEMPLATE [LEVELS]] : Dumps the template, or the entire SDB schema. dirty [OBJ] : Displays which parameters are dirty. run CMD [ARGS ...] : Run the SDB's CMD command (expert mode only!). event EVT [ARGS ...] : Send the EVT (event number) to the SDB (expert mode only!). console [on | off] : Direct all log messages to this console. Without arguments, toggles on and off. log [OPTIONS] : View log messages. See "log help" for more information. voiplog [OPTIONS] : View log messages. See "log help" for more information. mfg [OPTIONS] : Set or view MFG parameters. See "mfg help" for more information. mirror [PORT CAPTURE-PORT] | "off" : Mirror Ethernet traffic on PORT so that it may seen on CAPTURE-PORT. Specify "off" to turn mirroring off. resetstats [OBJ] ["all"] : Reset any statistics the object may have. The optional "all" argument will recursively reset all children's stats as well. If only "all" is given (OBJ is omitted), this will reset all statistics starting at the root node. metadata OBJ.PARAM : Returns metadata information about a given parameter. fwinstall URL | "last" : Install a firmware image. Use "last" to reuse the last URL. crashdump ["erase"] : Shows the most recent crash dump contents. The optional "erase" will erase both current and last saved crash dump contents. reboot [N] | ["cancel"] : Reboot the router in N seconds (default is 2). "cancel" argument can be issued to cancel a previous reboot command. source FILE : Read and process commands from FILE. . FILE : An alias for 'source'. exit : Exit from this shell. quit : An alias for 'exit'. magic : Enter magic mode. crash : Read and Write the Memory mapped registers
Well, seems simple enough then doesn't it? I don't understand the difference in sdump and dump, but I don't think it matters too much.
Now what you want to probably do next is do
mfg show and copy those values and then do dump and copy that text.
If you're new to screen, what you need to do is have
defscrollback 10000 in your ~/.screenrc and then to copy the text, just push CTRL-A and then
[. Then push space to get the first "mark" and then scroll up (with pg-up/up arrow) and press space again.
After that, just do
CTRL-A and then
> and it will write what you just "copied" into /tmp/screen-exchange.
From there, you can easily browse all of the available configuration options.
As you can tell from the dump log, there are a ton of configuration options. Here I'll give you a hint to the more useful ones, as well as some configuration stuff to be aware of
DNS problem fix:
ip.dns.domain-name = att.net ip.dns.primary-address = 18.104.22.168 ip.dns.secondary-address = 22.214.171.124 ip.dns.proxy-enable = on ip.dns.override-allowed = off
You should be able to change these to something more appropriate.
override-allowed should be turned on(otherwise I believe they will be reset by DHCP over the DSL link).
So, let's say we want to set the primary name server to 126.96.36.199, google's sane primary name server. We would enter this at the command line:
set ip.dns.primary-address 188.8.131.52
Now if that's about all the configuration we want to do and we want to save our changes and make the modem notice them, we have to do a few commands:
validate apply save
You don't necessarily have to do validate, but I assume it's safer to use it I think. I believe that this is what happens:
validatewill validate the changes to make sure that no data was input in a way that wouldn't make sense (like if nameserver was set to
applywill actually cause the modem to notice the changes and begin executing using those changes you've made
savewill cause the changes you made to persist after reboot. I assume it saves it to flash with this command.
mgmt.shell.ssh-port = 0 mgmt.shell.telnet-port = 0
These you should change to what port you want it to run on. Note though that I've yet to figure out the username and password used for SSH. I've searched through both the dump and through the GPL source code and can't find any hints really.
So, to enable these you can just do something like
set mgmt.shell.ssh-port 22 set mgmt.shell.telnet-port 23 validate apply save
If you want to enable remote access to telnet and/or ssh (I highly recommend not opening up telnet to the world) you can modify these values to something appropriate:
mgmt.remoteaccess.protocol = telnet mgmt.remoteaccess.port = 0 XX change this to 23 mgmt.remoteaccess.idle-timeout = 5 mgmt.remoteaccess.total-timeout = 20 mgmt.remoteaccess.max-clients = 4 mgmt.remoteaccess.protocol = ssh mgmt.remoteaccess.port = 0 XX change this to 22 mgmt.remoteaccess.idle-timeout = 5 mgmt.remoteaccess.total-timeout = 20 mgmt.remoteaccess.max-clients = 4
I haven't confirmed this, but I believe UPnP can be enabled by changing this to on:
mgmt.upnp.enable = off
Disabling "Potential connection issue" and "no connection" redirect loop crap:
mgmt.lan-redirect.enable = on
Change it to
off. lan-redirect is what causes that extremely annoying redirecting to happen when the connection is lost or "has possible problems". What the modem will do is when you request a nameserver, it will, instead of sending back no route, timeout, or the actual name servers response,
it will instead make every domain forward to 192.168.1.254, so that you can then load an HTML page that causes a redirect(but doesn't set it to do-not-cache) to
/cgi-bin/home.ha... So basically, you click
do not show, yet the page continues to try to redirect
due to modern web browser caching and the lack of a no-cache directive on the redirect page.
Disabling the DHCP server:
conn.dhcps-enable = on
Note that you'll have to configure a static connection to the modem to access it. I don't see much of a point in disabling it completely, as there is (still) no true bridge mode unfortunately.
Bridge mode discoveries:
There does not appear to be a straight forward PPPoE bridge mode, even with full control over the device. I believe there could be a way by doing some special stuff with the
link configuration objects, but I don't see anything obvious so far
Possible money saver
From this bootloader, you can change a lot of things AT&T probably would frown upon. Basically, you can make it look like another modem. I'm not 100% sure, but I believe 1 modem is tied to 1 account, making modems that are used worthless.
I'm not for sure about this though and will have to test it and research it more. I don't recommend changing anything in the
The NVG510 is really a decent modem, but has been kiddie-proofed so hard that it hurts. I hope this guide helps you to taking full control of your modem. Also, I don't recommend trying to evade your U-Verse accounts capabilities. I imagine AT&T won't care much if they catch you modifying your modem... they will care if you modified it to reach 16Mbit speeds when you only have a 3Mbit account though, and I'm sure they keep tabs on it. Don't be stupid.
Same goes for trying to boost wifi power or use channels not specified for use in your country.
True Bridge Mode
A very often wanted feature of the NVG510 is for it to just get out of your way and let your (hopefully more sane) router to deal with all the firewall and NAT business. After quite a bit of experimenting and starting over with
default and a bit of an accident, I believe I've figured it out.
Some of the values in the NVG510's configuration "database" appears to be magical, and lots of assumptions have to be made without real technical documentation. So, let's look at the
link object that appears to be linked to WAN and LAN
connections in an assumed manner.
Here is what was in my modem's dump about
links. Your's should look similar:
link.type = ethernet link.igmp-snooping = off link.mtu-override = 0 link.port-vlan.ports = lan-1 lan-2 lan-3 lan-4 ssid-1 ssid-2 ssid-3 ssid-4 link.port-vlan.priority = 0 link.type = ethernet link.mtu-override = 0 link.supplicant.type = eap-tls link.supplicant.qos-marker = AF1 link.supplicant.priority = 0 link.port-vlan.ports = vc-1 link.port-vlan.priority = 0 link.tagged-vlan.ports = ptm link.tagged-vlan.vid = 0 link.tagged-vlan.priority = 0
ptm is the PPP connection. So we basically want for the PPP connection to be routed straight to an ethernet port so our router can handle it. So here is what I did
set link.port-vlan.ports "lan-2 lan-3 lan-4" set link.port-vlan.ports lan-1
The first command sets the
LAN link so that only the LAN ports 2-4 is used. The next link sets the link for the
WAN side of the link. Previously, the port is vc-1. I assume vc-1 is hardwired to magically go to the
LAN somehow. Anyway, replacing vc-1 with
lan-1 basically makes the equivalent of a PPP bridge.
On the router side, all you have to do is use that port and the modem will do all of the PPP authentication, and I assume MRU shifting to 1500.. All your modem will get is a raw stream from AT&T's servers. So if you send it a DHCP client request, you'll get a response straight from AT&T's servers.
This is the only configuration required as well. This will short through all of the modem's crappy configuration and directly forward it to the first ethernet port(the one closest to the barrel jack power adapter).
And if for some odd reason you need to access the actual modem(such as for reconfiguration), just plug your network cable into another port. The built-in DHCP server runs just as before, except it will never be connected to the internet.
Configuration Template You can dump this for yourself, but to see what Motorola's "template" is for it's configuration options you can check out this pastebin. If you don't know what options a configuration object supports, this is a good bit to look at. Though a few things in the template don't exist in my NVG510 at least and will cause crashes if objects are created. (cifs will not work for me)