• Cannot connect to netgate servers during fresh pfsense install

    47
    2 Votes
    47 Posts
    15k Views
    F

    After a lot of struggle this was my solution;

    It seems a static ip in the 192.168.1.x range is restricted so I changed the ip address of my isp router to 192.168.13.x.

    Powered off my pfsense1100 booted with usb (only the righter slot works) and pressed the [y] button a couple of times to prevent autoboot. Then I started the ‘recovery’ instead of ‘install’. And in the recovery I only opened the shell to ping a website and confirmed that my internetconnection was working. Then I typed exit to start with the install. And everything worked instantly.

    During the install you get at 3 moments the feeling that everything is stuck. Especially during the last stage, -the real install- just wait for like 10 minutes.

  • Update from 23.09.1 to 24.03_1 always reverts

    12
    0 Votes
    12 Posts
    775 Views
    J

    Everything is running now.

    The DNS problems resulting from a misconfigured gateway.

    Thank's for your help.

    Johannes

  • PfSense packages can not be updated and if I try I get a crash report

    2
    0 Votes
    2 Posts
    135 Views
    D

    Now I did the following:
    env ASSUME_ALWAYS_YES=yes pkg-static bootstrap -f
    After that I went to System Update and it showed that I have a new Version available. Before that it always showed that 2.7.0 is the latest version for PfSense.
    So I updated from 2.7.0 to the new stable version 2.7.2
    After it upgraded and rebooted (it felt like it took much longer than usual)

    But now it seems to work somehow. The package manager shows items and the crash report does not show up anymore. I think the issue is no more. (I hope)

  • 2.4.0 does not boot without Monitor

    35
    0 Votes
    35 Posts
    17k Views
    B

    @stephenw10 No, 2.5.2. I am afraid I am a little behind... not proud of it though...

  • Issue upgrading from 2.7.0 to 2.7.2

    9
    0 Votes
    9 Posts
    810 Views
    stephenw10S

    Ah, then, yes, 2.7.0 is the last version that will see packages there. The dynamic repos will not pass branches to CE in Azure.

  • Trouble upgrading from 2.6.0 to 2.7.0, then to 2.7.2

    2
    0 Votes
    2 Posts
    152 Views
    stephenw10S

    I would remove the zeek pkg then upgrade, then re-install it. The setting should remain.

  • Latest software update on older Netgate models

    6
    0 Votes
    6 Posts
    334 Views
    stephenw10S

    There is only the EoL doc here: https://www.netgate.com/support/product-lifecycle

    Other than that the release notes include devices that specifically cannot run that version. For example the SG-1000 cannot run 23.01 or newer:
    https://docs.netgate.com/pfsense/en/latest/releases/23-01.html#errata-known-hardware-issues

    That's the only specific device to date. The 3100 is EoL and at some point will become difficult/impossible to build for but it still runs 24.08 at this point. Some packages are no available for it as they no longer build.

  • Why is an internet connection required?

    6
    0 Votes
    6 Posts
    394 Views
    S

    @stephenw10 Ok that would have probably worked too, I had considered getting one of my older downloads to take care of it. Either way, I'm not complaining or don't mean to. It's a free product first of all and second of all, if netgate owns it then they can do what they want with it and nobody is forcing me to download it. It's like if you own a house you should be able to paint it any color you want :) Personally I would paint it glow-in-the-dark haha.

  • Package manager 23.05.1-RELEASE is empty

    2
    0 Votes
    2 Posts
    124 Views
    stephenw10S

    Make sure the update repo branch is set the 23.05.1 still.

    At the command line run: pkg-static -d update
    See what errors are shown.

    Steve

  • Trouble updating from 2.6.0

    9
    0 Votes
    9 Posts
    534 Views
  • pfsense sophos xg 85 setup issue

    15
    0 Votes
    15 Posts
    720 Views
    stephenw10S

    Not if that is the case. eMMC has limited writes after which it will not allow further writes. It will fail and depending on the drive controller/firmware may at least fail gracefully to a read-only state.

    It may not be that. Can you write to it with anything?

  • 2100 SSD install steps

    13
    1 Votes
    13 Posts
    768 Views
    stephenw10S

    No you don't need to add a heatsink. We have never fitted one and don't see issues with heat. Unless maybe you have some drive that runs especially hot or is designed to use a heatsink. I'm not aware of any but someone may have produced one. 😉

  • libbe_init("") failed.

    2
    0 Votes
    2 Posts
    251 Views
    stephenw10S

    Usually that's because you are not running ZFS so the boot environments are not applicable.
    It's not an issue if you are running UFS, you can safely ignore it.

    Steve

  • Stuck at 23.08

    3
    0 Votes
    3 Posts
    195 Views
    J

    @stephenw10

    Dang bifocals…..

  • pfSense Cannot reach the netgate servers during fresh install

    4
    0 Votes
    4 Posts
    781 Views
    stephenw10S

    When the installer fails it will drop you at a prompt but the network settings will still be in place. You can try to ping (or do any other tests) from there.

  • SG3100 won't boot after upgrade.

    9
    0 Votes
    9 Posts
    547 Views
    stephenw10S

    Could be a switch issue on the 3100. Try running at the command line: etherswitchcfg
    That should return the switch config but if there are errors I would try re-flashing it.

  • Community Edition will be renewed or cancelled ?

    9
    1 Votes
    9 Posts
    1k Views
    S

    @planedrop said in Community Edition will be renewed or cancelled ?:

    it's not meant for production use cases.

    That's completely new to me, where are you got this information?

  • SG 2100 - Fails after update and cannot reinstall PFsense

    10
    0 Votes
    10 Posts
    468 Views
    stephenw10S

    Hmm, do you have anything smaller? Anything that's USB2?

    When you see that EHCI time out error you should do a full power cycle before testing anything else.

  • SG-2100 Fail After Update

    3
    0 Votes
    3 Posts
    196 Views
    B

    @stephenw10

    Yup. I figure out the problem once I got into the console. When I tried to access the tools menu, I received a fatal error telling me that there was not enough room to create a lock file. Deleted one of the BE files and I was off to the races.

  • Help Install Packeges

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