Re: [pfSense] 2.3.1 -> 2.3 ?

On Wed, Apr 13, 2016 at 4:53 AM, Olivier Mascia wrote: > Hello, > > I had a 2.3 RC installed and (mistakenly) let it auto-upgrade some hours ago. > It went straight to some 2.3.1 DEV instead of 2.3 REL as I expected (my > mistake). Is there any appropriate way to come back to

Re: [pfSense] vmware tools

On Wed, Apr 13, 2016 at 5:12 AM, Olivier Mascia wrote: > Reading this: https://doc.pfsense.org/index.php/Open_VM_Tools_package > after package installation and reboot, > > ps uxawww | grep vmware > > gives me this output which differs from the doc.pfsense.org article: > > root

Re: [pfSense] 2.3 - webConfigurator Fails

On Wed, Apr 13, 2016 at 5:46 PM, David White wrote: > I just upgraded to 2.3, and internet seems to be working fine, but the > webConfigurator is failing. > > pfSense is running on some older x86 hardware. Checking the system.log, I > see this entry: > > php-cgi: rc.bootup:

Re: [pfSense] 2.3 show stopper - bind package missing -- don't install if you need bind!

On Wed, Apr 13, 2016 at 5:17 PM, Steve Yates wrote: > I should restate/clarify that I was looking at the > https://doc.pfsense.org/index.php/2.3_New_Features_and_Changes > page which mentions the package system changed but doesn't specifically > mention the below Good point,

Re: [pfSense] 2.3 show stopper - bind package missing -- don't install if you need bind!

For a list of Packages in 2.3, see https://doc.pfsense.org/index.php/Package_Port_List For a list of packages removed from 2.3, see https://doc.pfsense.org/index.php/2.3_Removed_Packages Walter On Wed, Apr 13, 2016 at 3:17 PM, Steve Yates wrote: > I should restate/clarify

Re: [pfSense] 2.3 show stopper - bind package missing -- don't install if you need bind!

I should restate/clarify that I was looking at the https://doc.pfsense.org/index.php/2.3_New_Features_and_Changes page which mentions the package system changed but doesn't specifically mention the below, which is on the https://doc.pfsense.org/index.php/Upgrade_Guide#Package_System page that

Re: [pfSense] 2.3 show stopper -- in most cases openvpn client specific overrides will fail to send proper iroute/push route

On Wed, Apr 13, 2016 at 6:08 AM, mayak wrote: > hi all , > > openvpn will fail on v2.3 if you are using `client specific overrides` where > `iroute` and `push route` are being used: > > if the `tunnel network` is: > 10.16.52.8/30 > > and the `advanced section`: > iroute

Re: [pfSense] 2.3 show stopper - bind package missing -- don't install if you need bind!

On Wed, Apr 13, 2016 at 1:48 PM, Steve Yates wrote: > The release notes don't mention specific package compatibility Yes it does. "Packages The list of available packages in pfSense 2.3 has been significantly trimmed. We have removed packages that have been deprecated

Re: [pfSense] 2.3 show stopper - bind package missing -- don't install if you need bind!

The release blog post led me to the upgrade notes which have: https://doc.pfsense.org/index.php/Upgrade_Guide#Package_System "Packages require significant conversion for use on 2.3, currently only the most popular and supported packages are present on 2.3, so be aware that some packages are

Re: [pfSense] 2.3 show stopper - bind package missing -- don't install if you need bind!

On Wed, Apr 13, 2016 at 11:48 AM, Steve Yates wrote: > The release notes don't mention specific package compatibility but a lot > of that's third party. In System: Package Manager does the "platform: 2.2" > mean the package is compatible with only 2.2? Or is that because I'm

Re: [pfSense] 2.3 show stopper - bind package missing -- don't install if you need bind!

The release notes don't mention specific package compatibility but a lot of that's third party. In System: Package Manager does the "platform: 2.2" mean the package is compatible with only 2.2? Or is that because I'm looking at a v2.2 installation? Is there a package compatibility list for

Re: [pfSense] pfSense 2.3 and Unsupported Bandwidthd and Vnstat2

On Wed, 13 Apr 2016 06:44:12 -0500 "Peder Rovelstad" wrote: > First off, congratulations on the latest version. It is just beautiful in > its presentation of the management pages and so far I haven't run into any > (non-self-inflicted) problems, though it appears my VIA

[pfSense] pfSense 2.3 and Unsupported Bandwidthd and Vnstat2

First off, congratulations on the latest version. It is just beautiful in its presentation of the management pages and so far I haven't run into any (non-self-inflicted) problems, though it appears my VIA C7 platform is reaching its EOL. I may need to roll back to 2.2.5 and call it quits for

[pfSense] 2.3 show stopper -- in most cases openvpn client specific overrides will fail to send proper iroute/push route

hi all , openvpn will fail on v2.3 if you are using `client specific overrides` where `iroute` and `push route` are being used: if the `tunnel network` is: 10.16.52.8/30 and the `advanced section`: iroute 172.16.32.0 255.255.255.0; push "route 10.0.0.0 255.0.0.0"; push "route 172.16.0.0

Re: [pfSense] pfSense 2.3 "Secure Connection Failed"

On 12/04/2016 23:06, Chris Buechler wrote: > If it's the same browser and > system that can connect to 1 of 3 but not the other two, there's > something else going on there. Not sure what, haven't heard of that > from anyone else. Thanks Chris. Yes it's the same Windows 7 Pro with Firefox ESR 38

[pfSense] 2.3 show stopper - bind package missing -- don't install if you need bind!

hi all, upgraded to 2.3 and found that the bind package is missing. my whole network depends on its presence ... does anyone know when it might be available? thanks m -- Markets can remain irrational longer than you can remain solvent. — John Maynard Keynes

[pfSense] vmware tools

Reading this: https://doc.pfsense.org/index.php/Open_VM_Tools_package after package installation and reboot, ps uxawww | grep vmware gives me this output which differs from the doc.pfsense.org article: root55265 0.0 0.2 17000 2516 - S12:04PM 0:00.00 sh -c ps uxawww | grep

[pfSense] 2.3.1 -> 2.3 ?

Hello, I had a 2.3 RC installed and (mistakenly) let it auto-upgrade some hours ago. It went straight to some 2.3.1 DEV instead of 2.3 REL as I expected (my mistake). Is there any appropriate way to come back to 2.3 REL other than rebuilding it from scratch? (I don't have a problem