nemo
/
hn-classics
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
hn-classics/_stories/2009/9819363.md

35 KiB
Raw Permalink Blame History

created_at title url author points story_text comment_text num_comments story_id story_title story_url parent_id created_at_i _tags objectID year
2015-07-02T15:06:52.000Z What went wrong: SCTP (2009) http://blog.ipspace.net/2009/08/what-went-wrong-sctp.html mariuz 48 44 1435849612
story
author_mariuz
story_9819363
9819363 2009

[Source](http://blog.ipspace.net/2009/08/what-went-wrong-sctp.html "Permalink to What went wrong: SCTP « ipSpace.net by @ioshints

")

What went wrong: SCTP « ipSpace.net by @ioshints

Your browser failed to load CSS style sheets. Your browser or web proxy might not support elliptic-curve TLS

ipSpace Logo

Building network automation solutions

6 week online course

Start now!

back to overview

Monday, August 31, 2009

What went wrong: SCTP

Someone really wants to hear my opinion on SCTP (RFC 4960); he’s added a “what about SCTP” comment to several Internet-related posts I wrote in the last weeks. So, here are my totally unqualified (I have no hands-on experience) thoughts about SCTP.

Let me reiterate: I’m taking a 30,000-foot perspective here and whatever I’m writing could be completely wrong. If that’s the case, please point out my mistakes in your comments.

From the distance, the protocol looks promising. It provides datagram (unreliable messages), reliable message (record) and stream transport. Even more important, each connection can run across multiple IP addresses on each endpoint, providing native support for scalable IP multihoming (where each multihomed host resides in multiple PA address blocks from various Service Providers).

Second-hand evidence points to the viability of SCTP: it’s used in complex real-life signaling applications (SS7-over-IP), it’s implemented in Cisco IOS and IOS uses it for a variety of its transport needs (including high-availability solutions and reliable export of Netflow data).

However, SCTP will not solve the current IP multihoming issues (unless we’ll experience a world-wide Internet crash first). Here are just a few non-technical reasons why (if you have links to more in-depth information, please add them in the comments):

  • It was designed by the wrong working group. SCTP was a byproduct of the SIGTRAN working group which was focused on transport of PSTN signaling over IP networks.
  • It was never properly promoted. The SIGTRAN working group solved their problem and moved on.
  • It’s not shipped with Windows, which is a major showstopper as most clients that would benefit from SCTP’s IP multihoming support run on Windows.
  • Although it’s bundled in recent Linux kernels, the support files are not included in out-of-the box Linux distributions. To get it on my Fedora 11 distribution, I had to install lksctp-tools.
  • You can get libraries, source code, kernel patches and even commercial implementations of SCTP for most operating systems, but in most cases you have to do some installation and integration work. This is a great option if you want to play with the protocol, but not if you want to deploy generic applications over it.
  • Since it’s rarely used, there’s no support for it in the networking equipment. You can’t even match SCTP by name with extended access lists in Cisco IOS (you have to use its numeric protocol number). Obviously you cannot perform matches on SCTP port numbers. Passing SCTP across a firewall is a nightmare, as there’s no stateful inspection of SCTP traffic.

However, by far the biggest showstopper to SCTP adoption is the lack of session layer in TCP/IP and the broken Socket API. If you want to use SCTP with the Socket API, you have to indicate the protocol to use in the socket call, which means that every application that would benefit from SCTP support must be changed, recompiled and tested. There is no way that you could take existing applications, add SCTP support in the operating system and have a better-performing Internet as the result.

By Ivan Pepelnjak

Related posts by categories

15 comments:

Olivier Cahagne31 August, 2009 11:50

Note Firefox/Mozilla has some on-going activity to revive proper SCTP support, see https://bugzilla.mozilla.org/show_bug.cgi?id=486199

ReplyDelete

kajtzu31 August, 2009 20:57

I realize this is a blog that usually caters to vendor C stuff but Vendor J has SCTP stateful inspection in their ISG products.... :-)

ReplyDelete

Ivan Pepelnjak31 August, 2009 21:57

That's great news ... and an excellent topic for a follow-up post ;)

ReplyDelete

Ivan Pepelnjak31 August, 2009 21:57

That's great news ... and an excellent topic for a follow-up post ;)

