Date: Mon, 25 Mar 1996 06:31:16 -0800 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: Jian-Da Li <jdli@FreeBSD.csie.NCTU.edu.tw> Cc: freebsd-current@freebsd.org Subject: Re: 2.2-960323-SNAP: ipfw problem Message-ID: <26913.827764276@time.cdrom.com> In-Reply-To: Your message of "Mon, 25 Mar 1996 21:32:13 %2B0800." <199603251332.VAA00749@FreeBSD.csie.NCTU.edu.tw>
next in thread | previous in thread | raw e-mail | index | archive | help
This is entirely correct, and has been discussed here for weeks. The idea now is that ipfw blocks all by default and you have to add rules to make it accept things. I'm sure there's a single wildcard rule you can add to get your network working again, or simply turn ipfw off if you're not using it! Jordan > > Hi : > > I just upgraded to 960323 from 960212, and my network was dead. > After try&error for 2 hours, I found that if I add IPFW-related > functions into kernel, my network will die even localhost. > The problem is, my ipfw list is empty, it should not block any > host. > It's ok since I don't really use ipfw, but please check it. :) > Thanks. > > -- > > 李 建 達 (Jian-Da Li) 交大資工 > E-Mail : jdli@csie.nctu.edu.tw
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?26913.827764276>