Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 05 Oct 2005 16:40:29 -0000
From:      "Foo Ji-Haw" <jhfoo@nexlabs.com>
To:        "Chuck Swiger" <cswiger@mac.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: How do you patch a driver?
Message-ID:  <005601c5f9ba$c5c4f5e0$0600a8c0@ishtar>
References:  <00ad01c5c7c8$e187d7d0$c801a8c0@nexpc> <4340AB54.5080101@gmail.com><004a01c5c7d3$a6fb2170$c801a8c0@nexpc> <43410D8E.60602@gmail.com><010701c5c89a$f193a0f0$c801a8c0@nexpc> <4342957A.7060200@mac.com>

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

> Add:
>
> options IPFIREWALL_FORWARD
> options IPFIREWALL_DIVERT
>
> ...to your kernel config file.  This is mostly documented here:
>
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/firewalls-ipfw.html

Thanks for the tip. Unfortunately, the IPFIREWALL_FORWARD was not mentioned 
in the link you gave me (which I visited prior). Otherwise I wouldn't have 
lost 2 nights working on this. But that's over now. I'm working on another 
stumbling block on ipfw.

> Also note that ipfw forwarding alone may not do what you expect, unless 
> you make special efforts on the machine being forwarded to, to recognize 
> the additional IP addresses.  You might find using the redirect_host or 
> redirect_port directives to natd more appropriate for your purposes.
Thanks for your concern. For my purposes, it's only a gateway. The NAT 
router is further down the road. Appreciate the tip anyway.

>
> -- 
> -Chuck
>
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to 
> "freebsd-questions-unsubscribe@freebsd.org" 




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?005601c5f9ba$c5c4f5e0$0600a8c0>