[14:51] <zaki> hello
[16:31] <knx> hi. if i have a server connected with two ethernet ports, one connected to a router, can someone please help me understand what is necessary to be able to plug another device into the secondary ethernet port and be part of the same LAN (i.e. reach the same DHCP daemon).
[16:32] <knx> from what i can tell i have at least two options, either bridge eth0 and eth1, or use iptables and forward communication between eth0 and eth1 (and masquerade eth1?), or am i mistaken?
[16:32] <knx> sorry, meant "a server with two ethernet ports, one connected..."
[16:34] <knx> or can i specify the servers routing table such that eth0 and eth1 don't have to be bridged nor iptable'd in order to reach eachother?
[20:01] <Phanes> anybody using lxd/lxc?  not really finding a solid guide on custom image creation from scratch.  any suggested reading?
[20:37] <patdk-lap> Phanes, there is nothing to it
[20:37] <patdk-lap> it's the exact same why you would make an image for anything else, -kernel
[20:39] <Phanes> ok, so, if i make an image for virtualbox it's an entirely different process then if i make an iso for bare metal, if I make an image for qemu it's entirely different a process then if I make it for either of those, and if I make an image for hyper-v it's entirely different then if i make an image for any of those.  so if just one single person who knows how to do this could spare me the philosophical tripe and just link me to some docs on
[20:39] <Phanes> image creation in LXD i'd -very- much appreciate it in lieu of feeling stupid.
[20:40] <patdk-lap> hmm, the process for all of the above is the same
[20:40] <Phanes> that's not accurate
[20:40] <patdk-lap> virtualbox/qemu/bare/... all use the same image
[20:40] <Phanes> .ignore patdk-lap*!*@*
[20:40] <Phanes> does anyone actually know how to do this?
[22:17] <terabyte> hey. I have a choice, install a startup.service file via the debian package itself, or allow it to be configured via puppet. What's best practice/ standard?
[22:17] <Phanes> puppet should be used for all of that during the whole lifecycle of the server
[22:17] <Phanes> that's puppet's purpose
[22:18] <terabyte> ok. so the deb package should just install the package, and shouldn't install any .service files. Thanks
[22:23] <Phanes> no
[22:23] <Phanes> don't use debs on a puppet server
[22:24] <Phanes> you'll thank yourself later
[22:24] <Phanes> use the puppet abstraction layers for package management
[22:24] <terabyte> hm?
[22:25] <Phanes> puppet abstracts away distro-specific things
[22:25] <terabyte> I'm using package {}, but package is ultimately going to be a deb from some private repo.. And I also write the package. I guess it's a question of who's responsibility it is to create users/startup scripts. deb package or puppet...
[22:25] <Phanes> ah ok
[22:25] <terabyte> right
[22:25] <Phanes> oh
[22:26] <Phanes> that should be puppet
[22:26] <Phanes> since those are going to be configurable if you've written your service correctly
[22:26] <terabyte> ok
[22:26] <Phanes> but at the same time users not using puppet should not be expected to create those
[22:26] <terabyte> well this is the thing ^^
[22:27] <Phanes> heh yep.  it should go in the package but should be overridden in puppet
[22:27] <terabyte> ok cool.
[22:29] <terabyte> thanks *
[22:42] <Kiwi_Alien> good morning
[22:42] <Kiwi_Alien> I wish to make my samba ubuntu server only LAN
[22:42] <Kiwi_Alien> im a little confused
[22:43] <Kiwi_Alien> I read that i can simply just not give it a gateway?
[22:45] <compdoc> that can work. and you can block it on the router
[22:45] <compdoc> it will never be able to update
[22:46] <Kiwi_Alien> shouldnt have to worry about updates if its on lan?
[22:46] <Kiwi_Alien> An then if i wanted to, I could ssh in to then update?