Date: Fri, 17 Feb 2006 23:33:50 +0000 From: "Rick Helmus" <rhelmus@gmail.com> To: "Boris Samorodov" <bsam@ipt.ru>, freebsd-stable@freebsd.org Subject: Re: Ignoring firewall startup scripts Message-ID: <f9f64dbf0602171533y5c1e3a9ep@mail.gmail.com> In-Reply-To: <04572438@srv.sem.ipt.ru> References: <f9f64dbf0602171300j5bd874e4s@mail.gmail.com> <84894541@srv.sem.ipt.ru> <f9f64dbf0602171339g70f9fdbai@mail.gmail.com> <52731540@srv.sem.ipt.ru> <f9f64dbf0602171425y63f9eb1ct@mail.gmail.com> <04572438@srv.sem.ipt.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
2006/2/17, Boris Samorodov <bsam@ipt.ru>:
> Can you show exact messages which ipfw wrote when logging (the very
> first one, when you lost internet)? They may be left at
> /var/log/messages file.
>
I re-enabled the ipv6 stuff from rc.conf(including the commented
variables). It doesn't give any errors anymore, so they must have been
related to the blocked network device.
I checked /var/log/messages, it says that IPFW is succesfully
loaded("ipfw2 (+ipv6) initialized, divert loadable, rule-based
forwarding enabled, default to accept, logging disabled"). It doesn't
contain any logs from the previous boots anymore.
Anyway I just found out there is another command for ipv6
ipfw(ip6fw..), 'ip6fw list' lists the rules that /etc/rc.firewall6
creates :)
So ipv6 seems to do it's work, while ipv4 doesn't.
>
> Well, sometimes very strange things do occure. ;-)
>
Hehe yup. Though I want to try things that make more sense first ;)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f9f64dbf0602171533y5c1e3a9ep>