• Making internet connection on second router in stream work

    Moved
    3
    0 Votes
    3 Posts
    472 Views
    chpalmerC

    @jimp Thank you!

  • 1 Votes
    5 Posts
    1k Views
    w0wW

    @alex-atkin-uk
    Thanks for the information.

  • 2.7.0-DEVELOPMENT can't install snort without these errors

    Moved
    8
    0 Votes
    8 Posts
    1k Views
    w0wW

    @bmeeks
    Yes. On the previous snapshot it failed to install and today it is installed. Ok, will wait for the new version, thank you!

    pkg-static: Cannot delete vital package: pfSense! pkg-static: If you are sure you want to remove pfSense, pkg-static: unset the 'vital' flag with: pkg set -v 0 pfSense
  • mountroot> after updating to latest snapshot

    4
    0 Votes
    4 Posts
    563 Views
    JeGrJ

    @jimp I had a feeling it could be related to ZFS. I found the VM had an older snapshot from mid-October so just following a hunch rolled back to that und updated again - funny thing, THAT update actually worked and the system rebooted just fine. Weird, will have to test around a bit if that can be reproduced somewhere further. Wouldn't want that when 23.01 drops to happen to a 22.05 update :)

  • Issues with IPV6

    24
    0 Votes
    24 Posts
    4k Views
    B

    @louis2 You can find gateway monitoring in System->Routing->WAN_DHCP6 edit. You should do this for WAN_DHCP too just in case since it will prevent either interfaces from going down when you briefly lose a connection. For the prefix length keep /48 then. I still think it's worth trying all these settings, but also try them with and without 'Do not wait for a RA' enabled. If none of these work then maybe try changing some settings in your modem (bridge mode) and do a reboot on both devices.

  • PHP-error when disableing a FW-rule in an interface group

    2
    0 Votes
    2 Posts
    517 Views
    jimpJ

    Looks like that's already a known issue:

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

  • Ipv6 not working

    Moved
    16
    1 Votes
    16 Posts
    2k Views
    JKnottJ

    I have often uploaded capture files, so you have some other issue. In fact, I uploaded one just to show you I could, after you said you couldn't. Even if you can't, there's always Google drive, where you could leave it and provide a public link so we can get it.

  • CPU crypto disabled !??

    5
    0 Votes
    5 Posts
    783 Views
    Bob.DigB

    More a Déjà vu issue. 😉

  • 0 Votes
    7 Posts
    3k Views
    L

    I encountered a couple of php errors since I migrated to 2.7 freebsd 14 or what seems to be called ^devel^ now.

    They have one thing in common and that is exactly this error.
    Uncaught TypeError: Cannot access offset of type string on string in xyz

    Somehow (not at all sure) I have a feeling that it also have a relation with the xml parser (/etc/inc/xml*) . Some observations:

    /etc/inc/xmlparse.inc:73

    #0 [internal function]: startElement(Object(XMLParser), 'BR', Array) #1 /etc/inc/xmlparse.inc(188): xml_parse(Object(XMLParser), '<?xml version="...', false) #2 /etc/inc/xmlparse.inc(160): parse_xml_config_raw('/usr/local/pkg/...', 'packagegui', 'false') #3 /usr/local/www/pkg.php(65): parse_xml_config_pkg('/usr/local/pkg/...', 'packagegui')

    I also noticed an relation with parsing of arrays. When creating an interface or vpn-list.

    I hope this helps to identify the problem.

    Louis
    PS I noticed that there is already a php 8.2 option in FreeBSD ports

  • Font and screen size for UEFI boot based on FreeBSD 14

    1
    1 Votes
    1 Posts
    486 Views
    No one has replied
  • pfSense has detected a crash report or programming bug.

    9
    0 Votes
    9 Posts
    2k Views
    stephenw10S

    Cool. That's an odd place to see a panic from the filesystem. Let us know if it returns.

  • Can't check update/upgrade for 2.7 version

    Moved
    9
    0 Votes
    9 Posts
    2k Views
    JeGrJ

    @jimbob-indiana I updated our lab VMs for dev a while ago and the 2.7/23.01 snapshots on FreeBSD14 are addressing various things ATM. Be it EOL of PHP with many changes happening for PHP8 compatibility, to new drivers and stuff from FBSD14 being adapted to looking into the newly re-imported wireguard kernel stuff that lately dropped in FBSD14 again, there are many things to cover. Also stuff that has been out in Plus-22.05 like the portal and limiter running without IPFW now or quite a few QoL fixes in the UI there are many things to look after.

    Cheers

  • WAN_DHCP6 Stuck Pending

    10
    0 Votes
    10 Posts
    846 Views
    B

    In case my post isn't clear, when I said this worked before I upgraded to the latest 2.7.0 snapshot, I meant before the snapshot where pfSense changed over to FreeBSD 14. When pfSense changed over to FreeBSD 14, this issue emerged.

  • No RSA keys generated for SSH

    3
    0 Votes
    3 Posts
    479 Views
    W

    I dug a bit deeper and found the problem was with ExtraPUTTY. I could not agree with pfSense about the hash algorithm.

    Works fine with PUTTY.

  • FreeRADIUS Users not working in 2.7.0-DEVELOPMENT

    Moved
    3
    0 Votes
    3 Posts
    601 Views
    G

    @gmpreussner After digging some more, I believe that this is a bug, and I filed a ticket at https://redmine.pfsense.org/issues/13628

  • Pfsense dev version crash on easy rule

    Moved
    2
    0 Votes
    2 Posts
    371 Views
    stephenw10S

    Confirmed, php bug:

    Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /etc/inc/easyrule.inc:60 Stack trace: #0 /etc/inc/easyrule.inc(370): easyrule_find_rule_interface('lan') #1 /usr/local/www/easyrule.php(49): easyrule_parse_block('lan', '192.168.167.50', 'inet') #2 {main} thrown in /etc/inc/easyrule.inc on line 60 PHP ERROR: Type: 1, File: /etc/inc/easyrule.inc, Line: 60, Message: Uncaught TypeError: Cannot access offset of type string on string in /etc/inc/easyrule.inc:60 Stack trace: #0 /etc/inc/easyrule.inc(370): easyrule_find_rule_interface('lan') #1 /usr/local/www/easyrule.php(49): easyrule_parse_block('lan', '192.168.167.50', 'inet') #2 {main} thrown

    Tested in 2.7.0.a.20221103.0600

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

  • 1 Votes
    2 Posts
    248 Views
    D

    I need to check if this is not a windows problem. Because I restore 2.6 and It doesn't work too.

  • Update from 2.7.0.a.20220812.0002 to PHF 8.1 and FreeBSD Main Failed

    5
    0 Votes
    5 Posts
    1k Views
    B

    @cmcdonald Sorry for the delay to reply. I didn't have a chance to try this until today and I found when I made another attempt to upgrade, it worked without me having to try this. I appreciate your reply, even though I ended up not needing to try it.

  • IPV6 issue related to Managed RA (freebsd 14)

    4
    0 Votes
    4 Posts
    758 Views
    jimpJ

    You'll need to look closer at what the client is getting and using for its IPv6 address(es) in each of those cases but as I said it's still the client selecting the wrong address for that communication, not pfSense.

  • OpenVPN Client Export Error: /usr/local/www/vpn_openvpn_export.php:441

    2
    1 Votes
    2 Posts
    571 Views
    T

    @greenavocado said in OpenVPN Client Export Error: /usr/local/www/vpn_openvpn_export.php:441:

    Hi all,

    Ran into this issue where after creating OpenVPN server through Wizard and going to "Client Export" tab throws this error:

    Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /usr/local/www/vpn_openvpn_export.php:441 Stack trace: #0 {main} thrown in /usr/local/www/vpn_openvpn_export.php on line 441 PHP ERROR: Type: 1, File: /usr/local/www/vpn_openvpn_export.php, Line: 441, Message: Uncaught TypeError: Cannot access offset of type string on string in /usr/local/www/vpn_openvpn_export.php:441 Stack trace: #0 {main} thrown

    Tried following to no avail:

    Uninstalled and re-installed "Client Export" package Deleted and re-created OpenVPN server from Wizard

    Appreciate if anyone can chime in a fix or workaround.

    Thanks

    2.7.0-DEVELOPMENT (amd64)
    built on Mon Oct 24 06:06:05 UTC 2022
    FreeBSD 14.0-CURRENT

    Same here, I saw in redmine: https://redmine.pfsense.org/issues/13570 that it was solved, but it was not ported to last snapshot yet? I'm running "2.7.0-DEVELOPMENT (amd64) built on Tue Nov 01 06:05:17 UTC 2022 FreeBSD 14.0-CURRENT" but the error persist "Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /usr/local/www/vpn_openvpn_export.php:441 Stack trace: #0 {main} thrown in /usr/local/www/vpn_openvpn_export.php on line 441 PHP ERROR: Type: 1, File: /usr/local/www/vpn_openvpn_export.php, Line: 441, Message: Uncaught TypeError: Cannot access offset of type string on string in /usr/local/www/vpn_openvpn_export.php:441 Stack trace: #0 {main} thrown"

    best regards,

    jm
    TC

Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.