Netgate SG-1000 microFirewall

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - cmb

Pages: 1 [2] 3 4 5 6 ... 26
2.3.2 Development Snapshots / Welcome to the 2.3.2 board
« on: June 27, 2016, 02:56:03 pm »
2.3.2 snapshot builds are available

All open issues currently target 2.3.2 here

Resolved issues target 2.3.2 here

Note that most fixes going in currently also are going into the 2_3_1 branch for 2.3.1_x updates, so there are changes since the last update release which are included in 2.3.2 but not in those lists. The 2.3.1_6 resolved issues list includes additional things addressed in 2.3.2 as well as a future 2.3.1_6.

Upgrading to 2.3.2

If you're already on a 2.3.x version, you can upgrade to 2.3.2 by browsing to System>Update, Updater Settings tab. Change to Branch Development there and click Save. Go back to the System Update tab and upgrade there.

General Questions / MOVED: Acceso web pfsense
« on: June 16, 2016, 03:38:05 pm »

Documentation / MOVED: Dns bind doble vista
« on: June 14, 2016, 06:57:58 pm »

Messages from the pfSense Team / 2.3.1 Update 1 Available
« on: May 25, 2016, 05:56:17 pm »
2.3.1 Update 1 is now available. The changes can be found appended to the 2.3.1-RELEASE change list under Update 1.

2.3.1 snapshots are available for download.

This will be a short release cycle, so no major changes. We're a couple weeks out from release.

List of things confirmed fixed in 2.3.1
List of tickets needing feedback/testing confirmation
Open issues target 2.3.1

Please use the 2.3.1 snapshots board here for reporting feedback and any issues encountered.

Upgrading 2.3 to 2.3.1

To upgrade 2.3 beta, RC or release systems to 2.3.1, browse to System>Update, Update Settings tab. In the Branch drop down, choose "Development" or "Keep following 2.3 snapshots" depending on which of those is shown on the version you're currently running. Click Save, then browse to the System Update tab and click Confirm to upgrade.

If your gateway monitoring isn't working post-2.3 upgrade, it's likely one of two things.

Verify advanced options are sane

Browse to System>Routing and edit the gateway that's down. Then click Save. That will trigger the input validation that makes sure the configuration is valid, especially the advanced options. You may have had options set for apinger that are not valid for dpinger. If you get any errors upon saving, fix them, save, and apply changes.

Set ping payload size

Some modems have a bug that makes them drop pings with 0 byte payloads. dpinger uses a 0 byte payload by default because there isn't a need to include one and unnecessarily chew up bandwidth. If you have such a buggy upstream device, you'll need to set the payload to something greater than 0. System>Routing, edit the gateway, go to Advanced, and set payload to 1. Save and apply changes.

Pages: 1 [2] 3 4 5 6 ... 26