API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Jan 23rd, 2019
586
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 17.63 KB | None | 0 0
raw download clone embed print report
  1. pi@raspberrypi:~ $ pihole -d
  2. This process collects information from your Pi-hole, and optionally uploads it to a unique and random directory on tricorder.pi-hole.net.
  3.  
  4. The intent of this script is to allow users to self-diagnose their installations. This is accomplished by running tests against our software and providing the user with links to FAQ articles when a problem is detected. Since we are a small team and Pi-hole has been growing steadily, it is our hope that this will help us spend more time on development.
  5.  
  6. NOTE: All log files auto-delete after 48 hours and ONLY the Pi-hole developers can access your data via the given token. We have taken these extra steps to secure your data and will work to further reduce any personal information gathered.
  7.  
  8. *** [ INITIALIZING ]
  9. [i] 2019-01-24:01:03:52 debug log has been initialized.
  10.  
  11. *** [ INITIALIZING ] Sourcing setup variables
  12. [i] Sourcing /etc/pihole/setupVars.conf...
  13.  
  14. *** [ DIAGNOSING ]: Core version
  15. [i] Core: v4.0 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
  16. [i] Branch: master
  17. [i] Commit: v4.0-0-gddbdb51
  18.  
  19. *** [ DIAGNOSING ]: Web version
  20. [i] Web: v4.0 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
  21. [i] Branch: master
  22. [i] Commit: v4.0-0-gaf8c926
  23.  
  24. *** [ DIAGNOSING ]: FTL version
  25. [✓] FTL: v4.0 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
  26.  
  27. *** [ DIAGNOSING ]: dnsmasq version
  28. [i] 340:
  29.  
  30. *** [ DIAGNOSING ]: lighttpd version
  31. [i] 1.4.45
  32.  
  33. *** [ DIAGNOSING ]: php version
  34. [i] 7.0.30
  35.  
  36. *** [ DIAGNOSING ]: Operating system
  37. [✓] Raspbian GNU/Linux 9 (stretch)
  38.  
  39. *** [ DIAGNOSING ]: SELinux
  40. [i] SELinux not detected
  41.  
  42. *** [ DIAGNOSING ]: Processor
  43. [✓] armv7l
  44.  
  45. *** [ DIAGNOSING ]: Networking
  46. [✓] IPv4 address(es) bound to the eth0 interface:
  47. 192.168.0.106/24 does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127)
  48. 192.168.1.50/24 matches the IP found in /etc/pihole/setupVars.conf
  49.  
  50. [✓] IPv6 address(es) bound to the eth0 interface:
  51. fe80::59fe:a19e:d061:e8dd does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127)
  52.  
  53. ^ Please note that you may have more than one IP address listed.
  54. As long as one of them is green, and it matches what is in /etc/pihole/setupVars.conf, there is no need for concern.
  55.  
  56. The link to the FAQ is for an issue that sometimes occurs when the IPv6 address changes, which is why we check for it.
  57.  
  58. [i] Default IPv4 gateway: 192.168.0.1
  59. * Pinging 192.168.0.1...
  60. [✗] Gateway did not respond. (https://discourse.pi-hole.net/t/why-is-a-default-gateway-important-for-pi-hole/3546)
  61.  
  62.  
  63. *** [ DIAGNOSING ]: Ports in use
  64. *:22 sshd (IPv4)
  65. *:22 sshd (IPv6)
  66. *:80 lighttpd (IPv4)
  67. *:80 lighttpd (IPv6)
  68. *:53 pihole-FTL (IPv4)
  69. *:53 pihole-FTL (IPv6)
  70. 127.0.0.1:4711 pihole-FTL (IPv4)
  71. [::1]:4711 pihole-FTL (IPv6)
  72.  
  73. *** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
  74. dig: '' is not a legal name (unexpected end of input)
  75. [✗] Failed to resolve via localhost (127.0.0.1)
  76. dig: '' is not a legal name (unexpected end of input)
  77. [✗] Failed to resolve via Pi-hole (192.168.1.50)
  78. [✗] Failed to resolve doubleclick.com via a remote, public DNS server (8.8.8.8)
  79.  
  80. *** [ DIAGNOSING ]: Pi-hole processes
  81. [✗] dnsmasq daemon is inactive
  82. [✓] lighttpd daemon is active
  83. [✓] pihole-FTL daemon is active
  84.  
  85. *** [ DIAGNOSING ]: Setup variables
  86. TEMPERATUREUNIT=F
  87. ADMIN_EMAIL=regal8r8469@gmail.com
  88. WEBUIBOXEDLAYOUT=boxed
  89. PIHOLE_INTERFACE=eth0
  90. IPV4_ADDRESS=192.168.1.50/24
  91. IPV6_ADDRESS=
  92. PIHOLE_DNS_1=208.67.222.222
  93. PIHOLE_DNS_2=208.67.220.220
  94. QUERY_LOGGING=true
  95. INSTALL_WEB_SERVER=true
  96. INSTALL_WEB_INTERFACE=true
  97. LIGHTTPD_ENABLED=true
  98.  
  99. *** [ DIAGNOSING ]: Dashboard and block page
  100. [✗] Block page X-Header: X-Header does not match or could not be retrieved.
  101. HTTP/1.1 200 OK
  102. Content-type: text/html; charset=UTF-8
  103. Date: Thu, 24 Jan 2019 01:07:04 GMT
  104. Server: lighttpd/1.4.45
  105.  
  106. [✓] Web interface X-Header: X-Pi-hole: The Pi-hole Web interface is working!
  107.  
  108. *** [ DIAGNOSING ]: Gravity list
  109. -rw-r--r-- 1 root root 0 Jan 24 01:00 /etc/pihole/gravity.list
  110. -----head of gravity.list------
  111.  
  112. -----tail of gravity.list------
  113.  
  114. *** [ DIAGNOSING ]: contents of /etc/pihole
  115.  
  116. -rw-r--r-- 1 root root 381 Jan 24 00:20 /etc/pihole/adlists.list
  117. https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
  118. https://mirror1.malwaredomains.com/files/justdomains
  119. http://sysctl.org/cameleon/hosts
  120. https://zeustracker.abuse.ch/blocklist.php?download=domainblocklist
  121. https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt
  122. https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt
  123. https://hosts-file.net/ad_servers.txt
  124.  
  125. -rw-r--r-- 1 root root 46 Jan 24 01:00 /etc/pihole/local.list
  126. 192.168.1.50 raspberrypi
  127. 192.168.1.50 pi.hole
  128.  
  129. -rw-r--r-- 1 root root 234 Jan 24 00:56 /etc/pihole/logrotate
  130. /var/log/pihole.log {
  131. su root root
  132. daily
  133. copytruncate
  134. rotate 5
  135. compress
  136. delaycompress
  137. notifempty
  138. nomail
  139. }
  140. /var/log/pihole-FTL.log {
  141. su root root
  142. weekly
  143. copytruncate
  144. rotate 3
  145. compress
  146. delaycompress
  147. notifempty
  148. nomail
  149. }
  150.  
  151. *** [ DIAGNOSING ]: contents of /etc/dnsmasq.d
  152.  
  153. -rw-r--r-- 1 root root 1522 Jan 24 00:57 /etc/dnsmasq.d/01-pihole.conf
  154. addn-hosts=/etc/pihole/gravity.list
  155. addn-hosts=/etc/pihole/black.list
  156. addn-hosts=/etc/pihole/local.list
  157. localise-queries
  158. no-resolv
  159. cache-size=10000
  160. log-queries=extra
  161. log-facility=/var/log/pihole.log
  162. local-ttl=2
  163. log-async
  164. server=208.67.222.222
  165. server=208.67.220.220
  166. interface=eth0
  167.  
  168. *** [ DIAGNOSING ]: contents of /etc/lighttpd
  169.  
  170. -rw-r--r-- 1 root root 3027 Jan 24 00:56 /etc/lighttpd/lighttpd.conf
  171. server.modules = (
  172. "mod_access",
  173. "mod_accesslog",
  174. "mod_auth",
  175. "mod_expire",
  176. "mod_compress",
  177. "mod_redirect",
  178. "mod_setenv",
  179. "mod_rewrite"
  180. )
  181. server.document-root = "/var/www/html"
  182. server.error-handler-404 = "pihole/index.php"
  183. server.upload-dirs = ( "/var/cache/lighttpd/uploads" )
  184. server.errorlog = "/var/log/lighttpd/error.log"
  185. server.pid-file = "/var/run/lighttpd.pid"
  186. server.username = "www-data"
  187. server.groupname = "www-data"
  188. server.port = 80
  189. accesslog.filename = "/var/log/lighttpd/access.log"
  190. accesslog.format = "%{%s}t|%V|%r|%s|%b"
  191. index-file.names = ( "index.php", "index.html", "index.lighttpd.html" )
  192. url.access-deny = ( "~", ".inc", ".md", ".yml", ".ini" )
  193. static-file.exclude-extensions = ( ".php", ".pl", ".fcgi" )
  194. compress.cache-dir = "/var/cache/lighttpd/compress/"
  195. compress.filetype = ( "application/javascript", "text/css", "text/html", "text/plain" )
  196. include_shell "/usr/share/lighttpd/use-ipv6.pl " + server.port
  197. include_shell "/usr/share/lighttpd/create-mime.assign.pl"
  198. include_shell "find /etc/lighttpd/conf-enabled -name '*.conf' -a ! -name 'letsencrypt.conf' -printf 'include \"%p\"
  199. ' 2>/dev/null"
  200. $HTTP["url"] =~ "^/admin/" {
  201.  
  202. setenv.add-response-header = (
  203. "X-Pi-hole" => "The Pi-hole Web interface is working!",
  204. "X-Frame-Options" => "DENY"
  205. )
  206. $HTTP["url"] =~ ".ttf$" {
  207.  
  208. setenv.add-response-header = ( "Access-Control-Allow-Origin" => "*" )
  209. }
  210. }
  211. $HTTP["url"] =~ "^/admin/\.(.*)" {
  212. url.access-deny = ("")
  213. }
  214. include_shell "cat external.conf 2>/dev/null"
  215.  
  216. *** [ DIAGNOSING ]: contents of /etc/cron.d
  217.  
  218. -rw-r--r-- 1 root root 1496 Jan 24 00:56 /etc/cron.d/pihole
  219. 24 3 * * 7 root PATH="$PATH:/usr/local/bin/" pihole updateGravity
  220. 00 00 * * * root PATH="$PATH:/usr/local/bin/" pihole flush once quiet
  221. @reboot root /usr/sbin/logrotate /etc/pihole/logrotate
  222. */10 * * * * root PATH="$PATH:/usr/local/bin/" pihole updatechecker local
  223. 42 19 * * * root PATH="$PATH:/usr/local/bin/" pihole updatechecker remote
  224. @reboot root PATH="$PATH:/usr/local/bin/" pihole updatechecker remote reboot
  225.  
  226. *** [ DIAGNOSING ]: contents of /var/log/lighttpd
  227.  
  228. -rw-r--r-- 1 www-data www-data 826 Jan 24 00:57 /var/log/lighttpd/error.log
  229. 2019-01-20 06:25:01: (server.c.1534) logfiles cycled UID = 0 PID = 14319
  230. 2019-01-23 03:29:37: (log.c.217) server started
  231. 2019-01-23 03:30:00: (log.c.217) server started
  232. 2019-01-24 00:17:12: (log.c.217) server started
  233. 2019-01-24 00:22:49: (server.c.1828) server stopped by UID = 0 PID = 1
  234. 2019-01-24 00:22:50: (log.c.217) server started
  235. 2019-01-24 00:35:22: (server.c.1828) server stopped by UID = 0 PID = 1
  236. 2019-01-24 00:35:23: (log.c.217) server started
  237. 2019-01-24 00:43:30: (server.c.1828) server stopped by UID = 0 PID = 1
  238. 2019-01-24 00:43:31: (log.c.217) server started
  239. 2019-01-24 00:48:34: (server.c.1828) server stopped by UID = 0 PID = 1
  240. 2019-01-24 00:48:34: (log.c.217) server started
  241. 2019-01-24 00:57:25: (server.c.1828) server stopped by UID = 0 PID = 1
  242. 2019-01-24 00:57:26: (log.c.217) server started
  243.  
  244. *** [ DIAGNOSING ]: contents of /var/log
  245.  
  246. -rw-r--r-- 1 pihole pihole 31133 Jan 24 01:00 /var/log/pihole-FTL.log
  247. -----head of pihole-FTL.log------
  248. [2019-01-24 00:17:14.922] ########## FTL started! ##########
  249. [2019-01-24 00:17:14.922] FTL branch:
  250. [2019-01-24 00:17:14.922] FTL version: v4.0
  251. [2019-01-24 00:17:14.922] FTL commit: 8493df4
  252. [2019-01-24 00:17:14.922] FTL date: 2018-08-05 13:40:30 -0700
  253. [2019-01-24 00:17:14.922] FTL user: pihole
  254. [2019-01-24 00:17:14.924] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
  255. [2019-01-24 00:17:14.925] SOCKET_LISTENING: only local
  256. [2019-01-24 00:17:14.925] AAAA_QUERY_ANALYSIS: Show AAAA queries
  257. [2019-01-24 00:17:14.925] MAXDBDAYS: max age for stored queries is 365 days
  258. [2019-01-24 00:17:14.925] RESOLVE_IPV6: Resolve IPv6 addresses
  259. [2019-01-24 00:17:14.925] RESOLVE_IPV4: Resolve IPv4 addresses
  260. [2019-01-24 00:17:14.925] DBINTERVAL: saving to DB file every minute
  261. [2019-01-24 00:17:14.925] DBFILE: Using /etc/pihole/pihole-FTL.db
  262. [2019-01-24 00:17:14.925] MAXLOGAGE: Importing up to 24.0 hours of log data
  263. [2019-01-24 00:17:14.925] PRIVACYLEVEL: Set to 0
  264. [2019-01-24 00:17:14.925] IGNORE_LOCALHOST: Show queries from localhost
  265. [2019-01-24 00:17:14.925] BLOCKINGMODE: Null IPs for blocked domains
  266. [2019-01-24 00:17:14.925] REGEX_DEBUGMODE: Inactive
  267. [2019-01-24 00:17:14.925] Finished config file parsing
  268. [2019-01-24 00:17:14.925] INFO: No whitelist file found
  269. [2019-01-24 00:17:14.925] Compiled 0 Regex filters and -1 whitelisted domains in 0.1 msec (0 errors)
  270. [2019-01-24 00:17:14.952] Database successfully initialized
  271. [2019-01-24 00:17:14.968] Notice: Increasing queries struct size from 0 to 10000
  272. [2019-01-24 00:17:14.968] Notice: Increasing domains struct size from 0 to 1000
  273. [2019-01-24 00:17:14.968] Notice: Increasing clients struct size from 0 to 10
  274. [2019-01-24 00:17:14.968] New forward server: 1.0.0.1 (0/0)
  275. [2019-01-24 00:17:14.968] Notice: Increasing forwarded struct size from 0 to 4
  276. [2019-01-24 00:17:14.968] Notice: Increasing overTime struct size from 0 to 100
  277. [2019-01-24 00:17:14.968] New forward server: 1.1.1.1 (1/4)
  278. [2019-01-24 00:17:15.068] Notice: Increasing queries struct size from 10000 to 20000
  279. [2019-01-24 00:17:15.182] Notice: Increasing queries struct size from 20000 to 30000
  280. [2019-01-24 00:17:15.295] Notice: Increasing queries struct size from 30000 to 40000
  281. [2019-01-24 00:17:15.399] Notice: Increasing queries struct size from 40000 to 50000
  282. [2019-01-24 00:17:15.509] Notice: Increasing queries struct size from 50000 to 60000
  283.  
  284. -----tail of pihole-FTL.log------
  285. [2019-01-24 00:57:48.912] Notice: Increasing queries struct size from 100000 to 110000
  286. [2019-01-24 00:57:49.013] Notice: Increasing queries struct size from 110000 to 120000
  287. [2019-01-24 00:57:49.115] Notice: Increasing queries struct size from 120000 to 130000
  288. [2019-01-24 00:57:49.198] Notice: Increasing overTime struct size from 100 to 200
  289. [2019-01-24 00:57:49.216] Notice: Increasing queries struct size from 130000 to 140000
  290. [2019-01-24 00:57:49.318] Notice: Increasing queries struct size from 140000 to 150000
  291. [2019-01-24 00:57:49.421] Notice: Increasing queries struct size from 150000 to 160000
  292. [2019-01-24 00:57:49.525] Notice: Increasing queries struct size from 160000 to 170000
  293. [2019-01-24 00:57:49.629] Notice: Increasing queries struct size from 170000 to 180000
  294. [2019-01-24 00:57:49.734] Notice: Increasing queries struct size from 180000 to 190000
  295. [2019-01-24 00:57:49.839] Notice: Increasing queries struct size from 190000 to 200000
  296. [2019-01-24 00:57:49.898] New forward server: 208.67.220.220 (2/4)
  297. [2019-01-24 00:57:49.935] Imported 198949 queries from the long-term database
  298. [2019-01-24 00:57:49.935] -> Total DNS queries: 198949
  299. [2019-01-24 00:57:49.935] -> Cached DNS queries: 219
  300. [2019-01-24 00:57:49.935] -> Forwarded DNS queries: 3724
  301. [2019-01-24 00:57:49.936] -> Exactly blocked DNS queries: 2074
  302. [2019-01-24 00:57:49.936] -> Unknown DNS queries: 192932
  303. [2019-01-24 00:57:49.936] -> Unique domains: 472
  304. [2019-01-24 00:57:49.936] -> Unique clients: 7
  305. [2019-01-24 00:57:49.936] -> Known forward destinations: 3
  306. [2019-01-24 00:57:49.936] Successfully accessed setupVars.conf
  307. [2019-01-24 00:57:49.943] PID of FTL process: 4965
  308. [2019-01-24 00:57:49.944] Listening on port 4711 for incoming IPv4 telnet connections
  309. [2019-01-24 00:57:49.944] Listening on port 4711 for incoming IPv6 telnet connections
  310. [2019-01-24 00:57:49.944] Listening on Unix socket
  311. [2019-01-24 00:57:49.945] FATAL: Trying to free NULL pointer in free_whitelist_domains() (regex.c:72)
  312. [2019-01-24 00:57:49.945] INFO: No whitelist file found
  313. [2019-01-24 00:57:49.945] Compiled 0 Regex filters and -1 whitelisted domains in 0.1 msec (0 errors)
  314. [2019-01-24 00:57:49.946] /etc/pihole/gravity.list: parsed 0 domains (took 0.0 ms)
  315. [2019-01-24 00:57:57.186] New forward server: 208.67.222.222 (3/4)
  316. [2019-01-24 01:00:16.561] FATAL: Trying to free NULL pointer in free_whitelist_domains() (regex.c:72)
  317. [2019-01-24 01:00:16.561] INFO: No whitelist file found
  318. [2019-01-24 01:00:16.561] Compiled 0 Regex filters and -1 whitelisted domains in 0.2 msec (0 errors)
  319. [2019-01-24 01:00:16.562] /etc/pihole/gravity.list: parsed 0 domains (took 0.0 ms)
  320.  
  321. *** [ DIAGNOSING ]: Locale
  322. LANG=en_GB.UTF-8
  323.  
  324. *** [ DIAGNOSING ]: Pi-hole log
  325. -rw-r--r-- 1 pihole pihole 1153534 Jan 24 01:07 /var/log/pihole.log
  326. -----head of pihole.log------
  327. Jan 24 00:00:15 dnsmasq[641]: 188325 127.0.0.1/56372 query[A] 3.debian.pool.ntp.org from 127.0.0.1
  328. Jan 24 00:00:15 dnsmasq[641]: 188326 127.0.0.1/56372 query[AAAA] 3.debian.pool.ntp.org from 127.0.0.1
  329. Jan 24 00:00:15 dnsmasq[641]: 188327 127.0.0.1/56372 query[A] 3.debian.pool.ntp.org from 127.0.0.1
  330. Jan 24 00:00:15 dnsmasq[641]: 188328 127.0.0.1/56372 query[AAAA] 3.debian.pool.ntp.org from 127.0.0.1
  331. Jan 24 00:00:15 dnsmasq[641]: 188329 127.0.0.1/51553 query[A] 3.debian.pool.ntp.org from 127.0.0.1
  332. Jan 24 00:00:15 dnsmasq[641]: 188330 127.0.0.1/51553 query[AAAA] 3.debian.pool.ntp.org from 127.0.0.1
  333. Jan 24 00:00:15 dnsmasq[641]: 188331 127.0.0.1/51553 query[A] 3.debian.pool.ntp.org from 127.0.0.1
  334. Jan 24 00:00:15 dnsmasq[641]: 188332 127.0.0.1/51553 query[AAAA] 3.debian.pool.ntp.org from 127.0.0.1
  335. Jan 24 00:00:15 dnsmasq[641]: 188333 127.0.0.1/33818 query[A] 0.debian.pool.ntp.org from 127.0.0.1
  336. Jan 24 00:00:15 dnsmasq[641]: 188334 127.0.0.1/33818 query[AAAA] 0.debian.pool.ntp.org from 127.0.0.1
  337. Jan 24 00:00:15 dnsmasq[641]: 188335 127.0.0.1/33818 query[A] 0.debian.pool.ntp.org from 127.0.0.1
  338. Jan 24 00:00:15 dnsmasq[641]: 188336 127.0.0.1/33818 query[AAAA] 0.debian.pool.ntp.org from 127.0.0.1
  339. Jan 24 00:00:15 dnsmasq[641]: 188337 127.0.0.1/54804 query[A] 0.debian.pool.ntp.org from 127.0.0.1
  340. Jan 24 00:00:15 dnsmasq[641]: 188338 127.0.0.1/54804 query[AAAA] 0.debian.pool.ntp.org from 127.0.0.1
  341. Jan 24 00:00:15 dnsmasq[641]: 188339 127.0.0.1/54804 query[A] 0.debian.pool.ntp.org from 127.0.0.1
  342. Jan 24 00:00:15 dnsmasq[641]: 188340 127.0.0.1/54804 query[AAAA] 0.debian.pool.ntp.org from 127.0.0.1
  343. Jan 24 00:00:15 dnsmasq[641]: 188341 127.0.0.1/41308 query[A] 1.debian.pool.ntp.org from 127.0.0.1
  344. Jan 24 00:00:15 dnsmasq[641]: 188342 127.0.0.1/41308 query[AAAA] 1.debian.pool.ntp.org from 127.0.0.1
  345. Jan 24 00:00:15 dnsmasq[641]: 188343 127.0.0.1/41308 query[A] 1.debian.pool.ntp.org from 127.0.0.1
  346. Jan 24 00:00:15 dnsmasq[641]: 188344 127.0.0.1/41308 query[AAAA] 1.debian.pool.ntp.org from 127.0.0.1
  347.  
  348.  
  349. ********************************************
  350. ********************************************
  351. [✓] ** FINISHED DEBUGGING! **
  352.  
  353. * The debug log can be uploaded to tricorder.pi-hole.net for sharing with developers only.
  354. * For more information, see: https://pi-hole.net/2016/11/07/crack-our-medical-tricorder-win-a-raspberry-pi-3/
  355. * If available, we'll use openssl to upload the log, otherwise it will fall back to netcat.
  356.  
  357. [?] Would you like to upload the log? [y/N] y
  358. * Using openssl for transmission.
  359. [✗] There was an error uploading your debug log.
  360. * Please try again or contact the Pi-hole team for assistance.
  361. * A local copy of the debug log can be found at: /var/log/pihole_debug-sanitized.log
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!