Gargoyle Forum

Awesome thanks!

Attached. This is the config where I have both 192.168.3.48 and 208.67.222.123 listed so things actually work. *edit never mind "The board attachment quota has been reached" Here are the files: -------------- network -------------- config interface 'loopback' option ifname 'lo' option prot...

Entire configuration

I did some searching but the search function ignores the word "script" so nothing came up. Is there a handy script/cron already written to make a backup every x hours and save to an attached USB drive? I assume this would occur in crontab, but I'm mostly familiar with Debian and router com...

I have a /23 network with the gargoyle router on 192.168.2.1 and a pi-hole running on 192.168.3.48. When I put that into the DNS section of the basic setup, I get no DNS resolution. Is this a further issue of gargoyle not being set up to deal with larger /23 networks? Before this, I specified the Fa...

Super tip, that showed the problem. Below is a bit of output from logread: Thu Jan 6 20:24:29 2022 daemon.crit dnsmasq[2297]: bad DHCP host name at line 227 of /var/etc/dnsmasq.conf.cfg01411c Thu Jan 6 20:24:29 2022 daemon.crit dnsmasq[2297]: FAILED to start up And line 227 of /var/etc/dnsmasq.conf....

Ok, I can deal with that. I’ll just give out the range in the lower half.

Dnsmasq logs are where? Didn’t see them in /etc/logs.

Setting up a TL-WDR3600 from scratch with 1.13, and the DHCP server isn't handing out addresses. I'm basically copying the same setup from my old router on 1.10, but changing the subnet a bit. Am I missing something basic? Here's my /etc/config/network and /etc/config/dhcp files: config interface 'l...

Yes it is normal behaviour. I think you should look at a subnet calculator to understand what is going on. You’ve asked it to use a /23 (255.255.254.0) and it is doing just that :) Note that Gargoyle still isn’t well defined on subnets larger than a /24 so your mileage may vary I have it using a /2...