<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>okami.de</title>
	<atom:link href="http://www.okami.de/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.okami.de</link>
	<description></description>
	<lastBuildDate>Sun, 05 May 2013 13:53:43 +0000</lastBuildDate>
	<language>de-DE</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=401</generator>
		<item>
		<title>Kontakte, Kalender und Dateien synchronisieren &#8211; Android und Owncloud</title>
		<link>http://www.okami.de/2013/04/04/kontakte-kalender-und-dateien-synchronisieren-android-und-owncloud/</link>
		<comments>http://www.okami.de/2013/04/04/kontakte-kalender-und-dateien-synchronisieren-android-und-owncloud/#comments</comments>
		<pubDate>Thu, 04 Apr 2013 13:36:37 +0000</pubDate>
		<dc:creator>okami</dc:creator>
				<category><![CDATA[Howtos]]></category>
		<category><![CDATA[android]]></category>
		<category><![CDATA[Caldav]]></category>
		<category><![CDATA[Carddav]]></category>
		<category><![CDATA[Lotus Notes]]></category>
		<category><![CDATA[My Phone Explorer]]></category>
		<category><![CDATA[outlook]]></category>
		<category><![CDATA[Owncloud]]></category>
		<category><![CDATA[Synchronisation]]></category>
		<category><![CDATA[thunderbird]]></category>
		<category><![CDATA[Webdav]]></category>
		<category><![CDATA[WebDav Filemanager]]></category>

		<guid isPermaLink="false">http://www.okami.de/?p=1494</guid>
		<description><![CDATA[Jeder Smartphonebesitzer kennt das Problem: Er will eine simple Lösung um seine Daten(Kontakte, Kalender, Files) auf dem Handy, mit der Firma und der häuslichen Umgebung synchron halten zu können. Da in der Firma ein etwas...]]></description>
		<wfw:commentRss>http://www.okami.de/2013/04/04/kontakte-kalender-und-dateien-synchronisieren-android-und-owncloud/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>MyPhoneExplorer, Cyanogenmod 10.1 und ADB = Verbindungsprobleme via USB</title>
		<link>http://www.okami.de/2013/02/20/myphoneexplorer-cyanogenmod-10-1-und-adb-verbindungsprobleme-via-usb/</link>
		<comments>http://www.okami.de/2013/02/20/myphoneexplorer-cyanogenmod-10-1-und-adb-verbindungsprobleme-via-usb/#comments</comments>
		<pubDate>Wed, 20 Feb 2013 16:43:40 +0000</pubDate>
		<dc:creator>okami</dc:creator>
				<category><![CDATA[Howtos]]></category>
		<category><![CDATA[adb]]></category>
		<category><![CDATA[android]]></category>
		<category><![CDATA[Android 4.2.2]]></category>
		<category><![CDATA[Cyanogenmod]]></category>
		<category><![CDATA[cyanogenmod 10.1]]></category>
		<category><![CDATA[My Phone Explorer]]></category>
		<category><![CDATA[myphoneexplorer]]></category>

		<guid isPermaLink="false">http://www.okami.de/?p=1478</guid>
		<description><![CDATA[Mit dem Update auf Android 4.2.2, eines der letzten Nightlies von Cyanogenmod 10.1, kommt auch eine neues Sicherheitsfeature. Damit kann keine unautorisierte Verbindung über ADB mehr durchgeführt werden. Bei einem Verbindungsversuch kommt vorerst eine Abfrage, die am Smartphone bestätigt werden muss. Sonst kann keine Verbindung mehr hergestellt werden!]]></description>
		<wfw:commentRss>http://www.okami.de/2013/02/20/myphoneexplorer-cyanogenmod-10-1-und-adb-verbindungsprobleme-via-usb/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Howto NAT VPN Traffic on a Cisco ASA</title>
		<link>http://www.okami.de/2013/01/03/how-to-nat-vpn-traffic-on-a-cisco-asa/</link>
		<comments>http://www.okami.de/2013/01/03/how-to-nat-vpn-traffic-on-a-cisco-asa/#comments</comments>
		<pubDate>Thu, 03 Jan 2013 10:24:05 +0000</pubDate>
		<dc:creator>okami</dc:creator>
				<category><![CDATA[Netzwerk]]></category>
		<category><![CDATA[ASA]]></category>
		<category><![CDATA[cisco]]></category>
		<category><![CDATA[nat]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[site-to-site]]></category>
		<category><![CDATA[vpn]]></category>

		<guid isPermaLink="false">http://www.okami.de/?p=1434</guid>
		<description><![CDATA[Say you have to setup a Site-to-Site VPN to a third party who can't accept traffic from the subnet you have created on your internal network because your network overlaps with theirs, or as in my case, they just want one address coming over to their network. The answer is to NAT that VPN traffic using a non-overlapping IP address.]]></description>
		<wfw:commentRss>http://www.okami.de/2013/01/03/how-to-nat-vpn-traffic-on-a-cisco-asa/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Cisco ASA Firmware Update on Failover Cluster</title>
		<link>http://www.okami.de/2012/12/14/cisco-asa-firmware-update-im-failover-cluster/</link>
		<comments>http://www.okami.de/2012/12/14/cisco-asa-firmware-update-im-failover-cluster/#comments</comments>
		<pubDate>Fri, 14 Dec 2012 13:08:36 +0000</pubDate>
		<dc:creator>okami</dc:creator>
				<category><![CDATA[Netzwerk]]></category>
		<category><![CDATA[ASA]]></category>
		<category><![CDATA[asdm]]></category>
		<category><![CDATA[cisco]]></category>
		<category><![CDATA[failover]]></category>
		<category><![CDATA[ios]]></category>
		<category><![CDATA[redundanz]]></category>
		<category><![CDATA[upgrade]]></category>

		<guid isPermaLink="false">http://www.okami.de/?p=1343</guid>
		<description><![CDATA[First we need to copy the firmware update and the ASDM on the Units. Please note these are not synced unlike the configuration. With savings via ASDM once again on the active to the passive IP and then upload it via browser, alternatively via CLI and tftp:]]></description>
		<wfw:commentRss>http://www.okami.de/2012/12/14/cisco-asa-firmware-update-im-failover-cluster/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Cisco PIX/ASA Causes SMTP Banner Corruption</title>
		<link>http://www.okami.de/2012/12/03/cisco-pixasa-causes-smtp-banner-corruption/</link>
		<comments>http://www.okami.de/2012/12/03/cisco-pixasa-causes-smtp-banner-corruption/#comments</comments>
		<pubDate>Mon, 03 Dec 2012 07:40:15 +0000</pubDate>
		<dc:creator>okami</dc:creator>
				<category><![CDATA[Netzwerk]]></category>
		<category><![CDATA[ASA]]></category>
		<category><![CDATA[cisco]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[netzwerk]]></category>
		<category><![CDATA[SMTP]]></category>
		<category><![CDATA[Traffic Inspection]]></category>

		<guid isPermaLink="false">http://www.okami.de/?p=1311</guid>
		<description><![CDATA[Traffic inspection rules on a Cisco PIX or ASA firewall will sometimes cause the SMTP banner to appear corrupted. When testing access to your mail server trough AsA, you may notice that the SMTP banner looks like this:]]></description>
		<wfw:commentRss>http://www.okami.de/2012/12/03/cisco-pixasa-causes-smtp-banner-corruption/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
<!-- This Quick Cache file was built for (  www.okami.de/feed/ ) in 0.50048 seconds, on May 24th, 2013 at 2:08 am UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on May 24th, 2013 at 3:08 am UTC -->
<!-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
<!-- Quick Cache Is Fully Functional :-) ... A Quick Cache file was just served for (  www.okami.de/feed/ ) in 0.00020 seconds, on May 24th, 2013 at 2:34 am UTC. -->