The pfSense Store

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 - AhnHEL

Pages: [1] 2 3
1
Using a fresh install with a default setup, going into the Traffic Shaper and attempting to enable any Scheduler Type gets me:

Fatal error: Call to undefined method altq_root_queue::SetAvailableBandwidth() in /usr/local/www/firewall_shaper.php on line 283 Call Stack: 0.0000 237600 1. {main}() /usr/local/www/firewall_shaper.php:0 PHP ERROR: Type: 1, File: /usr/local/www/firewall_shaper.php, Line: 283, Message: Call to undefined method altq_root_queue::SetAvailableBandwidth()

Using the pfSense-CE-2.3-BETA-amd64-20160329-0150 ISO

Quote
Crash report begins.  Anonymous machine information:

amd64
10.3-RELEASE
FreeBSD 10.3-RELEASE #490 51f8df0(RELENG_2_3): Tue Mar 29 02:06:06 CDT 2016     root@pfs23-amd64-builder:/usr/home/pfsense/pfsense/tmp/obj/usr/home/pfsense/pfsense/tmp/FreeBSD-src/sys/pfSense

Crash report details:

PHP Errors:
[29-Mar-2016 22:06:51 Etc/UTC] PHP Fatal error:  Call to undefined method altq_root_queue::SetAvailableBandwidth() in /usr/local/www/firewall_shaper.php on line 283
[29-Mar-2016 22:06:51 Etc/UTC] PHP Stack trace:
[29-Mar-2016 22:06:51 Etc/UTC] PHP   1. {main}() /usr/local/www/firewall_shaper.php:0
[29-Mar-2016 22:09:07 Etc/UTC] PHP Fatal error:  Call to undefined method altq_root_queue::SetAvailableBandwidth() in /usr/local/www/firewall_shaper.php on line 283
[29-Mar-2016 22:09:07 Etc/UTC] PHP Stack trace:
[29-Mar-2016 22:09:07 Etc/UTC] PHP   1. {main}() /usr/local/www/firewall_shaper.php:0
[29-Mar-2016 22:15:13 Etc/UTC] PHP Fatal error:  Call to undefined method altq_root_queue::SetAvailableBandwidth() in /usr/local/www/firewall_shaper.php on line 283
[29-Mar-2016 22:15:13 Etc/UTC] PHP Stack trace:
[29-Mar-2016 22:15:13 Etc/UTC] PHP   1. {main}() /usr/local/www/firewall_shaper.php:0

2
Updated from 2.3-BETA (amd64) built on Thu Mar 17 13:01:48 CDT 2016 
             to 
2.3.b.20160326.1954 via the GUI.

Got a normal boot up and received a WAN IP with no errors.  Unable to connect to GUI again and no connection to internet.

Reverted back to the 17th Snap by memstick and was back in business.

Anyone else having a problem with the snap from the 26th? 
Is the Traffic Shaper still causing issues?  I'm using the Traffic Shaper by Interface (Codelq) and the Limiter function as well.

3
This is finally showing up as fixed in Bug Tracker

https://redmine.pfsense.org/issues/4383

But I'm still seeing IGMP blocks in my logs using an AMD64 snap from 6/15.

4
Post a bounty / FQ-CoDel - Join Me in this Bounty
« on: March 20, 2015, 11:50:04 am »
Pledging $20 to getting FQ-CoDel placed on top of the development TO DO List.  Hoping others will join in, considering increased interest in this feature.


https://forum.pfsense.org/index.php?topic=87931.0

https://forum.pfsense.org/index.php?topic=88503.0

https://forum.pfsense.org/index.php?topic=88162.msg501320#msg501320

5
Can anyone confirm this bug please?

Go to Services/DHCP Server and make a change.  Click Save.  Then Apply Changes.

After this, Apply Changes just reappears.  If you hit it again it will pop back up no matter how many times its clicked.

6
Been waiting for the GUI bug that has been affecting the recent snaps to be fixed to test out 2.2 on my home network so I upgraded from 2.1.3 to the June 3rd 1343 64 bit snap today and the upgrade froze at firmware upgrade in progress.  Forced a reboot and I got the following error on the console.

Call to undefined function pfSense_interface_listget() in /etc/inc/interfaces.inc on line 66.

Figured I botched the upgrade so I downloaded the Full ISO and proceeded to install from scratch but once installed and booted I got the exact same error.  pfSense doesnt get an IP and there are obviously no interfaces listed.  This is with a dual Intel PCIe card, em driver.

Installed 2.1.3 and I'm back in business so its not a malfunction with my card.

7
Just setup IPv6 on my network as it was recently provided by my ISP, Time Warner Cable - Road Runner.

Got a /128 for my WAN using DHCP6 and a /64 for LAN using Track Interface WAN

This appears to be working fine as I get a IPv6 IP on all my IPv6 enabled devices and testing it at test-ipv6.com give me a perfect 10/10 score.

When I go to Status/DHCPv6 Leases in the GUI, I get the following error though:

