Martineau
Part of the Furniture
Apologies, me trying to post (from memory without typos) on a phone and having a numpty moment is extremely embarrassingMartineau,
Newest Code Posted
Code:ASUSWRT-Merlin RT-AC68U 384.13-0 Wed Jul 31 17:27:27 UTC 2019 admin@RT-AC68U-1340:/tmp/home/root# cd /jffs/scripts admin@RT-AC68U-1340:/jffs/scripts# admin@RT-AC68U-1340:/jffs/scripts# ls -lah *-start -rwxr-xr-x 1 admin root 2.1K Nov 22 11:59 firewall-start -rwxr-xr-x 1 admin root 181 Nov 22 11:03 init-start -rwxr-xr-x 1 admin root 859 Nov 22 11:03 wan-start admin@RT-AC68U-1340:/jffs/scripts# admin@RT-AC68U-1340:/jffs/scripts# ipset list Valid_VPN_IP Name: Valid_VPN_IP Type: hash:net Revision: 6 Header: family inet hashsize 1024 maxelem 65536 comment Size in memory: 410 References: 2 Number of entries: 1 Members: 8.8.8.8 comment "snbforums.com" admin@RT-AC68U-1340:/jffs/scripts# admin@RT-AC68U-1340:/jffs/scripts# sh -x ./init-start + modprobe -sv xt_comment.ko + IPSET_NAME=Valid_VPN_IP + basename ./init-start + logger -st (init-start) 1817 Creating IPSET Valid_VPN_IP (init-start): 1817 Creating IPSET Valid_VPN_IP + ipset create Valid_VPN_IP hash:net comment admin@RT-AC68U-1340:/jffs/scripts# admin@RT-AC68U-1340:/jffs/scripts# sh -x ./firewall-start + IPADDR=192.168.2.26 + IPSET_NAME=Valid_VPN_IP + iptables -D FORWARD -s 192.168.2.26 -i br0 -p udp -m udp --dport 53 -j ACCEPT + iptables -D FORWARD -s 192.168.2.26 -i br0 -o tun1+ -m set --match-set Valid_VPN_IP dst -j ACCEPT -m comment --comment ALLOWED_thru_VPN + iptables -D FORWARD -s 192.168.2.26 -i br0 -o tun1+ -m set ! --match-set Valid_VPN_IP dst -j DROP -m comment --comment BLOCKED_thru_VPN + iptables -nvL FORWARD --line -t filter + grep state INVALID + cut -d -f1 + iptables -I FORWARD 5 -s 192.168.2.26 -i br0 -o tun1+ -m set ! --match-set Valid_VPN_IP dst -j DROP -m comment --comment BLOCKED_thru_VPN + iptables -nvL FORWARD --line -t filter + grep state INVALID + cut -d -f1 + iptables -I FORWARD 5 -s 192.168.2.26 -i br0 -o tun1+ -m set --match-set Valid_VPN_IP dst -j ACCEPT -m comment --comment ALLOWED_thru_VPN + iptables -nvL FORWARD --line -t filter + grep state INVALID + cut -d -f1 + iptables -I FORWARD 5 -s 192.168.2.26 -i br0 -p udp -m udp --dport 53 -j ACCEPT admin@RT-AC68U-1340:/jffs/scripts# admin@RT-AC68U-1340:/jffs/scripts# sh -x ./wan-start + IPSET_NAME=Valid_VPN_IP + basename ./wan-start + logger -st (wan-start) 1842 Adding domains to IPSET Valid_VPN_IP (wan-start): 1842 Adding domains to IPSET Valid_VPN_IP + nslookup snbforums.com + grep -oE ([0-9]{1,3}\.){3}[0-9]{1,3} + grep -v 127.0.0.1 + ipset add Valid_VPN_IP 8.8.8.8 comment snbforums.com ipset v6.32: Element cannot be added to the set: it's already added + ipset add Valid_VPN_IP 8.8.8.8 comment snbforums.com ipset v6.32: Element cannot be added to the set: it's already added + ipset add Valid_VPN_IP 104.27.127.97 comment snbforums.com + ipset add Valid_VPN_IP 104.27.126.97 comment snbforums.com + nslookup speedtest.net + grep -oE ([0-9]{1,3}\.){3}[0-9]{1,3} + grep -v 127.0.0.1 + ipset add Valid_VPN_IP 8.8.8.8 comment speedtest.net ipset v6.32: Element cannot be added to the set: it's already added + ipset add Valid_VPN_IP 8.8.8.8 comment speedtest.net ipset v6.32: Element cannot be added to the set: it's already added + ipset add Valid_VPN_IP 151.101.130.219 comment speedtest.net + ipset add Valid_VPN_IP 151.101.2.219 comment speedtest.net + ipset add Valid_VPN_IP 151.101.194.219 comment speedtest.net + ipset add Valid_VPN_IP 151.101.66.219 comment speedtest.net + nslookup whatismyipaddress.com + grep -oE ([0-9]{1,3}\.){3}[0-9]{1,3} + grep -v 127.0.0.1 + ipset add Valid_VPN_IP 8.8.8.8 comment whatismyipaddress.com ipset v6.32: Element cannot be added to the set: it's already added + ipset add Valid_VPN_IP 8.8.8.8 comment whatismyipaddress.com ipset v6.32: Element cannot be added to the set: it's already added + ipset add Valid_VPN_IP 104.16.154.36 comment whatismyipaddress.com + ipset add Valid_VPN_IP 104.16.155.36 comment whatismyipaddress.com admin@RT-AC68U-1340:/jffs/scripts#


I have updated post #10 to correct the spurious DNS entries being added to the IPSET and all three scripts will now print progress messages to Syslog.
So please use the new script versions and replace/rename init-start with services-start.
Hopefully this should finally fix your issue, and Syslog will now show the progress during the boot to highlight/expose any 'timing' conflicts.
Code:
grep -E "*-start" /tmp/syslog.log