And if they sold it to you, they didn't give you the passwords ???that is a pretty stupid idea, it the device is completly reset, than there is no way someone can get the credentials, so complete reset should be allowed in any circumstances.
Well, we can assume that these pads are used in the factory to program the device, so it should be possible to use them.It may also be possible to connect to it using SPI header pins on the right, but main CPU must not access it at the same time (would have to hold it in reset or something... in circuit programming may be tricky).
This is not a stupid feature. In a holiday resort youngsters thought to solve their internet connection by pushing the reset button. (like initiating a reboot). They whiped the config instead.that is a pretty stupid idea, it the device is completly reset, than there is no way someone can get the credentials, so complete reset should be allowed in any circumstances.
In a holiday resort youngsters thought to solve their internet connection by pushing the reset button. (like initiating a reboot). They whiped the config instead.
Ok, but what if you have 50+ or 100+ more APs to configure, would you have to follow the netinstall procedure for each one of them ? Is there a quicker way to do this ?I think that to prevent resetting device to factory default config, the "Configure script" option of netinstall is the way to go ... it replaces MT's default config and when device is ordered to reset to default configuration
AFAIK netinstall is the only way of replacing default config. Call it security featureOk, but what if you have 50+ or 100+ more APs to configure, would you have to follow the netinstall procedure for each one of them ? Is there a quicker way to do this ?I think that to prevent resetting device to factory default config, the "Configure script" option of netinstall is the way to go ... it replaces MT's default config and when device is ordered to reset to default configuration
Reset with script execution ?
Replace default config would be one of those operations that requires confirmation on the physical device (press the button).Ease of default config replacement inevitably clashes (or rather goes hand in hand) with ease to abuse it.
Yes that would be best...Replace default config would be one of those operations that requires confirmation on the physical device (press the button).Ease of default config replacement inevitably clashes (or rather goes hand in hand) with ease to abuse it.
If someone not experienced replaces the default configuration then he can contact an experienced user to fix it...And easily leads to even more bricked devices if config is replaced by person not experienced with ROS enough.
Well, I think we are not too worried about inexperienced persons fouling up their router, but more about criminal hackers taking over a router and at the same time replacing the default config so when the (inexperienced) owner does a full reset to defaults, the hacker still owns the device.If someone not experienced replaces the default configuration then he can contact an experienced user to fix it...