@kevinspooner If the device can't be accessed using the console after a reset the the issue isn't "pfSense" any more. It's worse. Like your PC, as soon as you put it on, the BIOS does show stuff on the screen - on the console access. Later on, the OS is read from the disk, and started. If the BIOS doesn't start, that's a bad sign. On your side, you could try to replace things like RAM/disks .... and triple check the power brick. If that's all a no go, then you could ask Netgate for more advise / help. Do triple check if console settings like serial speed and other are correct. Use known to work serial UDB cables. ....... edit : sh*t. It's a spam. He edited the quoted message. [image: 1612952774837-d68fd422-301a-4c8b-80d6-c2e3a20ef352-image.png]

@tiger-0 said in SG-3100 Keeps Initializing after Power outage: been a power outage Which can actually break the file system ** If this happens, hook up the console access, and then start the device. See what happens. After all the 'hardware enumeration' you'll see a message that says that the file system is dirty. A tool called 'fsk' is run to repair that situation. If it doesn't work out, you have to do it manually. Because this situation happens way before the GUI works, console access is mandatory. Use this Netgate video as a guide-line. Think about hooking up an UPS to your pfSense device. ** take your PC, and rip out the cable or battery while it's running. It will complain when it's restart. Do this several time, and you'll be good for a re install, loosing all your files. ( so please just believe me don't do this just to proof me wrong / right ) @tiger-0 said in SG-3100 Keeps Initializing after Power outage: We tried doing a hard reset but the indicator lights just keep blinking ( That's like playing 'Russisch roulette' with your pfSense device.

@stephenw10 Thank you very much.

Yes, I would not go to the dev version on the 3100 currently as it's still the Nov 27th snapshot. Steve

I've reset it to factory defaults and set it up from start. Now it looks OK.

@stephenw10 Hi and thank you for responding. Well, must be an invalid image? As I followed those exact directions from the ticket advice received on Friday. The system upgraded, but left intact no gid for 'wheel'. The new installer upgraded my system from 2.4.4 to 2.4.5 from the logs. And the pdf documentation downloaded rendered an english text, with a russian table of contents. That is the kicker, I can't search it properly. So must be invalid. I'll open a new ticket, try again. So glad you responded so quickly!

You can't if they are all using port 443 (or 80). You can either redirect port 443 to the internal IP or allow HAProxy to accept that connection on the firewall but not both. However that's exactly what HAProxy is for. It can accept all the connections on port 443 and send them to the correct server based on the requested URL. Steve

@stephenw10 Thanks Steve.

Same question, what have you actually tried there? What was the result? Have you only tested from the XG-7100? The on-board ix ports? Steve Edit: Discussion continued here: https://forum.netgate.com/topic/160384/sfp-transceiver-to-connect-to-adva-box

@alleykat It’s hardware. The CPU is a dualcore lowpower ARM CPU that does not contain a lot of horsepower. It’s actually the same CPU as in the SG-1100, but because SG-2100 has two physical NIC’s (SG-1100 only has one), it’s capable of handling interupts from each interface on each CPU core and thus has a higher throughput than SG-1100

@teamits so it still happened with pfblocker disabled and after I reset factory settings. I noticed in the logs the wan almost constantly had a dhcp error of it being notified there was a new IP...which was the IP that it was already using. There was also an arp error. After some googling it looked like other people with fios were having the same issue. I disconnected sg-2100 and reset the fios ONT which pulled a new IP from verizon and since then its been fine. I need to further research what exactly was going on but it seems to be something dhcp related to verizon.

Just the boot part : Cleaning takes time, as it found disk issues : @diesec said in SG-2100 veeeeery slow: WARNING: / was not properly dismounted To make it (a lot) boot faster : take your time to shut it down. Use the GUI halt command, or the SSH equivalent. Ripping out the power will stress the file system. And as said above : Compare boot times with a working WAN, and a non working WAN.

@teamits said in SG-3100 - NAT rule for single Public IP: Are you having the NAT rule create a linked firewall rule that allows traffic to 192.168.2.10:22? That should be the default. confirmed, this was working automatically. Figured out it was the source port needing to be "any". Thanks!

@arf_668 said in Control SG-4860 status LED?: ubuntu 16.04 You should update! I've never tried in Linux. I would probably start looking at OpenWRT where they have a bunch of LED control code. Back when I first started looking at this I used lcdproc as a reference where it was bit banging on the parallel port. The actual code I previously used was very similar to this: https://github.com/stephenw10/WGXepc/blob/master/WGXepc.c#L559 Though I don't recommend anyone uses my terrible code! The gpiobase for C2K is 0x500. You can get those details from the Intel docs. Steve

Just as alternative dual booting a MBP with Mint works great for console access. Drivers for everything already in kernel etc. Also I'm pretty sure if you install UEFI to the m.2 drive it will then boot from that by default. The 2.5 installer gives you more options in that respect. Steve

You may have been locked out by sshguard in which case just wait until your IP is unblocked again. Otherwise try connecting to the serial console and restarting php and the webconfigurator, console menu options 16 then 11. https://docs.netgate.com/pfsense/en/latest/solutions/sg-1100/connect-to-console.html Steve

I mean protonmail unfortunately.

@stephenw10 thanks for that, I just didn't know if I'd missed something where repo's changed or whatnot.

@stephenw10 Thanks for the confirmation. Now I know what do if it happens again. Also 2.5 seems to be coming soon for the fix.