pogmommy/nmrpflash
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update readme

Browse source
This commit is contained in:
Joseph C. Lehner 2016-02-09 08:42:32 +01:00
parent 03f7a59bd3
commit 3815dd0e9a
1 changed files with 10 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
README.md
View file

@ -9,6 +9,9 @@ tested with a Netgear EX2700, but is likely to work on many others as well.
Prebuilt binaries for Linux, OS X and Windows are available Prebuilt binaries for Linux, OS X and Windows are available
[here](https://github.com/jclehner/nmrpflash/releases). [here](https://github.com/jclehner/nmrpflash/releases).
To run `nmrpflash` on Windows, install
[WinPcap](https://www.winpcap.org/install/default.htm).
```` ````
Usage: nmrpflash [OPTIONS...] Usage: nmrpflash [OPTIONS...]
@ -36,7 +39,7 @@ the Netgear router.
For this example, we'll assume that your network interface is `eth0`. For this example, we'll assume that your network interface is `eth0`.
First, we have to assign a static IP address to our network interface. First, we have to assign a static IP address to our network interface.
In this example, we'll use `192.168.1.2`. All available network interfaces In this example, we'll use `192.168.1.2`. All available network interfaces
can be listed using can be listed using
```` ````
@ -60,18 +63,18 @@ Remote finished. Closing connection.
```` ````
### Common issues ### Common issues
###### No suitable network interfaces found. ###### "No suitable network interfaces found."
If you're *not* on Windows, rerun `nmrpflash -L` using `sudo`. In any case, If you're *not* on Windows, rerun `nmrpflash -L` using `sudo`. In any case,
use `-vvvL` to see more detailed messages, and file a bug report if applicable. use `-vvvL` to see more detailed messages, and file a bug report if applicable.
###### No response after 60 seconds. Bailing out. ###### "No response after 60 seconds. Bailing out."
The router did not respond. Try running `nmrpflash` with `-m` and specify The router did not respond. Try running `nmrpflash` with `-m` and specify
your router's MAC address. It's also entirely possible that your device does your router's MAC address. It's also entirely possible that your device does
not support the NMRP protocol. not support the NMRP protocol.
###### Timeout while waiting for 0x04. ###### "Timeout while waiting for 0x04."
After a successful file upload, `nmrpflash` waits for up to 120 seconds for an After a successful file upload, `nmrpflash` waits for up to 120 seconds for an
answer from your device. You can increase this by specifying a longer timeout answer from your device. You can increase this by specifying a longer timeout
@ -89,9 +92,9 @@ $ make && sudo make install
###### Windows ###### Windows
The repository includes a The repository includes a
[DevCpp](http://sourceforge.net/projects/orwelldevcpp/) [DevCpp](http://sourceforge.net/projects/orwelldevcpp/)
project file (`nmrpflash.dev`). Download the latest project file (`nmrpflash.dev`). Download the latest
[WinPcap Developer Pack](http://www.winpcap.org/devel.htm) [WinPcap Developer Pack](https://www.winpcap.org/devel.htm)
and extract it into the root folder of the nmrpflash sources. and extract it into the root folder of the nmrpflash sources.