Great, it works …

thanks a lot

And a little tip to who wants to use Freeradius 2 with PostgreSQL:
Accounting operations work correctly with MySQL but with PostgreSQL, don't update the radacct table. So, some attributes like Session-Timeout don't work.

I'm half way of making samba pkg work.

@Marcelloc, I have problem. In pfsense 2.1 packages are installing in /usr/pbi/*.
While creating tbz package, can I change the installation destination directory of package to /usr/pbi/samba?

By default it is installed in /usr/local with it's all dependencies.

Here is link to repository where I'm creating package - https://github.com/pszafer/SambaForFreeradiusPFSENSE

I finally figured out what went wrong. There where 2 issues.

The XML tag isn't used by PFSense at all, below a copy of the method PFSense uses to generate the rules (https://github.com/bsdperimeter/pfsense/blob/master/etc/inc/filter.inc).

You should not use a subdirectory for your package; leave it in '/usr/local/pkg'. Otherwise the system won't find your 'generate_rules' function.

function discover_pkg_rules($ruletype) { global $config, $g, $aliases; /* Bail if there is no pkg directory, or if the package files might be out of sync. */ if(!is_dir("/usr/local/pkg") || file_exists('/conf/needs_package_sync')) return ""; $rules = ""; $files = glob("/usr/local/pkg/*.inc"); foreach($files as $pkg_inc) { update_filter_reload_status(sprintf(gettext('Checking for %1$s PF hooks in package %2$s'), $ruletype, $pkg_inc)); $pkg = basename($pkg_inc, ".inc"); $pkg_generate_rules = "{$pkg}_generate_rules"; if (!function_exists($pkg_generate_rules)) require_once($pkg_inc); if(function_exists($pkg_generate_rules)) { update_filter_reload_status(sprintf(gettext('Processing early %1$s rules for package %2$s'), $ruletype, $pkg_inc)); $tmprules = $pkg_generate_rules("$ruletype"); file_put_contents("{$g['tmp_path']}/rules.test.packages", $aliases . $tmprules); $status = mwexec("/sbin/pfctl -nf {$g['tmp_path']}/rules.test.packages"); if ($status <> 0) { $errorrules = sprintf(gettext("There was an error while parsing the package filter rules for %s."), $pkg_inc) . "\n"; log_error($errorrules); file_put_contents("{$g['tmp_path']}/rules.packages.{$pkg}", "#{$errorrules}\n{$tmprules}\n"); continue; } $rules .= $tmprules; } } return $rules; }

I hope that this info will help someone figuring it out a lot faster than I did  ;)

Yep, that's normal.

HI Jimp,

Thanks for reply, i will check on my VM and may try on another cvsup server.

Once again, thx for ur guide

On 2.0.x and before, and on 2.1 up until late December, that's just a normal text file not a special database file.

On recent 2.1 snapshots it is actually an sqlite database.

@marcelloc:

Did you got it working?

Yes it works very finewith the patch. Youhave todowngrade the squidguard binary http://forum.pfsense.org/index.php/topic,47100.msg298331.html#msg298331

Greetings

Snowyrain

Thank you so much.. :)
It would be really helpful to me..

Thanks! :)
I got build Log.

Thanks for your reply. I will continue to work the way you suggested.

2.0.x must be built on 8.1.

Because adding an 'out' selector completely changes the entire philosophy of how rules have always been managed. It doesn't just add a feature. Its presence will make people think they need to use it, when they really don't, even if it's hidden.

Fixing the Floating rules list to better signify things like the interfaces being used is more feasible.

Making "out" easier to use is a bad idea. For most people, it doesn't do what they think it will do, and just makes things more complicated than they need to be.

Yes, it can make certain specific things easier, but for those cases, Floating rules work. If you find Floating rules deficient for that case, fix Floating rules.

This has been discussed several times before. I believe it has even been implemented by a few people for their own use.
See:
http://forum.pfsense.org/index.php/topic,48094.0.html
http://forum.pfsense.org/index.php/topic,43187.0.html

Steve

I shall do more testing. The underscores seem to work fine in my field names until I try to make those fields visible in my pkg.php views. If I take out the underscore, the same field shows fine.