Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 12 Jan 2003 00:06:56 +0100
From:      "Nikolaj Farrell" <nikk@home.se>
To:        "Adam Maas" <mykroft@explosive.mail.net>, "Ben Williams" <benwilliams@instantemail.net>
Cc:        <freebsd-questions@FreeBSD.ORG>
Subject:   Re: Re[2]: Problems w NIC
Message-ID:  <004901c2b9c6$23a11e60$0100a8c0@athlon>
References:  <001701c2b987$9fdf72e0$0100a8c0@athlon> <1042300066.51041.227.camel@localhost> <002a01c2b989$f2099e90$1200a8c0@gsicomp.on.ca> <000b01c2b98a$df9981c0$0100a8c0@athlon> <1042301568.51041.233.camel@localhost> <001201c2b98e$063311e0$0100a8c0@athlon> <1042303096.51041.237.camel@localhost> <000301c2b993$55e70610$0100a8c0@athlon> <20030111171152.GH25529@sub21-156.member.dsl-only.net> <001b01c2b995$0dbf6d30$0100a8c0@athlon> <20030111173058.GI25529@sub21-156.member.dsl-only.net> <000301c2b99a$65c6ba60$0100a8c0@athlon> <133553800012.20030111130531@instantemail.net> <011501c2b9c2$e06f9c00$7419cdcd@ticking>

next in thread | previous in thread | raw e-mail | index | archive | help


> Yeah, this is a classic example of ipfw enabled but not configured. Since
> the default rule is 'Deny all', you need to add allow statements to the
> config to see the network, or build a non-ipfw config (Being the internal
> box, you have no need for ipfw on it)
> 
> --Adam
> 

Nope. Kernel compiled IPFIREWALL_DEFAULT_TO_ACCEPT.
Also see my previous mail.

/Nikolaj



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?004901c2b9c6$23a11e60$0100a8c0>