Subcategories

  • Discussions about development snapshots for pfSense Plus 25.11

    9 Topics
    66 Posts
    yon 0Y
    I urgently need to upgrade to the latest version of FRR 10. last pid: 50887; load averages: 2.35, 2.29, 2.41 up 0+20:30:18 05:20:00 105 processes: 3 running, 102 sleeping CPU: 46.3% user, 0.0% nice, 21.0% system, 1.2% interrupt, 31.6% idle Mem: 1505M Active, 1806M Inact, 1921M Wired, 14G Free ARC: 228M Total, 66M MFU, 155M MRU, 533K Anon, 1302K Header, 4429K Other 185M Compressed, 414M Uncompressed, 2.24:1 Ratio Swap: 1024M Total, 1024M Free PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 77832 root 4 141 0 2583M 2462M CPU2 2 505:23 196.84% bgpd 38116 root 1 1 0 23M 11M select 2 7:55 1.61% openvpn 44320 root 8 0 0 228M 155M select 3 17:31 1.12% zebra 58666 root 1 0 0 14M 3664K select 0 47:36 0.70% miniupnpd 63264 root 1 0 0 23M 11M select 2 0:36 0.51% openvpn 41157 root 1 0 0 23M 11M select 0 1:14 0.39% openvpn 81930 root 1 0 0 23M 11M select 2 1:00 0.32% openvpn 22300 root 5 59 0 15M 3144K uwait 1 0:01 0.24% dpinger 62794 root 1 0 0 267M 234M select 2 0:32 0.16% bsnmpd 48156 root 1 5 0 15M 4236K CPU1 1 0:00 0.15% top 78090 root 1 0 0 26M 10M select 3 16:03 0.14% ntpd 95229 root 1 59 0 14M 3008K nanslp 2 0:01 0.06% cron 23298 root 5 59 0 15M 3140K uwait 1 0:01 0.04% dpinger 17794 root 5 47 0 15M 3140K uwait 3 0:01 0.04% dpinger 26716 root 5 59 0 15M 3140K uwait 2 0:01 0.03% dpinger 21621 root 5 59 0 15M 3140K uwait 0 0:01 0.03% dpinger 24135 root 5 59 0 15M 3148K uwait 1 0:01 0.03% dpinger 23729 root 5 59 0 15M 3152K uwait 1 0:01 0.03% dpinger 18311 root 5 57 0 15M 3192K uwait 1 0:01 0.03% dpinger 25099 root 5 59 0 15M 3136K uwait 0 0:01 0.03% dpinger 35794 root 1 0 0 25M 13M select 2 0:00 0.03% sshd-session 20955 root 5 59 0 15M 3132K uwait 3 0:01 0.03% dpinger 21956 root 5 59 0 15M 3136K uwait 0 0:01 0.03% dpinger 19832 root 5 59 0 15M 3148K uwait 3 0:01 0.03% dpinger 20181 root 5 59 0 19M 3276K uwait 1 0:01 0.03% dpinger 19392 root 5 59 0 15M 3140K uwait 2 0:01 0.03% dpinger 22947 root 5 59 0 15M 3144K uwait 1 0:01 0.02% dpinger 24345 root 5 59 0 15M 3140K uwait 2 0:01 0.02% dpinger 21305 root 5 59 0 15M 3140K uwait 0 0:01 0.02% dpinger 69255 root 1 0 0 14M 2892K kqread 1 0:13 0.02% tail 26294 root 5 59 0 15M 3136K uwait 1 0:01 0.02% dpinger 24687 root 5 59 0 15M 3140K uwait 1 0:01 0.02% dpinger 71886 root 1 0 0 14M 2880K select 1 0:12 0.02% tail 20571 root 5 59 0 15M 3140K uwait 1 0:00 0.02% dpinger 25472 root 5 59 0 19M 3272K uwait 1 0:01 0.01% dpinger 6517 root 9 0 0 58M 26M select 2 0:03 0.01% kea-dhcp4 22779 root 5 59 0 19M 3276K uwait 1 0:01 0.01% dpinger 18902 root 5 59 0 15M 3136K uwait 0 0:01 0.01% dpinger 25947 root 5 59 0 19M 3292K uwait 2 0:01 0.01% dpinger 68884 root 1 0 0 14M 3504K kqread 2 0:09 0.01% syslogd 17031 root 1 0 0 25M 8468K select 3 0:03 0.01% watchfrr 8925 root 9 0 0 46M 24M select 1 0:02 0.01% kea-dhcp6 663 root 1 0 0 125M 37M kqread 1 0:04 0.01% php-fpm 15542 root 1 0 0 23M 11M select 1 0:08 0.00% openvpn 50040 root 1 0 0 15M 3892K bpf 3 0:03 0.00% filterlog 51743 root 1 0 0 37M 14M kqread 1 0:51 0.00% nginx 37889 root 1 59 0 163M 67M accept 3 0:28 0.00% php-fpm
  • Pfsense Traffic Graphs

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

    clang gcc pfsense-tools
    19
    1
    0 Votes
    19 Posts
    3k 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
    126 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
    3k 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
    2k 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.
  • How to fork a pfSense package?

    4
    0 Votes
    4 Posts
    2k Views
    L
    @cybrnook It looks if you are referring to the pimd engine version [image: 1752688668863-854cb5be-fd74-43b0-848a-b83df5637c1b-image.png] Which is quite old, and as far as I know not working under FreeBSD. I have compiled the never released pimd-3.0.b1 version (using FreeBSD15 current).
  • Has the 25.07 RC been withdrawn?

    3
    1
    3 Votes
    3 Posts
    2k Views
    dennypageD
    @cmcdonald Appears to be back/fixed. Thanks.
  • 0 Votes
    27 Posts
    3k Views
    stephenw10S
    You can set the size it rotates at and the number of files to retain in the log settings at Status > Logs > Settings. As long as you have the space you should be able to increase it.
  • Pfsense forensics / Memory dump of psense

    Moved
    1
    0 Votes
    1 Posts
    843 Views
    No one has replied
  • Built-in NetBox importer for DNS, DHCP, etc

    Moved netbox importer dhcp dns
    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • 0 Votes
    3 Posts
    2k Views
    M
    @stephenw10 The Ultra Ethernet Consortium
  • Looking for PfSense Github 2.8.0 branch.

    1
    0 Votes
    1 Posts
    852 Views
    No one has replied
  • Bugs/Problems with Netgate Installer Beta

    13
    0 Votes
    13 Posts
    4k Views
    JeGrJ
    @stephenw10 Aye that's right
  • AbuseIPDB Scripting

    5
    0 Votes
    5 Posts
    3k Views
    0
    Hi guys, I create simple shell script reports for AbuseIPDB from filter.log file. Maybe it will be helpful to someone. It was tested over a one-week period and works as expected. Here is the link: ttps://github.com/whoami-0x44/abuseipdb-reporting-pfsense
  • QEMU VM: Version 2.8 Won't Boot

    24
    2
    0 Votes
    24 Posts
    5k Views
    stephenw10S
    Yes you can choose 2.8.0-beta from the installer menu. Edit: Now 2.8.0-RC
  • Sharing Errors in the Logfiles, which might need attention!

    2
    0 Votes
    2 Posts
    2k Views
    stephenw10S
    Nope, none of those are a big concern. Some of that could be cleaned up but they are just ugly.
  • 25.03 beta - Bufferbloat / FQ CoDel issues

    26
    0 Votes
    26 Posts
    6k Views
    RobbieTTR
    @w0w Seems so or possibly an interaction with if_pppoe and something else within the new beta. Regressing to 24.11 again and symptoms vanish. Reverting to the old backend on the beta seems fine too (albeit with the old pppoe issues). I had to work back again and re-test as I had the test diff patch applied with the revised beta, which drew some doubts on my results for a while. Fat-fingering in a config error when testing is something I try to avoid but you have to admit your mistakes. I'm waiting for the next beta drop really, to see if the changes also impact the issues I see. Opening up all the cores may just be peeling back something that was already latent and just masked by the old backend process. I did do a couple of tests that suggests the upload fq_codel settings may need adjusting against a different workload for if_pppoe; but too early to be sure. I'm also being nudged to try Kea again, as apparently it has matured a bit since its launch. ️
  • X-ray VPN implementation in future releases of pfSense+

    6
    0 Votes
    6 Posts
    3k Views
    stephenw10S
    Hmm, it does seem kinda shady! There's no FreeBSD port as far as I can see, though there is one for v2ray which this was forked from. You are asking about adding it as a client to connect to the xrayvpn service only? I'm not really seeing any advantages over existing VPN options TBH.
  • 2.8.0-BETA snapshots are now available

    24
    10 Votes
    24 Posts
    6k Views
    M
    @matthijs I had an issue with a static arp entry, but it was a wrong configuration on my side (an old wrong static arp entry/Mac address) The IP adres with this static ARP entry was in use by another host (with another MAC address) an that was an issue. I did not experience this in 2.7.2 So in fact 2.8.0 is behaving correctly
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.