Reset to Factory - from Program

ROO

Will - Send_COMMAND 0:1:0 "RESET FACTORY"
Clear the contents of the Netlinx to factory defaults? I want to provide a method that will cleanse a netlinx for removal from a classified environment. Don't have one on-hand to try it.

Thanks
ROO

Joe Hebert

ROO wrote: »

Will - Send_COMMAND 0:1:0 "RESET FACTORY"
Clear the contents of the Netlinx to factory defaults?

Is that a new command? I’ve never seen that one before.

ROO wrote: »

I want to provide a method that will cleanse a netlinx for removal from a classified environment. Don't have one on-hand to try it.

If you telnet into the master and do a *clean disk* or *format disk* that should wipe everything out.

jjames

"reset factory" probably isn't what you're looking for. There are commands to scrub everything, in fact - it warns you with this:

This command will wipe out all persistent and non-volatile data from the master including the file systems to comply with DOD 5220.22-M. This will render the master *inoperable* and will require the master firmware to be *reprogrammed* !!!

Since it's not listed in telnet's help (it might be through terminal), I'd rather not post it. Might want to call AMX to get that.

Joe Hebert

Joe Hebert wrote: »

Is that a new command? I’ve never seen that one before.

The *reset factory* command is listed right there in telnet help you goofball.

DHawthorne

"Clean Disk" will wipe all the files, but won't reset network or security settings. I would assume "Factory reset" does (too lazy to try though ).

jjames

"factory reset" resets everything to the factory settings.

IPSec, system security, users, groups, system numbers, server ports, clock manager, URL list, duet settings, IP settings, queue thresholds and device settings are all reset.

ericmedley

So, is this some kind of programming "Lemmings running of a cliff" kind of thing?

If you're trying to lock out a non-paying customer, there are less draconian ways to go about it.

jjames

ericmedley wrote: »

So, is this some kind of programming "Lemmings running of a cliff" kind of thing?

If you're trying to lock out a non-paying customer, there are less draconian ways to go about it.

The OP mentioned removal from a classified site; "factory reset" does not comply with DOD 5220.22-M.

That other command might be able to be done through telnet . . . it's just hidden, just like a bunch of other commands.

I love the analogy though of the "Lemmings running off a cliff". Memories....aaaahhhh!

ROO

More Information - & response.

jjames wrote: »

"reset factory" probably isn't what you're looking for. There are commands to scrub everything, in fact - it warns you with this:

This command will wipe out all persistent and non-volatile data from the master including the file systems to comply with DOD 5220.22-M. This will render the master *inoperable* and will require the master firmware to be *reprogrammed* !!!


Since it's not listed in telnet's help (it might be through terminal), I'd rather not post it. Might want to call AMX to get that.

We only communicate to the Netlinx through a 1-way RS232 connection, so I'm limited in the way I have access. But if the program running in the classified netlinx can purge itself or I can initiate the purge process from the RS232 connection from another Netlinx, the removal of the Netlinx for service or replacement of the classified Netlinx, then we can help the customer maintain his system, and I wouldn't need to be involved.

If the command meets the DOD5520.22-M in the warning - won't it meet the requirement when removing the device for maintenance or replacement? Sorry, I must be confused somewhere.

I had drakonian thoughts in the past (some customer's do bring it out in me), but haven't thought about actually destroying the program and making the Netlinx inoperable. This would be like quiting a company and destroying your computer on the way out the door. That just goes a little beyond my nature. Just haven't had that bad of day... :^)


Thanks
ROO

Hedberg

Your Netlinx master has a telnet server available at 127.0.0.1 (local host) port 23. You can open a tcp client to this server and communicate with the telnet server all within your program and all without a piece of cat 5 cable in sight (assuming that cat5 connections to the masters are not permissible in your environment). Any telnet "brick my master" command that you could do with a regular telnet session to the master, you should be able to accomplish with your Netlinx tcp client. I don't know what that command is, but even if it's not supported by send_command, you should be able to do it through the telnet server via the local host.