ReplyDelete

Ivan Pepelnjak31 August, 2009 22:00

Well, it's more like the author of this blog has a severe case of the non-C-blindness. I'm very familiar with what vendor C does but not what vendors J,H,N ... have to offer. However, this is my personal blog and thus does not have to be exclusively C-focused. Let's widen the perspective ;)

I'm most grateful for your additions, please keep them coming. A link to the relevant section of the product documentation would also be most appreciated.

ReplyDelete

kajtzu10 September, 2009 14:03

Stateful inspection in screenos 6.1.0, release notes http://www.juniper.net/techpubs/software/screenos/screenos6.1.0/rn_610_r2.pdf

SCTP protocol filtering in screenos 6.3.0 (very new) and only on the "high end" platforms, release notes http://www.juniper.net/techpubs/software/screenos/screenos6.3.0/630_rn_r1.pdf

SCTP ALG (one command) page 54 in http://www.juniper.net/techpubs/software/screenos/screenos6.3.0/630_ipv4_cli.pdf

Chapter 91 (high end platforms) how to filter it. Mostly geared towards telco packet core (signaling) protocols though.

HTH :)

ReplyDelete

Ivan Pepelnjak10 September, 2009 14:06

That's great. Thanks 8-)

ReplyDelete

Anonymous25 August, 2012 15:34

Yes Yes deleightfull backyard theorists.

As stated no working experience with it.

Now that SIP 3/4 G, wifi and other technologies have evolved to take advantage of such a protocall which was knowledge at the time of writing i might add.

You looked at the layers but failed to recognise why TCP and UDP techniques had been a key player.

A look at wiki or protocall comparisons once again would have shown you the pro's and con's.

But basicly we get tech chaff from such blogs wasting our time on google with such empty banter.

IBM and MS proved more usefull thank you for wasting another portion of my life and bandwidth that i will never get back.

(CENSORED)

ReplyDelete

Aris Paraskevopoulos27 June, 2013 00:28

Greeting! Well I am new to protocols and all network stuff but I really like them and want to learn as many things as I can. My opinion is that SCTP must mature before they use it as best option. It is really a promising protocol. 4G networks fully support it. So I think it is like IPv4 and IPv6. There is no need to use only IPv6 when you can use IPv4 with an IPv6 prefix. It will get years to upgrade all world's servers, routers and applications IP versions from 4 to 6, they just let it be, and it is not efficient or profitable at all to change that. So that's the way they move around SCTP too. They will not change a thing allready in use, optimized by TCP let's say in today's standards, but they will emerge new things into old ones using this awesome protocol!

ReplyDelete

Lennie23 July, 2013 15:50

You'll laugh when you read that WebRTC Datachannels uses SCTP over DTLS over UDP. :-)

ReplyDelete

Ivan Pepelnjak24 July, 2013 05:53

RFC 1925 section 2.6a ;)

ReplyDelete

Anonymous19 September, 2013 00:50

I've seen mention of a transparent TCP-to-SCTP shim that would allow unmodified applications to use SCTP.
http://www.eecis.udel.edu/~amer/PEL/poc/pdf/EuroBSDCon2007-bickhart-SCTP-Shim-layer.pdf

Variations of that ought to be possible for various OS's.

ReplyDelete

Michael14 October, 2013 13:21

I couldn't agree more with what you say about the broken socket API - please join the effort that's trying to fix that: https://sites.google.com/site/transportprotocolservices/

ReplyDelete

Michael14 October, 2013 14:38

About the shim by Ryan Bickhart et al, this gives you only the multihoming benefit transparently. You can do more transparently, cf. http://heim.ifi.uio.no/~michawe/research/publications/globecom2011.pdf , but for full benefit you really want to change the API, try using SCTP, and fall back to TCP using e.g. Happy Eyeballs: http://www.ipjforum.org/?p=378

ReplyDelete

Akhilesh04 April, 2014 15:11

I think the time has come and move on to multihoming transport protocols. We would have multihomed access network these days and would definately would help. Could you imagine a laptop with wireless, ethernet and 4G/3G dongle will improve lot customer experience. Even that would be applicable to mobility where we are talking about different access roaming.

ReplyDelete

Add comment

Load more...

