Hi
I have a dual processor, single core amd64 machine running a recent
cvsup of 8 stable. On this development machine I use netgraph(3) to
implement one to one NAT with one ng_nat(4) node. I use ipfw(8) rules
to direct traffic to netgraph nodes as needed based on table entries
using an ng_ipfw(4)
On Thu, Jan 14, 2010 at 02:46:35PM -0800, Erik Klavon wrote:
> I have several dual processor, single core amd64 machines running
> 8.0p1. These machines use netgraph to implement one to one NAT with
> one ng_nat(4) node for each network client behind them. ipfw(8) rules
> direc
On Thu, Jan 14, 2010 at 06:26:56PM -0800, Julian Elischer wrote:
> Erik Klavon wrote:
> >On Thu, Jan 14, 2010 at 04:22:31PM -0800, Julian Elischer wrote:
> >>Erik Klavon wrote:
> >>>Here are the hooks for one ng_nat(4) node of interest. At the time I
> >>&g
On Thu, Jan 14, 2010 at 04:22:31PM -0800, Julian Elischer wrote:
> Erik Klavon wrote:
> >Here are the hooks for one ng_nat(4) node of interest. At the time I
> >obtained this information, this node was working correctly. Everything
> >in this output looks correct.
> &
Hi
I have several dual processor, single core amd64 machines running
8.0p1. These machines use netgraph to implement one to one NAT with
one ng_nat(4) node for each network client behind them. ipfw(8) rules
direct traffic to netgraph nodes as needed based on table entries
using an ng_ipfw(4) node.
Hi Qing,
On Tue, Sep 15, 2009 at 05:05:46PM -0700, Li, Qing wrote:
> I have committed the code into -CURRENT and it's now merged into 8
> Release branch. So RC1 should contain the fix.
The patch worked for me as well. Thanks for fixing this so quickly and
for getting it in for RC1. I'll test agai
