kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x320 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff8153fae0 stack pointer = 0x28:0xfffffe000059d7b0 frame pointer = 0x28:0xfffffe000059d820 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = resume, IOPL = 0 current process = 21 (dom0) trap number = 12 panic: page fault cpuid = 0 time = 1623189232 KDB: enter: panic db:0:kdb.enter.default> bt Tracing pid 21 tid 100091 td 0xfffff800049a8000 kdb_enter() at kdb_enter+0x37/frame 0xfffffe000059d470 vpanic() at vpanic+0x197/frame 0xfffffe000059d4c0 panic() at panic+0x43/frame 0xfffffe000059d520 trap_fatal() at trap_fatal+0x391/frame 0xfffffe000059d580 trap_pfault() at trap_pfault+0x4f/frame 0xfffffe000059d5d0 trap() at trap+0x286/frame 0xfffffe000059d6e0 calltrap() at calltrap+0x8/frame 0xfffffe000059d6e0 --- trap 0xc, rip = 0xffffffff8153fae0, rsp = 0xfffffe000059d7b0, rbp = 0xfffffe000059d820 --- smp_targeted_tlb_shootdown() at smp_targeted_tlb_shootdown+0x420/frame 0xfffffe000059d820 pmap_ts_referenced() at pmap_ts_referenced+0x5c6/frame 0xfffffe000059d8f0 vm_pageout_worker() at vm_pageout_worker+0xf88/frame 0xfffffe000059dcb0 vm_pageout() at vm_pageout+0x193/frame 0xfffffe000059dcf0 fork_exit() at fork_exit+0x7e/frame 0xfffffe000059dd30 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe000059dd30 I don't recognize that backtrace, but it seems to be pretty deep in an area unlikely to have a bug. It see it's running in KVM. It could be an issue in the Hypervisor hardware, or something else in the VM settings, but it's unlikely to be a problem in pfSense itself. I'd snapshot it and upgrade it to 2.5.2-RC before anything else, though.

@hshs7129 You'd be better off putting it into bridge mode, so pfsense can handle IPv6 properly.

Hmm, I'm not aware of anything there that actually causes a kernel panic. You see any errors in the wireless logs? You might try a 2.5.2 snapshot. Or 2.6 even. But if this is the first time you've seen an issue since April it's almost impossible to know if it makes any difference. Steve

@beedsley I guess i posted too soon, 3rd try and it is successfully updated.

@viciousxusmc said in Suricata / Netmap Crashing on High Traffic Stable 2.4.5 Broken 2.5.1: Netmap and Suricata running in in-line mode See various posts from bmeeks about this on 2.5.x/FreeBSD 12, e.g. https://forum.netgate.com/topic/163853/snort-and-internet-speed-problem/9. It sounds like inline may be more problematic on 12.

@akegec thank you for your time and suggestion. I already cleared the cache for browser. used different browsers and computer as well. restated the pc/pfsense. I would also like to add that I can see required website in ip-permit logs. But it all never resolved the issue. Thank you

@ifixit not enought information but if i have to guess you need to set the vswitch to vlan10 or vlan4095 if you have configured vlans on pfsense

I would suggest as a first move installing some monitoring tools with historical data, for example telegraf (influxdb + grafana on separate machine) will show dropped packets, pf metrics, system ....

The interfaces themselves must be set as static. You would only set them to DHCP there if you want them to pull an IP from some other DHCP server, like you would for a WAN interface. You to enable a DHCP server instance on those interfaces in Services > DHCP Server. Doing that will allow a client connected to them to pull a lease in the correct subnet. Steve

EXTRA CONTENT: Configure the WebGUI to use HTTPS (port 443) using pfSense's terminal/console/shell. Using option 12 ("12) PHP shell + pfSense tools") perform the commands... $config['system']['webgui']['protocol'] = "https"; $config['system']['webgui']['port'] = "443"; write_config(); exec; ... and exit... exit Use option 11 ("11) Restart webConfigurator") to restart the WebGui. Test WebGUI access (HTTPS, port 443)... curl -k https://10.2.0.101 NOTE: Use "-k" flag to avoid "curl" give the "SSL certificate problem" error message. This will workaround it allowing insecure connections. [Ref(s).: https connection using CURL from command line ] NOTE: Requests on port 80 (HTTP) will automatically be redirected to port 443 (HTTPS). TIP: This file contains many of the ways that pfSense uses to consume its settings... vi /conf/config.xml ... based on these templates we can define ways to use option 12 ("12) PHP shell + pfSense tools") to perform configurations like this example... $config['system']['webgui']['port'] = "443"; write_config(); exec; . Thanks! =D

@sdok said in Install Plex Media Server along side?: I donno if it will come out 1:1 in the end. Yeah there for sure would be some config issues with interface names.. em vs vmx, igb, etc. depending on what the hardware is and vm naming, etc. How complicated is the config - rules, other packages, vlans, etc. etc. A vanilla sort of config can be up in minutes for sure.. Just clean without any restore, etc. You could spend way more time trying to figure out how to manipulate the xml to work as restore on different vm software vs just doing clean from scratch setup - depending on how far your away from just base install.. wan/lan = internet sort of thing.

@gabacho4 I thought i was alone on this issue but it seems there are few people having this issue https://redmine.pfsense.org/issues/11979

@viragomann, thanks a lot buddy!! that's totally fixed the GW off-line issue. That's the way it came from the ISP but never actually noticed the mask is 255.255.255.255. Good catch! hats -off!!! I can now carry one with rest of the config. -San

@stex there was bugs in privileges. Maybe this helps: docs.netgate.com/pfsense/en/latest/troubleshooting/authentication.html

Thank you for the link, however sadly it does not cover the questions that were asked and only covers a basic network setup and the most useful add-ons to install. I know putting the pfsense in front of the UDM Pro would be the easiest thing to do however would this not log all traffic shown as coming from the WAN interface IP address of the UDM Pro? This is not what I want to achieve as I want to monitor all traffic from all internal Vlans showing the original devices IP address. In and out? Sorry if I did not make it clear.

@viragomann Ah, okay got it. I thought I could do it with the admin user I setup through the GUI but I had to SSH into the machine using root@192... all good now, thanks!

Below is the complete process to enable access to the pfSense's server sshd (ssh, port 22) from a private network... Using option 8 ("8) Shell") turning off the firewall with the command... pfctl -d ... and access pfSense server through the ssh (port 22)... ssh root@<PFSENSE_SRV_IP> ... using the initial password "pfsense". TIP: We recommend changing the initial password. Using option 12 ("12) PHP shell + pfSense tools") perform the commands... unset($config['interfaces']['wan']['blockpriv']); write_config(); exec; ... and exit... exit Using option 8 ("8) Shell") again, add a rule to allow access through port 22 on the wan interface... easyrule pass wan tcp any any 22 TIP: The "any any" parameters allow you to restrict the source IP and destination IP respectively. NOTE: The above command will turn on the firewall (same as pfctl -e) and this will drop the ssh connection (port 22), but the ssh connection will be allowed. PLUS: For more explanations about why private networks and loopback addresses are blocked by default on WAN here Block private networks - What does that do, what is it used for ? and here Address Allocation for Private Internets.

If you're actually hitting the max processes limit something is amiss. If you are though you should see it in Status > Monitoring. Do you see a slow rise in the processes number or a spike just before it crashes? Steve