You don't have to log in to post a comment, but please do provide your real name/URL. Anonymous comments might get deleted.

[][86][

[ Newer Post ][87] Home [ Older Post ][88]

[Sidebar][89] [ ][86]

Follow us

[ ][90] [ ][91] [ ][92]

SUBSCRIBE TO SDN MAILING LIST

[More information][92]

POPULAR POSTS

  • [How to Become a Better Networking Engineer][93]
  • [Revisited: The Need for Stretched VLANs][94]
  • [Using EVPN in Very Small Data Center Fabrics][95]
  • [BGP in EVPN-Based Data Center Fabrics][96]
  • [Brief Recap: Tech Field Day at Cisco Live Europe 2018][97]
  • [EVPN Is More than VPLS on Steroids][98]
  • [Worth Reading: Whiteboxes for Everyone][99]
  • [Use YANG Data Models to Configure Network Device with Ansible][100]
  • [How Useful Is Microsegmentation?][101]
  • [Automation Win: MPLS/VPN Service Deployment][102] see more

TAGS

  • [Data Center (547)][103]
  • [SDN (315)][104]
  • [virtualization (254)][105]
  • [IPv6 (248)][106]
  • [security (215)][107]
  • [BGP (197)][108]
  • [switching (159)][109]
  • [Fabric (155)][110]
  • [IP routing (154)][111]
  • [OpenFlow (149)][112]
  • [Automation (131)][113]
  • [Overlay networks (130)][114]
  • [WAN (124)][115]
  • [Design (123)][116]
  • [OSPF (113)][117]
  • [MPLS VPN (105)][118]
  • [network management (103)][119]
  • [cloud (102)][120]
  • [firewalls (95)][121]
  • [MPLS (87)][122]
  • [EEM (78)][123]
  • Internet (76)
  • [load balancing (71)][124]
  • [QoS (67)][125]
  • [bridging (66)][126]
  • [command line interface (65)][127]
  • [DMVPN (62)][128]
  • [LAN (61)][129]
  • [VXLAN (49)][130]
  • [DHCP (44)][131]
  • [configuration (40)][132]
  • [Service Providers (38)][133]
  • [web (37)][134]
  • [access control (36)][135]
  • [http (33)][136]
  • [traffic engineering (33)][137]
  • [EIGRP (32)][138]
  • [SAN (31)][139]
  • [vMotion (29)][140]
  • [NAT (28)][141]
  • [PPP (28)][142]
  • [Scalability (28)][143]
  • [ipsec (27)][144]
  • [DNS (25)][145]
  • [FCoE (25)][146]
  • [Link aggregation (22)][147]
  • [VPN (22)][148]
  • [IS-IS (19)][149]
  • [CEF (18)][150]
  • [ARP (14)][151] see more

BLOG ARCHIVE

  • [ 2018 (39) ][152]
    • [ February 2018 (19) ][153]
    • [ January 2018 (20) ][154]
  • [ 2017 (236) ][155]
    • [ December 2017 (21) ][156]
    • [ November 2017 (23) ][157]
    • [ October 2017 (24) ][158]
    • [ September 2017 (22) ][159]
    • [ August 2017 (16) ][160]
    • [ July 2017 (10) ][161]
    • [ June 2017 (18) ][162]
    • [ May 2017 (21) ][163]
    • [ April 2017 (19) ][164]
    • [ March 2017 (24) ][165]
    • [ February 2017 (20) ][166]
    • [ January 2017 (18) ][167]
  • [ 2016 (235) ][168]
    • [ December 2016 (19) ][169]
    • [ November 2016 (22) ][170]
    • [ October 2016 (22) ][171]
    • [ September 2016 (23) ][172]
    • [ August 2016 (17) ][173]
    • [ July 2016 (12) ][174]
    • [ June 2016 (18) ][175]
    • [ May 2016 (21) ][176]
    • [ April 2016 (18) ][177]
    • [ March 2016 (22) ][178]
    • [ February 2016 (24) ][179]
    • [ January 2016 (17) ][180]
  • [ 2015 (251) ][181]
    • [ December 2015 (13) ][182]
    • [ November 2015 (20) ][183]
    • [ October 2015 (22) ][184]
    • [ September 2015 (20) ][185]
    • [ August 2015 (20) ][186]
    • [ July 2015 (19) ][187]
    • [ June 2015 (24) ][188]
    • [ May 2015 (22) ][189]
    • [ April 2015 (23) ][190]
    • [ March 2015 (23) ][191]
    • [ February 2015 (24) ][192]
    • [ January 2015 (21) ][193]
  • [ 2014 (263) ][194]
    • [ December 2014 (15) ][195]
    • [ November 2014 (24) ][196]
    • [ October 2014 (26) ][197]
    • [ September 2014 (26) ][198]
    • [ August 2014 (20) ][199]
    • [ July 2014 (16) ][200]
    • [ June 2014 (26) ][201]
    • [ May 2014 (21) ][202]
    • [ April 2014 (22) ][203]
    • [ March 2014 (23) ][204]
    • [ February 2014 (21) ][205]
    • [ January 2014 (23) ][206]
  • [ 2013 (270) ][207]
    • [ December 2013 (16) ][208]
    • [ November 2013 (20) ][209]
    • [ October 2013 (24) ][210]
    • [ September 2013 (25) ][211]
    • [ August 2013 (25) ][212]
    • [ July 2013 (22) ][213]
    • [ June 2013 (21) ][214]
    • [ May 2013 (26) ][215]
    • [ April 2013 (25) ][216]
    • [ March 2013 (22) ][217]
    • [ February 2013 (21) ][218]
    • [ January 2013 (23) ][219]
  • [ 2012 (218) ][220]
    • [ December 2012 (12) ][221]
    • [ November 2012 (19) ][222]
    • [ October 2012 (22) ][223]
    • [ September 2012 (13) ][224]
    • [ August 2012 (20) ][225]
    • [ July 2012 (17) ][226]
    • [ June 2012 (11) ][227]
    • [ May 2012 (15) ][228]
    • [ April 2012 (20) ][229]
    • [ March 2012 (22) ][230]
    • [ February 2012 (22) ][231]
    • [ January 2012 (25) ][232]
  • [ 2011 (290) ][233]
    • [ December 2011 (20) ][234]
    • [ November 2011 (27) ][235]
    • [ October 2011 (26) ][236]
    • [ September 2011 (25) ][237]
    • [ August 2011 (24) ][238]
    • [ July 2011 (14) ][239]
    • [ June 2011 (25) ][240]
    • [ May 2011 (26) ][241]
    • [ April 2011 (25) ][242]
    • [ March 2011 (28) ][243]
    • [ February 2011 (24) ][244]
    • [ January 2011 (26) ][245]
  • [ 2010 (303) ][246]
    • [ December 2010 (32) ][247]
    • [ November 2010 (24) ][248]
    • [ October 2010 (27) ][249]
    • [ September 2010 (27) ][250]
    • [ August 2010 (27) ][251]
    • [ July 2010 (28) ][252]
    • [ June 2010 (32) ][253]
    • [ May 2010 (25) ][254]
    • [ April 2010 (25) ][255]
    • [ March 2010 (29) ][256]
    • [ February 2010 (13) ][257]
    • [ January 2010 (14) ][258]
  • [ 2009 (240) ][259]
    • [ December 2009 (16) ][260]
    • [ November 2009 (22) ][261]
    • [ October 2009 (18) ][262]
    • [ September 2009 (11) ][263]
    • [ August 2009 (14) ][264]
      • What went wrong: SCTP
      • [Disable flapping BGP neighbors][265]
      • [Do not EVER run OSPF or IS-IS with your Internet c...][266]
      • [What went wrong: the Socket API][267]
      • [Turn a switch into a hub … the Microsoft way][268]
      • [Regular expressions in EEM applets][269]
      • [Questions on BGP AS-path filters in non-transit ne...][270]
      • [What went wrong: TCP/IP lacks a session layer][271]
      • [Data Center Interconnect][272]
      • [IOS access list numbering scheme][273]
      • [Broadband traffic management][274]
      • [IOS Hints comments work with Facebook Connect][275]
      • [Blackhat 2009 Router Exploitation presentation][276]
      • [Router LSA quiz: the results][277]
    • [ July 2009 (22) ][278]
    • [ June 2009 (22) ][279]
    • [ May 2009 (21) ][280]
    • [ April 2009 (22) ][281]
    • [ March 2009 (26) ][282]
    • [ February 2009 (24) ][283]
    • [ January 2009 (22) ][284]
  • [ 2008 (333) ][285]
    • [ December 2008 (24) ][286]
    • [ November 2008 (27) ][287]
    • [ October 2008 (29) ][288]
    • [ September 2008 (27) ][289]
    • [ August 2008 (26) ][290]
    • [ July 2008 (23) ][291]
    • [ June 2008 (31) ][292]
    • [ May 2008 (32) ][293]
    • [ April 2008 (29) ][294]
    • [ March 2008 (28) ][295]
    • [ February 2008 (30) ][296]
    • [ January 2008 (27) ][297]
  • [ 2007 (261) ][298]
    • [ December 2007 (17) ][299]
    • [ November 2007 (30) ][300]
    • [ October 2007 (26) ][301]
    • [ September 2007 (26) ][302]
    • [ August 2007 (24) ][303]
    • [ July 2007 (12) ][304]
    • [ June 2007 (21) ][305]
    • [ May 2007 (23) ][306]
    • [ April 2007 (21) ][307]
    • [ March 2007 (22) ][308]
    • [ February 2007 (21) ][309]
    • [ January 2007 (18) ][310]
  • [ 2006 (39) ][311]
    • [ December 2006 (10) ][312]
    • [ November 2006 (8) ][313]
    • [ October 2006 (17) ][314]
    • [ September 2006 (1) ][315]
    • [ August 2006 (3) ][316]

The author

![Ivan Pepelnjak Photo][317]

Ivan Pepelnjak (CCIE#1354 Emeritus), Independent Network Architect at ipSpace.net, has been designing and implementing large-scale data communications networks as well as teaching and writing books about advanced internetworking technologies since 1990.

[ ][90] [ ][318]

More content

Shortcuts

Subscribe to

  • [ Blog posts ][91]
  • [ Software Gone Wild podcast ][320]
  • [ Videos ][321]
  • [ SDN mailing list ][322]
  • [ Follow @ioshints ][323]

Disclaimer

The opinions expressed in individual articles, blog posts, videos or webinars are entirely the author’s opinions.

[Read more][324]

Copyright 2006 - 2017 ipSpace.net AG![counter stats][325]

[86]: [87]: http://blog.ipspace.net/2009/09/cisco-ios-is-not-authoritative-dhcp.html "Newer Post" [88]: http://blog.ipspace.net/2009/08/disable-flapping-bgp-neighbors.html "Older Post" [89]: http://blog.ipspace.net# [90]: https://twitter.com/ioshints [91]: http://feed.ipspace.net/blog/ [92]: https://www.ipspace.net/Subscribe/Five_SDN_Tips [93]: http://blog.ipspace.net/2018/01/how-to-become-better-networking-engineer.html [94]: http://blog.ipspace.net/2018/01/revisited-need-for-stretched-vlans.html [95]: http://blog.ipspace.net/2018/02/using-evpn-in-very-small-data-center.html [96]: http://blog.ipspace.net/2018/01/bgp-in-evpn-based-data-center-fabrics.html [97]: http://blog.ipspace.net/2018/02/brief-recap-tech-field-day-at-cisco.html [98]: http://blog.ipspace.net/2018/02/evpn-is-more-than-vpls-on-steroids.html [99]: http://blog.ipspace.net/2018/02/worth-reading-whiteboxes-for-everyone.html [100]: http://blog.ipspace.net/2018/01/use-yang-data-models-to-configure.html [101]: http://blog.ipspace.net/2018/02/how-useful-is-microsegmentation.html [102]: http://blog.ipspace.net/2018/02/automation-win-mplsvpn-service.html [103]: http://blog.ipspace.net/search/label/Data%20Center [104]: http://blog.ipspace.net/search/label/SDN [105]: http://blog.ipspace.net/search/label/virtualization [106]: http://blog.ipspace.net/search/label/IPv6 [107]: http://blog.ipspace.net/search/label/security [108]: http://blog.ipspace.net/search/label/BGP [109]: http://blog.ipspace.net/search/label/switching [110]: http://blog.ipspace.net/search/label/Fabric [111]: http://blog.ipspace.net/search/label/IP%20routing [112]: http://blog.ipspace.net/search/label/OpenFlow [113]: http://blog.ipspace.net/search/label/Automation [114]: http://blog.ipspace.net/search/label/Overlay%20networks [115]: http://blog.ipspace.net/search/label/WAN [116]: http://blog.ipspace.net/search/label/Design [117]: http://blog.ipspace.net/search/label/OSPF [118]: http://blog.ipspace.net/search/label/MPLS%20VPN [119]: http://blog.ipspace.net/search/label/network%20management [120]: http://blog.ipspace.net/search/label/cloud [121]: http://blog.ipspace.net/search/label/firewalls [122]: http://blog.ipspace.net/search/label/MPLS [123]: http://blog.ipspace.net/search/label/EEM [124]: http://blog.ipspace.net/search/label/load%20balancing [125]: http://blog.ipspace.net/search/label/QoS [126]: http://blog.ipspace.net/search/label/bridging [127]: http://blog.ipspace.net/search/label/command%20line%20interface [128]: http://blog.ipspace.net/search/label/DMVPN [129]: http://blog.ipspace.net/search/label/LAN [130]: http://blog.ipspace.net/search/label/VXLAN [131]: http://blog.ipspace.net/search/label/DHCP [132]: http://blog.ipspace.net/search/label/configuration [133]: http://blog.ipspace.net/search/label/Service%20Providers [134]: http://blog.ipspace.net/search/label/web [135]: http://blog.ipspace.net/search/label/access%20control [136]: http://blog.ipspace.net/search/label/http [137]: http://blog.ipspace.net/search/label/traffic%20engineering [138]: http://blog.ipspace.net/search/label/EIGRP [139]: http://blog.ipspace.net/search/label/SAN [140]: http://blog.ipspace.net/search/label/vMotion [141]: http://blog.ipspace.net/search/label/NAT [142]: http://blog.ipspace.net/search/label/PPP [143]: http://blog.ipspace.net/search/label/Scalability [144]: http://blog.ipspace.net/search/label/ipsec [145]: http://blog.ipspace.net/search/label/DNS [146]: http://blog.ipspace.net/search/label/FCoE [147]: http://blog.ipspace.net/search/label/Link%20aggregation [148]: http://blog.ipspace.net/search/label/VPN [149]: http://blog.ipspace.net/search/label/IS-IS [150]: http://blog.ipspace.net/search/label/CEF [151]: http://blog.ipspace.net/search/label/ARP [152]: http://blog.ipspace.net/2018/ [153]: http://blog.ipspace.net/2018/02/ [154]: http://blog.ipspace.net/2018/01/ [155]: http://blog.ipspace.net/2017/ [156]: http://blog.ipspace.net/2017/12/ [157]: http://blog.ipspace.net/2017/11/ [158]: http://blog.ipspace.net/2017/10/ [159]: http://blog.ipspace.net/2017/09/ [160]: http://blog.ipspace.net/2017/08/ [161]: http://blog.ipspace.net/2017/07/ [162]: http://blog.ipspace.net/2017/06/ [163]: http://blog.ipspace.net/2017/05/ [164]: http://blog.ipspace.net/2017/04/ [165]: http://blog.ipspace.net/2017/03/ [166]: http://blog.ipspace.net/2017/02/ [167]: http://blog.ipspace.net/2017/01/ [168]: http://blog.ipspace.net/2016/ [169]: http://blog.ipspace.net/2016/12/ [170]: http://blog.ipspace.net/2016/11/ [171]: http://blog.ipspace.net/2016/10/ [172]: http://blog.ipspace.net/2016/09/ [173]: http://blog.ipspace.net/2016/08/ [174]: http://blog.ipspace.net/2016/07/ [175]: http://blog.ipspace.net/2016/06/ [176]: http://blog.ipspace.net/2016/05/ [177]: http://blog.ipspace.net/2016/04/ [178]: http://blog.ipspace.net/2016/03/ [179]: http://blog.ipspace.net/2016/02/ [180]: http://blog.ipspace.net/2016/01/ [181]: http://blog.ipspace.net/2015/ [182]: http://blog.ipspace.net/2015/12/ [183]: http://blog.ipspace.net/2015/11/ [184]: http://blog.ipspace.net/2015/10/ [185]: http://blog.ipspace.net/2015/09/ [186]: http://blog.ipspace.net/2015/08/ [187]: http://blog.ipspace.net/2015/07/ [188]: http://blog.ipspace.net/2015/06/ [189]: http://blog.ipspace.net/2015/05/ [190]: http://blog.ipspace.net/2015/04/ [191]: http://blog.ipspace.net/2015/03/ [192]: http://blog.ipspace.net/2015/02/ [193]: http://blog.ipspace.net/2015/01/ [194]: http://blog.ipspace.net/2014/ [195]: http://blog.ipspace.net/2014/12/ [196]: http://blog.ipspace.net/2014/11/ [197]: http://blog.ipspace.net/2014/10/ [198]: http://blog.ipspace.net/2014/09/ [199]: http://blog.ipspace.net/2014/08/ [200]: http://blog.ipspace.net/2014/07/ [201]: http://blog.ipspace.net/2014/06/ [202]: http://blog.ipspace.net/2014/05/ [203]: http://blog.ipspace.net/2014/04/ [204]: http://blog.ipspace.net/2014/03/ [205]: http://blog.ipspace.net/2014/02/ [206]: http://blog.ipspace.net/2014/01/ [207]: http://blog.ipspace.net/2013/ [208]: http://blog.ipspace.net/2013/12/ [209]: http://blog.ipspace.net/2013/11/ [210]: http://blog.ipspace.net/2013/10/ [211]: http://blog.ipspace.net/2013/09/ [212]: http://blog.ipspace.net/2013/08/ [213]: http://blog.ipspace.net/2013/07/ [214]: http://blog.ipspace.net/2013/06/ [215]: http://blog.ipspace.net/2013/05/ [216]: http://blog.ipspace.net/2013/04/ [217]: http://blog.ipspace.net/2013/03/ [218]: http://blog.ipspace.net/2013/02/ [219]: http://blog.ipspace.net/2013/01/ [220]: http://blog.ipspace.net/2012/ [221]: http://blog.ipspace.net/2012/12/ [222]: http://blog.ipspace.net/2012/11/ [223]: http://blog.ipspace.net/2012/10/ [224]: http://blog.ipspace.net/2012/09/ [225]: http://blog.ipspace.net/2012/08/ [226]: http://blog.ipspace.net/2012/07/ [227]: http://blog.ipspace.net/2012/06/ [228]: http://blog.ipspace.net/2012/05/ [229]: http://blog.ipspace.net/2012/04/ [230]: http://blog.ipspace.net/2012/03/ [231]: http://blog.ipspace.net/2012/02/ [232]: http://blog.ipspace.net/2012/01/ [233]: http://blog.ipspace.net/2011/ [234]: http://blog.ipspace.net/2011/12/ [235]: http://blog.ipspace.net/2011/11/ [236]: http://blog.ipspace.net/2011/10/ [237]: http://blog.ipspace.net/2011/09/ [238]: http://blog.ipspace.net/2011/08/ [239]: http://blog.ipspace.net/2011/07/ [240]: http://blog.ipspace.net/2011/06/ [241]: http://blog.ipspace.net/2011/05/ [242]: http://blog.ipspace.net/2011/04/ [243]: http://blog.ipspace.net/2011/03/ [244]: http://blog.ipspace.net/2011/02/ [245]: http://blog.ipspace.net/2011/01/ [246]: http://blog.ipspace.net/2010/ [247]: http://blog.ipspace.net/2010/12/ [248]: http://blog.ipspace.net/2010/11/ [249]: http://blog.ipspace.net/2010/10/ [250]: http://blog.ipspace.net/2010/09/ [251]: http://blog.ipspace.net/2010/08/ [252]: http://blog.ipspace.net/2010/07/ [253]: http://blog.ipspace.net/2010/06/ [254]: http://blog.ipspace.net/2010/05/ [255]: http://blog.ipspace.net/2010/04/ [256]: http://blog.ipspace.net/2010/03/ [257]: http://blog.ipspace.net/2010/02/ [258]: http://blog.ipspace.net/2010/01/ [259]: http://blog.ipspace.net/2009/ [260]: http://blog.ipspace.net/2009/12/ [261]: http://blog.ipspace.net/2009/11/ [262]: http://blog.ipspace.net/2009/10/ [263]: http://blog.ipspace.net/2009/09/ [264]: http://blog.ipspace.net/2009/08/ [265]: http://blog.ipspace.net/2009/08/disable-flapping-bgp-neighbors.html [266]: http://blog.ipspace.net/2009/08/do-not-ever-run-ospf-or-is-is-with-your.html [267]: http://blog.ipspace.net/2009/08/what-went-wrong-socket-api.html [268]: http://blog.ipspace.net/2009/08/turn-switch-into-hub-microsoft-way.html [269]: http://blog.ipspace.net/2009/08/regular-expressions-in-eem-applets.html [270]: http://blog.ipspace.net/2009/08/questions-on-bgp-as-path-filters-in-non.html [271]: http://blog.ipspace.net/2009/08/what-went-wrong-tcpip-lacks-session.html [272]: http://blog.ipspace.net/2009/08/data-center-interconnect.html [273]: http://blog.ipspace.net/2009/08/ios-access-list-numbering-scheme.html [274]: http://blog.ipspace.net/2009/08/broadband-traffic-management.html [275]: http://blog.ipspace.net/2009/08/ios-hints-comments-work-with-facebook.html [276]: http://blog.ipspace.net/2009/08/blackhat-2009-router-exploitation.html [277]: http://blog.ipspace.net/2009/08/router-lsa-quiz-results.html [278]: http://blog.ipspace.net/2009/07/ [279]: http://blog.ipspace.net/2009/06/ [280]: http://blog.ipspace.net/2009/05/ [281]: http://blog.ipspace.net/2009/04/ [282]: http://blog.ipspace.net/2009/03/ [283]: http://blog.ipspace.net/2009/02/ [284]: http://blog.ipspace.net/2009/01/ [285]: http://blog.ipspace.net/2008/ [286]: http://blog.ipspace.net/2008/12/ [287]: http://blog.ipspace.net/2008/11/ [288]: http://blog.ipspace.net/2008/10/ [289]: http://blog.ipspace.net/2008/09/ [290]: http://blog.ipspace.net/2008/08/ [291]: http://blog.ipspace.net/2008/07/ [292]: http://blog.ipspace.net/2008/06/ [293]: http://blog.ipspace.net/2008/05/ [294]: http://blog.ipspace.net/2008/04/ [295]: http://blog.ipspace.net/2008/03/ [296]: http://blog.ipspace.net/2008/02/ [297]: http://blog.ipspace.net/2008/01/ [298]: http://blog.ipspace.net/2007/ [299]: http://blog.ipspace.net/2007/12/ [300]: http://blog.ipspace.net/2007/11/ [301]: http://blog.ipspace.net/2007/10/ [302]: http://blog.ipspace.net/2007/09/ [303]: http://blog.ipspace.net/2007/08/ [304]: http://blog.ipspace.net/2007/07/ [305]: http://blog.ipspace.net/2007/06/ [306]: http://blog.ipspace.net/2007/05/ [307]: http://blog.ipspace.net/2007/04/ [308]: http://blog.ipspace.net/2007/03/ [309]: http://blog.ipspace.net/2007/02/ [310]: http://blog.ipspace.net/2007/01/ [311]: http://blog.ipspace.net/2006/ [312]: http://blog.ipspace.net/2006/12/ [313]: http://blog.ipspace.net/2006/11/ [314]: http://blog.ipspace.net/2006/10/ [315]: http://blog.ipspace.net/2006/09/ [316]: http://blog.ipspace.net/2006/08/ [317]: https://www.ipspace.net/v3/images/picture_ivan_footer_big_screen.jpg [318]: https://www.linkedin.com/in/ivanpepelnjak/ [319]: https://www.ipspace.net/Podcasts [320]: http://feed.ipspace.net/podcast/software.gone.wild [321]: http://feed.ipspace.net/podcast/ [322]: http://www.ipspace.net/Subscribe/Five_SDN_Tips [323]: https://twitter.com/intent/follow?screen_name=ioshints&tw_p=followbutton [324]: http://www.ipspace.net/About_Ivan_Pepelnjak#Disclaimer [325]: http://c14.statcounter.com/counter.php?sc_project=1812606&java=0&security=a1b8d99a&invisible=1