<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Sep 26, 2015 at 1:19 PM, Alex Carver <span dir="ltr"><<a href="mailto:agcarver+ale@acarver.net" target="_blank">agcarver+ale@acarver.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div id=":16l" class="" style="overflow:hidden">Don't bother. Too much extra overhead and if something with the VM<br>
system fails or is compromised then lots of other problems happen.<br>
<br>
Just set the thing up to pass whatever open ports you need straight<br>
through and open the service ports (SSH, etc.) to only the inside<br>
network. If you need to access the router from the outside, bounce<br>
through an internal machine first instead of allowing a direct<br>
connection to the router.<br>
<br>
You could also set the internal service ports to accept connections from<br>
only a select few internal machines.</div></blockquote></div><br>Turns out it doesn't even matter. I wasn't thinking about the CPU when I had my little brainstorm. The CPU doesn't support VT extensions and that just isn't worth the slowness -- <a href="http://ark.intel.com/products/77774/Intel-Pentium-Processor-G3220T-3M-Cache-2_60-GHz">http://ark.intel.com/products/77774/Intel-Pentium-Processor-G3220T-3M-Cache-2_60-GHz</a><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>James Sumners<br><a href="http://james.sumners.info/" target="_blank">http://james.sumners.info/</a> (technical profile)</div><div><a href="http://jrfom.com/" target="_blank">http://jrfom.com/</a> (personal site)</div><div><a href="http://haplo.bandcamp.com/" target="_blank">http://haplo.bandcamp.com/</a> (band page)</div></div></div></div></div>
</div></div>