SG-1100

jimp

Is it still advisable to edit the xml file for the vlan config?
I had lotsa issues in porting an APU2 config to a SG-1100.

Splicing that in will speed things up considerably, so it's still a good idea. Same with any of the switch-based units. After you import you should be able to create the tags and then assign them, then apply and it will reboot, but hand editing the config is faster if you know how.

Rico

@jimp wouldn‘t this be a great hangout topic?
Moving from homemade XY to Netgate integraded Switch Hardware or vice versa.
config.xml VS GUI
Since more and more Netgate devices with Switch pop up I think this question will come more often now?
I‘d enjoy it.

-Rico

Gil

@jimp Is it worth considering writing a script to edit the config file? I can see a lot of users migrating configs

Maxburn

@gil said in SG-1100:

@jimp Is it worth considering writing a script to edit the config file? I can see a lot of users migrating configs

If it is more than a find replace for interface names I might be interested. I've done the find/replace before and the hard part was knowing what the new ones were.

For some strange reason the video out on my box I generally run pfSense in (when it's not in a VM) is cut off at the bottom and I can't see the command line to do the adapter select/replace when restoring a foreign config. Tried overscan adjustments etc and didn't work, please don't @ me here, don't want to clutter this thread up.

But anyway, yes I'm interested in this process.

Gil

If it is more than a find replace for interface names I might be interested. I've done the find/replace before and the hard part was knowing what the new ones were.

I was kind of thinking that the script would pull the interface settings from the "new device" default config file; and port them across to the desired config file.
ie: an input config and an output config
My question is: Is it only the 'interfaces" portion of the xml that requires changing? Or is it more comlpex than that if you have bridges etc.. ?

SteveITS

@gil said in SG-1100:

the script would pull the interface settings from the "new device" default config file; and port them across to the desired config file

Typically the interface is tied only to where it is assigned, e.g. LAN, and then LAN is referenced elsewhere.

Also it has been a while but I am pretty sure that when restoring one is prompted to assign interfaces, if they differ from interfaces in the backup.

Often what I do on a new device is pull up the default config, look at the interface names to see what they are, look at the hardware settings like power/crypto, and then restore and edit the hardware settings back again.

akuma1x

Will there maybe be a wall-mount bracket available for the SG-1100?

Jeff

Gil

when restoring one is prompted to assign interfaces, if they differ from interfaces in the backup.

This usually works ok, but it went pair shaped for me. I think it is to do with the vlans on the SG-1100 ?

Gil

@gil Thought I'd retry editing the xml config from the APU2 and then uploading it to my SG-1100.
I cut & pasted the 'interfaces" portion of the APU2 xml - using the default 'interfaces' from the SG-1100 xml.
Then uploaded it to the SG-1100
The SG-1100 then required manual re-configuration via the console as it couldn't assign ports and had no vlans. - hence no lan connectivity.
Do I need to copy other portions of the xml - such as the Vlan section? & any other sections?

jimp

The switch on the 1100 makes it tricky (same as the 7100 and 3100) but you can help it a bit.

Make a backup from the 1100 and your old device
Copy the switch config and VLAN config from the 1100 config to your old device config backup
Optionally edit the interface names in the old device config to what you want them to be now
Restore the config

There is an option to keep the switch config when restoring, which helps, but you still need to add the VLANs back before you can remap the interfaces. You should be able to do this in the GUI after the restore. For example, restore and choose to keep the switch config, then at the assign interfaces screen, switch over to the VLANs tab and add in VLANs to match the stock 1100 VLAN config, then go back to assignments and pick the correct ports. Just make sure not to click apply on anything until you are completely done, since that will trigger a reboot.

Gil

@jimp Okay, that works. - But I now get an error in an Openvpn client connection.

Jan 27 16:40:29 openvpn 42429 ERROR: FreeBSD route add command failed: external program exited with error status: 1
Jan 27 16:40:29 openvpn 42429 /sbin/route add -net 192.168.1.0 10.11.99.1 255.255.255.0

All interfaces are correctly assigned and all firewall rules are also as they were.

Gil

I should add that the OpenVPN connection is successful and the Tunnel IP address is assigned corectly from the remote server.