I followed the detailed post above, its on the right path but the build script is clearly designed with obstacles.

So if rename to pfSense it blocks the build.

So then try to rename appropriate files from pfSense to nonSense since they dont distribute with that name

in addition it tries to fetch packages from dead netgate url's.

The showstopper is when renaming the 3 files in here to nonSense

pfsense # ls /root/work/pfsense/pfsense/tmp/FreeBSD-src/release/conf/
pfSense_make.conf          ufw_installer_make.conf    ufw_recover_make.conf
pfSense_src-env.conf      ufw_installer_src-env.conf ufw_recover_src-env.conf
pfSense_src.conf          ufw_installer_src.conf    ufw_recover_src.conf

Then running build.sh again, the build script itself renames them back to pfSense and then complains it cannot find the nonSense files, so its sabotaging itself.

I blocked the script doing the sabotage by making the filles immune (root cannot even write/delete)

chflags schg nonSense_*

But now hitting repo clone errors.

Since I only need to compile a custom kernel I might just try to compile the kernel in the traditional FreeBSD way, as I am only oing this to get a patched kernel to fix a nasty panic bug.

My method is automated, Even the people who connect to these remote devices in many cases dont know anything about linux, or security.  So with a bit or code i wrote, When you SSH to the SG-1000 it automatically redirects you into telnet to the proper device, no need to issue any telnet commands, etc.  You SSH, and its as if you have gone directly to the telnet device in question.

The SG-1000 would also take the place of the firewalling of the crappy DSL Modems, as they could be put in transparent mode, and the pfsense then utilized for a much better firewalling solution and access control.

It would be a simultaneous upgrade to the firewall, and the telnet device at the same time, as well as facilitating better security for any other devices connected in that location.

My code supports tunneling each user account to a different telnet device, not just 1 telnet device.  So its flexible in its usage, and works on bigger models as well, such as SG-2220, and 2440.

Looking for syslogs with external host data (i.e. public internet facing)

I have internal network logs and can collect without an issue.

This topic has been readen 1177 times. It means that many people interested in this technology, really good thing to drop NPt away in IPv6 Multihoming.

@huzbub:

Can PFBlockerNG DNSBL be used in conjunction with OpenDNS?  I realize this may be a little redundant as OpenDNS does much of what PFBlocker does but I like the multiple layers of protection and additional customization of PFBlocker.

I used the guide below to get OpenDNS setup and it indicates that DNS Resolver must be disabled.  And if I understand correctly the DNS Resolver is required for PFBlocker to work.

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

DNS Resolver & Forwarder

Once you completed the above process, you need to disable DNS Resolver and enable DNS Forwarder.
(I am not sure if DNS Resolver can be configured with OpenDNS, I tried to configure it but no luck. With DNS Forwarder, everything work well. Maybe someone can help out to explaining it WHY)
To do this, you need to go to Services > DNS Resolver > Enable: (Unchecked)
After that, Go to Services > DNS Forwarder > Enable: Checked
Interfaces: All
Click Save

Any help appreciated!

The DNS Resolver (Unbound) can be enabled in Resolver or Forwarder mode. Don't confuse that with the DNS Forwarder (DNSMasq).

So you can check the DNS forwarder option in the Resolver. And add the OpenDNS servers to the pfSense General tab settings to utilize both DNSBL and OpenDNS.

sorry i guess you didn't understood what i said. I have made a custom pfsense iso which doesnt boot so i was wondering if anyone can help with that . The iso i made is bootable , but it shows the error " cant find kernel".

@renato.nogueira:

@doktornotor:

If you do not want the webgui, just don't install it.

pkg remove pfSense-pkg-squid pkg install squid

sorry, the pfsense is 2.0.1

No, there is no formal spec or XSD.

Thanks for raising Rajko and thanks for the fix devs.

Thank you both for the helpful replies. Might not be a bad idea to add a note about that to the Developer Style Guide (e.g. Whenever possible, the preferred way to reference interfaces is by using the logical interfaces name eg opt2 yada yada…)

@thallam08:

Issue is still there in 2.3.3 and 2.3.3_p1

Not really, don't necropost.

https://github.com/pfsense/pfsense/blob/RELENG_2_3/src/usr/local/bin/dhcpd_gather_stats.php

I made a small test patch (have not submitted a PR yet because I wanted feedback first) that seems to solve the issue for me. At least in my case it was caused by Console opt 16 restart php-fpm, killing that made check_reload_status go into a nosedive.  So I wrapped it with a start/stop. Been testing that for a couple days and so far it has helped. Any thoughts?

Side note: since it doesn't seem possible to build a "pfSense" platform from source, what is the recommended method for trying to make & test changes to check_reload_status.c in case it needs to be worked on?

edit: didn't get any comments here so I submitted PR#3637

I think it's fairly obvious that it's broken on purpose and you won't get any assistance from pfSense guys here, whatsoever.

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

Dude dunno what are you after here. There's no user-configurable stuff in there and in general nothing of user interest in there either. The file was split to one per PHP extension. There's nothing to patch, fix, add, edit or invent there.

And no, there's is no easy way to look.