Just upgraded to 2.2.2
-
Last Friday night, I upgraded our main pfSense instance from 2.1.5 x86 virtual machine to 2.2.2 amd64. I created a config.xml backup and then restored it on a newly-built virtual machine.
Two issues, one minor and one I have no idea how severe.
-
The Supermule interface stats widget barfed after upgrade and its GUI was filled with syntax errors. I just removed that widget.
-
Error message in WebGUI after bootup:
There were error(s) loading the rules: /tmp/rules.debug:126: macro 'VoIP_Phones' not defined - The line in question reads [126]: match inet proto udp from $VoIP_Phones to any tracker 1433538114 queue (qVoIP) label "USER_RULE: Connections From Upstream SIP Server"
The alias seems to exist and is properly defined. I don't know if I should be concerned or not.
-
-
That means the alias isn't there for some reason. Does it show up in the list under Diag>Tables?
-
It sure does, also under Firewall - Aliases and with the correct contents. Everything seems to be working as expected. It may have been a phantom error during restore of the XML.
-
Looks like I missed a biggie:
- Our FTP site no longer works. Try to connect and I get:
Transfer channel can't be opened. No connection could be made as the target machine actively refused it. Could not retrieve directory listing.
It was working perfectly under 2.1.5. My port forwards and rules are there and intact. It just doesn't work anymore after upgrade. Nothing of note in the firewall logs.
-
-
Thanks Heper. It was affecting my FTP server (not client), but I already had all of that stuff done. What fixed it for me was totally bizarre.
When I had first set this up a year or so ago I was pretty green. I had defined the passive port range different from the NAT'd port range for some reason that I don't remember. Originally I had 30000-30100 reserved for passive FTP (we don't have many FTP users at all so a small range was fine) and mapped it to 20-120. Duh, so stupid, but I didn't know what I was doing with pfSense at the time. I saw that, nuked the port remapping and let it sit natively at 30000-30100 and it's been working fine ever since.
