iperf

It shouldn't – but that still doesn't solve the problem here (cron spam). It's only relevant to arpwatch. Even if arpwatch supported some other mail mechanism, should we decide to include this script in base as sendmail or if some other package uses it the crontab spam would still occur. (Re)moving sendmail to alleviate cron spam doesn't fix anything, it only stops the notifications from letting the admin know that shit's broken. Fixing the broken shit is the cure.

Thanks for the link. The recommended video did provide links to more sophisticated scenarios, but none yet reflect my particular circumstances. It has however clarified the forum area that I need to post to (probably NAT), so thanks for that and regards to Dr Strangelove? ;)

xx.xx.1.80-180(Vlan1), xx.xx.2.80-180(Vlan2) xx.xx.3.80-180(Vlan3) & xx.xx.4.180(Vlan4). No idea why you wouldn't put those scopes on a subnet boundary.  But I'm gay for easy rules later. Attached an image I did. Doesn't directly speak to your situation but gets the point across I think.  Just ignore the fact that I have the WAN VLAN everywhere.  You probably won't do that.  You'll probably have just one untagged port with your modem on it. [image: VLAN-pfSense.png] [image: VLAN-pfSense.png_thumb]

Sorry to drudge up an old topic, but how did the replacement card work out? I am looking at using that card as well.

https://github.com/pfsense/pfsense/blob/RELENG_2_2/usr/local/www/guiconfig.inc https://github.com/pfsense/pfsense/tree/RELENG_2_2/usr/local/www/csrf

https://doc.pfsense.org/index.php/Accessing_modem_from_inside_firewall

here a patch to use with "system patches"-package: add a new patch, name it. Put the following into "Patch contents: --- sshd.orig +++ sshd @@ -102,1 +102,3 @@ - $sshconf .= "Ciphers aes128-ctr,aes256-ctr,arcfour256,arcfour,aes128-cbc,aes256-cbc\n"; + $sshconf .= "Ciphers chacha20-poly1305@openssh.com,aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr\n"; + $sshconf .= "KexAlgorithms curve25519-sha256@libssh.org,diffie-hellman-group-exchange-sha256\n"; + $sshconf .= "MACs hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-512,hmac-sha2-256,umac-128@openssh.com\n"; Base directory is /etc/ Tick "Ignore whitespaces" At last tick "auto apply". save, test, apply when no errors. done

This is the reason  :- Stopped at 6449MB    :'( I bought Kingston SE9 G2 for replacement ;D Thank you all :) [image: sandisk8g.jpg] [image: sandisk8g.jpg_thumb]

Works just fine here. With dead pfSense versions, you are pretty much on your own.

You don't need multiple ports.  Search for Apache Virtual Hosts using your favorite search engine.  Also called name-based virtual hosts.

Why install packages and modify files when its not necessary? Thanks for the tip on the existing reboot script though, I'll update my command :) You know your help might be better recieved if you offered it with a touch of deocrum.  In each post of this thread you've given a derogatory comment, expression (rolling eyes) or just plain condecending.  This attitude probably accounts for your high number of smite points. No one wants to receive help from someone being like that.  Something to reflect on for future posts.

have you followed this? https://doc.pfsense.org/index.php/OpenVPN_with_RADIUS_via_Active_Directory also, openvpn questions should goto the openvpn sub-forum

There was no clear known cause I could see in the crash report, but everything centered around your bce0 NIC. Hardware issue perhaps? Or maybe some tuning changes need made. db:0:kdb.enter.default>  show pcpu cpuid        = 9 dynamic pcpu = 0xfffffe010daed800 curthread    = 0xfffff800037f0000: pid 12 "irq256: bce0" curpcb      = 0xfffffe00003a9cc0 fpcurthread  = none idlethread  = 0xfffff800035f5000: tid 100012 "idle: cpu9" curpmap      = 0xffffffff82181fd8 tssp        = 0xffffffff8219d338 commontssp  = 0xffffffff8219d338 rsp0        = 0xfffffe00003a9cc0 gs32p        = 0xffffffff8219ed90 ldt          = 0xffffffff8219edd0 tss          = 0xffffffff8219edc0 db:0:kdb.enter.default>  bt Tracing pid 12 tid 100072 td 0xfffff800037f0000 bce_intr() at bce_intr+0x4e1/frame 0xfffffe00003a9b20 intr_event_execute_handlers() at intr_event_execute_handlers+0xab/frame 0xfffffe00003a9b60 ithread_loop() at ithread_loop+0x96/frame 0xfffffe00003a9bb0 fork_exit() at fork_exit+0x9a/frame 0xfffffe00003a9bf0 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe00003a9bf0 Fatal trap 12: page fault while in kernel mode cpuid = 9; apic id = 01 fault virtual address = 0x18 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff804ad801 stack pointer         = 0x28:0xfffffe00003a9a90 frame pointer         = 0x28:0xfffffe00003a9b20 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 12 (irq256: bce0) There were several link state transitions for bce0 along with watchdog timeouts before the crash, but the message buffer isn't timestamped so there is no way to tell if they were immediately before the crash or some time ago: bce0: /usr/pfSensesrc/src/sys/dev/bce/if_bce.c(7869): Watchdog timeout occurred, resetting! <5>bce0: link state changed to DOWN bce0: <5>bce0: link state changed to UP Gigabit link up! bce0: Gigabit link up! <5>bce0: link state changed to DOWN bce0: <5>bce0: link state changed to UP Gigabit link up! bce0: Gigabit link up! bce0: /usr/pfSensesrc/src/sys/dev/bce/if_bce.c(7869): Watchdog timeout occurred, resetting! <5>bce0: link state changed to DOWN bce0: <5>bce0: link state changed to UP Gigabit link up! bce0: Gigabit link up! bce0: /usr/pfSensesrc/src/sys/dev/bce/if_bce.c(7869): Watchdog timeout occurred, resetting! <5>bce0: link state changed to DOWN bce0: <5>bce0: link state changed to UP Gigabit link up! bce0: Gigabit link up! <5>ovpns3: link state changed to DOWN <5>ovpns3: link state changed to UP <5>ovpns3: link state changed to DOWN <5>ovpns3: link state changed to UP bce0: /usr/pfSensesrc/src/sys/dev/bce/if_bce.c(7869): Watchdog timeout occurred, resetting! <5>bce0: link state changed to DOWN bce0: <5>bce0: link state changed to UP Gigabit link up! bce0: Gigabit link up! bce0: /usr/pfSensesrc/src/sys/dev/bce/if_bce.c(7869): Watchdog timeout occurred, resetting! <5>bce0: link state changed to DOWN bce0: <5>bce0: link state changed to UP Gigabit link up! bce0: Gigabit link up! I'd be suspicious of that NIC if it were me.