[19:19] <apb1963> 16.04 Is it possible to setup a dhcpd server with 1 ethernet card, or must I have 2?
[19:23] <apb1963> I'm running into this error: No subnet declaration for enp5s0 (external IP redacted) and I can't help but wonder if it's because I don't have two ethernet cards.
[19:27] <apb1963> Or if perhaps this error " Not configured to listen on any interfaces!" is more relevant even though it comes after the above.  The odd thing is, I do in fact setup the Listen device in /etc/default/isc-dhcp-server
[19:29] <apb1963> Yeah... I'm starting to think it's because I only have the one card... so the external address is not on the same network, so it has no device to use on the local net.
[19:30] <apb1963> Which is of course the network I need to allocate IPs on.
[19:31] <apb1963> Maybe I can get the one card to respond to both internal and external addresses?
[19:31] <apb1963> I'm sure there's a way to do that.  OK, thanks!
[19:36] <_KaszpiR_> apb1963 sure you can have dhcp with 1 card
[19:36] <_KaszpiR_> and it looks liek you're missing config section for the subnet
[19:37] <_KaszpiR_> you may also vlans to separate public and private network
[19:38] <_KaszpiR_> *also use vlans
[19:38] <_KaszpiR_> but it may require additional network configuration on the switch level and so on
[20:20] <apb1963> _KaszpiR_, That's just it... I'm not missing a config section for the 192.168.1 network.  But the card is an external IP.  My router died and I figured I'd just setup the software to replace it.
[20:21] <apb1963> i'm not all that familiar with vlans and I suspect it's overkill for my  home network.
[20:23] <apb1963> So, it wants a config section for the IP associated with the card - an external address.  From the network's point of view, that same machine is NOT on the 192.168.1 network.
[20:23] <apb1963> Which I suspect is why it's giving me the errors.
[20:24] <apb1963> Because there is no interface associated with that subnet.
[20:24] <apb1963> And so, I'm guessing I need to use a virtual IP for the internal address.
[20:25] <apb1963> But then it occurred to me that I have a wireless card installed.  And that's where I'm at now... looking at how to set the wireless card for the internal subnet.
[20:26] <apb1963> Oh... I was looking at how to setup virtual IPs... it requires disabling network manager, or modifying one of its file after first messing with the GUI - I need a pure cli solution.
[20:27] <apb1963> Which is why I'm leaning towards two cards.
[20:28] <_KaszpiR_> apb1963 better get second card
[20:29] <_KaszpiR_> especially if you do not have a router
[20:29] <_KaszpiR_> nor manageable switch
[20:34] <apb1963> no router, no switch... well there's a router from my ISP but it's a black box.
[20:34] <apb1963> _KaszpiR_, by second card, you mean a second ethernet card or is the wireless card sufficient?
[20:35] <_KaszpiR_> I'd sujggest second ethernet card
[20:35] <_KaszpiR_> unless all the other devices are wireless only
[20:36] <apb1963> Yes, except one is both wired & wireless...  Once I bring it up, it will be swapping roles with this machine.
[20:37] <apb1963> I'm unclear as to why it's an issue.  They protocol should really be relevant as long as they can talk to each other.  By protocol I mean tcp/ip.
[20:38] <apb1963> sorry, that last sentence was confused.
[20:39] <apb1963> I'm unclear as to why it's an issue.  As long as they both speak the same protocol (tcp/ip) then whether wired or wireless I wouldn't expect to make a difference.  Or am I wrong?
=== xMopxShell is now known as xMopx