Anton Aylward wrote:
On 04/01/2016 01:12 PM, Per Jessen wrote:
Why bother? when you've got DHCP running anyway, it's easier to let it hand out the fixed addresses too, IMHO. It's a standard one-liner in dhcpd.conf as opposed to fiddling with various interfaces on different devices.
While your latter statement is true your former statement is not.
I do NOT have DHCP running. KISS.
The DHCP services are done in the Linksys wifi router and are entirely internal to that router. They do not magically feed out the "WAN" port on the main LAN. I do not have any config files for DHCP set up. Becuase i'm not running a DHCP server. KISS.
For the sake of completeness in this reply, I will acknowledge that dnsmasq *CAN* also do DHCP, but remember that the PC is running on a switch and would have to listening to some broadcast stuff that the switch might or might not pass to the PC from anything on the switch but wouldn't be coming from anything plugged into the wifi or ATA routers (see above). That's more setup. KISS.
I have dnsmasq running, Just that. KISS. No config file, set up, no details of anything on the command line. The simplest possible setting. Its there to do DNS. Nothing more. KISS. Its simpler that setting up a full blown DNS Server. BTDT, too fiddly. KISS.
As for "fiddling" with the interfaces on the wifi and the ATA routers, no I didn't do that beyond setting up the WAN port and setting up the TUN address of my VOIP service and setting the wifi password. KISS again; the DHCP stuff on each is there by default.
I thought you said "the PERMANENTLY HARD-WIRED and 'resident' devices, my PC, the database server under my desk, the printer, the Linksys ATA for my phones all have static WAN addresses."
And yes I have done DHCP servers as you suggest. I'd done that at home to try it out. I have the config archived if I ever need to go back to those headaches. I've set it up many times in a corporate setting and integrated it with a 'classical' DNS service. Complete with cryptographic key :-) or rather "-( 'cos its all a pain in the ass if its not actually needed and in a home setting and SMB where little changes, its a complexity that's not needed.
That's why I don't bother.
Oddly, with your predilection for KISS, you seem to have neglected the principle in all of the above :-) Personally, I find running DHCP matches KISS exceptionally well. Except for the router/firewall, all of my internal systems and devices use DHCP, as they all do by default. No per-device setup required. Known devices don't change all hat often and have their line in dhcpd.conf for years. The main 40 lines of that file never change. I fail to spot any headaches and complexities. -- Per Jessen, Zürich (11.8°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org