halcyonardency

/etc/amd.net.map:
========================cut========================
localhost       type:=link;fs:=/
*               host==${key};type:=link;fs:=/ \
                hostd==${key};type:=link;fs:=/ \
                fs:=${autodir}/${rhost}/root/${rfs};type:=host;rhost:=${key};rfs:=/;opts:=nosuid,nodev

halcyonardency

I wrote a simple PHP script to simulate activity (sleep for 500ms).  I set up a vhost to handle PHP requests via mod_fcgid. I 
- used PHP5.2, PHP5.3, PHP5.4 -- doesn't seem to matter. 
- used the latest trunk snapshot of mod_fcgid (2.3.8), and that didn't change behavior 
- used Apache 2.2.22 (and 2.2.17) with both worker and prefork mpms

Trying to figure out how to prevent serialized blocking of requests  in mod_fcgid.


test.php script:

halcyonardency

width:500
gopts:eNq9kE9Lw0AQxb-KUHrcP23oZSGHtd0WQUuJRTwUZN1MmkiaLLObtMp-eLcgeGiqnjwNb4Y385tHloGoQEgJ1b706YTzKHpAXxldk1q_Qp3ehIVaCmO72869b6sDbADn0HiC-piy1nr2AU3rHLOABVtAXxmIIikb7SbThFpsc2rLU0IdmA7BAcYLtAHPLpe-XLYoYi5yx4V8UplcqR9wyEGf_hXpQT6H-TBPOowYZKbkFfwR58ZwXhQD87DaZHfr7RWnuJePcdbhToxndFoXY_eL4StMofv9Xz3ndM8fi1i_Pbu3TxXF0VY==
drange:86400
start:end-86400s
end:now-4493s
comment:2012-08-09T21\:48\:16Z\t\t to \t\t2012-08-10T21\:48\:16Z
getImage:
graphid:1344639789900_graph_1284

halcyonardency

getComment:function(u,p) {
	var q=new Date(), 	
	   s=q.minus(p).toPretty(),
    	   o=q.minus(u+p).toPretty();
	var r="\\t\\t to \\t\\t";
	var t=o+r+s;
	t=t.replace(/:/g,"\\:");
	return t
}

halcyonardency

2.7	5km N of Brawley, California	2012-08-26 14:47:18	33.026°N	115.538°W	10.9
3.1	5km WNW of Brawley, California	2012-08-26 14:46:11	32.996°N	115.591°W	12.5
2.5	2km SW of Brawley, California	2012-08-26 14:45:25	32.967°N	115.551°W	13.1
2.9	4km NNW of Brawley, California	2012-08-26 14:42:51	33.022°N	115.541°W	11.5
2.5	4km ENE of Westmorland, California	2012-08-26 14:37:49	33.051°N	115.577°W	0.0
2.7	5km N of Brawley, California	2012-08-26 14:34:48	33.027°N	115.532°W	11.8
2.5	4km NW of Brawley, California	2012-08-26 14:30:54	33.005°N	115.565°W	12.4
3.8	6km N of Brawley, California	2012-08-26 14:26:39	33.038°N	115.527°W	12.4
3.6	4km SE of Westmorland, California	2012-08-26 14:23:23	33.005°N	115.591°W	14.3
3.6	6km W of Brawley, California	2012-08-26 14:23:10	32.973°N	115.599°W	8.5

halcyonardency

RewriteEngine On
RewriteBase /foo/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /foo/file.php [L]

halcyonardency

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                     wr01.chnd1.xxx.xxxx -    0 |  351 |  351 |    0 |    0 |    0 |    0 |
|            ip70-171-199-1.tc.ph.cox.net -   42 |  131 |   76 |    6 |   10 |   34 |    7 |
|________________________________________________|______|______|______|______|______|______|

halcyonardency

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                     wr01.chnd1.xxx.xxxx -    0 |  162 |  162 |    0 |    0 |    0 |    0 |
|                               10.39.0.1 -   19 |   92 |   75 |    0 |   13 |   35 |    6 |
|                            172.21.0.116 -   17 |   96 |   80 |    6 |   13 |   39 |   10 |
|                            70.169.73.90 -   20 |   91 |   73 |    0 |   19 |   49 |   14 |
|          chnddsrj01-ae2.0.rd.ph.cox.net -   18 |   95 |   78 |    0 |   15 |   47 |    7 |
|                              68.1.1.121 -   25 |   83 |   63 |    0 |   57 |   98 |   51 |

halcyonardency

The Chromecast has some challenges when compared to a simple RasberryPI/Cubieboard setup. 

With the army of developer resources Google has at it's disposal, it's clear Google didn't allocate any effort into some simple security measures.  Any wireless configuration beyond perhaps "default" router settings simply won't work with this device.

Here are things I found to be a bit frustrating, lacking, or outright insecure:

1. Requires publicly broadcasting SSID
2. Doesn't allow for SSID pinning to preferred AP-mac addresses
3. Requires AP isolation turned off
4. Broadcasts it's own non-secured configuration network when it cannot reach the intended AP

halcyonardency

Sep 10 14:55:35 SOMEHOST collectd[20478]: -1 Type `three/gauge' isn't defined.