Skip to main content

Posts

Showing posts from 2014

qfabric 巨大的失敗

https://code.facebook.com/posts/360346274145943/introducing-data-center-fabric-the-next-generation-facebook-data-center-network/ 平台( platform)是只能暗地來的,  對照那時的"ONE"口號, 一副就是要把客戶綁死在自家 的架構, 是沒人要買單的  綁在一家偉大的3 stage CLOS 晶片沒人想跟 , 竟然橫空出了Spine-leaf架構,連TRILL的的 戰爭的不太提了,  IS-IS想靠2/3層整合再壯大的想法要等等 不過 , facebook這例和google 的B4/ Andromeda 一樣, 不是一般人玩得起的

SDN 2.0

https://www.sdncentral.com/news/scott-shenker-preaches-revised-sdn-sdnv2/2014/10/ 也是時候了,  SDN 只和data center打轉有點無聊了(真的好像只有少少幾家有需求-在台灣?),  Telco+NFV才有的玩 不過, 對黑手來說, 終極挑戰來了, 不只是特定專業技能, 更是底層的基本功,還有各領域的domain know-how

SDN - from ipspace 快下載來讀

http://blog.ipspace.net/2014/09/just-published-sdn-and-openflow-hype.html 這裡的大多文章都在Ivan 的blog登過, 不過 , 這合集相當有系統的呈現  SDN 的現況 另外, 有一個Openflow 的定義一直反覆被提起,  就是 OF就只是控制層與轉送層 的溝通協議 , 有了新工具,  但已被驗證三十年的網路架構問題 , 不必然會能迎刃 而解

from Neil Gainman

I watched my peers , and my friends, and the ones who were older than me and watch how miserable  some of them were: I'd listen to them telling me that they couldn't envisage a world where they  did what they had always wanted to do any more because now they had to earn a certain amount every month just to keep where they were. They  couldn't go and do the things that mattered, and  that they had really wanted to do ; and that seemed  as a big tragedy as any problem of failure.

網路黑手的技能投資

這麼多年技術來來去去 生生死死 老賊如果把時間浪擲在只能活幾年的技術 無疑是非常不划算的( 我說的就是你 "ATM" "IBM" !!!) 未來還是當黑手的命 也是自己選的 不過 能做自己喜歡的 毋寧是幸福的 我不喜警察抓小偷的遊戲,  但又有偷窺狂 想看看別人的life 跑龍套的 也該下戲了 anyway, road builder 依然是我想做的 回到原點 要投注心力在能活很久 又能累積的技能 (1) Linux - openstack /opendaylight /docker/...... (2) python (3) TCP - 太太深奧了 (4) HTTP ........

big data approach on security

Network Security Through Data Analysis: Building Situational Awareness Data-Driven Security: Analysis, Visualization and Dashboards Applied Network Security Monitoring: Collection, Detection, and Analysis example : Facebook ThreatData 終究, 威脅總是能繞過防護進入內網, 不過, 至少不能完全不設防 ,  入侵總是會留下線索, 只是, 是哪個人有哪種工具可以快速的看見

努力上樓 : Application Performance on the Network

是要更努力上樓 http://apmblog.compuware.com/2014/06/10/understanding-application-performance-on-the-network-part-i-a-foundation-for-network-triage/ http://apmblog.compuware.com/2014/06/19/understanding-application-performance-on-the-network-bandwidth-and-congestion/ http://apmblog.compuware.com/2014/06/26/understanding-application-performance-on-the-network-tcp-slow-start/ http://apmblog.compuware.com/2014/07/03/understanding-application-performance-on-the-network-packet-loss/ http://apmblog.compuware.com/2014/07/10/understanding-application-performance-on-the-network-processing-delays/ http://apmblog.compuware.com/2014/07/24/understanding-application-performance-on-the-network-the-nagle-algorithm/ http://apmblog.compuware.com/2014/08/12/understanding-application-performance-network-part-tcp-window-size/ http://apmblog.compuware.com/2014/08/21/understanding-application-performance-on-the-network-chattiness-application-windowing/

很有趣, FW簡史

http://www.networkworld.com/article/2452691/security0/the-firewall-questions-abound-about-its-future-role-in-cloud-mobile-and-sdn-environments.html#jump Why proxy failed? And stateful won? It reminds me Why MPLS(or IP) won? And ATM failed Why cell based MPLS failed? and frame based won? Why L2 <*> ? And L3 <*> ................................................

網路黑手的困境

http://www.businessinsider.com/microsofts-ceo-email-2014-7 起源自2008年, 開始對網路這事業感到迷惘,  先是對跨網路技術領域的難度 感到迷惘, 再是對發展方向感到不知所措 對MS,我想很多人有很多想法, 面對各類前所未有的競爭,  他們的變革想法 也許能提供一些參考 Anyway , 現在是不興奮也不沮喪,  但很想繼續看下去, 有機會也想跑跑龍套

