[TriLUG] OwnCloud network setup question

[Igor Partola]

iptables/ip6tables would be the way to go to restrict access. It's not
clear exactly what your setup is. Will the NIC2 get its own public IPv4
address that's separate from your main router?

Is your main goal here to make OwnCloud inaccessible from the LAN (as in
put it into a real DMZ), or just to make it easier to access OwnCloud
without doing port forwarding?

DynDNS will not help with firewalling, only with making access from the
WAN easier, if your public IPv4 address changes.

Igor

On Tue, Jul 02, 2013 at 10:55:37AM -0400, Carl Crider wrote:
> Hey guys,
> 
> I recently finished a new Debian media server / XBMC setup, and I would like
> to run OwnCloud on it as well. The OwnCloud install and config is straight
> forward, but my question is about networking.
> 
> I'm thinking of installing another NIC that will be dedicated to OwnCloud
> access. The idea is that I can connect this NIC directly to my bridge in
> order to separate the internal LAN from the outside world.
> 
> So the setup would be:
> NIC1 - Internal LAN / my home network
> NIC2 - OwnCloud access only
> 
> Now to the questions:
> Can someone suggest the best (secure) configuration for something like this?
> Should I use iptables or something else?
> Would it be easier to have DynDNS or similar? (note: easy is not always my
> favorite way)
> 
> Thanks
> 
> ~Carl
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://www.trilug.org/pipermail/trilug/attachments/20130702/d243faa0/attachment.pgp>