pfSesnse 1.5.2 to 2.7.2 Proxmox
-
Hello,
I have been trying to upgrade from 1.5.2 to 2.7.2 - when i try to do it from the UI i get "Unable to check for updates"
I then make a full config backup of my 1.5.2 and install a fresh 2.7.2 and then restore my config but then it all loses connection and the only way to get it back is to assign the WAN interface and add IPs but all my other connections are then gone and not assigned and i lose all my rules and settings and so on
Its like the 2.7.2 is not assigning to the NICS correctly and its also missing other setting like the firewall rules and even HTTPS for the GUI.
When upgrading to 1.6.0 it works fine, but still the same issues i cant upgrade from there to 2.7.2 and i get the "Unable to check for updates"
I have tried endless commands which dont seem to work.
any help would be great - just seems like so many issues with pfsense recently
-
You mean 2.5.2? There was never a 1.5.2 release.
When you restore the config into 2.7.2 does it ask you to reassign the NICs?
Where does it fail in the next boot?
Steve
-
Yes sorry 1.5.2
Doesnt ask me anything and no errors on boot at all.
all looks to be assigned but nothing works or pings, and its not the firewall rules.
Only works when i assign the nic and add the ip again.
-
Hmm, how do you have the interfaces configured? Anything exotic?
What does Status > Interfaces show after importing the config?
If resaving the WAN allows it to connect something must be missing from the running interface settings.
-
@stephenw10 Nothing exotic - all the hardware is the same, its just a VM ontop of proxmox.
Not sure how it can work perfectly fine on 1.6.0 when i restore the config, but doesnt on 1.7.2 so something must be wrong on 1.7.2
-
I assume you mean 2.6 and 2.7.2.
Right something in the interface is coming up differently. So how is it configured? vtnet NICs? PCI pass through? DHCP?
-
@stephenw10 im going to try try and hardset the MAC's on each interface to see if that helps when i restore.
-
still didnt work, on the boot it says its mapped to the right nics and there is no errors on the boot - no idea what is going on with 2.7.2 but works on 2.6.0
-
something very strange is going on....
i can ping the secondary upgraded pfsense (2.7.2) from my primary (2.5.2) but i cant access it from our NAT - no reason why not and always worked before and works on 2.6.0
this is driving me crazy
-
@stephenw10 send you a PM - mind if i send you my config for a quick check?
-
@netcetera-chris said in pfSesnse 1.5.2 to 2.7.2 Proxmox:
i cant access it from our NAT
Exactly how are you trying to connect that's failing there?
-
so we have a main office network which connects to multiple networks / vlans via NAT and works perfect but since the upgrade to 2.7.2 i cant ping or access the 2.7.2. pfsense - i have disabled the firewall - this all makes 0 sense.
-
when i re-assign the interface and add the IP and reboot the pfsense it then works. this has to be an issue with 2.7.2
-
Ok so pfSense here is routing between the main network and the VLANs? It has interfaces in all those subnets?
The NAT is port forwarding between them?
The primary and secondary here are an HA pair? Or devices at different sites?
-
@stephenw10 I have managed to access the pfsense webgui via a different ip and it seems all the settings and nic's are correct, but still the wan IP does not ping and neither does the other networks, i cant see any reason why not - i have made any any rules and NAT works from our primary firewall.
something is going on strange with this
-
@stephenw10 They are HA pair, im just upgrading the secondary - i can access via the office network subnet to the same subnet ip on the upgraded pfsense.
but still cant get to the other networks. - i have sent you a private message and uploaded the config.
-
ok, im getting closer to the issue.
On my NAT its going from the CARP Gateway it doesnt work, but it does work when going from the interface IP..
so what has changed - how can i fix this?
-
For reference it was this: https://redmine.pfsense.org/issues/14026
