Date: Sun, 11 May 2014 21:44:26 -0700 (PDT) From: "Chris H" <bsd-lists@bsdforge.com> To: "Ronald F. Guilmette" <rfg@tristatelogic.com> Cc: freebsd-ipfw@freebsd.org Subject: Re: Where do the boot time messages go? Message-ID: <8fb4ad9509f5ec232873ade4f2f3128c.authenticated@ultimatedns.net> In-Reply-To: <1756.1399868907@server1.tristatelogic.com> References: <1756.1399868907@server1.tristatelogic.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > In my /etc/rc.conf file, I have the following (among other things): > > firewall_enable="YES" > firewall_type="/etc/fw.rules" > firewall_logging="YES" > > And of course, on my system, the /etc/fw.rules file is full of ipfw > "add" commands. > > During a normal boot of FreeBSD, I can see those add commands being > processed. They are shown, briefly, whizzing by, on the console. > > During a recent reboot, I also saw something at about the same time > that looked like it might possibly have been some sort of ipfw error > or warning message. > > I would like to investigate. > > Unfortunately it appears that all of the console messages that are > being logged, during the time when ipfw is processing my local firewall > rules file, are not in fact stored into either /var/log/messages nor > even into /var/log/security. (I know. I looked.) > > So, um, where do these messages go, exactly? > > I really would like to have a look at the ones from the last boot. While unlikely, have a look at /var/run/dmesg.boot. I see you have: firewall_logging="YES" Isn't it possible to DEFINE the firewall LOG? :) In other words; you ask it to log, but don't tell it WHERE. :) Doing so should provide the answers you're looking for. Best wishes. --Chris > _______________________________________________ > freebsd-ipfw@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ipfw > To unsubscribe, send any mail to "freebsd-ipfw-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8fb4ad9509f5ec232873ade4f2f3128c.authenticated>