NetBurner Community Forum

Thanks for the information. The recovery jumper boots the device to the alternate monitor, which uses defaults such as DHCP. It does not support AutoIP.

Once in the alternate monitor, you would need a PC and the MOD54417 to be on a network with a DHCP server so the MOD54417 can get IP settings ...

The purpose of the recovery jumper is to put you in the Alternate Monitor as you have in your last post. Are you saying you cannot interact with the Alternate Monitor?

The other issue could be if something is interfering with the address or data bus. Are these plugged into your own h/w? If so, does any other module work in the same h/w?

Yes, have you tried the shorting jumper recovery procedure? https://www.netburner.com/NBDocs/Develo ... overy.html

Hello. I think they should be the same.

That is the utility that compresses the image and processes it for storage in the flash memory.

Hello,

Thank you very much for the quick follow up on that issue!

Hello RebootExpert,

It is not currently implemented, but is on our list to add as a feature. It is supported in the underlying system code, but needs to be exposed and tested in an API. That is something we will begin looking at in January and hopefully be in the next release.

Hello,

That is some great troubleshooting, and thank you very much for sharing the results. We have been checking the behavior and any fixes from 3.5.0 to the latest 3.5.3, and will post back to you as soon as we know more. Have a great weekend and thank you again.

The NetBurner device will know what AutoIP address it wants immediately since it is based on the MAC address. It will then immediately do a ping to verify no one else is using that same address. This should only take about a second unless someone else has that address.

Now if you have a direct ...