2 issues on latest builds
-
t1) upgraded to the 28th aug nanobsd snap and after a few minutes it just rebooted and then i saw the below in console and then kept rebooting
vr0: promiscuous mode enabled
ath0_wlan0: promiscuous mode enabled
Syncing OpenVPN settings…done.
Starting syslog...done.
Configuring firewall...Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x0
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc09baae1
stack pointer = 0x28:0xe2de3a54
frame pointer = 0x28:0xe2de3a70
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 0 (ath0 taskq)
trap number = 12
panic: page fault
Uptime: 27s
Cannot dump. Device not defined or unavailable.
Automatic reboot in 15 seconds - press a key on the console to abort
Rebooting...- from the past few days including 26th aug nanobsd snap i think my states r dropping and every few minutes my yahoo messenger seems to logout and relogin automatically, what i guess the issue might be is apinger or any changes lately to it as i got just one wan conenction and the default gateway is not pingable so apinger as usual keeps showing it as offline but in the past that didnt make any difference but i guess now its creating issues of state drops etc and this happens with less than 100 states entries with just one lan client so state tables getting full cant be possible.
-
You have to put a valid monitor ip otherwise it will clear states.
-
but then how was it working fine till now and what i dont understand is y is apinger coming into effect when u have only one pppoe wan connection?
-
i guess the panic is the same mentioned in the below thread
http://forum.pfsense.org/index.php/topic,27896.0.html -
Panic should be fixed on the next new build (which is going now). Should up be in a few hours.
