Network Problem with custom kernel
oremanj at webserver.get-linux.org
Mon Jun 16 21:51:01 PDT 2003
On Tue, Jun 17, 2003 at 10:31:36AM +0545 or thereabouts, Rohit Neupane seemed to write:
> I'm new to freebsd. I'm using 4.6.2-RELEASE. After compiling a custom
> kernel I'm getting problem in the network. When I try to ping any
> machine I get message "ping: sendto: No route to host" I can't even
> ping the localhost .
> I guess my network interface is properly detected. ifconfig shows my
> network interface is xl0
> I've allowed everything in the firewall on the very first rule.
> These are the options I've put in the kernel
> device miibus
> device xl
> options INET
> options INET6
> options MROUTING
> options IPFIREWALL
> options IPFIREWALL_VERBOSE
> options IPFIREWALL_FORWARD
> options IPFIREWALL_VERBOSE_LIMIT=100
> options IPFIREWALL_DEFAULT_TO_ACCEPT
> options IPDIVERT
> options IPFILTER
> options IPFILTER_LOG
> options IPFILTER_DEFAULT_BLOCK
^^^^^^^^^^^^^ That's it, right there.
> options IPSTEALTH
> I guess I'm missing something. Also, how can I do "make distclean" (as
> in linux) if I want to recompile then kernel ?
> Thanks a lot.
You've blocked all traffic by default. Blocking via firewall doesn't just
block incoming packets; it blocks outbound ones too.
You have three options:
* Remove the IPFILTER_DEFAULT_BLOCK line
* Run `ipf -D'
* Set up an IPF firewall
But really, why would you have both IPFIREWALL and IPFILTER in the kernel? You
should only have one.
> Rohit Neupane
> freebsd-questions at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
More information about the freebsd-questions