<?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>The life, is too crazy</title>
	<atom:link href="https://blog.ychsiao.org/feed" rel="self" type="application/rss+xml" />
	<link>https://blog.ychsiao.org</link>
	<description>Yuan-Chung Hsiao&#039;s technical note and murmuring</description>
	<lastBuildDate>Tue, 16 Jul 2019 16:49:27 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.7.2</generator>
	<item>
		<title>notion.so</title>
		<link>https://blog.ychsiao.org/notion-so.html?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=notion-so</link>
					<comments>https://blog.ychsiao.org/notion-so.html#respond</comments>
		
		<dc:creator><![CDATA[Yuan-Chung Hsiao]]></dc:creator>
		<pubDate>Tue, 16 Jul 2019 16:05:34 +0000</pubDate>
				<category><![CDATA[Life]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[Work]]></category>
		<guid isPermaLink="false">https://blog.ychsiao.org/?p=1242</guid>

					<description><![CDATA[總算找到理由拔掉evernote，點我加入notion XD https://www.notion.so/]]></description>
		
					<wfw:commentRss>https://blog.ychsiao.org/notion-so.html/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>vCenter 5.1 upgrade step and issue</title>
		<link>https://blog.ychsiao.org/vcenter-5-1-upgrade-step-and-issue.html?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=vcenter-5-1-upgrade-step-and-issue</link>
					<comments>https://blog.ychsiao.org/vcenter-5-1-upgrade-step-and-issue.html#respond</comments>
		
		<dc:creator><![CDATA[Yuan-Chung Hsiao]]></dc:creator>
		<pubDate>Sun, 16 Sep 2012 15:22:03 +0000</pubDate>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[5.1]]></category>
		<category><![CDATA[Single Sign On]]></category>
		<category><![CDATA[vcenter]]></category>
		<category><![CDATA[vmware]]></category>
		<guid isPermaLink="false">https://blog.ychsiao.org/?p=740</guid>

					<description><![CDATA[安裝vCenter 5.1的步驟為: vCenter Single Sign On vCenter Inventory Service vCenter vSphere Web Client 在安裝Single Sign On時候會出現Error 29155.Identity source discovery error ，根據官方文件KB2034374，是無解的XD。我的做法是，把vCenter以外的軟體都先移除掉就可以了。 &#160; 接著再裝vCenter Server時候會卡在 vCenter Server administrator recognized by vCenter Single Sign On. 然後你輸入什麼都不對，總是出現 Wrong Input &#8211; either a command line argument is wrong, a file cannot be found or the spec file doesn&#8217;t contain the [&#8230;]]]></description>
		
					<wfw:commentRss>https://blog.ychsiao.org/vcenter-5-1-upgrade-step-and-issue.html/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Amazon VPC介紹與建置-進階路由設定與結語</title>
		<link>https://blog.ychsiao.org/amazon-vpc%e4%bb%8b%e7%b4%b9%e8%88%87%e5%bb%ba%e7%bd%ae-%e9%80%b2%e9%9a%8e%e8%b7%af%e7%94%b1%e8%a8%ad%e5%ae%9a%e8%88%87%e7%b5%90%e8%aa%9e.html?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=amazon-vpc%25e4%25bb%258b%25e7%25b4%25b9%25e8%2588%2587%25e5%25bb%25ba%25e7%25bd%25ae-%25e9%2580%25b2%25e9%259a%258e%25e8%25b7%25af%25e7%2594%25b1%25e8%25a8%25ad%25e5%25ae%259a%25e8%2588%2587%25e7%25b5%2590%25e8%25aa%259e</link>
					<comments>https://blog.ychsiao.org/amazon-vpc%e4%bb%8b%e7%b4%b9%e8%88%87%e5%bb%ba%e7%bd%ae-%e9%80%b2%e9%9a%8e%e8%b7%af%e7%94%b1%e8%a8%ad%e5%ae%9a%e8%88%87%e7%b5%90%e8%aa%9e.html#respond</comments>
		
		<dc:creator><![CDATA[Yuan-Chung Hsiao]]></dc:creator>
		<pubDate>Tue, 07 Feb 2012 10:12:20 +0000</pubDate>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[Work]]></category>
		<category><![CDATA[amazon]]></category>
		<category><![CDATA[aws]]></category>
		<category><![CDATA[cloud]]></category>
		<category><![CDATA[juniper]]></category>
		<category><![CDATA[vpc]]></category>
		<guid isPermaLink="false">https://blog.ychsiao.org/?p=695</guid>

					<description><![CDATA[機器建好了，接下來你應該會想要從內部連入管理啦，但會發現其實除了Public Subnet那個EIP能連入，Private Subnet你會連不上。這邊需要把AWS的BGP路由redistribution。 Screen OS設定Redistrbution給OSPF: set vrouter &#8220;trust-vr&#8221; set access-list 5 set access-list 5 permit ip 172.16.2.0/23 10 set route-map name &#8220;bgpredist&#8221; permit 10 set match ip 5 set protocol ospf set redistribute route-map &#8220;bgpredist&#8221; protocol bgp exit 最後你就可以在你的Router上看到路由啦。 &#160; 也可以測試一下routing與latency &#160; 結語 以上是VPC的應用，建議在接觸時候還是要懂一些網路路由協定與VPN協定，會比較好上手。依你的需求可以在不同Region建立不同VPC，或是同一個Region建立不同VPC都可以。最後還是要考慮到latency，如果慢到一種程度有些服務並不適合放上去，燒錢也沒意義。在測試的期間，在遙遠的EU與US-East開機器起來燒，事後發現還蠻痛的XD。 成本部分，每個VPC建起來後，每小時是$0.05米金，在任何的Region都是相同價錢。]]></description>
		
					<wfw:commentRss>https://blog.ychsiao.org/amazon-vpc%e4%bb%8b%e7%b4%b9%e8%88%87%e5%bb%ba%e7%bd%ae-%e9%80%b2%e9%9a%8e%e8%b7%af%e7%94%b1%e8%a8%ad%e5%ae%9a%e8%88%87%e7%b5%90%e8%aa%9e.html/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Amazon VPC介紹與建置-EC2建置</title>
		<link>https://blog.ychsiao.org/amazon-vpc%e4%bb%8b%e7%b4%b9%e8%88%87%e5%bb%ba%e7%bd%ae-ec2%e5%bb%ba%e7%bd%ae.html?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=amazon-vpc%25e4%25bb%258b%25e7%25b4%25b9%25e8%2588%2587%25e5%25bb%25ba%25e7%25bd%25ae-ec2%25e5%25bb%25ba%25e7%25bd%25ae</link>
					<comments>https://blog.ychsiao.org/amazon-vpc%e4%bb%8b%e7%b4%b9%e8%88%87%e5%bb%ba%e7%bd%ae-ec2%e5%bb%ba%e7%bd%ae.html#respond</comments>
		
		<dc:creator><![CDATA[Yuan-Chung Hsiao]]></dc:creator>
		<pubDate>Tue, 07 Feb 2012 10:11:27 +0000</pubDate>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[Work]]></category>
		<category><![CDATA[amazon]]></category>
		<category><![CDATA[aws]]></category>
		<category><![CDATA[cloud]]></category>
		<category><![CDATA[juniper]]></category>
		<category><![CDATA[vpc]]></category>
		<guid isPermaLink="false">https://blog.ychsiao.org/?p=693</guid>

					<description><![CDATA[在兩邊的VPN都建立起來後，接下來就是把EC2叫起來了，首先一樣要先設好Security Group，特別的是要指定這個Security Group在某個VPC上面喔。 你可以開一台Web(Public Subnet)與一台DB(Private Subnet)。寫這篇文章時候新介面改成這樣還真不習慣，平常都用API開習慣了。 開機器的時候要注意一下，VPC的Instance Type需從m1.large起跳，記得要選Lanuch into a VPC，這樣你才能選Subnet。當然別忘了選剛建好的Security Group。 儲存設定後，會給你確認一下，你要再檢查幾個比較重要的設定，不然機器開起來就要收錢啦。 這是另一台VPC的設定，注意看Lanuch into a VPC的介面是不一樣了 建立完成後，Public Subnet上的Web Server，需要一個EIP給他使用，否則外面是連不進來的(請看第一篇介紹)。一樣注意要把EIP選成VPC使用。 這邊可以針對Instance或是Network Interface來binding，請依你的需求囉。]]></description>
		
					<wfw:commentRss>https://blog.ychsiao.org/amazon-vpc%e4%bb%8b%e7%b4%b9%e8%88%87%e5%bb%ba%e7%bd%ae-ec2%e5%bb%ba%e7%bd%ae.html/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Amazon VPC介紹與建置-VPN網路設定</title>
		<link>https://blog.ychsiao.org/amazon-vpc%e4%bb%8b%e7%b4%b9%e8%88%87%e5%bb%ba%e7%bd%ae-vpn%e7%b6%b2%e8%b7%af%e8%a8%ad%e5%ae%9a.html?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=amazon-vpc%25e4%25bb%258b%25e7%25b4%25b9%25e8%2588%2587%25e5%25bb%25ba%25e7%25bd%25ae-vpn%25e7%25b6%25b2%25e8%25b7%25af%25e8%25a8%25ad%25e5%25ae%259a</link>
					<comments>https://blog.ychsiao.org/amazon-vpc%e4%bb%8b%e7%b4%b9%e8%88%87%e5%bb%ba%e7%bd%ae-vpn%e7%b6%b2%e8%b7%af%e8%a8%ad%e5%ae%9a.html#respond</comments>
		
		<dc:creator><![CDATA[Yuan-Chung Hsiao]]></dc:creator>
		<pubDate>Tue, 07 Feb 2012 10:11:17 +0000</pubDate>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[Work]]></category>
		<category><![CDATA[amazon]]></category>
		<category><![CDATA[aws]]></category>
		<category><![CDATA[cloud]]></category>
		<category><![CDATA[juniper]]></category>
		<category><![CDATA[vpc]]></category>
		<guid isPermaLink="false">https://blog.ychsiao.org/?p=690</guid>

					<description><![CDATA[VPC與硬體式VPN對接 VPC上設定好後，接下來就是設定自家的VPN設備，在這邊我們以Juniper SSG(Screen OS 6.2 or 6.3)做對接，Cisco的ISR有空再寫好了(誤)。有關VPN設備的基本概念就不講了，在下面設定還會有BGP的設定，不清楚就照貼(再誤)。Screen OS架構部分，需要先把Trust與Untrust的介面先切出來。我的設計習慣會是把Trust對內，Untrust對外。 接著拿出AWS提供的VPC範本，通常要做一些修改。AWS預設是把Trust Zone與AWS接起來的，對接介面是ethernet0/0，建立tunnel的介面名稱是tunnel.1與tunnel.2，會與你的環境有些差異，需要自行修改。 以下是VPC所提供的設定檔，紅字部分是需要注意的部分，至於prehare key就是AWS提供啦，不要亂動XD。 set ike p1-proposal ike-prop-vpn-51b81250-1 preshare group2 esp aes128 sha-1 second 28800 set ike gateway gw-vpn-51b81250-1 address 27.x.x.x id 27.x.x.x main outgoing-interface ethernet0/0 preshare &#8220;blahblah&#8221; proposal ike-prop-vpn-51b81250-1 set ike p2-proposal ipsec-prop-vpn-51b81250-1 group2 esp aes128 sha-1 second 3600 set ike gateway gw-vpn-51b81250-1 dpd-liveness interval 10 set vpn IPSEC-vpn-51b81250-1 [&#8230;]]]></description>
		
					<wfw:commentRss>https://blog.ychsiao.org/amazon-vpc%e4%bb%8b%e7%b4%b9%e8%88%87%e5%bb%ba%e7%bd%ae-vpn%e7%b6%b2%e8%b7%af%e8%a8%ad%e5%ae%9a.html/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Amazon VPC介紹與建置-VPC介面設定</title>
		<link>https://blog.ychsiao.org/amazon-vpc%e4%bb%8b%e7%b4%b9%e8%88%87%e5%bb%ba%e7%bd%ae-vpc%e4%bb%8b%e9%9d%a2%e8%a8%ad%e5%ae%9a.html?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=amazon-vpc%25e4%25bb%258b%25e7%25b4%25b9%25e8%2588%2587%25e5%25bb%25ba%25e7%25bd%25ae-vpc%25e4%25bb%258b%25e9%259d%25a2%25e8%25a8%25ad%25e5%25ae%259a</link>
					<comments>https://blog.ychsiao.org/amazon-vpc%e4%bb%8b%e7%b4%b9%e8%88%87%e5%bb%ba%e7%bd%ae-vpc%e4%bb%8b%e9%9d%a2%e8%a8%ad%e5%ae%9a.html#respond</comments>
		
		<dc:creator><![CDATA[Yuan-Chung Hsiao]]></dc:creator>
		<pubDate>Tue, 07 Feb 2012 10:11:16 +0000</pubDate>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[Work]]></category>
		<category><![CDATA[amazon]]></category>
		<category><![CDATA[aws]]></category>
		<category><![CDATA[cloud]]></category>
		<category><![CDATA[juniper]]></category>
		<category><![CDATA[vpc]]></category>
		<guid isPermaLink="false">https://blog.ychsiao.org/?p=688</guid>

					<description><![CDATA[這是VPC的畫面，點下Get started creating a VPC。 選要的環境，依前一篇的需求，我們選第三個。 輸入IPSec VPN的位置，我的IP是127.0.0.1，不要亂打啊。 接下來是你的VPC網路環境設定。這邊需要做調整的是: IP CIDR block 我這邊用172.16.2.0/23。 要用哪個網段來當VPC，注意，不能與目前內部有使用到的網段重複，請與網管負責人確認一下。 Public Subnet 我這邊用172.16.2.0/24。 對外VPC的網段。 Private Subnet 我這邊用172.16.3.0/24。 對內的VPC網段。 通通設定好後就給他按下Create VPC，建立速度不一定= =。 建立完成後，在VPC Dashboard就會出現一些資訊，事實上會先下載設定檔啦，不過忘記抓圖，下一張再來處理XD。這張圖可以看到目前VPC連線是Down的(廢話)。 如果忘記下載設檔，可以點VPC Connections/Download Configuration，來下載範本。 我這邊測試的設備是Juniper SSG系列。 最後，建議先看一下Subnet，要記一下有關於Public/Private Subnet所對映到的Subnet ID/Availability Zone，等下EC2建機器的時候會用到。]]></description>
		
					<wfw:commentRss>https://blog.ychsiao.org/amazon-vpc%e4%bb%8b%e7%b4%b9%e8%88%87%e5%bb%ba%e7%bd%ae-vpc%e4%bb%8b%e9%9d%a2%e8%a8%ad%e5%ae%9a.html/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