Insightful!

the network vendor now needs to bring a very different set of skills and solutions to the table. 但那是? http://pedrormarques.wordpress.com/2014/07/04/the-crux-of-the-matter/

beyond 500k internet routing table

from http://bgp.potaroo.net/

Lessons learned (3) - Latency is speed independent

雖然是101的等級,  還是很常忘記 SF<-> NY bandwidth     latency 40Gbps          20ms 400Gbps        20ms 100Mbps       20ms http://www.o3bnetworks.com/media/45606/o3b_latency_mobile%20backhaul_130417.pdf http://www.itu.int/ITU-D/asp/CMS/Events/2009/PacMinForum/doc/Theme-2_O3b_Latency_White_Paper.pdf

Middlebox

http://en.wikipedia.org/wiki/Middlebox 老狗就是忘不了會的把戲,  或自己深愛的遊戲 J的怪招FBF對付了這個議題好久了,  該到下個階段了 上層的服務各個虛擬化,  一下可以起好多個,  還會跑來跑去, 網路不快點跟著跑是不行的 Middlebox的更加難搞之處在於, "stateful" ,  這個需求讓網路更難應付 不是放了Middlebox, 問題就解了,  重點在於網路如何將"合適" 須被處理的 流量送至Middlebox 越來越有趣了

如果你只能讀一本web security的書

應該是這本了, 又開了眼界了, 有技術書是這麼寫的, 沒有針對這題目有絕對的自信是不能寫出這本書的 The Tangled Web: A Guide to Securing Modern Web Applications 不過, 以下的補充了更多的細節 The Web Application Hacker's Handbook: Finding and Exploiting Security Flaws Web Application Defender's Cookbook: Battling Hackers and Protecting Users The Browser Hacker's Handbook

更進階的WAF, from stands still to moving target

http://www.shapesecurity.com/

google的大反攻來了

http://googlecloudplatform.blogspot.tw/ 要找個時間試一下 http://googlecloudplatform.blogspot.tw/2014/04/enter-andromeda-zone-google-cloud-platforms-latest-networking-stack.html https://cloud.google.com/events/google-cloud-platform-live/ 更別說可怕的andromeda

真敢說

http://pedrormarques.wordpress.com/2014/02/26/the-next-fashion/ " By now just about everyone has realized that OpenFlow is just vaporware. Technically, there was never any content behind the hype. The arguments used to promote OpenFlows revolutionary properties where simply the ignorance of all previous technologies that used the exact same design ideas from  SS7  to  PBB-TE ."

未來的運營商

Google, Microsoft Challenge Service Providers 原來看似不是競爭對手的Google, Apple, Amazon.., 都陸續打起來了,  未來Google/Microsoft也是運營商的對手吧吧, 除了在地化的優勢, 我實在看不出其他的優勢, 全自動/智能的顯著優勢真是想到就可怕 想複製他們的建置經驗嗎? 我想還是聽聽就好, 這些建置cloud networking platform的人, 是真能從零到設計出一台先進的網路設備加網管平台

技術取得與遺失史

Cray/UNIX Firewall/Internet/Mosiac/NCSA/Ether Switching/VLAN/RMON/FDDI/2.4k modem/Codex/Telebit/Xylogics/ SunOS/Solaris/IRIX/AIX dial & lease line& X.25&FR(FRAD)& TDM(DCS/MUX) AIX/T3/C/C++/JAVA IBM/RSRB/STUN/DSLW/Mainfame/400/Token Ring RIP/IGRP/EIGRP/Catalyst/OSPF/CCIE ATM/IISP/PNNI/UNI3.1&4 BRAS/DSL/SDH/WDM MPLS/VPN/TE/FRR/BGP/Multicast/Qos/JNCIP Telecom/IMS/Voice P2MP/MOD/Metro Ethernet Mobility/1588/PGW/offload HTTP/LB/Caching/Video/ADC/APM/CDN Virtualization/Cloud/AWS Security/Malware/APT/Botnet/DDOS

還是覺得J的方案才漂亮

http://pedrormarques.wordpress.com/ 但是LDP L2VPN 的前車之鑑.... key takeaways "But classifying flows is a function that must be implemented as distributed as possible in any system that is designed to do anything more than be an educational tool." " It is encouraging that a few years into the OpenFlow meme the majority of the people that initially ignored “networking 101″ have managed to re-discover it. Hopefully in a couple more years we can collectively move on." "Back to networking: In a CLOS fabric design there is no aggregation layer. That is the mission of the OpenContrail vrouter. Provide the ability to  route  traffic between networks with the necessary levels of policy control, in a distributed way."

非常到位

不要为了SDN而SDN – Google的SDN和你没关系 一兩個Hop搞openflow也許 OK吧, 再大的, 再說吧 SDN要搞的是中央嚴密管控,  如連流進網路的是什麼都不想管 實在不需搞這麼大