2.3.1 Snapshots Testing and Feedback - ARCHIVED

Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

H

Status > Interfaces presentation

• • hda

2

0
Votes

2
Posts

1.0k
Views

C

Fixed, thanks.
J

Status > Monitoring custom date range added (WIP)

• • jdillard

17

0
Votes

17
Posts

3.4k
Views

J

Just pushed changes that should fix the UTC offset issues.
S

OpenVPN Client Traffic gets lost

• • Starko

3

0
Votes

3
Posts

1.1k
Views

S

I'm sorry, the error disappeared after another reboot. Forgot to close the topic. Thanks for your answer.
?

(Solved)System Information Widget-Temperature Section visual bug

• • A Former User

6

0
Votes

6
Posts

1.4k
Views

P

No problem. I put a note on 6232 pointing to 6251. I happened to notice 6251 first, but both report the same issue.
H

IPv6 or Unbound broken ?

• • hda

4

0
Votes

4
Posts

1.4k
Views

H

Sheesh, whatever. Reboot helped. 2.3.1.a.20160422.2257
And WAN-IPv6 is on igb0 again…
H

Difference in version versus update

• • hda

2

0
Votes

2
Posts

989
Views

C

The "built on" is the kernel build date. Since updates no longer have to contain a new kernel if nothing has changed there, the date of your snapshot can be newer than the kernel's build time. That used to not be true since every update updated everything. Probably ought to be changed at some point but not something worth bothering with at the moment.
J

MOVED: monitoring feature request

• • jdillard

1

0
Votes

1
Posts

808
Views

No one has replied
G

Monitoring request

• • grandrivers

8

0
Votes

8
Posts

2.6k
Views

J

You care correct, sometimes I forget I'm not dealing with raw data. Not having raw data makes me sad :(

The best resolution you can do for a 2 day period is 5 minutes, because the data starts being averaged out by that point. I'll push some more changes today, but the new custom range will default to the lowest resolution possible, so if you want you can play around with ranges and watch the the highest resolution possible lower as you get further in the past.
J

MOVED: Own logo

• • jdillard

1

0
Votes

1
Posts

1.1k
Views

No one has replied
R

Odd notifications…

• • rcfa

6

0
Votes

6
Posts

1.7k
Views

R

OK, paying a bit more precise attention:

This:
Filter Reload There were error(s) loading the rules: /tmp/rules.debug:116: macro 'IPsec' not defined - The line in question reads [116]: pass out on $IPsec all tracker 1000000961 tracker 1000000962 keep state label "IPsec internal host to host" @ 2016-04-19 23:10:06
seems to follow this:
Crash report begins. Anonymous machine information: amd64 10.3-RELEASE FreeBSD 10.3-RELEASE #17 3110597(RELENG_2_3): Mon Apr 18 04:07:52 CDT 2016 root@ce23-amd64-builder:/builder/pfsense/tmp/obj/builder/pfsense/tmp/FreeBSD-src/sys/pfSense Crash report details: PHP Errors: [19-Apr-2016 23:10:04 Etc/UTC] PHP Stack trace: [19-Apr-2016 23:10:04 Etc/UTC] PHP 1\. {main}() /etc/rc.filter_configure_sync:0 [19-Apr-2016 23:10:04 Etc/UTC] PHP 2\. filter_configure_sync() /etc/rc.filter_configure_sync:37 [19-Apr-2016 23:10:04 Etc/UTC] PHP 3\. filter_generate_optcfg_array() /etc/inc/filter.inc:277 [19-Apr-2016 23:10:04 Etc/UTC] PHP 4\. get_configured_interface_with_descr() /etc/inc/filter.inc:1107 [19-Apr-2016 23:10:04 Etc/UTC] PHP Stack trace: [19-Apr-2016 23:10:04 Etc/UTC] PHP 1\. {main}() /etc/rc.filter_configure_sync:0 [19-Apr-2016 23:10:04 Etc/UTC] PHP 2\. filter_configure_sync() /etc/rc.filter_configure_sync:37 [19-Apr-2016 23:10:04 Etc/UTC] PHP 3\. filter_generate_gateways() /etc/inc/filter.inc:288 [19-Apr-2016 23:10:04 Etc/UTC] PHP 4\. return_gateways_array() /etc/inc/filter.inc:880 [19-Apr-2016 23:10:04 Etc/UTC] PHP 5\. get_configured_interface_with_descr() /etc/inc/gwlb.inc:593 [19-Apr-2016 23:10:04 Etc/UTC] PHP Stack trace: [19-Apr-2016 23:10:04 Etc/UTC] PHP 1\. {main}() /etc/rc.filter_configure_sync:0 [19-Apr-2016 23:10:04 Etc/UTC] PHP 2\. filter_configure_sync() /etc/rc.filter_configure_sync:37 [19-Apr-2016 23:10:04 Etc/UTC] PHP 3\. filter_generate_gateways() /etc/inc/filter.inc:288 [19-Apr-2016 23:10:04 Etc/UTC] PHP 4\. return_gateway_groups_array() /etc/inc/filter.inc:881 [19-Apr-2016 23:10:04 Etc/UTC] PHP 5\. return_gateways_status() /etc/inc/gwlb.inc:891 [19-Apr-2016 23:10:04 Etc/UTC] PHP 6\. return_gateways_array() /etc/inc/gwlb.inc:418 [19-Apr-2016 23:10:04 Etc/UTC] PHP 7\. get_configured_interface_with_descr() /etc/inc/gwlb.inc:593 [19-Apr-2016 23:10:04 Etc/UTC] PHP Stack trace: [19-Apr-2016 23:10:04 Etc/UTC] PHP 1\. {main}() /etc/rc.filter_configure_sync:0 [19-Apr-2016 23:10:04 Etc/UTC] PHP 2\. filter_configure_sync() /etc/rc.filter_configure_sync:37 [19-Apr-2016 23:10:04 Etc/UTC] PHP 3\. filter_generate_gateways() /etc/inc/filter.inc:288 [19-Apr-2016 23:10:04 Etc/UTC] PHP 4\. return_gateway_groups_array() /etc/inc/filter.inc:881 [19-Apr-2016 23:10:04 Etc/UTC] PHP 5\. return_gateways_status() /etc/inc/gwlb.inc:891 [19-Apr-2016 23:10:04 Etc/UTC] PHP 6\. return_gateways_array() /etc/inc/gwlb.inc:444 [19-Apr-2016 23:10:04 Etc/UTC] PHP 7\. get_configured_interface_with_descr() /etc/inc/gwlb.inc:593 [19-Apr-2016 23:10:04 Etc/UTC] PHP Stack trace: [19-Apr-2016 23:10:04 Etc/UTC] PHP 1\. {main}() /etc/rc.filter_configure_sync:0 [19-Apr-2016 23:10:04 Etc/UTC] PHP 2\. filter_configure_sync() /etc/rc.filter_configure_sync:37 [19-Apr-2016 23:10:04 Etc/UTC] PHP 3\. filter_generate_gateways() /etc/inc/filter.inc:288 [19-Apr-2016 23:10:04 Etc/UTC] PHP 4\. return_gateway_groups_array() /etc/inc/filter.inc:881 [19-Apr-2016 23:10:04 Etc/UTC] PHP 5\. return_gateways_array() /etc/inc/gwlb.inc:892 [19-Apr-2016 23:10:04 Etc/UTC] PHP 6\. get_configured_interface_with_descr() /etc/inc/gwlb.inc:593
within short order. There seems to be a correlation between these two…
H

