Dhcp not updating lease

If HA is required, we'll need to address this via different architecture, and not by relying on NFS.

I feel we shouldn't support NFS at all -- it's a corner case that hugely impacts performance. The smart-proxy and DCHP server are in the same cluster and traffic is layer 2 so latency should be very low. I'll test with the DHCP server and smart-proxy on the same host.

• Tips for Securing Your Home Router Seemingly minor and easily overlooked settings can still have profound security implications.

Here are some steps you can take to make sure your wired or wireless home router and by extension, your network is as secure as possible.

After the files are catted and tailed before they go into the while loops, run it through a grep -v "#" and then pipe it through all that.

However, it still doesn't explain why my machines are correctly able to resolve my static hosts but not dynamic.

DHCP-induced address changes can be problematic any time you want a computer or other networked device to have a predictable IP address, such as when you want remote access to a PC or NAS device.The DNS Forwarder option "Register DHCP leases in DNS forwarder" does not work. I'm seeing the same as here: can tell you why the leases aren't going in /etc/hosts and have a pretty simple fix (although it's so shallow I'm not even going to post a patch file).However, now that I'm getting the dynamic leases in the /etc/hosts file, I'm resolving them with nslookup on the lan, but no other network services resolve the host correctly.'/usr/lib/ruby/vendor_ruby/sinatra/base.rb:870:in `call'/usr/lib/ruby/vendor_ruby/rack/methodoverride.rb:21:in `call'/usr/lib/ruby/vendor_ruby/rack/commonlogger.rb:33:in `call'/usr/lib/ruby/vendor_ruby/sinatra/base.rb:212:in `call'/usr/share/foreman-proxy/lib/proxy/log.rb:63:in `call'/usr/lib/ruby/vendor_ruby/rack/protection/xss_header.rb:18:in `call'/usr/lib/ruby/vendor_ruby/rack/protection/path_traversal.rb:16:in `call'/usr/lib/ruby/vendor_ruby/rack/protection/json_csrf.rb:18:in `call'/usr/lib/ruby/vendor_ruby/rack/protection/base.rb:50:in `call'/usr/lib/ruby/vendor_ruby/rack/protection/base.rb:50:in `call'/usr/lib/ruby/vendor_ruby/rack/protection/frame_options.rb:31:in `call'/usr/lib/ruby/vendor_ruby/rack/nulllogger.rb:9:in `call'/usr/lib/ruby/vendor_ruby/rack/head.rb:11:in `call'/usr/lib/ruby/vendor_ruby/sinatra/showexceptions.rb:21:in `call'/usr/lib/ruby/vendor_ruby/sinatra/base.rb:175:in `call'/usr/lib/ruby/vendor_ruby/sinatra/base.rb:1949:in `call'/usr/lib/ruby/vendor_ruby/sinatra/base.rb:1449:in `block in call'/usr/lib/ruby/vendor_ruby/sinatra/base.rb:1726:in `synchronize'/usr/lib/ruby/vendor_ruby/sinatra/base.rb:1449:in `call'/usr/lib/ruby/vendor_ruby/rack/builder.rb:138:in `call'/usr/lib/ruby/vendor_ruby/rack/urlmap.rb:65:in `block in call'/usr/lib/ruby/vendor_ruby/rack/urlmap.rb:50:in `each'/usr/lib/ruby/vendor_ruby/rack/urlmap.rb:50:in `call'/usr/lib/ruby/vendor_ruby/rack/builder.rb:138:in `call'/usr/lib/ruby/vendor_ruby/rack/handler/webrick.rb:60:in `service'/usr/lib/ruby/1.9.1/webrick/httpserver.rb:138:in `service'/usr/lib/ruby/1.9.1/webrick/httpserver.rb:94:in `run'/usr/lib/ruby/1.9.1/webrick/server.rb:191:in `block in start_thread' Accessing leases file over NFS will absolutely destroy the performance: we no longer will be able to track updates and will have to parse the leases on every request.On top of that, accessing leases over NFS adds additional latency.Basically the file /etc/rc.parse-isc-dhcpd is parsing the dhcp.lease file, and it is greping out the word "lease".Unfortunately, this appears in several places in the comments section.Forum rules 1) This is a user forum for Synology users to share experience/help out each other: if you need direct assistance from the Synology technical support team, please use the following form:https://myds.synology.com/support/suppo ... lang=enu2) To avoid putting users' Disk Station at risk, please don't paste links to any patches provided by our Support team as we will systematically remove them.Our Support team will provide the correct patch for your Disk Station model. Apr 20 dhcpserver.cgi: synodhcp_remove_expired_lease.c:22 Can not open DHCP lease file Apr 20 dhcpserver.cgi: synodhcp_remove_expired_lease.c:98 Generating temporary lease file failed Apr 20 dhcpserver.cgi: dhcpserver.cpp:499 Cannot remove expired lease Apr 20 dhcpserver.cgi: dhcpserver.cpp:503 Can not open DHCP lease file Apr 20 dhcpserver.cgi: synodhcp_remove_expired_lease.c:22 Can not open DHCP lease file Apr 20 dhcpserver.cgi: synodhcp_remove_expired_lease.c:98 Generating temporary lease file failed Apr 20 dhcpserver.cgi: dhcpserver.cpp:499 Cannot remove expired lease Apr 20 dhcpserver.cgi: dhcpserver.cpp:503 Can not open DHCP lease file Things I tried (with no success):- restarted DHCP-server package- Rebooted the Synology DS212 I don't want to uninstall and reinstall the DHCP-server package, because have a lot of reserved ip-addresses I don't want to lose.... Apr 20 dhcpserver.cgi: synodhcp_remove_expired_lease.c:22 Can not open DHCP lease file Apr 20 dhcpserver.cgi: synodhcp_remove_expired_lease.c:98 Generating temporary lease file failed Apr 20 dhcpserver.cgi: dhcpserver.cpp:499 Cannot remove expired lease Apr 20 dhcpserver.cgi: dhcpserver.cpp:503 Can not open DHCP lease file Apr 20 dhcpserver.cgi: dhcpserver.cpp:404 Can not open DHCP static file Apr 20 dnsmasq[28341]: warning: interface static does not currently exist I'll try this out, I'm having the same issue ! In /etc/dhcpd/I had to change all localhost IPs to the correct ones. Mine were looking like this:interface=bond0dhcp-range=set:bond00,192.168.1.50,192.168.1.100,255.255.255.0,36000dhcp-option=tag:bond00,option:router,127.0.0.1dhcp-option=tag:bond00,option:dns-server,192.168.1.10,192.168.1.205dhcp-option=tag:dns,option:dns-server,127.0.0.1dhcp-option=tag:dns,option:router,127.0.0.1port=0interface=dnsdhcp-range=set:dns,127.0.0.1,127.0.0.1,255.255.255.0,86400dhcp-host=:41:e,asa5505.dintid.dk,192.168.1.1,infinite And it should look like thisinterface=bond0dhcp-range=set:bond00,192.168.1.50,192.168.1.100,255.255.255.0,36000dhcp-option=tag:bond00,option:router,192.168.1.1dhcp-option=tag:bond00,option:dns-server,192.168.1.10,192.168.1.205dhcp-option=tag:dns,option:dns-server,192.168.1.10dhcp-option=tag:dns,option:router,192.168.1.1port=0interface=dnsdhcp-range=set:dns,192.168.1.50,192.168.1.100,255.255.255.0,86400dhcp-host=:41:e,asa5505.dintid.dk,192.168.1.1,infinite In /etc/dhcpd/I had to change all localhost IPs to the correct DNS, Router and DHCP respectively.'/usr/lib/ruby/vendor_ruby/sinatra/base.rb:947:in `each'/usr/lib/ruby/vendor_ruby/sinatra/base.rb:947:in `route! '/usr/lib/ruby/vendor_ruby/sinatra/base.rb:1059:in `block in dispatch! '/usr/lib/ruby/vendor_ruby/sinatra/base.rb:1041:in `block in invoke'/usr/lib/ruby/vendor_ruby/sinatra/base.rb:1041:in `catch'/usr/lib/ruby/vendor_ruby/sinatra/base.rb:1041:in `invoke'/usr/lib/ruby/vendor_ruby/sinatra/base.rb:1056:in `dispatch!'/usr/lib/ruby/vendor_ruby/sinatra/base.rb:882:in `block in call! '/usr/lib/ruby/vendor_ruby/sinatra/base.rb:1041:in `block in invoke'/usr/lib/ruby/vendor_ruby/sinatra/base.rb:1041:in `catch'/usr/lib/ruby/vendor_ruby/sinatra/base.rb:1041:in `invoke'/usr/lib/ruby/vendor_ruby/sinatra/base.rb:882:in `call!