Date: Fri, 3 Jan 2014 08:05:55 -0500 From: Alejandro Imass <aimass@yabarana.com> To: "Rudy (bulk)" <crapsh@monkeybrains.net> Cc: freebsd-jail@freebsd.org Subject: Re: Allowing routing table visibility in jails to make multiple IPs work properly Message-ID: <CAHieY7R_M95UxVX=sY%2B32hF1JUiC4tw2eRko7tNswChN8cw%2BZw@mail.gmail.com> In-Reply-To: <52C66E09.80307@monkeybrains.net> References: <201311301000.rAUA00eG045983@freefall.freebsd.org> <52C66E09.80307@monkeybrains.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jan 3, 2014 at 3:00 AM, Rudy (bulk) <crapsh@monkeybrains.net> wrote: > > I'm having issues when putting multiple IPs on a jail... one external, one > internal (on a different vlan). The source IP from the jail is always the > first IP, so a solution is to use ipfw_nat to nat when using the internal > vlan to the 'second ip'. Ugly hack. and it doesn't work when there is an > MTU difference between the vlans: > Greetings Rudy, I had the same exact problem and found that the problem is natd. Actually it is mentioned in natd's documentation. If you want to get rid of this problem you need to get rid of natd and nat your jail traffic with some other means. Kernel nat should be a solution but I've never gotten around to test if it actually solves the problem. Please share if you find a way to fix this. Best, Alejandro Imass
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHieY7R_M95UxVX=sY%2B32hF1JUiC4tw2eRko7tNswChN8cw%2BZw>