Probably this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215471

Try removing the virtual cd drive.

Steve

On install of OS you have options to recover config.xml from previous install before format drive.
FYI: now you can auto backup config for free out of box to netgate servers in encrypted way. Or if you have paranoid you can use curl script to download backups on another unix-based machine internally.

I completed the install with pfSense-CE-memstick-2.4.4-RELEASE-p3-amd64.img

I put the Allied Telesis 2711FX back in and it goes back into a panic.

Seems others have run into no support for this card in freebsd.

http://freebsd.1045724.x6.nabble.com/12-STABLE-CURRENT-Dell-PowerEdge-2950-Allied-Telesis-AT-2711FX-SC-100MBit-fibre-NIC-not-recognized-td6328982.html

@NogBadTheBad said in random sources feed: rs_read for hardware device 'intel secure' key ring" returned no entropy:

Anything in the BIOS that can be switched off for the Intel secure key ring / random number generator ?
https://software.intel.com/en-us/blogs/2012/05/14/what-is-intelr-secure-key-technology

You may be better looking in the FreeBSD forums, I'm not sure if pfSense even uses the Intel RNG maybe @jimp or someone else from @netgate

@biggsy said in odd issue with ram?:

@bmeeks

Thanks for the link. I think I get what it's all about. Just found it strange that both topics seemed to be about memory shortage under two different hypervisors.

I found precious little information about that specific error. In fact, practically nothing. I did see SRAT issues mentioned for ESXi and Hyper-V, though. It might take looking into some hypervisor source code to see what the error really means. Hopefully such code is commented enough that you could discern what might be up.

I connected hdd to another motherboard and the system booted. I made the setting and returned hdd to q1900m. Now I go through web interface

Just a heads up we moved the LAGG to an Intel X550-T2 and this appears to have removed (dodged) the issue

there are 3 LED related functions in the Check Point kernel ...

janus_pld_red_led_set (Bit 0x01) janus_pld_yellow_led_set (Bit 0x02) janus_pld_green_led_set (Bit 0x08)
they write to port 0x348 ... this seems to be the Altera MAX II chip (PLD) next to the diag display
btw: the PLD also monitors powersupply status
... and there are 4 LED related functions for 'Phalanx PLD' ... phalanx_pld_red_led_set phalanx_pld_yellow_led_set phalanx_pld_green_led_set phalanx_pld_disk_led_set *****
this might be the explanation for the 'missing' led on the frontpanel PCB (Bit 0x04 is assume)
hope this helps - sorry for the late reply ;)
/paketix

@cinlung said in Connecting PON Modem to PFSense has very high latency:

FO PON modem

directly conect a pc on port 1 of your pon modem a do a test, more likely is a ISP problem

@Renat hello sir thanks for this thread it help me a lot. I have to observed this machine if error still exists. Thumbs up! ;)

AMD A6-6400K APU with Radeon(tm) HD Graphics
2 CPUs: 1 package(s) x 2 core(s)
AES-NI CPU Crypto: Yes (inactive)

I have 1 NIC card attached on my machine. Winyao E350T4 PCI-E X1 Quad Port 10/100/1000Mbps Gigabit Ethernet Network Card Server Adapter LAN I350-T4 NIC This is the specs the NIC card having 4 ports. I hope that the error be fixed. ;)

@Erly-Araújo it was on older version of pfsense https://www.netgate.com/blog/pfsense-2-4-1-release-now-available.html

"Truncated ELF file" => standard OS commands are unreadable.

Leave the disk as is.
Salvage config.xml
Reboot using a install device and install from scratch.

When you are asked to format the destination drive, do no go for quick one, but chose the non-default total format with check (I didn't re install pfSense on a physical disk, mine just wont die after nearly 10 years ...)

https://forum.netgate.com/topic/146189/crash-report-after-update

Thanks for the reply, but I think I got it all set and figured out.

After reading about the XG-7100's setup, I created VLANs for each of my LANs with the one LAGG, and then reassigned the interfaces to the new VLANs. Everything is all good now.

@kiokoman said in Locked out of WebGUI:

from the console using option 15

15) Restore recent configuration

or you can try

pkg delete pfSense-pkg-darkstat-3.1.3_4

you probably have to manually delete all reference to darkstat from the xml config later
or
reinstall everything

Thanks for your help.

I actually had tried that but only tried reinstalling the backup prior to installing Darkstat. What I didn't notice was that it had, for some reason, installed Darkstat about 4 times in a row. So I restored a configuration from last week and it worked and let me have access to the WebGUI. This seems like a weird happening.

I then restored a local backup and everything appears to be working again. I installed Darkstat again it appears to be working as well.

uhm 1.7.11 was my doing, a trivial patch to permit uppercase name for the tabs on status monitoring
https://github.com/pfsense/FreeBSD-ports/pull/662
idk but i don't think it can't be that
I just ran the same commands on my 2.4.4-p3 and i had same results of @Gertjan. so all fine here

@stephenw10 That is a perfect temporary solution for us! Now I can at least get back into my LDAPS and user configs. Thanks! I'm going to do some testing in our non production environment and see if I get get things syncing again. Thanks for your help with this

@pfsensenoobie
You need more than 4GB RAM in order to enjoy zfs's file caching. I have three pfSense boxes running with zfs and M.2 stripes. No problems so far. I think the greatest advantage of zfs is that you don't have to think about how you want to partition the drive.

In case of heavy storms, one cannot exclude the risks due to induction damages caused by lightning...