Install and configure dnsmasq on Synology NAS 

ipkg dnsmasq
In /opt/etc/dnsmasq.conf, modify the path where dhcp lease file is saved:
dhcp-leasefile=/opt/var/dnsmasq/dnsmasq.leases

Comments

Post a Comment

Popular posts from this blog

Connect the Xiaomi Yi Ants Cam to your Synology Surveillance Station

1) Ensure the current firmware of your cam allows you to see the steam without authentication. You can check this using vlc and connecting to rtsp://192.168.1.128:554/ch0_0.h264 If you are able to see the stream, you can go to the next point. Otherwise you have to downgrade the firmware of your cam : Simply place this file on the root of an SD card, insert the SD card in the cam and reset it (a reboot may be sufficient) 2) Create the following file on your synology using putty /volumeX/@appstore/SurveillanceStation/device_pack/camera_support/Xiaomi.conf with this content: [Xiaomi*Ants] api = custom resolution_h264 = 1280x720 default_resolution_h264 = 1280x720 fps_h264_640x480 = 5,10,15,20,25,30 fps_h264_1280x720 = 5,10,15,20,25,30 default_fps_h264_1280x720 = 10 default_image-quality = 5 h264 = rtsp mpeg4 = rtsp mjpeg = rtsp motion = h264,mpeg4,mjpeg motion_param = sensitivity,threshold rtsp_keepalive = none rtsp_protocol = auto,udp,tcp 3) In the surveillanc...
Read more

TXT_DB error number 2 failed to update database

As I m completly unaware of the openssl use, I only write here some observations I made : If after the command : openssl ca -out cert.pem -infiles req.pem you got the following error message : failed to update database TXT_DB error number 2 This is probably because you have generated your own signing certificate with the same Common Name (CN) information that the CA certificate that you've generated before. Simply input a different Common Name each time you are asked should do the trick. Credit : 1
Read more

Progress database odbc error : Broker rejects connection

I was trying to link a Progress database to an SQL Express server few days ago. The connection has first worked fine, but at one moment, I was not able to run any queries and finally got this error message : DataDirect ODBC Progress OpenEdge Wire Protocol driver Broker rejects connection In my case, this error was caused by too many active connections from the user I used to connect from ODBC. But all the applications were closed. So I've used the utility proshut to list all connected users and to kill the unreleased connections: list connected users : [path to proshut] proshut.bat [path to your db] .db -C list kill a specific user :  [path to proshut] proshut.bat [path to your db] .db -C disconnect [user number] #1 #2
Read more