Moved to Netgate 6100

hulleyrob

Hi folks, just moved to a new 6100

Had a few problems when migrating from a home built box running 2.5.2

Imported the config and got everything working except SSH. That was a bit of a pain but eventually managed to login via ssh all the keys were missing and never generated despite the message saying they would be. Should there be a menu to do this?

Now that's sorted the main question would be what's the best way of stopping the blue light from flashing and that setting persisting after a reboot?

echo 0 > /dev/led/blue1 works but I want this to be set after every boot.

If the best way is a config.xml shellcmd then that's fine just thought I would check im not making this harder for myself.

Thanks
Rob

stephenw10

Hmm, new SSH keys should be generated if you import a config with it enabled. It's no different to enabling SSH in the GUI or at the console menu.

That's as good a way of disabling the Blue LED as any. You might find it is re-enabled if anything else sets the LEDs again after boot. Like an upgrade becoming available.

Steve

hulleyrob

@stephenw10 Hi Steve, my public keys carried over with the config it was only the setup on the new device that didn't complete despite the message saying this would continue in the background but after 1 hour I decided to see what was going on and ended up creating the missing keys myself.

I did try toggling and saving enable SSH in the menu in case that was the trigger before doing so but it didn't seem to do anything.

stephenw10

Hmm, sounds like it got stuck on something in the restore. Did that config include Squidguard? I have seen that get stuck a few times.
SSH keys are not stored in the config, I expect them to be regenerated when a config is restored.

Steve

hulleyrob

@stephenw10 just checked the config I used over as I had installed that in the past but the only reference to "squid" was this:

		<item>
			<minute>0</minute>
			<hour>0</hour>
			<mday>*</mday>
			<month>*</month>
			<wday>*</wday>
			<who>root</who>
			<command>/usr/local/sbin/squid -k rotate -f /usr/local/etc/squid/squid.conf</command>
		</item>

stephenw10

Hmm, not that then. You can remove that cron-job if you don't have Squid installed.

Hard to say what that might have been then. You'd have to check the process list while it was stuck, after restring the config.

Steve