Warning: Invalid argument supplied for foreach() in /usr/local/www/status_dhcpv6_leases.php on line 108 Warning: Invalid argument supplied for foreach() in /usr/local/www/status_dhcpv6_leases.php on line 108

Do I have something misconfigured?




8
Packages / Snort 2.9.4.1 pkg v. 2.5.5 Issue(s)
« on: April 10, 2013, 10:09:10 am »
Totally uninstalled pkg v 2.5.4 and then ran "find /* | grep -i snort | xargs rm -rv" to remove any left over traces of Snort.

Reinstalled Snort to get the new pkg v. 2.5.5  but I cant get it to start, with fatal error.

Code: [Select]
Apr 10 11:08:11 php: /snort/snort_interfaces.php: Interface Rule START for HTTP Inspect(em1)...
Apr 10 11:08:11 snort[49458]: FATAL ERROR: /usr/pbi/snort-amd64/etc/snort/snort_30901_em1/preproc_rules/decoder.rules(1) Unknown ClassType: protocol-command-decode
Apr 10 11:08:10 php: /snort/snort_interfaces.php: Toggle(snort starting) for WAN(HTTP Inspect)...
Apr 10 11:08:05 php: /snort/snort_preprocessors.php: Building new sig-msg.map file for WAN...
Apr 10 11:08:01 php: /snort/snort_preprocessors.php: Resolving and auto-enabling any flowbit-required rules for WAN...
Apr 10 11:08:00 php: /snort/snort_preprocessors.php: Updating rules configuration for: WAN ...
Apr 10 11:08:00 check_reload_status: Syncing firewall

I've unchecked every Preprocessor rule and setting on the Preprocessor Tab but I still get the same error.

9
Creating a firewall rule and in Source, check Single Host or Alias.  Enter a host IP or Alias.

Finish completing any other necessary settings to Save Rule.

When you return after saving, the Source type shows Network instead of Single Host or Alias as saved.

Can anyone else confirm this in a snapshot after February 13th, 16:49?  This was on a box with a new install, starting from scratch.

This isn't happening on my box with a February 5th Snap that has been updated regularly.

10
2.1 Snapshot Feedback and Problems - RETIRED / New Error with OpenVPN 2.3
« on: January 16, 2013, 06:13:27 pm »
I'm seeing this error numerous times in my /Status/System Logs/OpenVPN log entries while connecting through Road Warrior tunnel.

Quote
openvpn[93131]: client1/aaa.bbb.ccc.ddd:xxxx write UDPv4: Operation not permitted (code=1)

Seems to be cosmetic since I can connect fine, but was wondering if anyone had any insight or confirmation of reproducing this error.  Only started after upgrading to the latest snap that featured the newer OpenVPN 2.3.

11
Updated to today's snapshot with the 12:14 timestamp.  Upgraded firmware fine and rebooted but OpenVPN process was not running and refuses to start.  OpenVPN logs states initiation successful but no tunnels were working.  Downgraded to an 11/19 snap and I'm back in business.  I assume its related to one of these commits.

https://github.com/bsdperimeter/pfsense/commit/775130e706d36a0252a2948f818876eb2e85ca70
https://github.com/bsdperimeter/pfsense/commit/938fc5b018a758c8dbbe2ce6680b92f3cb1c2185

12
Upgraded from the July 7th amd64 snap to the July 13th amd64 and I'm getting a crash report or programming bug at every bootup.  System Logs look fine but through the monitor I see the following error right before bootup is complete

Parse error: syntax error, unexpected T_STRING in /etc/inc/pkg-utils.inc on line 550

Seems to still be running fine in spite of error.  Any thoughts?


Update: Related to package installation yet I dont have any packages installed on this box.  Going to System/Packages in the Web GUI gives the same error as above.

13
When I click on save in the web gui in the Services DHCP Server page, I get the below pictured error.  July 7th amd64 snap but obviously related to this commit

https://github.com/bsdperimeter/pfsense/commit/9bc59815c6eba7051a401404d4d0b0c7842a9d2f

If I manually enter the LAN address in the gateway section of the DHCP Server page then the error naturally goes away but it seems this should be automatically done without manually typing my LAN address.

14
2.0-RC Snapshot Feedback and Problems - RETIRED / 2.0 HEAD
« on: July 05, 2011, 03:26:27 am »
I smell an official release coming real soon  ;) ;) ;) ;) ;)

https://github.com/bsdperimeter/pfsense/commit/dc4106cf8d1ddaaee5fcc89e9d4403aa28b0da44

https://github.com/bsdperimeter/pfsense/commit/579f00da688e35bdada0f0f46f2897599b708480


Take a bow, great work guys.  Its come a long way since the old Alpha-Alpha days, much appreciated.

15
2.0-RC Snapshot Feedback and Problems - RETIRED / 2.0 RC3
« on: June 16, 2011, 10:33:28 pm »
Not official but I dont believe RC2 was ever officially released either.

https://github.com/bsdperimeter/pfsense-tools/commit/e91c7ff3e0e9bb4d52e29c921918b3d8295fd266

Pages: [1] 2 3