Gargoyle Forum

Devices with Broadcom WiFi chipsets have limited OpenWrt supportability (due to limited FLOSS driver availability for Broadcom chips). Consider this when chosing a device to buy, or when deciding to flash OpenWrt on your device because it is listed as supported. See Broadcom WiFi for details. Altho...

Maybe implement a DNS loop there. Set up a manual DNS server on Pi-hole other than on the router.

Or you can try setting the DHCP server to delegate its own DNS server using setting 6: viewtopic.php?f=5&p=57829#p57829

Probably yes. For example, if you have a Belkin router, you need to set different temperature limits. The temperature limits are stored in the file /usr/sbin/fan_monitor and you have to set the values yourself. You can see in real time how you are doing at the temperature: while true; do a=`cat /sys...

I simplified it a bit. Access the router via SSH using PuTTY (https://www.gargoyle-router.com/phpbb/viewtopic.php?f=8&t=8505) and run these commands, which will do everything for you: wget --no-check-certificate http://gargoyle.romanhk.cz/WRT1900AC%20Fan%20Control/fan_control -P /etc/init.d/ wge...

Use this command to define clients to use the DNS server you define.
The command is written to the /etc/dnsmasq.conf file.

I don't know if we all understand each other here. I've never said that users should install OpenWrt packages when they don't really need them (like ftpd, samba, minidlna, miniupnpd). If someone wants to test version 1.13.x, this should be done with the supplied Gargoyle packages - not from the Open...

LOL! Sorry Guys! I do what RomanHK write. Now works almost ok. Thanks! I still user vsftpd, installed using ssh. vsftpd dont create /etc/config/vsftpd And USB Storage via dont create the ftp user in /etc/passwd. In logread: Sat Nov 21 13:10:20 2020 daemon.err uhttpd[1945]: uci: Entry not found Sat ...

Why write it over and over ... , I edited my post viewtopic.php?p=57711#p57711, so take a look.

Try "Factory Reset" with "Failsafe Mode": viewtopic.php?p=57637#p57637

What sound weird to me is that the drive used to work correctly in the past. This was just an idea, but it is possible that there was an incompatibility by upgrading to a new version (linux kernel module or other packages). It is possible that the new kernel uses different USB commands and therefor...