Unless you have HIPAA, PHIPA, SOX, CISSP, work for DoD, or just a company who values privacy. Then you get a Blackberry and download the right apps. There should be no such thing as an iphone or droid at a company who has security requirements. Please tell me I’m wrong with citations of how an iphone or droid is fully compliant with FIPS140-2 and is listed on the appropriate NIST site so I can show my attorney. Then I will snuggle up in my happy google cloud or let my coworkers get all happy in their iphone cloud.

I do envy you people who are arguing about megapixels and screen size. Not becuase your petty arguments have merit, just because I want the happy ladder instead of the Escher staircase.

One side note- I still challenge anyone to show me an iphone app with a real business use for me that can’t be replicated by blackberry or droid. So far it doesn’t exist. I think these are all fairly equal platforms and just flavors, not fat vs carbs.

The combination of facebook owning your data, and you being excluded from that ownership/permissions editing should be something to ponder.

The argument with users should go like this – We block malware/adware. If Mapquest has recently changed partnerships and signed with someone who has a negative reputation, that does not give us a valid reason to stop using exisiting tools to block malware/adware. Write to mapquest or use Google maps, Bing maps, etc.

Mapquest hangs on Loading and just spins

I have a client who is having problems with Comcast and intermittent outages. We have both talked to comcast over the last few years to discuss the issue and come to no resolution or attempt at real troubleshooting. Tuesday a tech is finally coming out.

I will have pingdom stats this time to show how often the connection drops. Pingdom checks the firewall at the residence. It is possible for pingdom stats to be off in a few rare cases where the firewall is down. Currently that would occur because the power has been out or the hardware failed. Should give a pretty accurate show of Comcast uptime in a residence. I will update the stats if the hardware fails or power drops.

To troubleshoot the intermittent internet issue:

1. Ran pings from in the house to a bunch of addresses. In windows ping -t ping.mit.edu, fire up another command prompt, ping -t www.msu.edu, colorado.edu, etc. In linux just ping.
2. Swapped access points, copying config from ddwrt and moving to the other
3. New installation of DDWRT
4. Grounded cable splitters
5. Swapped cable splitters and coax
6. Called comcast, had them add a mac address for my newest cable modem. Seems on newer cheap ones you can’t copy the MAC. This guy was extremely helpful. Told me the Up link had some poor signal strength. At the time of the call. Only the cable modem was plugged in. This tells me there is a signal strength problem outside the house.
7. Tried with the Untangle UTM appliance inline and without.
None of these steps over a very long period of time has solved the issue, and now all hardware has been replaced.

Time will tell. And you will be able to monitor this locations performance as well as others on my Monitoring page very soon.

Be nice to the troubleshooting guy. I was nice to this one today and he was very very helpful. Crazy to have a native english speaker at 5 on a Sunday in the US. Maybe my comcast stock is worth holding on to. (disclaimer there… I own about $1000 worth of comcast stock. It pays pathetic dividends, I don’t recommend it.)

replace phone# with your 10 digit number

netsh ipsec static add policy description=”ossec block list”

netsh ipsec static add filter filterlist=”ossecfilter” srcaddr= 69.89.20.50 dstaddr=me protocol=tcp mirrored=yes

netsh ipsec static add rule policy=”ossec” filterlist=”ossecfilter” filteraction=block desc=”list of ips to block”

netsh ipsec static set policy assign=y

This blocks windowsnerd.com

Add another entry for slashdot. Ipsec doesn’t like having an empty entry so leave an addy in there to seed it for a delete in another step:

netsh ipsec static add filter filterlist=”ossecfilter” srcaddr= 216.34.181.45 dstaddr=me protocol=tcp mirrored=yes

Now if you open the ipsec MMC, you will see an applied ipsec policy, crack it open and you will see both entries for each IP.

Try going to windowsnerd.com, slashdot.com and another page. The first two will not work. All traffic has been blocked

Unblock -

netsh ipsec static delete filter filterlist=”ossecfilter” srcaddr= 69.89.20.50 dstaddr=me protocol=tcp mirrored=yes

Repeat – now you can block and unblock by running the static add and static delete command over and over. It will update the policy you created in the first step. Not quite as cool as adding to hosts.deny and firewall, but the same end result.

This example is for use on an application like OSSEC. If you desire, you can specify per port, IP addy, DNS name, whatever you want.