Joseph C. Lehner

Does `nmrpflash` work with the library provided by RedHat? I.e. when running ``` # ln -s /usr/lib64/libpcap.so.1.9.1 /usr/lib64/libpcap.so.0.8 ``` beforehand?

I'll consider forcing the linker to use `libpcap.so.1` for the next build! I'll leave this open until then.

It's been almost two years now, but the fix isn't as easy as it first seemed. There is no `.so` name that is common to both distros, as can be...

I'm thinking about releasing Linux builds as [AppImages](https://appimage.org/) in the future. Can you verify that the file below runs as is on Fedora? [nmrpflash-0.9.20-19-g382346c-linux-x86_64.tar.gz](https://github.com/jclehner/nmrpflash/files/12565855/nmrpflash-0.9.20-19-g382346c-linux-x86_64.tar.gz)

Never mind. I've tested it myself, and it works as expected! Finally closing this!

Did you turn off the router before executing `nmrpflash.exe`?

Does the router boot up normally? And if not, do the LEDs light up? How did it get bricked (if it did)?

Does the attached version fix your issue? [nmrpflash-0.9.17-4-g784536c-win32.zip](https://github.com/jclehner/nmrpflash/files/8926973/nmrpflash-0.9.17-4-g784536c-win32.zip)

Try using the `-m` option to manually specify the router's MAC address. If that doesn't work, you could also try blind mode (`-B`) as a last resort.

Have you tried pressing `Ctrl` + `C` when you get the "Waiting for Ethernet connection." message?