answers:
log 03 = yes. i got 4 ips!! (2x ipv6 + 2x ipv4), and noone of them are my openwrt public ip, so they has to belong to CF .... this is the nslookup for windows at my job, try yourself
C:\Windows\System32>nslookup al-anon.cl
Servidor: xx.xxxxxx.xxx.xxx.xx
Address: x.x.x.x
Respuesta no autoritativa:
Nombre: al-anon.cl
Addresses: 2400:cb00:2048:1::681f:5774
2400:cb00:2048:1::681f:5674
104.31.87.116
104.31.86.116
password = as i don't know any script documentation, i found this for myself (same as installing ca-certificates pkg) comparing the script output and CF api doc ... i ignore if there is a test environment (would be terrific)
log 07 = i think this shouldn'd be this way ... in one hand, the ip detection (htp:/dyndns/checkip, wan eth ip or whatever) detects the public ip of your router .. in the other hand, dns queries return ips owned by cloudflare cdn, i think since CF provides you a front layer of redundancy, security and cache, this is ok ... so the ips from your server and CF will be always different, and this is the point in this case
log 09 = agree... would be cool also if we can obtain record id from CF webpage or somewhere to input directly in script config skipping one step (afraid.org script does similar, it also protects your real login)
log 10 = the registered ips inside cloudflare records should always be the same as obtained with nslookup, so i think this step could be also skipped
i think the real point here is to keep your router connectivity in 2 ways.. between cloudflare (for users browsing your webpage), and beetween YOU (for admin your router, access home network, etc.)
B E F O R E
HOME : INTERNET
:
your home your : internet
network router : surfer
:
,~~~~~. | | : O
( cloud )---[::::]---- /|\
`~~~~~' / \ / \
/ :\
+-+ : \ O
server |=| : /|\ YOU
+-+ : / \
A F T E R
HOME : INTERNET
:
your home your : cloudflare internet
network router : dns+cdn surfer
:
,~~~~~. | | : +---+ O
( cloud )---[::::]--X--| ? |-------/|\
`~~~~~' / \ +---+ / \
/ :X
+-+ : \ O
server |=| : /|\ YOU
+-+ : / \
(image powered by notepad++ column select 
)
in the example above, i think the connections marked with "X" are the critical, but as i see, the one to cloudflare cdn should be the scope of this script ... if cloudflare can supply a (sub)domain pointing directly to your router ip would be great, but in the meanwhile there is the ddns service we used before
i clearly see cloudflare is not intended for accesing your router remotely, but as a way to protect your web server for loads, attacks, etc. with a front layer .... so according this i think the way this script should work is just "ping" cloudflare service to say "hi, i am here" so it can note your router ip *internally* to reach your ENDPOINT WEBSERVER when it requests ... so the detection/update should be in the *endpoint ip* registered in cloudflare records
(Last edited by atesin on 17 Dec 2016, 23:22)
