• 2.1.5 upgrade to 2.2 on XPS R400 failed

    10
    0 Votes
    10 Posts
    2k Views
    stephenw10S

    Excellent.  :)
    Use /boot/loader.conf.local for custom loader tweaks like that. It won't be overwritten by a firmware update for example. Though this almost certainly won't be an issue in 2.2.1.
    gpioapu is an addition in pfSense, it's not included in FreeBSD.
    Normally that value will be set by the BIOS to return the motherboard model for example. The driver looks to see if it's running on the APU but for some reason it seems there's a condition in which it loads anyway. Seemingly this includes when no value is able to be obtained for variable. Your board is almost certainly too old to have any smbios features so it's returning 'null' when queried.
    Edit: Looks like that box produced about the same time smbios was introduced but for whatever reason it doesn't have it.

    I was just running a test to see if that worked but the box I have to do it is so slow you beat me to it! Good to see that works anyway.

    Steve

  • Havp not working after upgrade to 2.2 from 2.1.x

    7
    0 Votes
    7 Posts
    2k Views
    B

    Hi,

    Is there any solution?
    I want to use havp on pfSense 2.2.

  • What Squid version and SquidGuard or DansGuardian?

    46
    0 Votes
    46 Posts
    26k Views
    M

    Ok, here is what i did.

    I created "warning.mydomain.net" in the vHosts package and copied squid_clwarn.php
    to "/usr/local/vhosts/warning.mydomain.net"

    I also added "warning.mydomain.net" to the DNS Resolver Host Overrides.

    In squidclamav.conf i changed to:

    redirect http://warning.mydomain.net/squid_clwarn.php

    No more certificate warnings!

    What about the other stuff from my logs i was asking about?
    And what someone share his Clamav settings for performance?

  • [Solved] 2.1.2=>2.2 NanoBSD, Something went wrong with fstab entry

    2
    0 Votes
    2 Posts
    711 Views
    P

    Just for the record: I wasn't able to fix this problem with an "online" pfsense.

    To fix the problem, I had to reinstall the whole system. Don't forget to backup your configuration settings.

  • Ram issue on 2.2 amd64 full install

    12
    0 Votes
    12 Posts
    2k Views
    stephenw10S

    @kejianshi:

    Are you also mixing and matching oil and brake fluid in your car?  Don't do that either.

    That analogy may be a little extreme.  ;)

    Closer to running 10w30 oil and topping it up with 5w10. You shouldn't do it but it's unlikely to cause a problem. If it does though your dealer just going to turn around and say 'well we said use this oil and you didn't so no replacement engine for you!'.

    I have run dissimilar memory modules successfully many times however I couldn't recommend it for a production environment.

    Steve

  • How to install .Pbi package on pfSense 2.0.3

    16
    0 Votes
    16 Posts
    4k Views
    A

    I got it.

    Thanks & Regards

    amitaussie

  • Ugrading from version 2.0-RC1(i386)

    4
    0 Votes
    4 Posts
    782 Views
    stephenw10S

    Hmm, long while since I've used 2.0! I assume it doesn't say underneath the graph then? From your state-table size and number of mbufs it looks like a small ammount.
    You can grep for it in the boot log from the command line like so:

    [2.2-RELEASE][root@pfsense.fire.box]/root: cat /var/log/dmesg.boot | grep memory real memory  = 1072627712 (1022 MB) avail memory = 1015791616 (968 MB) agp0: aperture size is 256M, detected 764k stolen memory

    You can probably also run that from Diagnostics > Command Prompt.

    Steve

  • 2.2 Upgrade on Firebox - Kernel panic during package installation

    7
    0 Votes
    7 Posts
    2k Views
    C

    The only person in the world! Cool. My mother always told me I was special ;)

    Yes, it's running a 533 Mhz FSB Pentium M. I'll try to replace it with the stock processor in a couple of weeks, and do a fresh install. I'm about to move, most of my stuff is already packed and for now it's easier to just run the Firebox for a while without Radius.

    I think I'll have to stick with WPA2-PSK for a little while  :-X

    Thanks for your input!

  • Update to 2.2 new SSH NAT not working.

    28
    0 Votes
    28 Posts
    3k Views
    R

    Looks like I will take another workstation toss in a couple quality NICs and create another test FW.  If .36 fails to receive traffic it's ISP problem for sure. 
    Thanks all for the help/info.

  • 0 Votes
    12 Posts
    6k Views
    K

    Confirmed
    I reinstall a clean 2.1.5 and did basic config

    edit the boot file /boot/loader.conf to add the line hw.ata.atapi_dma="0"
    created a new one /boot/loader.conf.local and put the line hw.ata.atapi_dma="0"

    Upgrade from the internet to 2.2 and next boot with new version was done without problems.

    Thx guys !!!

  • 0 Votes
    8 Posts
    3k Views
    B

    jimp, mystery solved.  Bottom-line:

    The pfSense release 2.2 ufslabels.sh script fails to set $DEV properly

    The ufslabels.sh f76cbd6 or later in git contains the fix

    Manually labelling the swap partition will silently fail if you don't disable swap first (swapoff)

    Thanks for all your help.  In hindsight, I should have simply run the latest ufslabels.sh per your suggestion instead of simply inspecting the difference on github.

    Best,
    Bruce

    Here are the supporting diag/debug details.

    Command-logging of 2.2 ufslabels.sh script (the grep regular expression fails to return the swap device entry)

    + [ y = y ] + echo 'Disabling swap to apply label' Disabling swap to apply label + /sbin/swapoff /dev/ada0s1b + echo 'Applying label to swap parition' Applying label to swap parition + SWAPNUM=0 + find_fs_device /dev/ada0s1b + unset DEV + /usr/bin/grep -e '[[:blank:]]/dev/ada0s1b[[:blank:]]' /etc/fstab + awk '{print $1;}' + DEV='' + DEV='' + [ '' != '' ] + echo 'Activating new fstab' Activating new fstab + /bin/mv -f /etc/fstab /etc/fstab.old + /bin/mv -f /etc/fstab.tmp /etc/fstab + echo 'Re-enabling swap' Re-enabling swap + /sbin/swapon -a

    Command-logging of post-2.2 ufslabels.sh script (the grep regular expression properly returns the swap device).

    + echo 'Applying label to swap partition' Applying label to swap partition + SWAPNUM=0 + find_fs_device /dev/ada0s1b + unset DEV + /usr/bin/grep -e '[[:blank:]]*/dev/ada0s1b[[:blank:]]' /etc/fstab + awk '{print $1}' + DEV=/dev/ada0s1b + DEV=ada0s1b + [ ada0s1b != '' ] + SWAPDEV=ada0s1b + [ -n ada0s1b ] + echo 'Disabling swap ada0s1b to apply label' Disabling swap ada0s1b to apply label + /sbin/swapoff /dev/ada0s1b swapoff: /dev/ada0s1b: Invalid argument + /sbin/glabel label swap0 /dev/ada0s1b + SWAPNUM=1 + echo 'Activating new fstab' Activating new fstab + /bin/mv -f /etc/fstab /etc/fstab.old + /bin/mv -f /etc/fstab.tmp /etc/fstab + echo 'Re-enabling swap' Re-enabling swap + /sbin/swapon -a ```****
  • 2.2 - Restore config unable to ping/reach router

    1
    0 Votes
    1 Posts
    431 Views
    No one has replied
  • Unit goes offline/drops interfaces

    1
    0 Votes
    1 Posts
    594 Views
    No one has replied
  • New Install of 2.2 Missing System-> Packages

    6
    0 Votes
    6 Posts
    2k Views
    D

    @stephenw10:

    There's no package manager if you're running the live-cd by mistake.  ;)

      ;D ;D ;D

  • 32-bit 2.2 webConfigurator hangs

    5
    0 Votes
    5 Posts
    750 Views
    D

    I'm not suggesting your should wait for anything. What I'm suggesting is that when you plop 64bit on the same inadequate HW there's absolutely not gonna be any improvement regarding performance. Saying that 32-bit pfSense 2.2 on 1GB RAM is unuseable is a non sequitur.

  • 0 Votes
    2 Posts
    430 Views
    P

    LAN and WAN are in the same 192.168.1.0/24 subnet. That does not work.
    When plugging a system into an upstream private network for testing or whatever, make sure to first change the LAN IP/subnet to some private address space that does NOT overlap with what the WAN DHCP is about to receive.

  • Md5 and 256 checksum failure for latest amd64 version

    4
    0 Votes
    4 Posts
    919 Views
    M

    Ok, its ok now. it was a download problem.

  • Can't seem to get up and running

    5
    0 Votes
    5 Posts
    2k Views
    stephenw10S

    @hayedid:

    Sure, triple NAT may not be a perfect plan, but shouldn't it work?

    It should, theoretically. Some services have a hard time with multiple layers of NAT but most stuff works fine. The fact that yours didn't implies one of your devices was doing something wrong almost certainly the Asus since switching that to AP mode fixed it. Handing out the wrong gateway, incorrect subnet mask, bad route, it could be many things. Running it in access point mode is much better though.

    @hayedid:

    I really need to be able to see and login to my modem and router.  If they are in bridge mode, I lose that ability.

    You can still access the Asus in access point mode. Often you can still access an upstream router in 'modem' or bridge mode by using an additional IP on the WAN. See:
    https://doc.pfsense.org/index.php/Accessing_modem_from_inside_firewall

    @hayedid:

    Incidentally, I did turn 'Block Private Networks' off since my modem is not setup in bridge mode.  Does this open me up to any additional hacking?

    No. Everything from WAN is blocked by default anyway. That settings only serves as an additional block if you have a public IP on WAN. You should never see private IPs on the WAN in that situation so anything that arrives from a private address must be bogus and should be rejected even if you have port forwards set up.

    Steve

  • Upgrade to 2.2 breaks Squid reverse proxy

    4
    0 Votes
    4 Posts
    3k Views
    R

    Check this out

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

  • 2.2 Watchdog Timeout

    3
    0 Votes
    3 Posts
    791 Views
    stephenw10S

    Yeah, at the very least tell use what NICs you have so we can point you at some appropriate tweaks.

    Steve

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