Subcategories

  • 25.11-DEVELOPMENT snapshots are now available

    Pinned Locked
    1
    4 Votes
    1 Posts
    193 Views
    No one has replied
  • Update to pfSense packages with XMLRPC sync functionality

    Pinned
    8
    2 Votes
    8 Posts
    624 Views
    L
    @RobbieTT There isn’t an official guide for trimming pfSense boot times since most delays come from legacy compatibility layers and service startup waits. A practical starting point is looking through /boot/loader.conf and /boot/loader.conf.local. Things like long USB probe delays, console waits, and unused driver modules can often be disabled or shortened.
  • What skills are needed for Development

    Pinned
    7
    0 Votes
    7 Posts
    15k Views
    J
    @jits: It just dawned on me one morning in the shower that calculus is going to be the key to solving your future programming frustrations. You should try Lisp.
  • pfSense GUI search alpha version for testing

    20
    1 Votes
    20 Posts
    1k Views
    patient0P
    @w0w thanx, now all typing-in works well and fast
  • New PPPoE backend, some feedback

    252
    0 Votes
    252 Posts
    44k Views
    P
    I tried it this moring before working hours but i could not reliably reproduce the stale state. Didn't have much time to test but i tried a few enable/disable interfaces and pause/resume of the virtual machine of the primary firewall so that the failover occurs and pppoe needs to reconnect. This morning everything worked as expected. A few notes on my side: Both firewalls only had an uptime of less than a day. so it might be that the issue only occurs on longer uptime, maybe also if something happens on the provider side in regards to the pppoe session. Also i did reconfigure the dhcp v6 settings accoring to the post of @wow which seemed to make the IPv6 stuff (more) stable than before. The only things i've seen from the (debug) logs which kind of are hinting towards an error are the following lines: Sep 19 07:55:53 kernel if_pppoe: pppoe0: failed to set default route 17 Sep 19 07:55:42 kernel if_pppoe: pppoe0: pap failure Sep 19 07:55:41 kernel if_pppoe: pppoe0: failed to clear IP address: 49 we can safely ignore the pap failure in my case as this must be due to the failover i was testing. in this case the provider thinks the pppoe session for my user is still active (on the other firewall) so i get a few pap failures in failover until the provider closes the stale session of the other firewall. I've seen the other errors (default route/ip address) previously though and those might be related to some error. anyway I will do another test in a couple of days and keep you posted... edit: i extracted the relevant parts of the pppoe debug log. don't know if that is any help, but i am posting it anyway: [25.07.1-RELEASE][root@pfSense.xxxxxxxxxx]/root: bzcat /var/log/ppp.log.* | grep "Sep 19" | grep -v output Sep 19 07:43:00 pfSense newsyslog[73829]: logfile turned over due to size>500K Sep 19 07:43:05 pfSense kernel: if_pppoe: pppoe0: lcp input(opened): <echo-req id=0x3 len=8 Sep 19 07:43:05 pfSense kernel: if_pppoe: pppoe0: got lcp echo req, sending echo rep Sep 19 07:43:15 pfSense kernel: if_pppoe: pppoe0: lcp input(opened): <echo-req id=0x4 len=8 Sep 19 07:43:15 pfSense kernel: if_pppoe: pppoe0: got lcp echo req, sending echo rep Sep 19 07:43:25 pfSense kernel: if_pppoe: pppoe0: lcp input(opened): <echo-req id=0x5 len=8 Sep 19 07:43:25 pfSense kernel: if_pppoe: pppoe0: got lcp echo req, sending echo rep Sep 19 07:43:35 pfSense kernel: if_pppoe: pppoe0: lcp input(opened): <echo-req id=0x6 len=8 Sep 19 07:43:35 pfSense kernel: if_pppoe: pppoe0: got lcp echo req, sending echo rep Sep 19 07:43:45 pfSense kernel: if_pppoe: pppoe0: lcp input(opened): <echo-req id=0x7 len=8 Sep 19 07:43:45 pfSense kernel: if_pppoe: pppoe0: got lcp echo req, sending echo rep Sep 19 07:43:46 pfSense kernel: if_pppoe: pppoe0: lcp close(opened) Sep 19 07:43:46 pfSense kernel: if_pppoe: pppoe0: lcp opened->closing Sep 19 07:43:46 pfSense kernel: if_pppoe: pppoe0: phase terminate Sep 19 07:43:46 pfSense kernel: if_pppoe: pppoe0: ipcp down(opened) Sep 19 07:43:46 pfSense kernel: if_pppoe: pppoe0: ipcp opened->starting Sep 19 07:43:46 pfSense kernel: if_pppoe: pppoe0: ipcp close(starting) Sep 19 07:43:46 pfSense kernel: if_pppoe: pppoe0: ipcp starting->initial Sep 19 07:43:46 pfSense kernel: if_pppoe: pppoe0: ipv6cp down(opened) Sep 19 07:43:46 pfSense kernel: if_pppoe: pppoe0: ipv6cp opened->starting Sep 19 07:43:46 pfSense kernel: if_pppoe: pppoe0: ipv6cp close(starting) Sep 19 07:43:46 pfSense kernel: if_pppoe: pppoe0: ipv6cp starting->initial Sep 19 07:43:48 pfSense kernel: if_pppoe: pppoe0: pap failure Sep 19 07:43:58 pfSense kernel: if_pppoe: pppoe0: failed to set default route 17 Sep 19 07:44:00 pfSense newsyslog[82494]: logfile turned over due to size>500K Sep 19 07:35:30 pfSense newsyslog[52425]: logfile turned over due to size>500K Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: LCP keepalive timeout Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: lcp close(opened) Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: lcp opened->closing Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: phase terminate Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: ipcp down(opened) Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: ipcp opened->starting Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: ipcp close(starting) Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: ipcp starting->initial Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: ipv6cp down(opened) Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: ipv6cp opened->starting Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: ipv6cp close(starting) Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: ipv6cp starting->initial Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: lcp closing->stopped Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: timeout Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: disconnecting Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: lcp down(stopped) Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: lcp stopped->starting Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: phase establish Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: Down event (carrier loss), taking interface down.if_pppoe: pppoe0: lcp close(starting) Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: lcp starting->initial Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: phase dead Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: session 0x1bd connected Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: lcp open(initial) Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: lcp initial->starting Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: phase establish Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: lcp up(starting) Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: lcp starting->req-sent Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: lcp input(req-sent): <conf-req id=0xb7 len=18 Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: lcp parse opts: Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: lcp parse opt values: Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: lcp req-sent->ack-sent Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: lcp input(ack-sent): <conf-ack id=0x16 len=14 Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: lcp ack-sent->opened Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: lcp tlu Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: up Sep 19 07:35:48 pfSense kernel: if_pppoe: pppoe0: phase authenticate Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: pap success Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: phase network Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipcp open(initial) Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipcp initial->starting Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipv6cp open(initial) Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipv6cp initial->starting Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipcp up(starting) Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipcp starting->req-sent Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipv6cp up(starting) Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipv6cp starting->req-sent Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipcp input(req-sent): <conf-req id=0x99 len=10 Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipcp parse opts: Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipcp parse opt values: Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipcp req-sent->ack-sent Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipcp input(ack-sent): <conf-nak id=0x18 len=22 Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipcp nak opts: Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipv6cp input(req-sent): <conf-req id=0x40 len=14 Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipv6cp parse opts: Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipv6cp parse opt values: Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipv6cp req-sent->ack-sent Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: failed to set default route 17 Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipcp input(ack-sent): <conf-ack id=0x1a len=22 Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipcp ack-sent->opened Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipcp tlu Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: failed to set default route 17 Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipv6cp input(ack-sent): <conf-ack id=0x19 len=14 Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipv6cp ack-sent->opened Sep 19 07:35:49 pfSense kernel: if_pppoe: pppoe0: ipv6cp tlu Sep 19 07:35:55 pfSense kernel: if_pppoe: pppoe0: lcp input(opened): <echo-req id=0x0 len=8 Sep 19 07:35:55 pfSense kernel: if_pppoe: pppoe0: got lcp echo req, sending echo rep Sep 19 07:36:06 pfSense kernel: if_pppoe: pppoe0: lcp input(opened): <echo-req id=0x1 len=8 Sep 19 07:36:06 pfSense kernel: if_pppoe: pppoe0: got lcp echo req, sending echo rep Sep 19 07:36:15 pfSense kernel: if_pppoe: pppoe0: lcp input(opened): <echo-req id=0x2 len=8 Sep 19 07:36:15 pfSense kernel: if_pppoe: pppoe0: got lcp echo req, sending echo rep Sep 19 07:36:25 pfSense kernel: if_pppoe: pppoe0: lcp input(opened): <echo-req id=0x3 len=8 Sep 19 07:36:25 pfSense kernel: if_pppoe: pppoe0: got lcp echo req, sending echo rep Sep 19 07:36:35 pfSense kernel: if_pppoe: pppoe0: lcp input(opened): <echo-req id=0x4 len=8 Sep 19 07:36:35 pfSense kernel: if_pppoe: pppoe0: got lcp echo req, sending echo rep Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: LCP keepalive timeout Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: lcp close(opened) Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: lcp opened->closing Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: phase terminate Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: ipcp down(opened) Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: ipcp opened->starting Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: ipcp close(starting) Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: ipcp starting->initial Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: ipv6cp down(opened) Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: ipv6cp opened->starting Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: ipv6cp close(starting) Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: ipv6cp starting->initial Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: lcp closing->stopped Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: timeout Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: disconnecting Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: lcp down(stopped) Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: lcp stopped->starting Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: phase establish Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: Down event (carrier loss), taking interface down.if_pppoe: pppoe0: lcp close(starting) Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: lcp starting->initial Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: phase dead Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: session 0x1bd connected Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: lcp open(initial) Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: lcp initial->starting Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: phase establish Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: lcp up(starting) Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: lcp starting->req-sent Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: lcp input(req-sent): <conf-req id=0x36 len=18 Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: lcp parse opts: Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: lcp parse opt values: Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: lcp req-sent->ack-sent Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: lcp input(ack-sent): <conf-ack id=0x1f len=14 Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: lcp ack-sent->opened Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: lcp tlu Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: up Sep 19 07:42:28 pfSense kernel: if_pppoe: pppoe0: phase authenticate Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: pap success Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: phase network Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipcp open(initial) Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipcp initial->starting Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipv6cp open(initial) Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipv6cp initial->starting Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipcp up(starting) Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipcp starting->req-sent Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipv6cp up(starting) Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipv6cp starting->req-sent Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipcp input(req-sent): <conf-req id=0x22 len=10 Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipcp parse opts: Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipcp parse opt values: Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipcp req-sent->ack-sent Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipcp input(ack-sent): <conf-nak id=0x21 len=22 Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipcp nak opts: Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipv6cp input(req-sent): <conf-req id=0x36 len=14 Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipv6cp parse opts: Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipv6cp parse opt values: Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipv6cp req-sent->ack-sent Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: failed to set default route 17 Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipcp input(ack-sent): <conf-ack id=0x23 len=22 Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipcp ack-sent->opened Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipcp tlu Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: failed to set default route 17 Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipv6cp input(ack-sent): <conf-ack id=0x22 len=14 Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipv6cp ack-sent->opened Sep 19 07:42:29 pfSense kernel: if_pppoe: pppoe0: ipv6cp tlu Sep 19 07:42:35 pfSense kernel: if_pppoe: pppoe0: lcp input(opened): <echo-req id=0x0 len=8 Sep 19 07:42:35 pfSense kernel: if_pppoe: pppoe0: got lcp echo req, sending echo rep Sep 19 07:42:45 pfSense kernel: if_pppoe: pppoe0: lcp input(opened): <echo-req id=0x1 len=8 Sep 19 07:42:45 pfSense kernel: if_pppoe: pppoe0: got lcp echo req, sending echo rep Sep 19 07:42:55 pfSense kernel: if_pppoe: pppoe0: lcp input(opened): <echo-req id=0x2 len=8 Sep 19 07:42:55 pfSense kernel: if_pppoe: pppoe0: got lcp echo req, sending echo rep Sep 19 07:43:00 pfSense newsyslog[73829]: logfile turned over due to size>500K Sep 19 07:25:28 pfSense kernel: if_pppoe: pppoe0: failed to set default route 17 Sep 19 07:27:28 pfSense kernel: if_pppoe: pppoe0: failed to clear IP address: 49 Sep 19 07:27:29 pfSense kernel: if_pppoe: pppoe0: pap failure Sep 19 07:31:18 pfSense kernel: if_pppoe: pppoe0: LCP keepalive timeout Sep 19 07:31:18 pfSense kernel: if_pppoe: pppoe0: failed to set default route 17 Sep 19 07:31:18 pfSense kernel: if_pppoe: pppoe0: failed to set default route 17 Sep 19 07:34:59 pfSense kernel: if_pppoe: pppoe0: lcp input(opened): <echo-req id=0x7 len=8 Sep 19 07:34:59 pfSense kernel: if_pppoe: pppoe0: got lcp echo req, sending echo rep Sep 19 07:35:30 pfSense newsyslog[52425]: logfile turned over due to size>500K
  • How does one build 2.8.0 kernel with a patch applied to it?

    4
    1 Votes
    4 Posts
    1k Views
    bmeeksB
    @nazar-pc said in How does one build 2.8.0 kernel with a patch applied to it?: No sources for 2.8.1 kernel either and no dev branch for pfSense CE to test whatever is being worked on Yep, the same difficulty exists when wanting to build packages fully compatible with pfSense CE. That was already the case for Plus, but now with no 2.8.x CE branches available on the public GitHub, package building is hindered as well.
  • new if_pppoe Backend - getting HA/CARP to work like in MPD

    30
    1 Votes
    30 Posts
    2k Views
    zjamaliZ
    @perrin Installed new package, now its work for reconcile on vhid 1 [image: 1758191884884-12dce092-e863-455c-ac7a-683781dea3bb-image.png]
  • pfsense 2.8.1 ISO

    2
    0 Votes
    2 Posts
    525 Views
    patient0P
    @g405tsh311 the online installer you "buy" for $0 in the Netgate store gets the versions dynamically, 2.8.1 is among them. [image: 1757746372965-screenshot-2025-09-13-at-08.49.56.jpeg]
  • How can I develop my own plugins?

    Moved
    5
    0 Votes
    5 Posts
    1k Views
    stephenw10S
    Also see: https://docs.netgate.com/pfsense/en/latest/development/develop-packages.html
  • 0 Votes
    2 Posts
    76 Views
    stephenw10S
    Yup, seeing that here. Likely related to the upstream firmware API issue. But those drivers shouldn't need to load anything without the hardware present anyway.
  • [2.8.1.b] Multiple limiter issue

    13
    0 Votes
    13 Posts
    2k Views
    stephenw10S
    I suspect the root cause here is the same as this: https://redmine.pfsense.org/issues/15770
  • 0 Votes
    1 Posts
    458 Views
    No one has replied
  • Shell scripts at /usr/local/etc/rc.d - when will they be executed?

    2
    0 Votes
    2 Posts
    1k Views
    GertjanG
    @luckman212 I use a manually added FreeBSD package, 'munin' that came with a file to be placed in /usr/local/etc/rc.d/ As per pfSense needs, I renamed it - added the .sh extension, and now the munin process get started at boot, and stopped at shutdown. I made this install many years ago, and as far as I know, the script only executes during boot and system shutdown. Not for network or other events etc. If FreeBSD would look like a Debian system (or clone) using init or systemd I could tell you way more, and I even think pfSEnse isn'tv really FreeBSD (no surprise, at it is, and it isn't ^^). Look at the kea script for an example, the first 3 / 4 lines. Afaik, pfSense it self, see here /etc/, all de rc...... files - for example rc.bootup - will all all these files. pfSense handle the hardware and software system events, and call whatever is needed, if system processes like 'unbound' needed to be restarted. So : and also during certain system events (e.g. interface link changes, IP address changes, and gateway events). never saw that happening with my own processes - as pfSense isn't really aware that these are running ones the system is up.
  • PfSense Github 2.8.0 branch

    1
    1 Votes
    1 Posts
    554 Views
    No one has replied
  • Pfsense Traffic Graphs

    Moved
    6
    0 Votes
    6 Posts
    1k Views
    stephenw10S
    Not currently, it would require some development.
  • pfsense-tools.git clang gcc

    clang gcc pfsense-tools
    19
    0 Votes
    19 Posts
    2k Views
    P
    @dennypage said in pfsense-tools.git clang gcc: @phil80 said in pfsense-tools.git clang gcc: portsnap fetch properly fetches freebsd ports collection FWIW, portsnap is very dead as far as the FreeBSD folk are concerned. All references to it were removed from the documentation 5 years ago, and its use is no longer supported. The original announcement is here: [HEADS UP] Planned deprecation of portsnap. Thank you for the reminder. I usually only use Latest. I always use git for collaboration In short life or one use jails, portsnap is way faster to fetch than git for one package compile Based on your linked article, I'll favor git in the future
  • pfSsh.php playback script to change username

    Moved
    1
    0 Votes
    1 Posts
    51 Views
    No one has replied
  • Connections/states DROP when changing web configurator COLOR!!

    16
    0 Votes
    16 Posts
    2k Views
    stephenw10S
    Mmm, so prevent source tracking for specific IPs or subnets? I did wonder if sticky connections could be per gateway group. That seems like it should be possible. You could then use rules to route specific clients or subnets to a non-sticky group.
  • Private WLAN

    11
    0 Votes
    11 Posts
    2k Views
    stephenw10S
    OK so it looks like you had two issues: The installer didn't work as you expected it to but you were able to get 2.8 installed and booted. The resulting install didn't behave as you expected. That's independent of the installer and 2.7.2 would have behaved identically in that situation. So after install you assigned two interfaces, pfSense names them WAN and LAN but any interface can be anything. And you configured them both to be DHCP since both subnets already have a DHCP server? The typical subnet conflict that users hit when installing behind another firewall if that pfSense uses 192.168.1.1/24 as the default LAN address and that subnet is also used by the upstream firewall WAN side. I assume you didn't hit that since both subnets already existed in your network so must be using different subnets? What are they? However you then say you set the LAN back to a static address? Presumably in the same subnet? By default pfSense creates firewall rules on the LAN interface to allow access to the webgui there. That applies whether the LAN is static or DHCP. How exactly were you trying to connect? From where?
  • Nexus re-installing

    4
    1 Votes
    4 Posts
    1k Views
    stephenw10S
    Currently nothing I'm aware of but going forward some functions will likely be written in go and hence in the Nexus package. Obviously that assumes the Nexus package is always present so it is automatically re-installed at upgrade.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.