Date: Fri, 19 Sep 2008 16:48:51 -0700 From: Julian Elischer <julian@elischer.org> To: "Ahrenholz, Jeffrey M" <jeffrey.m.ahrenholz@boeing.com> Cc: antipsychic <antipsychic@gmail.com>, freebsd-virtualization@freebsd.org Subject: Re: natd & vimage Message-ID: <48D43A63.8080808@elischer.org> In-Reply-To: <0DF156EE7414494187B087A3C279BDB40A94021D@XCH-NW-6V1.nw.nos.boeing.com> References: <FDDBDFB6-AE66-436C-B3A3-8D0AF9664186@gmail.com> <0DF156EE7414494187B087A3C279BDB40A93F94B@XCH-NW-6V1.nw.nos.boeing.com> <48D2F9B1.8020507@elischer.org> <0DF156EE7414494187B087A3C279BDB40A94021D@XCH-NW-6V1.nw.nos.boeing.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ahrenholz, Jeffrey M wrote: >> please make sure that your fixes go into the vimage branch.. >> we need all the help we can get :-) > > I got the latest vimage branch using cvsup and was able to cleanly apply > my patch, looks like nothing has changed in the divert/mroute files. > Unfortunately it seems that I spoke too soon because my patch locks up > on a dual-core system (I must've been testing with a non-SMP box). So > I'll have to write back when I have something that actually works. > > Another trick, if you just want to nat between vimages, you could > probably use the ng_nat netgraph node... that's why netgraph is the "official" way to connect vimages :-) can you send your diffs anyhow? I never completed the virtualisation of divert. I'll see what I can do with them. > > -Jeff
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48D43A63.8080808>