admin@router:/tmp/mnt/apps/skynet# grep -F "151.101.192" skynet.ipset
add Skynet-Whitelist 151.101.192.0/22 comment "CDN-Whitelist: AS54113"
admin@router:/tmp/mnt/apps/skynet# grep cdnwhitelist skynet.cfg
cdnwhitelist="enabled"
Like i said i've re-installed CDN whitelisting is already enabled by default. I haven't touched a thing. I'm only telling you what the logs are reporting back. Unless the logs are incorrect it seems we're going around in circles.I already mentioned that the Fastly CDN is whitelisted automatically in Skynet if CDN whitelisting is enabled. This includes 151.101.192.0/22. I would focus on determining if your CDN whitelisting is working and able to fetch the whitelists from api.hackertarget.com.
Bash:admin@router:/tmp/mnt/apps/skynet# grep -F "151.101.192" skynet.ipset add Skynet-Whitelist 151.101.192.0/22 comment "CDN-Whitelist: AS54113 admin@router:/tmp/mnt/apps/skynet# grep cdnwhitelist skynet.cfg cdnwhitelist="enabled"
Post the output of those two commands if you really want to solve this. Adamm doesn't maintain the content of the lists, so there's not a lot for him to do with this problem in my opinion.Like i said i've re-installed CDN whitelisting is already enabled by default. I haven't touched a thing. I'm only telling you what the logs are reporting back. Unless the logs are incorrect it seems we're going around in circles.
here is what is says for mePost the output of those two commands if you really want to solve this. Adamm doesn't maintain the content of the lists, so there's not a lot for him to do with this problem in my opinion.
Can you browse to this list used to populate the whitelist?
So that's why your whitelists are incomplete. The site that hosts the lists is limiting requests, which has been a problem with a popular script like Skynet.That link just defaults to a page with "
API count exceeded - Increase Quota with Membership"
Typical. I guess it is a good thing Skynet has a manual whitelist.So that's why your whitelists are incomplete. The site that hosts the lists is limiting requests, which has been a problem with a popular script like Skynet.
firewall whitelist asn AS54113
Just ran it through TOR and a VPN still the same results, so i don't think an IP change will fly.In other parts of the script, Adamm had created a semi-random User Agent string that may have worked around such a limit with other providers. Maybe a similar approach would work here. But you'd need @Adamm for that change.
Try running this command to see if it takes:
If it fails, try again at random times. Or force your WAN IP to change somehow. Not sure.Code:firewall whitelist asn AS54113
It looks like despite not being able to access the page, skynet will still take the whitelist command. My whitelist appears to be much larger now after running your command.In other parts of the script, Adamm had created a semi-random User Agent string that may have worked around such a limit with other providers. Maybe a similar approach would work here. But you'd need @Adamm for that change.
Try running this command to see if it takes:
If it fails, try again at random times. Or force your WAN IP to change somehow. Not sure.Code:firewall whitelist asn AS54113
curl -fsL --retry 3 --connect-timeout 3 -A "ASUSWRT-Merlin RT-N66U v$(nvram get buildno)_$(nvram get extendno) / $(tr -cd 0-9 </dev/urandom | head -c 20)" "https://api.hackertarget.com/aslookup/?q=AS54113" | grep -oE '([0-9]{1,3}\.){3}[0-9]{1,3}/[0-9]{1,2}' | awk -v asn="AS54113" '{printf "add Skynet-Whitelist %s comment \"CDN-Whitelist: %s\"\n", $1, asn }' | ipset restore -!
As proof of concept, I need to stop distracting you from that awesome FlexQoS. You are brilliant.Another option is to try this manually one-time as a proof-of-concept:
I set the model as N66U since it can't run skynet and would not be a common UA String.Bash:curl -fsL --retry 3 --connect-timeout 3 -A "ASUSWRT-Merlin RT-N66U v$(nvram get buildno)_$(nvram get extendno) / $(tr -cd 0-9 </dev/urandom | head -c 20)" "https://api.hackertarget.com/aslookup/?q=AS54113" | grep -oE '([0-9]{1,3}\.){3}[0-9]{1,3}/[0-9]{1,2}' | awk -v asn="AS54113" '{printf "add Skynet-Whitelist %s comment \"CDN-Whitelist: %s\"\n", $1, asn }' | ipset restore -!
In this case, as with many part of FlexQoS, I've just borrowed more of Adamm's own code.As proof of concept, I need to stop distracting you from that awesome FlexQoS. You are brilliant.
Update Skynet and try again. new version available.Does that one piece of code work then? If that's the case i'll re-install Skynet and just use that code.
It appears the IP is blaclisted but also is whitelisted. Whitelisted IP's has the priority over blacklisted once so the site should be accessible.Another associated IP blocked: 151.101.1.21
Thank you for reporting the issue.Update Skynet and try again. new version available.
Still no issues here with PayPal.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!