Disabling Iface-MoDem(igb0) pulls Iface-WAN(igb0) down

• • hda

5

0
Votes

5
Posts

1.1k
Views

D

@hda:

pfSense-2.3.1-DEV full amd64. I use a MoDem in bridge with pfSense in PPPoE.
So I created a separate interface on WAN for the MoDem to see it.

You're not creating a separate interface. You are creating a pfSense interface on the physical interface that was already in use by mpd5, the PPPoE daemon, for your WAN interface.

When you disable the modem interface, line 465 (I'm looking at 2.3) of /usr/local/www/interfaces.php will call interface_bring_down() with the destroy parameter set to true on the modem interface. interface_bring_down() (in /etc/inc/interfaces.inc) does not contain a check as to whether the physical interface is in use for PPPoE - it will just ifconfig down the physical interface. At this point, the ground is torn out from under mpd5 daemon as well as the underlying netgraph structure used for PPPoE on the interface. Things go very wrong at this point - worst case, you'll get a kernel panic.

Arguably interface_bring_down() should check that the physical interface is not in use for a PPPoE port, CARP or similar before calling pfSense_interface_destroy() on the interface (line 1438 of /etc/inc/interfaces.inc).

If you want to disable the parent assignment, find some other way to disabling the interface, as cmb says.
A

Você quis dizer: addon sarg não disponível addon not available sarg

• • alexrenew

2

0
Votes

2
Posts

778
Views

D

As mentioned in the 2.3 Removed Packages documentation page, Sarg has been discontinued - use LightSquid instead.
H

[solved ] 2.3-release CP - crash report

• • heper

8

0
Votes

8
Posts

3.3k
Views

P

PR already merged, that was quick.
Redmine issue https://redmine.pfsense.org/issues/6203 for tracking.
N

Periodic RRD & DHCP Leases Backup

• • NOYB

4

0
Votes

4
Posts

1.5k
Views

N

PR submitted. https://github.com/pfsense/pfsense/pull/2883
F

2.3 Phantom Packages and small quirks

• • faranda

1

0
Votes

1
Posts

874
Views

No one has replied
M

Lightsquid not starting

• • maverick_slo

2

0
Votes

2
Posts

2.0k
Views

M

Reinstall of package fixed it.
Probably update updated some module to newer version than it should?

3 / 3