• Cannot update firmware for 7100 1U

    5
    0 Votes
    5 Posts
    478 Views
    B
    @stephenw10 You got it! The command you sent me only resulted in errors: [23.05.1-RELEASE][root@FW-A.local]/root: pkg-static search flashrom pkg-static: Repository pfSense-core missing. 'pkg update' required pkg-static: An error occured while fetching package pkg-static: An error occured while fetching package pkg-static: An error occured while fetching package pkg-static: An error occured while fetching package pkg-static: An error occured while fetching package pkg-static: An error occured while fetching package pkg-static: An error occured while fetching package pkg-static: An error occured while fetching package However, I went to the update settings in the web UI and the branch was set to 23.09.1. I uninstalled the package "Netgate_Firmware_Update", changed the branch to 23.05.1, reinstalled "Netgate_Firmware_Package", and it worked! Thank you so much!
  • Netgate 7100 freezes when temperature above 50°C

    26
    0 Votes
    26 Posts
    4k Views
    stephenw10S
    I will do. Thanks for checking that.
  • 7100 with static null4 route

    4
    1 Votes
    4 Posts
    421 Views
    stephenw10S
    Hmm, there was a bunch of work around gateways and I recall testing this at the time but it appears to be a regression: https://redmine.pfsense.org/issues/15669
  • SG-3100 M.2 install

    23
    0 Votes
    23 Posts
    3k Views
    E
    I found solution for the m.2 setenv m2boot 'scsi reset; fatload scsi 0:1 200000 ubldr.bin; go 200000;' saveenv reset Then it should boot correctly from the m.2 It looked like this for me as default. setenv m2boot 'scsi reset; fatload scsi 0:0 200000 ubldr.bin; go 200000;'
  • Netgate 2100 Stalling - HW issue?

    16
    0 Votes
    16 Posts
    1k Views
    stephenw10S
    Hmm, that must have been a while ago, we no longer use that ticket system. Do you have the serial number or NDI from it? You can send it to me in chat. Was that 2100 installed in the same location? Same network?
  • 0 Votes
    15 Posts
    799 Views
    stephenw10S
    Yes, if the console is completely unresponsive then it won't help but the console is often the last thing to still function.
  • Netgate 3100 failure after house power outage

    9
    0 Votes
    9 Posts
    772 Views
    S
    @DaveM WAN is already the Internet. Rules are incoming not outgoing. So LAN needs a rule “to any.”
  • Netgate 6100 SSDs

    58
    0 Votes
    58 Posts
    15k Views
    JonathanLeeJ
    @stephenw10 I got this usbc NVMe drive it can clock 10gbps that’s a wow factor to me
  • Netgate 6100 PPPOE performance

    1
    0 Votes
    1 Posts
    228 Views
    No one has replied
  • Periodic disconnection when connecting to serial via a Mac on Netgate 2100

    17
    0 Votes
    17 Posts
    925 Views
    JonathanLeeJ
    @CarAnalogy I have only accessed my system over putty with Windows 10, and Windows 11, and OSX iMac 2009 era with a special set of software to access terminal sessions. Never putty on iMac
  • How to reinstall pfsense plus on my 2100?

    5
    0 Votes
    5 Posts
    635 Views
    stephenw10S
    If you really have no on-line possibility then open a ticket with TAC to discuss. There are options.
  • Netgate 4200 Behavior: Power Button Standby, LEDs Brightness, Coreboot

    4
    0 Votes
    4 Posts
    1k Views
    Y
    @JonathanLee said in Netgate 4200 Behavior: Power Button Standby, LEDs Brightness, Coreboot: https://forum.netgate.com/topic/186169/netgate-2100-customization-of-leds-guide I customized all my LEDs. Check it out.. Thanks for the extensive guide on setting LED behavior - it's interesting to learn how they can be customized based on firewall states (something more involved than "off" or "time of day"), which is a cool use case for them. Great idea. I look forward to experimenting when I get pfSense set up. The 4200 is using an Atom CPU, so power states could be different than how ARM-based devices behave. @stephenw10 said in Netgate 4200 Behavior: Power Button Standby, LEDs Brightness, Coreboot: That is the full powered down state (S5). The LED controller is still active but the CPU is not. Thank you for the confirmation about power states and for the information on basic LED manipulation and coreboot, straight from the source! I'm glad to know that what I'm seeing on the 4200 is indeed its expected behavior and it is in fact turning off after all, with the intended exception of the LED controller. To reiterate in different words, the intended power behavior is more akin to a TV or receiver (off but LED standby glow) rather than to a PC (fully dark), and it's safe to unplug once the orange glow begins. I figured it was probably a user education issue, so thanks for the user education. Upon closer inspection of the LED glow escaping the case airholes, there exist some additional diagnostic LEDs on the motherboard that I suspect may not be addressable by the pfSense LED controller - at least I've never seen reference to anyone doing that. Thus, regardless of what programming we can accomplish with the three case LEDs, we'll need to open the case anyway in order to silence its overglow. I successfully solved my issue and my walls no longer light up - Netgate's SSD guide for the 4200 was easy to follow to open the case up. For future users who may run across this post, these are the things I did. Tools: thick black electrical tape, scissors, plastic tweezers, plastic watercolors paintbrush, camera. The butt of the paintbrush was used extensively to push tape down into small places, smooth it out onto surfaces, and as a fishtape to pull stuff underneath the motherboard without detatching it. Clear plastic lightguides on the front face of the case (horizontal); they peek through at the bottom of the motherboard. Can cover everything except the front face that goes into the case LED cutouts. Horizontal lightguides underneath the motherboard. These are hard to reach individually, so I did one large floor-to-ceiling height belt-like strip attached at the front to get them all at once. The paintbrush can help fish the tape through. Vertical 3-high lightguide on the back side of the motherboard. Easy to reach and really cover. Surfaces that lightbleed from the horizontal front might reflect off of: floor underneath motherboard near lightguides. Surfaces lightbleed from the vertical guides might reflect off of: rear case fascia right next to the lightguide, console port cage side, ethernet ports cage side. Surfaces light from under-mainboard LEDs (green) reflects off of: silver colored detatchable panel at the bottom of the case. (don't cover up airholes). Three (3) diagnostic green LEDs on the top surface of the motherboard periodically spaced along the edge by the SSD (labeled D47, D79, D78). They don't stick out and are very small (but mighty!), so it may help to take a photo with the unit powered up for reference. Two (2) green status LEDs on the SSD if you have the MAX one installed (Innodisk P80 3TE6 on mine). These are on the top surface about a third of the way off the mainboard, two exterior edges next to one of the large chips. Two (2) green LEDs on the bottom surface of the motherboard on the opposide edge as the top-facing LEDs. These are easiest to access through the removable door on the bottom of the case. I didn't remember to write down their designators. With all that taped up, there's only a little bit of lightbleed visible from the lightguides if looking directly down into the case (expected as one can never realistically block 100%) and most importantly no overglow at all onto the walls. Much better!
  • disabling certain processes during reboot

    11
    0 Votes
    11 Posts
    496 Views
    stephenw10S
    Yup, there's no easy way to do it. It would be easier to enable or disable a policy routing rule to move traffic to to the VPN instead. Though there is also no way to set that disabled at boot in the gui.
  • 6100 Bricked again…..???

    16
    0 Votes
    16 Posts
    1k Views
    stephenw10S
    One other thing you should try is a different USB cable. Surprisingly we have seen bad cables present like that. Though it's hard to imagine how that could be possible.....
  • 0 Votes
    5 Posts
    580 Views
    keyserK
    @ltctech Yes, it was the passive DAC cable you linked to above. I had no issues using “allow unsupported tranciever” on the switch. It was an Aruba 5400R ZL2 modular chassis switch with a 8 port SFP+ v3 module.
  • Desktop Appliance Upgrade Options

    10
    0 Votes
    10 Posts
    649 Views
    D
    I am unaware of that but bad firmware does make sense. Even like the N5095 or N5105 would be a lot better in terms of performance specs/rating.
  • 4200 initial access and setup

    5
    0 Votes
    5 Posts
    501 Views
    S
    @davidstoll adding in, they will convert the config for free for their hardware.
  • 0 Votes
    2 Posts
    217 Views
    C
    After reading a comment in this thread - https://www.reddit.com/r/Netgate/comments/1bzsv4m/the_sfp_10gbaset_80m_copper_rj45_transceiver_for/ - I found the problem. I was testing to a 1gig port on a Cisco switch. Temporarily moved it to a 10G port on a server and the interface is up and working.
  • SG-2220 → SG-1100 migration (failed)

    4
    0 Votes
    4 Posts
    338 Views
    04CC400
    @stephenw10 Hey, TAC has delivered, thanks.
  • Netgate 8300 released…

    2
    2 Votes
    2 Posts
    333 Views
    M
    @keyser holy mama [image: 1719262527073-b29ca74a-8645-4301-8129-574affefcb51-image.png]
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.