Upgrade pfsense CE 2.7.0 to 2.7.1
-
@cclarsen said in Upgrade pfsense CE 2.7.0 to 2.7.1:
Before I attempted the 2.7.1 upgrade, I updated all the packages that showed they were out of date
That will break things, never do that. See my sig. Uninstall packages as suggested per the upgrade guide, or just upgrade and the upgrade will uninstall/reinstall for you.
-
This post is deleted! -
@Patch Thanks Patch ... I will try that. It has been somewhat frustrating to get some images placed on this site. If necessary I will just past a link.
-
S saidin referenced this topic on
-
@stephenw10 Hi Stephen,
So my update problem with my secondary servers appears to be DNS. In the unbound DNS resolver, If I include either WAN or localhost in the outgoing DNS window I get resolution on my secondary. I am including localhost. I had already included localhost in the Interfaces window, as per normal in my understanding, unless of course I got them reversed. pfBlockers windows tend to confuse the isse. I always thought that for the firewall to be able to access the Internet I need to put localhost in Network interfaces. Now I am wondering if I got them switched, that is if I need to put localhost in the outgoing window instead. As localhost is not an Internet port I am a little confused as to what is happening.
I have to think about this for a little while, run some tests, reresarch it, and understand it. Understanding is important. Just enabling things because they work is not recommended procedure.
Of course your wise input is always appreciated.
Roy
-
What did you have selected for outgoing interfaces when it was failing?
-
@stephenw10 Just the virtual wan ip. I did the same thing for Squid.
I just did the Squid change recently. Squid is supposed to turn itself off anyway, so I don't really know if the vip is necessary there. Maybe not on the DNS resolver either. Of course we want DNS to work on the secondary unit.
I think I just chose those in each of those spots because it seemed appropriate. There is not much posted on using the vip in those packages. I just remember bbcan posting how to setup pfblocker on an early post including suggestions for the DNS resolver. But of course he didn't design pfBlocker for HA although there is a place for a VIP. On some of my equipment I have not been able to use that function. It does not function as expected. On those boxes I had problems with flooding when I tried the VIP on pfblocker. It is a very complex setup though with 4 heads. When I have a chance I will work it out the problems on the 12 to 5 shift.
That being said, I am grateful for bbcan's contribution. pfBlocker is an extremely useful package and I am glad for it and his efforts to maintain it.
Right now I just want to work on the appropriate DNS setting regardless of what any post might say.
Thanks for your suggestions.
-
@reberhar said in Upgrade pfsense CE 2.7.0 to 2.7.1:
Just the virtual wan ip.
Ah, well that would explain it. The WAN CARP VIP is only ever valid on the master node so a backup node could not use that to send DNS queries.
-
@stephenw10 Yes of course.
So should I include the wan and/or the localhost? I am assuming the wan.
-
It could be either. If you only have one WAN it doesn't really matter. Using localhost as source allows Unbound to use any interface as long NAT rules exist on it (and not to a CARP VIP!).
-
@stephenw10 localhost then. I didn't think about localhost being connected to all the wans.
Thanks,
Roy
-
@reberhar Thanks again Stephen,
It was still a long night fixing these problems at then ends of all my tunnels. The DNS being wrong and the updates being out of sync caused me several unexpected and unanticipated problems with one the pfSense secondary servers, including some certificate errors that the rehash couldn't fix. Some of the udates were interrupted because of the way I had done the DNS and me switching CARP states. I had to wait for the update certificates on the update server to time out. On these distant units I need to be more patient and give time for updates to finish. The latency and the tunnels can cause the update feedback to be lost, eventhough pfSense is still faithfully working along. A server can return, even after a very long wait.
This faithfulness and solidness of pfSense and FreeBSD has always impressed me. The programming must be quite awesome.
Thanks for your help and patience. Would I have figured it out alone? Yes I thinks so, but it is such a help to be able to ask. Research and trial and error work, but it is time consuming. Getting help on key points, however seemingly simple can be a big boost.
Thanks so much. You guys are really great.
-
@reberhar Hi guys, there is still another issue I am researching.
Automatic backup does not show any items in the list, although they appear when I put the key in other installation.
The following error is from a manual backup, not cron.
An error occurred while uploading the encrypted pfSense configuration to https://acb.netgate.com/save (Failed to connect to acb.netgate.com port 443 after 10108 ms: Couldn't connect to server) @ 2023-12-02 13:20:01
The machine in not able to fetch the repo.
pfSense-repoc: failed to fetch the repo data
The only repo that is available is 2.7.1 and that is selected.
DNS works from the gui and the command line, that is nslookup resolves.
ping fails of acb.netgate.com and at the command line it says ...
PING acb.netgate.com (208.123.73.212): 56 data bytes
ping: sendto: Permission denied
ping: sendto: Permission denied
ping: sendto: Permission denied
ping: sendto: Permission denied
ping: sendto: Permission deniedIt can ping other sites.
Static update gives...
[2.7.1-RELEASE][root@srofirewallsecondary.santarosa.sro]/root: pkg-static update -f
Updating pfSense-core repository catalogue...
pkg-static: An error occured while fetching package
pkg-static: An error occured while fetching package
repository pfSense-core has no meta file, using default settings
pkg-static: An error occured while fetching package
pkg-static: An error occured while fetching package
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg-static: An error occured while fetching package
pkg-static: An error occured while fetching package
repository pfSense has no meta file, using default settings
pkg-static: An error occured while fetching package
pkg-static: An error occured while fetching package
Unable to update repository pfSense
Error updating repositories!Rehashing gives ...
[2.7.1-RELEASE][root@srofirewallsecondary.santarosa.sro]/root: certctl rehash
Scanning /usr/share/certs/untrusted for certificates...
Scanning /usr/share/certs/trusted for certificates...
Skipping untrusted certificate /usr/share/certs/trusted/Cybertrust_Global_Root.pem (/etc/ssl/untrusted/76cb8f92.0)
Skipping untrusted certificate /usr/share/certs/trusted/DST_Root_CA_X3.pem (/etc/ssl/untrusted/2e5ac55d.0)
Skipping untrusted certificate /usr/share/certs/trusted/GlobalSign_Root_CA_-_R2.pem (/etc/ssl/untrusted/4a6481c9.0)
Skipping untrusted certificate /usr/share/certs/trusted/Hellenic_Academic_and_Research_Institutions_RootCA_2011.pem (/etc/ssl/untrusted/1636090b.0)
Skipping untrusted certificate /usr/share/certs/trusted/Network_Solutions_Certificate_Authority.pem (/etc/ssl/untrusted/4304c5e5.0)
Skipping untrusted certificate /usr/share/certs/trusted/Staat_der_Nederlanden_EV_Root_CA.pem (/etc/ssl/untrusted/03179a64.0)
Skipping untrusted certificate /usr/share/certs/trusted/TrustCor_ECA-1.pem (/etc/ssl/untrusted/7aaf71c0.0)
Skipping untrusted certificate /usr/share/certs/trusted/TrustCor_RootCert_CA-1.pem (/etc/ssl/untrusted/5d3033c5.0)
Skipping untrusted certificate /usr/share/certs/trusted/TrustCor_RootCert_CA-2.pem (/etc/ssl/untrusted/3e44d2f7.0)
Scanning /usr/local/share/certs for certificates...I tried this update line from the upgrade problem section of netgate forum. I wonder if it is right for 2.7.1. It failed.
[2.7.1-RELEASE][root@srofirewallsecondary.santarosa.sro]/root: fetch -qo /usr/local/share/pfSense/keys/pkg/trusted/ https://raw.githubusercontent.com/pfsense/pfsense/RELENG_2_4_5/src/usr/local/share/pfSense/keys/pkg/trusted/pkg.pfsense.org.20160406
I fetch: transfer timed outI am wondering if I need to do a reinstall. The box about 2500 miles from here the way the plane flies. It is a virtual machine.
Thanks for any help you can offer.
-
@reberhar said in Upgrade pfsense CE 2.7.0 to 2.7.1:
ping: sendto: Permission denied
That implies something locally blocking access. Do you have Snort or Suricata installed with blocking enabled?
Steve
-
@stephenw10 Gosh I should have thought of that. Working late can fry the brain I guess. Lots of little problems too.
Old chinese proverb says, "Many hands make light work."
It was blocked, now I just have to disable the rule that is doing it.
It was complaining of a bad checksum ... hmmm, maybe something to do with the virtual machine or hardware.
Thanks again! I wish I could send you something for Xmas.
Yes things seem to be working now.
Thanks Steve
-
@SteveITS
I was stuck on 2.7.0 with no packages in package manager after a downgrade to 2.7.0 from the Plus version.
I used ssh and ran the certctl rehash command and was able to upgrade to 2.7.2, and all the packages came with it!
Thanks, Steve. -
I looked up to download 2.7.2 but on the official website 2.7.1 is only available.
-
Yup the mirrors will be updated shortly.
-
@stephenw10 My 2.7.2 is up on my servers. One server I had to reboot because DNS did not reach the users, but I think that was an HA/CARP problem. A reboot of the primary server, the one with the problem, fixed that.
On one server, one of the modems went offline. It really was the modem because the cable connection went to autosync. I tried to bounce the connection, but no joy. I had to go to the site and power cycle the (T-Mobile) modem. The ethernet connection connection on the modem itself had disconnected. Really unusual. I am glad I was close by.
Roy
-
@reberhar Oh for bouncing the ethernet connection it is:
ifconfig interface down ; ifconfig interface up
Interface being the interface name, like maybe eth0 or igb0.
If you have only one modem you can use this too. That is why you do both these commands at once. If you do the first one only the port/interface will go offline and you will lose connection to that wan.
Roy
-
Cheers mate.
I only hit this snag when going from 2.7.0 to 2.7.2 on my work CARP cluster, so I missed it in the change notes for 2.7.1, which I have successfully upgraded to on several smaller systems. The update was showing but I usually like to do a pre-emptive reboot before an upgrade on a box with six months uptime. It stopped showing up after the reboot. Rehashing the certs sorted that out.
Well, the secondary is back up so let's fail over to it and see how it goes (I'm at home doing this from the outside!) ...
(edit) ... the primary has rebooted. It too forgot about the 2.7.2 update. I ran the cert rehash twice because I might have not waited long enough the first time - about one minute! I have been using the web GUI Diagnostics -> Command Prompt to run certctl.
... wait for reboot, AD DC still pinging over IPv6 IPSEC VPN ...
... its just come back up.. Leave CARP maint mode ... all good. My monitoring systems (Icinga1 and 2) didn't go berserk, so the 70 odd VPNs held up through out.
