how to go from old computer running pfsense to a sg-1100
-
steve,
yeah, 2.4.5, not 2.5
i will update my dell to 2.4.5, backup the config and restore it on the sg-1100
thanks much,
-
You can just leave your DELL as backup, no need to upgrade. Only take a backup via the WebGUI and thats it, then shut it down.
Flash your SG-1100 with the latest 2.4.5 factory Image, restore your DELL config and let it fly. :-)-Rico
-
i updated the sg-1100 to 2.4.5 and that went smooth.
i am using it now as my main router.as @teamits wrote above, based on the documentation.
"if the new target hardware has different NICs than the system where the backup was taken, a prompt will appear to re-assign the NICs after restoring the configuration."will i get a prompt, and if so, how will i be able to see it, as there is no video to hook up a monitor?
thanks much,
dave -
You should see it in the GUI when you upload the config, you will be taken to the interfaces re-assign page to set them.
If not though you would see it at the console:
https://docs.netgate.com/pfsense/en/latest/solutions/sg-1100/connect-to-console.htmlOn the SG-1100 you will need the switch and vlan config to get connectivity. If you have any issues please open a ticket and we can assist: https://go.netgate.com/
We are very busy in support right now though, we may not be able to respond as quickly as we would like.Steve
-
sure i understand that you are busy.
and my case is not an emergency,but i tried to update to 2.4.5 and it failed
please advise,
thanksUpdating repositories metadata...
Updating pfSense-core repository catalogue...
Fetching meta.txz: . done
Fetching packagesite.txz: . done
Processing entries: . done
pfSense-core repository update completed. 6 packages processed.
Updating pfSense repository catalogue...
Fetching meta.txz: . done
Fetching packagesite.txz: .......... done
Processing entries:
Processing entries............. done
pfSense repository update completed. 439 packages processed.
All repositories are up to date.
Setting vital flag on pkg... done.
Removing vital flag from php72... done.
Downloading upgrade packages...
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
Checking for upgrades (109 candidates): .......... done
Processing candidates (109 candidates): .......... done
The following 124 package(s) will be affected (of 0 checked):New packages to be INSTALLED:
python37: 3.7.6 [pfSense]
arm64resetbutton: 0.2 [pfSense]
isc-dhcp44-server: 4.4.1_4 [pfSense]
isc-dhcp44-relay: 4.4.1 [pfSense]
isc-dhcp44-client: 4.4.1_1 [pfSense]
php72-intl: 7.2.29 [pfSense]
icu: 65.1,1 [pfSense]
lua-resty-core: 0.1.17 [pfSense]
lua-resty-lrucache: 0.09 [pfSense]
luajit-openresty: 2.1.20190912_2 [pfSense]
libxslt: 1.1.34 [pfSense]
libgcrypt: 1.8.5 [pfSense]
libgpg-error: 1.36 [pfSense]
py37-ply: 3.11 [pfSense]
py37-setuptools: 41.4.0_1 [pfSense]Installed packages to be UPGRADED:
wpa_supplicant: 2.6_2 -> 2.9 [pfSense]
wol: 0.7.1_3 -> 0.7.1_4 [pfSense]
unbound: 1.8.1 -> 1.9.6 [pfSense]
uclcmd: 0.1_2 -> 0.1_3 [pfSense]
strongswan: 5.7.1 -> 5.8.2 [pfSense]
sshguard: 2.2.0_4 -> 2.4.0_3,1 [pfSense]
sqlite3: 3.24.0_1 -> 3.30.1 [pfSense]
smartmontools: 6.6_1 -> 7.0_2 [pfSense]
scponly: 4.8.20110526_2 -> 4.8.20110526_4 [pfSense]
rrdtool: 1.7.0_2 -> 1.7.2_1 [pfSense]
relayd: 5.5.20140810_2 -> 5.5.20140810_5 [pfSense]
readline: 7.0.3_1 -> 8.0.1 [pfSense]
radvd: 2.17_5 -> 2.18_2 [pfSense]
python27: 2.7.15 -> 2.7.17_1 [pfSense]
py27-setuptools: 39.2.0 -> 41.4.0_1 [pfSense]
php72-zlib: 7.2.10 -> 7.2.29 [pfSense]
php72-xmlwriter: 7.2.10 -> 7.2.29 [pfSense]
php72-xmlreader: 7.2.10 -> 7.2.29 [pfSense]
php72-xml: 7.2.10 -> 7.2.29 [pfSense]
php72-tokenizer: 7.2.10 -> 7.2.29 [pfSense]
php72-sysvshm: 7.2.10 -> 7.2.29 [pfSense]
php72-sysvsem: 7.2.10 -> 7.2.29 [pfSense]
php72-sysvmsg: 7.2.10 -> 7.2.29 [pfSense]
php72-sqlite3: 7.2.10 -> 7.2.29 [pfSense]
php72-sockets: 7.2.10 -> 7.2.29 [pfSense]
php72-simplexml: 7.2.10 -> 7.2.29 [pfSense]
php72-shmop: 7.2.10 -> 7.2.29 [pfSense]
php72-session: 7.2.10 -> 7.2.29 [pfSense]
php72-readline: 7.2.10 -> 7.2.29 [pfSense]
php72-posix: 7.2.10 -> 7.2.29 [pfSense]
php72-pecl-zmq: 1.1.3_2 -> 1.1.3_3 [pfSense]
php72-pecl-mcrypt: 1.0.1 -> 1.0.3 [pfSense]
php72-pear-XML_RPC2: 1.1.3_1 -> 1.1.4 [pfSense]
php72-pear-Net_SMTP: 1.8.0 -> 1.9.0 [pfSense]
php72-pear: 1.10.5_1 -> 1.10.6 [pfSense]
php72-pdo_sqlite: 7.2.10 -> 7.2.29 [pfSense]
php72-pdo: 7.2.10 -> 7.2.29 [pfSense]
php72-pcntl: 7.2.10 -> 7.2.29 [pfSense]
php72-openssl: 7.2.10 -> 7.2.29 [pfSense]
php72-opcache: 7.2.10 -> 7.2.29 [pfSense]
php72-mbstring: 7.2.10 -> 7.2.29 [pfSense]
php72-ldap: 7.2.10 -> 7.2.29 [pfSense]
php72-json: 7.2.10 -> 7.2.29 [pfSense]
php72-hash: 7.2.10 -> 7.2.29 [pfSense]
php72-gettext: 7.2.10 -> 7.2.29 [pfSense]
php72-filter: 7.2.10 -> 7.2.29 [pfSense]
php72-dom: 7.2.10 -> 7.2.29 [pfSense]
php72-curl: 7.2.10 -> 7.2.29 [pfSense]
php72-ctype: 7.2.10 -> 7.2.29 [pfSense]
php72-bz2: 7.2.10 -> 7.2.29 [pfSense]
php72-bcmath: 7.2.10 -> 7.2.29 [pfSense]
php72: 7.2.10 -> 7.2.29 [pfSense]
pftop: 0.7_8 -> 0.7_9 [pfSense]
pfSense-u-boot-env: 20181018_2 -> 20200316 [pfSense]
pfSense-rc: 2.4.4_2 -> 2.4.5 [pfSense-core]
pfSense-pkg-ipsec-profile-wizard: 0.11 -> 0.12 [pfSense]
pfSense-pkg-aws-wizard: 0.7_6 -> 0.8 [pfSense]
pfSense-kernel-pfSense: 2.4.4_2 -> 2.4.5 [pfSense-core]
pfSense-default-config-serial: 2.4.4_2 -> 2.4.5 [pfSense-core]
pfSense-base: 2.4.4_2 -> 2.4.5 [pfSense-core]
pfSense-Status_Monitoring: 1.7.6 -> 1.7.11_1 [pfSense]
pfSense: 2.4.4_2 -> 2.4.5 [pfSense]
perl5: 5.26.2 -> 5.30.1 [pfSense]
pcre: 8.42 -> 8.43_2 [pfSense]
openvpn: 2.4.6_1 -> 2.4.8 [pfSense]
openldap-client: 2.4.46 -> 2.4.48 [pfSense]
oniguruma: 6.8.1 -> 6.9.3 [pfSense]
ntp: 4.2.8p12 -> 4.2.8p14 [pfSense]
nginx: 1.14.0_6,2 -> 1.16.1_11,2 [pfSense]
nettle: 3.4 -> 3.5.1_1 [pfSense]
netgate-ping-auth: 20181211 -> 20200310 [pfSense]
netgate-ca: 20180827 -> 20191211 [pfSense]
mpd5: 5.8_8 -> 5.8_10 [pfSense]
mobile-broadband-provider-info: 20170310 -> 20190618_1 [pfSense]
miniupnpd: 2.0.20180503,1 -> 2.1.20190210,1 [pfSense]
links: 2.16,1 -> 2.16_2,1 [pfSense]
libzmq4: 4.2.3 -> 4.3.1_1 [pfSense]
libxml2: 2.9.7 -> 2.9.10 [pfSense]
libunistring: 0.9.10 -> 0.9.10_1 [pfSense]
libucl: 0.8.0 -> 0.8.1 [pfSense]
libnghttp2: 1.32.0 -> 1.40.0 [pfSense]
liblz4: 1.8.2,1 -> 1.9.2,1 [pfSense]
libidn2: 2.0.5 -> 2.3.0_1 [pfSense]
libffi: 3.2.1_2 -> 3.2.1_3 [pfSense]
libevent: 2.1.8_1 -> 2.1.11 [pfSense]
libedit: 3.1.20170329_2,1 -> 3.1.20191211,1 [pfSense]
libargon2: 20171227 -> 20190702 [pfSense]
ldns: 1.7.0_1 -> 1.7.1_1 [pfSense]
json-c: 0.13 -> 0.13.1_1 [pfSense]
ipmitool: 1.8.18_1 -> 1.8.18_2 [pfSense]
hostapd: 2.6_2 -> 2.9 [pfSense]
gmp: 6.1.2 -> 6.1.2_1 [pfSense]
glib: 2.50.3_4,1 -> 2.56.3_7,1 [pfSense]
gettext-runtime: 0.19.8.1_1 -> 0.20.1 [pfSense]
filterdns: 2.0_1 -> 2.0_3 [pfSense]
expat: 2.2.5 -> 2.2.8 [pfSense]
dnsmasq: 2.79,1 -> 2.80_4,1 [pfSense]
dhcpleases: 0.3_1 -> 0.3_2 [pfSense]
dhcp6: 20080615.2 -> 20080615.2_2 [pfSense]
curl: 7.62.0 -> 7.67.0 [pfSense]
cpdup: 1.18 -> 1.20 [pfSense]
ccache: 3.4.2 -> 3.7.1 [pfSense]
ca_root_nss: 3.39 -> 3.51 [pfSense]
bsnmp-ucd: 0.4.2 -> 0.4.4 [pfSense]
bind-tools: 9.12.2P1 -> 9.14.9 [pfSense]
aws-sdk-php72: 3.61.8 -> 3.103.2 [pfSense]Installed packages to be REINSTALLED:
php72-pecl-radius-1.4.0.b1 [pfSense] (option added: EXAMPLES)
php72-pear-Net_Socket-1.0.14 [pfSense] (ABI changed: 'freebsd:11:aarch64:64' -> 'freebsd:11:*')
check_reload_status-0.0.8 [pfSense] (needed shared library changed)Number of packages to be installed: 15
Number of packages to be upgraded: 106
Number of packages to be reinstalled: 3The process will require 201 MiB more space.
120 MiB to be downloaded.
[1/124] Fetching wpa_supplicant-2.9.txz: .......... done
[2/124] Fetching wol-0.7.1_4.txz: .... done
[3/124] Fetching unbound-1.9.6.txz: .......... done
[4/124] Fetching uclcmd-0.1_3.txz: .. done
[5/124] Fetching strongswan-5.8.2.txz: .......... done
[6/124] Fetching sshguard-2.4.0_3,1.txz: .......... done
[7/124] Fetching sqlite3-3.30.1.txz: .......... done
[8/124] Fetching smartmontools-7.0_2.txz: .......... done
[9/124] Fetching scponly-4.8.20110526_4.txz: ... done
[10/124] Fetching rrdtool-1.7.2_1.txz: .......... done
[11/124] Fetching relayd-5.5.20140810_5.txz: .......... done
[12/124] Fetching readline-8.0.1.txz: .......... done
[13/124] Fetching radvd-2.18_2.txz: ...... done
[14/124] Fetching python27-2.7.17_1.txz: .......... done
[15/124] Fetching py27-setuptools-41.4.0_1.txz: .......... done
[16/124] Fetching php72-zlib-7.2.29.txz: .. done
[17/124] Fetching php72-xmlwriter-7.2.29.txz: .. done
[18/124] Fetching php72-xmlreader-7.2.29.txz: .. done
[19/124] Fetching php72-xml-7.2.29.txz: ... done
[20/124] Fetching php72-tokenizer-7.2.29.txz: .. done
[21/124] Fetching php72-sysvshm-7.2.29.txz: . done
[22/124] Fetching php72-sysvsem-7.2.29.txz: . done
[23/124] Fetching php72-sysvmsg-7.2.29.txz: . done
[24/124] Fetching php72-sqlite3-7.2.29.txz: ... done
7538588:error:14099044:SSL routines:ssl3_send_client_verify:internal error:/usr/local/poudriere/jails/pfSense_factory-v2_4_5_aarch64/usr/src/crypto/openssl/ssl/s3_clnt.c:3266:
Child process pid=53021 terminated abnormally: Segmentation fault
Failed -
@jojothehumanmonkey said in how to go from old computer running pfsense to a sg-1100:
Segmentation fault
If you're updating the 1100 there have been a few posts in the last week or so with that type of error message on an 1100. We haven't done any 2.4.5 updates yet.
-
@teamits said in how to go from old computer running pfsense to a sg-1100:
We haven't done any 2.4.5 updates yet
not sure who you mean when you write 'We'.
somehow, rebooting over and rebooting, using the serial console, which worked on my windows laptop. i got 2.4.5 running.
i tried to update the config but that did not go well, so i have to factory reset the sg-1100.
i think that i will have to manually reconfigure the sg-1100 from scratch.
but that is ok.so thanks to all for helping and be safe.
-
@jojothehumanmonkey said in how to go from old computer running pfsense to a sg-1100:
not sure who you mean when you write 'We'.
Me, my company. We're a Netgate partner and pfSense user.
Sorry if it didn't work. It's been a while since I did config importing cross-hardware but as I recall I did get prompted for the interfaces which is what the docs say. In a pinch the config .xml file can be edited and sections copied/pasted, say if you have a lot of firewall rules.
-
@teamits,
thanks much
-
Yup, from a failed upgrade like that I would install 2.4.5 clean and then import the config again.
We can assist with both those things if you open a ticket: https://go.netgate.com/
Steve
-
This post is deleted!
