<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Pedro Pérez on Medium]]></title>
        <description><![CDATA[Stories by Pedro Pérez on Medium]]></description>
        <link>https://medium.com/@pjperez?source=rss-7f8f99b120e0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*dmyd2xK8dxvp8b1a.png</url>
            <title>Stories by Pedro Pérez on Medium</title>
            <link>https://medium.com/@pjperez?source=rss-7f8f99b120e0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 05:23:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pjperez/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Monitoring your website for free with Azure Functions and PowerShell with SMS alerts — done in 5…]]></title>
            <link>https://medium.com/@pjperez/monitoring-your-website-for-free-with-azure-functions-and-powershell-with-sms-alerts-done-in-5-894fe1fcbe5b?source=rss-7f8f99b120e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/894fe1fcbe5b</guid>
            <category><![CDATA[monitoring]]></category>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[hacking]]></category>
            <dc:creator><![CDATA[Pedro Pérez]]></dc:creator>
            <pubDate>Wed, 07 Dec 2016 17:24:30 GMT</pubDate>
            <atom:updated>2016-12-07T17:24:30.803Z</atom:updated>
            <content:encoded><![CDATA[<h3>Monitoring your website for free with Azure Functions and PowerShell with SMS alerts — done in 5 minutes</h3><p>So called <em>serverless </em>computing has arrived to pretty much all major cloud computing platforms, including Azure under the “<a href="https://azure.microsoft.com/en-gb/services/functions/">Azure Functions</a>” name. As curious as I am, I was wondering what all the fuss was about so I came up with a use case to try it out.</p><p>One of the best things about Azure Functions is that I can code and test my PowerShell (or Bash!) script locally, then upload it to Functions just to have it running periodically without having to spin up a server anywhere.</p><p><strong>Disclaimer:</strong> I am not a developer, so I tried to stick to something I feel comfortable with. That’s PowerShell :-)</p><p>My chosen use case was to get an SMS if one of my sites is down. Sounds useful enough, so let’s start building the solution.</p><p>Let’s first make sure you have a Twilio account (get one for free <a href="https://www.twilio.com/try-twilio">here</a>) and that you have your account sid, auth token and Twilio number handy.</p><p>Now back to Azure Functions, <a href="https://azure.microsoft.com/en-gb/services/functions/">let’s click on Try it for free</a> and create any function as PowerShell is not an option on this screen (I guess because it’s in experimental phase right now):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0tXWpvWPtgzgy-Zz_RXfTw.png" /></figure><p>Then go ahead and create a new TimeTrigger function for PowerShell:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mBKP2rD7JZEyn1q5ohR9_A.png" /><figcaption>We want a time triggered function</figcaption></figure><p>I’ve also selected to run it every time instead of the default 5 minutes:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MNsJ9w7WFFHHkq3un0JewQ.png" /><figcaption>Just change the default 5 for a 1</figcaption></figure><p>Once created, paste the below code and make sure you populate the <strong>$poorsodnumber </strong>variable with your phone number.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/bc1831646fb0244f72f7545273b1004a/href">https://medium.com/media/bc1831646fb0244f72f7545273b1004a/href</a></iframe><p>The code basically sends a GET request to <a href="https://bing.com/">https://bing.com</a> and checks if the returned HTTP status code is 200. If it is, it just logs a message on the console, but if it’s not it will send an SMS to our number using Twilio’s API.</p><p>Don’t forget to save your changes!!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WmGaTc6CT-rwbtCi1ikXJw.png" /><figcaption>Don’t run it yet, we’re almost there…</figcaption></figure><p>Now if you had a free Azure account and created your function app from the Azure Portal, you would be able to edit environment variables here:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IWroTTSTzBSbcXTPFFrSzQ.png" /><figcaption>Apparently not available without a free Azure account!</figcaption></figure><p>As we just started playing without an account and can’t edit environment variables, we have to go back to our code and change <strong>$env:TWILIO_ACCOUNT_SID</strong>, <strong>$env:TWILIO_AUTH_TOKEN</strong> and <strong>$env:TWILIO_NUMBER</strong> with the actual values for each of them from our Twilio account.</p><p><strong>Press <em>save and run</em> and that’s it! Our little function is running already! </strong>but unless your site is down, you won’t be getting any SMS any time soon. You should be seeing instead this sort of output on your console:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/966/1*kTRLgn308TCyTXhAFtiyXw.png" /><figcaption>Bing is UP!</figcaption></figure><p>I wanted to make sure Twilio integration worked, so I’ve changed the expected status code in our function from “200” to “404”. That would tell my script to send me an SMS if we <strong>don’t</strong> get a 404 — as we know Bing is up, we won’t be getting a 404 and I’ll get an SMS.</p><p>Console will spill different output as per our PowerShell code:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x_ziXxGXWIpP9vPIgF5YyQ.png" /><figcaption>And my phone got an SMS! :)</figcaption></figure><p>It doesn’t get much more faster and cooler than that, really.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=894fe1fcbe5b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On troubleshooting networks: Traceroute]]></title>
            <link>https://medium.com/hackernoon/on-troubleshooting-networks-traceroute-92a1569011f?source=rss-7f8f99b120e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/92a1569011f</guid>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[troubleshooting]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Pedro Pérez]]></dc:creator>
            <pubDate>Fri, 16 Sep 2016 15:31:53 GMT</pubDate>
            <atom:updated>2017-07-13T22:54:57.372Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/420/1*jQk0LXWfUvo3f5s6gA_9-w.png" /></figure><p>I’d like to start a series of posts talking about networking concepts. Nothing extremely complex and just for fun. I thought it would be a good idea to start talking about traceroute as it’s one of the most known troubleshooting tools.</p><p>Hope you enjoy the reading.</p><h3>Traceroute.</h3><p>Any of you working with networks have used traceroute at some point to troubleshoot a connectivity issue, but how much do we really know about how it works and about interpreting its results?</p><p>Most of you know that traceroute “uses ICMP”, but this is a very broad statement and not always 100% accurate. Why do I say that? Well, let’s start by analysing one of the most common traceroute implementations, tracert.exe from Windows.</p><h3>tracert.exe</h3><p>This implementation of traceroute in its most simple usage takes just one parameter: The destination IP address we would like to trace our route to.<br>What does <strong>tracert.exe</strong> under the hood when we hit enter? It immediately sends 3 ICMP packets with Type 8 Code 0, also known as Echo Request or more commonly Ping, to the destination IP address.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*37QDZyfVT-AlRf_7k66fSQ.png" /><figcaption>These 3 ICMP packets have a particularity though: Their TTL value is 1.</figcaption></figure><p><a href="https://en.wikipedia.org/wiki/Time_to_live">The TTL is an IP header</a> that gets decremented in 1 every time an IP packet is moved from a subnet to another. In other words, every time a router forwards a packet, it decrements the TTL of the packet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/735/1*VOwVRxMUpLNk2Eb2nfsU0w.png" /><figcaption>Expanded IP header in Wireshark</figcaption></figure><p>So <strong>tracert.exe</strong> sent 3 pings to the destination IP address, with a TTL value of 1. Where do these packets go first? Well, given that the destination IP address is not another host in our network, our computer running <strong>tracert.exe</strong> will look up its own routing table to make a decision on where to send this packet. For most scenarios we will have a computer with simply a default route, which then points to what we call a default gateway (because it is the gateway designated for the default route).</p><p>The packet reaches the default gateway, which would be a network device with routing capabilities. Probably a router or a firewall. This router will look into the packet headers to decide what to do with it. In normal situations I would mention now that the router will check its own routing table too, but there’s one thing the router will also check apart from the destination IP address: The TTL header.</p><p>As we have mentioned before, the TTL header has a value of 1 and a router will decrement it when forwarding the packet, so in our case the router will have to forward the packet with a TTL value of 0. Is that even possible? Well, a broken IP stack might want to do it, but the short answer is <strong>no</strong>. Once you have to forward a packet and decrease its TTL value to 0, instead of forwarding it you will <strong>drop it </strong>and send a notification back to the <strong>original sender</strong>. Who is the <strong>original sender </strong>in our case? Our computer.</p><p>What kind of notification will the router send back to our computer? If only we had some sort of standardized <strong>I</strong>nternet <strong>C</strong>ontrol <strong>M</strong>essage <strong>P</strong>rotocol!</p><p>That’s right, the router will send back an <a href="https://en.wikipedia.org/wiki/Internet_Control_Message_Protocol#Control_messages">ICMP packet of Type 11 Code 0</a>, also known as “TTL Expired (or TTL exceeded) in transit”. This ICMP will also contain the original dropped packet as its payload, so your computer can identify the packet that has been dropped.</p><p>Well, that’s all fine, but how does <strong>tracert.exe</strong> take advantage of this? Easy! ICMP packets are of course IP packets, so they have IP headers, right? What useful information could <strong>tracert.exe </strong>use from the IP headers? <strong>The source IP address</strong>. As the TTL Expired packet is a new packet originated on the router, the source IP address is the IP address of the router, so <strong>tracert.exe</strong> will read that IP address and identify who is the first hop:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OVSQQ64mSdCYn7m0qO410w.png" /></figure><p>As you can see in the screenshot above, our computer <strong>192.168.1.103 </strong>sends 3 pings to <strong>8.8.8.8</strong> (with TTL==1 that can’t be seen in the screenshot, but you can see in previous screenshots on this article) and gets 3 TTL Expired packets back from <strong>192.168.1.254</strong>. That’s how <strong>tracert.exe </strong>identified the first hop and how it measured the latency between us and that hop (time difference between sending the ping and receiving the TTL Expired packet). The process is the same until the TTL is big enough to reach the destination without expiring in transit, in which case we will get a reply to our ping (Echo Reply ICMP).</p><p>So yeah, we could say that <strong>tracert.exe</strong> “Uses ICMP”, because there’s no other protocol higher than layer 3 involved.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/411/1*xHRjfNhZK5ePT2EQt-ZNjg.png" /><figcaption>Request timed out at hop #2. What’s going on?</figcaption></figure><h3>Request timed out.</h3><p>It’s not rare to see this message on our <strong>tracert.exe</strong> output. What does this mean? In a nutshell, it means that we never got a TTL expired ICMP packet nor an Echo Reply ICMP back for those pings sent. Reason?</p><p>- The router is configured to not send those replies for security or economy reasons.<br>- Either our pings got lost before arriving to the router or the ICMP replies got lost in their way back to us.</p><p>In the above screenshot, I’m inclined to think that the router at hop #2 is configured to not send those ICMP packets back, just because the rest of the hops seem to be in good health and reporting back, so I would discard heavy packet loss in the path (see? We have started getting something useful out of <strong>tracert.exe</strong>’s results).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/416/1*jz8F4RLPN1yUFkHFCqiM6A.png" /><figcaption>Fun fact: After hop #9 we have crossed the Atlantic Ocean (+100ms).</figcaption></figure><p>There are other occasions where the <strong>Request timed out</strong> messages do appear after certain hop and we never get a new hop IP address. In those cases, like in the screenshot above and just after hop #14, there is a device dropping the ICMP packets. In some occasions you’ll be missing also a bunch of results until the very last one: In that case, the intermediate device is dropping ICMPs that are not pings (echo request and echo reply).</p><p>In this case and with only this output, we can’t say for sure how many hops there are until destination and <strong>tracert.exe</strong> would keep going until hop #30 (by default).</p><p>How do you go past this? You can’t. <em>But I’ve heard about </em><a href="http://linux.die.net/man/1/tcptraceroute"><em>tcptraceroute</em></a><em>!</em> — Yes, <strong>tcptraceroute </strong>is a bit different, but it’s not going to do the job on many scenarios. Let me explain why:</p><p><strong>Tcptraceroute </strong>sends TCP SYN packets to the destination, starting with TTL == 1 and increasing its value every time after getting a result. Still, we have to receive TTL Expired ICMPs to be able to identify who dropped the packet — we won’t be able to get them if a device is dropping ICMPs.</p><p>Why <strong>tcptraceroute </strong>then? Because if the final host doesn’t reply to ping, it might reply to your TCP SYN packet. Or a firewall in between might let TCP traffic inbound but not ICMP inbound (and permit anything outbound, including TTL Expired ICMPs).<br><br>There’s one more detail I’d like to highlight from the screenshot above. The theory is that tracert.exe hops should be increasing its latency, even if it’s less than 1ms and doesn’t reflect on the output, but how come does take longer to get to hop #6 than hop #7? ICMPs surely don’t travel back in time. With what we know now, that each hop is measured independently and the latency is how long does it take for us to get a TTL Expired ICMP back after we send our ping, having higher latency on a farther hop doesn’t sound that crazy. From the above screenshot I can’t be sure, but it’s probably one of these two:</p><ul><li><strong>ICMP Throttling</strong>: Some network administrators, especially at ISPs with busy networks, configure policies to reply to these ICMPs with a very low priority so they might be very fast forwarding your ICMPs to the next hop, but when they are the ones that have to reply to them, they will probably delay the response a bit further.</li><li><strong>Network fluctuations</strong>: A device in the path might have been more overloaded than when we tested hop #7.</li></ul><p>The latency difference between #6 and #7 is not that big, but in some cases you might see up to 100ms delay on closer hops. Don’t get fooled by this, there might be no issues at all in the path even with those weird results.</p><blockquote>Fun fact: Most traceroute implementations in Linux use UDP by default.</blockquote><p>So, again, traceroute doesn’t necessarily “Use ICMP”, but it surely relies on it :-)</p><p><em>If you think this article has been either useful or entertaining, please don’t forget to click on the tiny green heart below to recommend it to other fellow readers. I would also be extremely grateful if you could share this among your friends and colleagues on your favourite social network. You could also take a look at </em><a href="https://wormhole.network/"><em>Wormhole Network</em></a><em>, a company that provides on-demand secure private networks as a service. It may be of your interest.</em></p><p><em>Thank you!</em></p><figure><a href="http://bit.ly/HackernoonFB"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0hqOaABQ7XGPT-OYNgiUBg.png" /></a></figure><figure><a href="https://goo.gl/k7XYbx"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vgw1jkA6hgnvwzTsfMlnpg.png" /></a></figure><figure><a href="https://goo.gl/4ofytp"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gKBpq1ruUi0FVK2UM_I4tQ.png" /></a></figure><blockquote><a href="http://bit.ly/Hackernoon">Hacker Noon</a> is how hackers start their afternoons. We’re a part of the <a href="http://bit.ly/atAMIatAMI">@AMI</a> family. We are now <a href="http://bit.ly/hackernoonsubmission">accepting submissions</a> and happy to <a href="/service/mailto:partners@amipublications.com">discuss advertising &amp; sponsorship</a> opportunities.</blockquote><blockquote>If you enjoyed this story, we recommend reading our <a href="http://bit.ly/hackernoonlatestt">latest tech stories</a> and <a href="https://hackernoon.com/trending">trending tech stories</a>. Until next time, don’t take the realities of the world for granted!</blockquote><figure><a href="https://goo.gl/Ahtev1"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*35tCjoPcvq6LbB3I6Wegqw.jpeg" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=92a1569011f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/on-troubleshooting-networks-traceroute-92a1569011f">On troubleshooting networks: Traceroute</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The TTL Trick]]></title>
            <link>https://medium.com/@pjperez/the-ttl-trick-c78f1279817d?source=rss-7f8f99b120e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/c78f1279817d</guid>
            <category><![CDATA[troubleshooting]]></category>
            <category><![CDATA[wireshark]]></category>
            <category><![CDATA[networking]]></category>
            <dc:creator><![CDATA[Pedro Pérez]]></dc:creator>
            <pubDate>Sun, 27 Mar 2016 18:07:06 GMT</pubDate>
            <atom:updated>2016-04-04T11:24:22.868Z</atom:updated>
            <content:encoded><![CDATA[<h4>Or the importance of knowing networking fundamentals so you can blame the network :-)</h4><p>I have met several network engineers during my life. Most of them are very clever and pragmatic people.</p><p>These engineers can solve the majority of the problems in their network by looking at logs and configuration files, so they slowly move away from the very foundation of their networks: The protocols.</p><p>I’m not going to claim I’m a rockstar IP or TCP guy, but I can say that I <strong>really</strong> like to know what’s under the hood and love to see all the pieces of the puzzle coming together to paint the final picture. This has helped me multiple times in the past. One of these little pieces of knowledge, which has become a trick after the years, is what I like to call <em>The TTL Trick</em>.</p><h4>Help! $YOURAPP doesn’t work!</h4><p>Helping people running their distributed applications has probably been the most common task through my career.</p><p>My troubleshooting methods have changed over the years, especially when I moved from actually managing the network (where I would check logs and apply my logic) to working for a software company, where my company’s applications could be affected by a potential network issue and I had zero access to the network gear.</p><p>Right now, what I always ask for is for simultaneous network captures. Simultaneous as in client and server captured at the same time. Eventually this could be extended to more captures from other devices in between, but in the first place it’s not always easy to get the needed information to even draw a little network diagram, less to understand where should we capturing.</p><p>So, in summary, <em>pcaps or it didn’t happen</em>. By the way, I like my captures full, not filtered based on someone else’s criteria, thank you. It makes me sad to not find the root cause of an issue because someone decided to only capture the application’s traffic, not capturing that ICMP “fragmentation needed but DF bit set” that tells you there’s some MTU <em>issue</em>.</p><p>Why do I really, totally, completely need these captures? For lots of reasons, but the focus of this article is on the TTL header, so that’s why.</p><p>The TTL or Time To Live is a field in the IP header:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/544/1*8r5sZ2l5pIE5GzT39nulfA.png" /><figcaption>The TTL header amounts for 8 bits or 1-byte of data</figcaption></figure><p>This field could be considered a security feature, thought to avoid packets moving through your network in a routing (or layer 3 — remember OSI) loop until the end of the days. A routing loop happens when a packet that needs to get from A to B is bounced as a ping-pong ball between two hosts that have conflicting routes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*6sevKvVisS6Wh_lD4M5Wgw.gif" /><figcaption>A packet destined for Network 10 jumps from R1 to R2 to R3, then again to R1… You get it now.</figcaption></figure><p>How does such a tiny field in the headers avoid packets looping <em>ad infinitum</em> inside your network? In a classy way.</p><p>Every time a new packet is put on the wire, it has an initial value in the TTL field that gets decreased when the packet is routed to another network. Once the value in the TTL header reaches zero, the packet is dropped and not forwarded nor accepted by the device that just received it.</p><p>I told you it was classy.</p><p>Now you will be wondering <em>what’s the initial TTL value?</em> — It depends, and it actually depends on the vendor of the OS (<em>actually depends on the network stack, but these two are usually in a one to one relationship</em>). Here are some values I remember on top of my head:</p><ul><li>Windows OS: 128</li><li>Most Linux distros: 64</li><li>Some Cisco gear (e.g. ASA): 256</li><li>F5 LTM, even though it’s Linux based, seems to use 256 too.</li><li>Riverbed seems to use 64 on their WAN accelerators.</li><li>Watchguard and Fortigate firewalls seem to use 64 as well.</li></ul><p>In all honesty, the different maximum values never were a big problem for anyone nor reason for a big discussion.</p><p>A routing loop is a problem big enough for a network engineer, who at that stage probably doesn’t care if the lost packets jumped 64 or 256 times. I guess engineers working on very high bandwidth environments with routing nightmares (ISPs? Telcos? Big Corporate?) might not agree with my statement, but still not the point of this article.</p><h4>What’s the TTL trick then? Scenario 1</h4><p>Now let’s imagine for a second that you have your fancy application running on your fancy network, but some connections are lost. The described symptoms are that <em>a user is working and suddenly there’s an error on screen about a lost connection</em>. Of course you will pass the ticket to the network guys. I mean, the error says <strong>connection</strong> right? There might be even an IP address somewhere. All good…</p><p>All good until the network team comes back and shows you a packet capture from the client side, where your server is sending a TCP Reset to kill the connection. Dammit!</p><p>Now you have two tasks: Send the ticket to the server guys (it has to be their fault now) and check the application logs for the first time, just in case there’s something quite not right there. Now here comes a first surprise: You have a server-side error message that claims the client actually killed the connection. You know what? It has to be the network but you can’t prove it.</p><p>Or can’t you? Of course you can! remember that fancy packet capture the network team sent across to show you how it was totally not their fault? Well, you better install Wireshark now and open the capture to analyse.</p><p>As it turns out, both your client and the server are running Windows, and now thanks to this article you know the Windows TTL is 128.</p><p>You brush up your Wireshark skills and find the broken conversation (<em>i.e. you apply the filter the network team told you</em>). There it is, A fancy three-way handshake. You remember that from your CCNA (syn, syn ack, ack).</p><p>Care to look at any packet coming from the server for me please? You check the TTL field in the IP headers and write down the number on your notepad. It’s probably something close to 128. Let’s say you see 124, so there are 4 routing hops between your user and your server.</p><p>Now you’re going to scroll down (unless you’re a monster that reverse orders the packet list!) and find the TCP Reset packet. Click. Click click. Expand IP headers. Boom!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*Z-W-ZLGgLPdfJ3Q-4-E93w.gif" /></figure><blockquote>“Fuck you” said the network</blockquote><p>The TTL is 255 and the header checksum is correct, so that value is real. What the actual f…?</p><p>Some network device, one hop away (so not in your user’s subnet gateway), is royally screwing you. This device crafted the TCP Reset packet from scratch, for some weird (security?) reason.</p><p>With this little information you have been able not only to blame those pesky network engineers, but also showed them where in the network is the problem.</p><p>If I was you, I would call it a day and go home because it can’t get any better from here. Remember to get your pay raise on your way out.</p><h4>What’s the TTL trick then? Scenario 2</h4><p>Now here comes the other common scenario, which is also a bit more tricky.</p><p>On the previous scenario we could have blamed a network device with a simultaneous capture and showing: That both sides received a TCP Reset from the remote side, but they didn’t send any.</p><p>On this second scenario, there are no new packets in the network.</p><p>Your user complains about the same symptoms and a simultaneous trace actually shows that your server is sending a TCP Reset to the client. OK, it must be the server guys fault, let’s blame them! but let’s also check our application logs just in case. After some troubleshooting time, you find that the server actually receives corrupt data from the client, so of course it doesn’t like that data, throws an exception and resets the connection. Talk about resilient software.</p><p>Time to trace on the client, maybe?</p><p>Tracing on the client shows that the data is right. Oh well, what could be happening here? Now you’ve already spent a few precious hours, plus involved the server and network guys who said they couldn’t see any problems either.</p><h4>Too many man-hours for a problem that you could have already solved.</h4><p>Back to those simultaneous traces. Server-side shows the user’s packets have a TTL of 58, while the user-side trace shows the packets have a TTL of 128.</p><p>Well, I’m a firm believer of The Church of the Asymmetric Routing (TCAR), but there’s no way on Earth there are 70 hops difference between the two paths.</p><p>You know again that both the client and server are running Windows, so their TTL must be close to 128 in your company’s internal networks. Why do these packets have their TTL changed? Looking again at the user-side trace, you can see they leave the user’s workstation with a TTL of 128. Yep, the TTL has been changed somewhere. Somehow.</p><p>Let’s go back once again to the server-side trace. Look at the three way handshake. Chances are the syn and ack packets from the user side will not have a TTL of 58, but something around 122 (depending on the asymmetry of your network). Why do these packets have TTL 122 and the rest TTL 58?</p><p>Application Layer Filtering, Intrusion Protection / Detection, Deep Packet Inspection, you name it. All these technologies care about layer 7 protocols, so they’ll try to inspect the TCP (or UDP) payload to look for those layer 7 protocols (and their payloads!) like e.g. HTTP or even your application’s ;-)</p><p>While the connection is being established, these network appliances will act as a normal firewall: matching rules, forwarding packets, creating a connection entry in the table. Your packets during the three way handshake are mostly uninteresting and are forwarded unharmed, but as soon as the L7 protocol that your application uses comes into play, these appliances will rip the packets apart and try some magic on them like sanitization, compression, optimization, etc</p><p>Chances are the data will not follow your application’s protocol any more and your server will not understand the packet, thus throwing an exception and killing the connection. You know, you could’ve handled that exception. I mean, it’s not like transport protocols like TCP don’t have mechanisms to retransmit packets, right?</p><p>In any case, this has happened and still happens more often than some networking (and especially network security) vendors would like to admit. It is fucking difficult to get application filtering right.</p><p>Show the network team this capture, tell them that they left running some obscure magical feature on a firewall in the network (potentially running an OS based on Linux, due to a TTL close to 64) and that it’s screwing up your application. In the meanwhile, file a bug to make the application more resilient to these quirks.</p><p>Another.Case.Solved.</p><p><em>If you think this article has been either useful or entertaining, please don’t forget to click on the tiny green heart below to recommend it to other fellow readers. I would also be extremely grateful if you could share this among your friends and colleagues on your favourite social network. You could also take a look at </em><a href="https://wormhole.network/"><em>Wormhole Network</em></a><em>, a company that provides on-demand secure private networks as a service. It may be of your interest.</em></p><p><em>Thank you!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c78f1279817d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[VPN solutions are a pain in the *ss]]></title>
            <link>https://medium.com/@pjperez/vpn-solutions-are-a-pain-in-the-ss-4036a226298d?source=rss-7f8f99b120e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/4036a226298d</guid>
            <category><![CDATA[vpn]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Pedro Pérez]]></dc:creator>
            <pubDate>Sat, 20 Feb 2016 19:13:55 GMT</pubDate>
            <atom:updated>2016-02-20T19:13:55.635Z</atom:updated>
            <content:encoded><![CDATA[<p>I’m often amazed at the amount of man-hours Humanity spends on troubleshooting VPN links.</p><p>It is probably one of the most common issues for every IT department of certain size out there, and let’s be frank with each other: Most of us hardly understand how that VPN <strong>really </strong>works.</p><h4>The Problem: I need to securely access and manage my remote assets.</h4><p>SSH and RDP are quite secure protocols, and leave them publicly reachable is not the end of the world; but at the same time we should be reducing attack surface. It’s also a PITA to deal with brute-force attacks if they get too insistent. There are some solutions for that (e.g. fail2ban), but then again we’re adding layers of complexity for a problem that could be solved in a much more elegant way.</p><h4>The Solution: Close public access and setup a VPN link.</h4><p>If your services are not publicly reachable and you require authentication on a previous system (VPN), you’re limiting the attack surface and increasing security overall. You’re also adding an extra layer of encryption, which is usually nice.</p><h4>The New Problem: VPNs are complex.</h4><p>Have you ever heard that someone who tries to solve an issue with regex, suddenly has two issues? Well, with VPNs you could say something similar.</p><p>A VPN link is not always managed by a sole team or by the same company, even though the remote resources might belong to the same company or project. Also, a VPN link often implies fairly expensive hardware, expensive support contracts with vendors and expensive skilled personnel. Even with all that covered, downtime still happens and it’s not uncommon to spend hours if the teams at both ends of the VPN can’t agree on a diagnosis.</p><p>Of course any reader could show me a hundred and one examples of working VPN links untouched for years. I’ve seen them, too; but let’s be honest, only the mention of the VPN acronym makes some support engineers sweat. Running a maintenance on VPN hardware (usually a firewall) without the collaboration of the team responsible for every single VPN peer connected is nothing short of a nightmare.</p><p>Why are VPNs so complex? Why is interoperability more often than not a real PITA? Why nobody seems to give a flying f*ck about it? Who the f*ck really wants to deal with VPN pains?</p><p>I can’t answer all those questions, but I can help with easing some of the frustration.</p><h4>The New Solution: Cloud VPN service</h4><p>I’ve been successfully running a Cloud VPN service called <a href="https://wormhole.network/">Wormhole Network</a> for a while now. It has been promoted as an overlay networking solution, but it really excels at removing all the complexity present on a VPN solution. Why?</p><ul><li>You don’t need expensive hardware.</li><li>So you don’t need expensive support contracts.</li><li>Which means that you don’t need highly skilled staff to run it.</li><li>It uses well-known technologies like SSL and only needs outbound traffic permissions.</li><li>So it works out of the box!</li><li>And it doesn’t require you to change any firewalls configurations. Anywhere.</li><li>All traffic is encrypted using well-known standards.</li><li>You can control which servers join the network, regardless of their physical or logical location.</li><li>You can add servers with overlapping IP addresses and it still works as it should.</li></ul><p>All this <strong>out of the f*cking box.</strong> It is so amazing that you only need to sign up <strong>for free</strong>, create a hub (our lingo for <strong>network</strong>) in one of our servers, download the agent (<a href="http://www.softether.org/">SoftEther</a>!), download the configuration file, load it into the agent and you’re already connected. Actually, it’s even shorter with our <a href="https://wormhole.zendesk.com/hc/en-gb/articles/207287085-Connecting-a-Linux-server-to-your-hub">Linux autosetup script</a>.</p><p>It’s an extremely flexible solution. So flexible that I’ve worked on some concepts to <a href="https://github.com/pjperez/docker-wormhole">add multi-host networking to Docker containers</a>, create <a href="https://github.com/pjperez/docker-whminecraft">hidden Minecraft servers</a> and test network performance between Docker containers (<a href="https://github.com/pjperez/docker-iperfclient">Client </a>| <a href="https://github.com/pjperez/docker-iperfserver">Server</a>). <a href="https://wormhole.network/">Wormhole </a>also has <a href="https://github.com/WormholeNet/">an API under development</a>, so you can potentially join your servers to your network as soon as they’re deployed.</p><p>A multi-site VPN could look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_ntal65Iqr90SKZOR7BIBA.png" /><figcaption>The stuff nightmares are made of. Also known as potential clusterf*ck.</figcaption></figure><p>Configuring and maintaining multiple VPN links like the above is complex and costly, especially when remote access gets also in the mix with site to site links. The above also requires that [1] you have VPN hardware and [2] your cloud providers have compatible VPN hardware. As you can see, some VPS or bare metal servers could be left out of the equation if their provider can’t offer you a way of setting up a VPN with them.</p><p>Why don’t we make it easy?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*en3cfpQOKpB_j6fzCtKSgg.png" /><figcaption>Complexity? Gone!</figcaption></figure><p><em>Et voilà</em>! All the resources are on the same flat network. OK, that was a bit overkill, but it’s actually a scenario some customers like to have for management, like an out of band management network or an extended private LAN. You might prefer other scenarios, though.</p><p>Again, there’s no need to have VPN hardware, configure VPN software or deal with 3rd party teams to setup a tunnel. <a href="https://wormhole.network/"><strong>Wormhole </strong></a><strong>makes it transparent and removes all the complexity.</strong></p><p><a href="https://wormhole.network/">Try it now for free</a> and please let me know your thoughts by sending an e-mail to <em>pedro@wormhole.network</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4036a226298d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a product (III)]]></title>
            <link>https://medium.com/hackernoon/building-a-product-iii-74d2f737af7?source=rss-7f8f99b120e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/74d2f737af7</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[enterpreneurship]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Pedro Pérez]]></dc:creator>
            <pubDate>Sat, 06 Feb 2016 21:31:27 GMT</pubDate>
            <atom:updated>2016-02-06T21:31:27.773Z</atom:updated>
            <content:encoded><![CDATA[<h4>Unfreeze and iterate</h4><p>I was scared to show my minimum viable product (MVP) to the world. I was terrified to not get it right on the first try, and I had nightmares about not hitting bullseye on my first shot. Those feelings kept me from launching and pushed me to lie to myself. “It’s not ready, it’s not feature-complete” I thought, but then again I only wanted a minimum viable product. What’s the point of the MVP if it’s not minimum?</p><p>Some people had a look at it and recommended that I did this or that. They also suggested different features and why the current status of the product wasn’t mature. Of fucking course it’s not mature, it’s an MVP. You probably need 100x the money and 10x the time to get a mature product.</p><p>I showed my product to the world. I expected lots of traffic, emails to answer, architectures to scale and customers requesting more features. I was scared that I wouldn’t be able to cope with the sheer amount of work that was coming to me. I didn’t want to disappoint my users…</p><blockquote>but the world gave exactly zero flying fucks about my product. Oh boy.</blockquote><p>One, maybe two days of disappointment, then it clicked. Try again, try harder. Have another look at your proposal, have another look at your product. How is it perceived? Identify what does not work. Change it.</p><p>That was my new motivator. Learn why this didn’t work, learn to be on my customers’ shoes. Iterate, get better, improve.</p><blockquote>Success, even overnight success, doesn’t happen overnight.</blockquote><p>It requires effort and persistence. Work extra hard on getting your first users and learn from them. Knock on people’s doors. Approach them one by one.</p><p>When I was a kid, I remember I had this feeling where my friends and I would discover a new competitive game or video-game, and I’ll end up thinking I’ve ruined it because I learned how to win. I studied the game, I tried different tactics, tried to bend the rules, push them to the limit.</p><blockquote>Once a crack was found I will push and push until I just didn’t win but dominated. Then it wasn’t fun anymore.</blockquote><p>It didn’t work. What’s the point on clinging onto it? Carry on, get your next move ready, give it another shot. This time you’ll be wiser.</p><h4>“Building a product” series.</h4><p>I’m writing these articles as a way to record and share my learning, while I try to reinvent myself.</p><p>This is the third article in the series, and these are the two previous:</p><p><a href="https://medium.com/@pjperez/building-a-product-i-dc9232e92c65">Building a product (I) — Or how I’m moving from a job to a career</a></p><p><a href="https://medium.com/@pjperez/building-a-product-ii-a9f44bbbf04a">Building a product (II) — Riding the emotional roller-coaster while trying to define my product</a></p><p>These are part of my experiences while building <a href="https://wormhole.network/">Wormhole</a>, a cloud virtual networking solution that empowers you to extend your private networks between different cloud and hosting providers.</p><p>If you haven’t tried it yet, you should, it’s fucking awesome.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=74d2f737af7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/building-a-product-iii-74d2f737af7">Building a product (III)</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a product (II)]]></title>
            <link>https://medium.com/hackernoon/building-a-product-ii-a9f44bbbf04a?source=rss-7f8f99b120e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/a9f44bbbf04a</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Pedro Pérez]]></dc:creator>
            <pubDate>Sun, 31 Jan 2016 00:02:48 GMT</pubDate>
            <atom:updated>2016-02-06T21:32:26.530Z</atom:updated>
            <content:encoded><![CDATA[<h4>Riding the emotional roller-coaster while trying to define my product</h4><p>When you’re not an expert on a field, the fear of the unknown acts in funny ways. Sometimes you’re super excited because you don’t know how actually difficult it is to move forward, and in some other occasions you are extremely low on morale because you don’t know that it’s actually not that difficult.</p><p>That’s my emotional roller-coaster now.</p><p>I’m learning a lot, but oh boy! the disappointments are one after the other. The best thing though is that I’ve been able to overcome the feelings of despair and identified many of my mistakes. So here are some lessons for myself.</p><h4>Define your product</h4><p>I have started with a specific idea in mind. I would offer a service on top of an existing open source software. For that matter, I would build a web application that has to interface with several deployments of this software.</p><p>Does that tell you something? No, me either.</p><blockquote>If my own product doesn’t tell me anything, how can I sell it to anyone?</blockquote><p>You need to have a clear picture of what’s your product, and be able to define it in a sentence. Unfortunately I’m telling myself my product is too technical to be able to summarize. It also has so many possibilities that I couldn’t possibly choose one… but I have to, and even if it’s technical I still should be able to explain it. Those are only excuses to avoid the reality: I’m still not good at it.</p><p>It is important to have a definition of what you want to build. Only by <a href="https://medium.com/@pjperez/on-the-importance-of-knowing-where-are-you-going-317c870f9f9b#.sifv6rgwb">knowing where are you going</a> you will be able to choose your best path. If you have no goal, no final destination, you will steer around with no clear direction and under someone else’s command.</p><p>So here’s my current try at defining my product:</p><blockquote>Wormhole is a cloud virtual networking solution that simplifies your network and helps you save thousands on complex and costly VPN and MPLS solutions.</blockquote><p>Meh. I’m pretty sure it can be done better, but that’s my current best take. It’s not the first, but as I’ve steered from my initial target market, I had to also change my message.</p><p>How you define your product does actually pave the way for many other aspects of your product. E.g. What features should we include now? and which ones in the future?</p><p>Let’s imagine my product goes after enterprise customers — that implies that its main value should be “our product takes the risk from your and puts it on our lap”. On the other hand, small businesses and freelancers are more happy to shave a few thousand and risk eventual downtime of your service.</p><p>So not only defining your product will mark which features you should work on, but it also requires you to work on knowing your customers. It’s not enough to know how to reach them, you have to know what they want to hear.</p><h4>“Building a product” series.</h4><p>I’m writing these articles as a way to record and share my learning, while I try to reinvent myself.</p><p>This is the second article in the series, and this is the previous one:</p><p><a href="https://medium.com/@pjperez/building-a-product-i-dc9232e92c65">Building a product (I) — Or how I’m moving from a job to a career</a></p><p>These are part of my experiences while building <a href="https://wormhole.network/">Wormhole</a>, a cloud virtual networking solution that empowers you to extend your private networks between different cloud and hosting providers.</p><p>If you haven’t tried it yet, you should, it’s fucking awesome.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a9f44bbbf04a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/building-a-product-ii-a9f44bbbf04a">Building a product (II)</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a product (I)]]></title>
            <link>https://medium.com/@pjperez/building-a-product-i-dc9232e92c65?source=rss-7f8f99b120e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/dc9232e92c65</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Pedro Pérez]]></dc:creator>
            <pubDate>Mon, 25 Jan 2016 21:16:40 GMT</pubDate>
            <atom:updated>2016-01-25T21:16:40.866Z</atom:updated>
            <content:encoded><![CDATA[<h4>Or how I’m moving from a job to a career</h4><p>You work your ass off every day at the office while thinking about the future. Would I earn more or get more recognition? Does the company know my value?</p><p>The answers to the above questions of course vary from person to person and company to company, but in general terms the answer to the first one is “Yes, but less than you would like” and the second is “Probably yes, but you probably don’t know the value you have for your company”. Honestly, we tend to overvalue ourselves because we’re human and we want to be happy, but companies are not human. If they were human they would be dysfunctional psychopaths. Remember Scrooge? Well, he acted just like most companies do.</p><p>Our inability to realise the psychopathic nature of companies leads to frustration and burnout. We have to understand we are we standing to be able to choose were do we want to go.</p><p>Companies are stupid. All of them. Persons are clever, but companies are stupid and that’s why they appoint persons as CEOs and other decision-making positions and give them power.</p><blockquote>C level executives are people that either received training to take advantage of that or they managed to understand it all by themselves.</blockquote><p>How do these people take advantage of the situation? Well, as I’ve said above companies are stupid, so you have to act on consequence. Companies employ people to do what they want but can’t do, and what do companies want? Like Life, they want to grow and thrive. So, in other words, you were hired by your company to help it grow and thrive.</p><p>It doesn’t matter if you’re the smarter person in your company or the most knowledgeable. Well, it probably matters, but just up to a certain point. You don’t thrive inside a company by showing around your qualifications or beating your co-workers at the pub quiz. You thrive at a company when the company can get a good value ratio out of you. If you cost £100k, but the company thinks it can get £500k out of your work, you’re in a really good position. Unfortunately the ratio is not always that good, so you might be at the top of what the company wants to pay for your value.</p><h4>Choose between job or career</h4><p>We are all different, so not all of us have the same goals. While some are looking for a stable position where they feel safe, with the idea of enjoying the rest of their day building a family and living life in general, some others like the idea of growing their career, enjoy not only their free time but also their time at work. Even so, there are different ways of enjoying your work. I personally enjoy growing my career and improving my value ratio for my company, which implies being more valuable to my customers and my colleagues, too.</p><p>If growth keeps your mind busy, you’re building a career. If not, you are probably happy with having your current job and actually find that this article is irrelevant to your interests.</p><p>One of the tasks you have to set for yourself when you focus on growth is <a href="https://medium.com/@pjperez/on-the-importance-of-knowing-where-are-you-going-317c870f9f9b#.wbz6kx2ir">knowing where do you want to go</a>. Set yourself a goal, work towards something reachable and not towards Utopia. They say working to reach Utopia makes you advance, but it’s also devastatingly despairing. It also makes enjoying life more difficult, as you feel you have to keep working until you’ve reached the next checkpoint, so you end up using free time to keep working.</p><p>I had to think about my goals and where I want to be. I’ve changed my mind a few times during the last years or even months, but I’m now pretty sure I’d like to work on a product. Ultimately I would like to be responsible for a product’s failure or success. The problem is that I have little idea outside the technical sphere.</p><blockquote>There are constraints in life that will shape your career. Learn to embrace them and make the most out of it.</blockquote><p>I’ve got two challenges now. The first one is that I’ve got monthly expenses to cover like housing and food. Expenses that in all honesty I’m not happy to get rid of, as they are why I grow my career for. On the other hand, as I’ve mentioned I know very little about Product Management. I don’t know about you, but I get excited when there are challenges on my way, because I know there’s a morale boost at the end of the journey.</p><blockquote>Challenges require solutions, and solutions require action plans.</blockquote><p>My action plan is to learn Product Management by actually building a product. Why would a company trust my untested product management skills, if I don’t trust them myself? If I can be that good, why don’t I just go ahead and put those skills to work?</p><p>So here’s what I’m going to do. I’m going to build a product and on my journey I’m going to learn different aspects of Product Management. I’m going to gain experience and knowledge, and I’m going to spend my money to fund this product instead of paying for training.</p><p>Once I’ve built, launched and hopefully matured the product, I’ll add it to my CV and it’s going to be the single thing that’s going to get me new positions in the next 3 years.</p><p>I want to document my journey here. I might not go into full detail with everything I do, but at least I’d like to record my learnings so others can discuss them.</p><p>Who’s up for a similar challenge?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dc9232e92c65" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Securely connect VMs from different cloud providers]]></title>
            <link>https://medium.com/@pjperez/securely-connect-vms-from-different-cloud-providers-f62ce3bfe082?source=rss-7f8f99b120e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/f62ce3bfe082</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[vpn]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Pedro Pérez]]></dc:creator>
            <pubDate>Thu, 14 Jan 2016 21:03:19 GMT</pubDate>
            <atom:updated>2016-01-14T21:03:19.010Z</atom:updated>
            <content:encoded><![CDATA[<p>I have to admit I’ve struggled to get a title for this article. I know this is going to be useful to many people, but the more useful it is to you, the less chances I’ll get your attention with a technical description on the title.</p><p>This is mainly aimed at developers who have VMs or VPS on different providers. Some of you had to fight with complex VPN devices and solutions to connect one site to another, but the majority of you probably didn’t think about having your VM in DigitalOcean in the same network as another VM in Azure or AWS.</p><p>Why didn’t you think about it? Because it’s been fucking complex in the past. IPSec mostly sucks and very few people really fully understand the protocol (hint: I don’t); and I better not start talking about different vendor implementations.</p><p>Anyway, I’ve been working on a side project recently, specially after discovering a great open source software called <a href="http://www.softether.org/">SoftEther</a>. SoftEther is at first sight a VPN software made of different components (client, server, bridge). At second sight, it’s a whole lot of complexity put together and you run away from it, unless networking is your area of interest.</p><blockquote>My project has been to simplify this all, so it can be used by the people that don’t bother with this things <strong>but can really take advantage of it</strong>.</blockquote><p>I’m thinking about developers that need a service to make their work easier, but don’t want to spend days on setting up and maintaining complex VPN solutions or spend heaps of cash on expensive VPN hardware, maintenance contracts and networking contractors.</p><p>This is not a VPN from the service point of view. Technically it is — as I’m offering you a Virtual Private Network, but this goes a bit further than the typical VPN. It definitely falls into the SDN realm as it’s nothing more than software, running on multiple servers; some people would even call it SDN-WAN. All that is fine and dandy, but it doesn’t explain why you need itand how can it help you.</p><h3>Frontend in AWS and Backend in Azure? Why not?</h3><p>Maybe AWS gives you a better deal on egress traffic, or maybe you just like it more than any other, but Azure might have much better options for running DB servers. Careful, you probably don’t want to expose your DB servers to the world for your AWS servers to be able to reach them, or send those SQL queries over the Internet. <strong>You need encrypted communications and you need to reduce the attack surface by not exposing services.</strong></p><p>In the past you would have to go through the trauma of setting up a site to site VPN. That would take a few days (even when hiring external consultants) and then you could forget about it… Until it stopped working and you had no idea where to start looking because no one knows how this stuff really works.</p><h4>Calm. Take a deep breath. That can’t happen again, you’re safe now. I’m here to help.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*jaxD9Rpz4gOuc_r1r4ngxg.png" /><figcaption>Just like in SciFi culture, two technically isolated spaces are connected through a wormhole.</figcaption></figure><p>Come my side project, <a href="https://wormhole.network/">Wormhole Network</a>. Now you just need to create what we call <strong>a hub, </strong>which is how we refer to our virtual networks, and create <strong>one user</strong> in our system per each machine you’d like to connect to the hub. That can be done in about 30 seconds from our web interface.</p><p>Then you will download <a href="https://github.com/pjperez/wormholetools">our setup script from our public repo</a> and run it on every machine you wanted to be part of this network.</p><p><strong>That’s it.</strong></p><p>No configuration on any of the platforms, no troubleshooting, no cryptic firewall configurations. <strong>No complexity.</strong></p><p>Do you like how it sounds? <a href="https://wormhole.network/">Come over</a>, I’ve just opened doors.</p><p>I would say Wormhole Network is on a beta phase at the moment. It has its core features and some thorough testing behind, but now I’m just letting it go in the wild.</p><p>If you have any troubles, feel free to email me on pedro at wormhole.network or <a href="https://wormhole.zendesk.com/">open a case in our zendesk</a> if you need technical, architectural or any other kind of in-depth help.</p><p>Enjoy.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f62ce3bfe082" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SD-WAN made easy]]></title>
            <link>https://medium.com/@pjperez/simple-sd-wan-205a701e2c46?source=rss-7f8f99b120e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/205a701e2c46</guid>
            <category><![CDATA[vpn]]></category>
            <category><![CDATA[dns]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Pedro Pérez]]></dc:creator>
            <pubDate>Thu, 14 Jan 2016 19:52:48 GMT</pubDate>
            <atom:updated>2016-01-30T01:02:28.510Z</atom:updated>
            <content:encoded><![CDATA[<p>What is SD-WAN? Apparently, it means Software Defined WAN, and WAN stands for Wide Area Network.</p><p>We might say that SD-WAN is also probably a poor man’s MPLS, as it is a mean of privately connecting distributed points (servers, clients, full networks). Many SD-WAN solutions are technically overlay networks, which means that all the traffic inside that network is actually encapsulated on the physical network. In other words, you have a Virtual Private Network (sounds familiar?) with a twist.</p><p>I was wondering if there was a way I could have my own SD-WAN without deploying complex software, needing beefy servers or shelling enterprise-grade amounts of money. Of course there was :)</p><p>I’m using a software called <a href="http://www.softether.org/">SoftEther VPN</a> both on the client and server side of things. SoftEther is an <em>Open-Source Free ​Cross-platform Multi-protocol VPN Program</em> developed by the SoftEther VPN Project led by Daiyuu Nobori from the <a href="http://www.tsukuba.ac.jp/english/">University of Tsukuba, Japan</a>.</p><h4>Architecture</h4><p>The architecture is actually very simple. We just need a server reachable on port 443/TCP:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y1XifeRAYujJjL5IUAC6lg.png" /></figure><p>All the clients will connect to it, creating an overlay layer ethernet network between them. So the above diagram, will become this (if you can image the grey line is actually a layer 2 network :)):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jrmgj0-riniyElQp7tNUpg.png" /></figure><h4>Features</h4><ul><li><strong>Hole-punching through firewalls</strong>: The clients are only creating outgoing connections through port 443/TCP on your physical network, which is a port commonly open on many networks. If you can browse the Internet, you can use this.</li><li><strong>Layer 2 network</strong>: Freedom to build any IPv4 or IPv6 designs on top of the SD-WAN, even if your hosting provider doesn’t support it. Avoid complex networks managed by others and overly complex firewall configurations.</li><li><strong>Control which hosts join the network, one by one</strong>: Only hosts with the client software installed and the correct credentials can join the network.</li><li><strong>Distributed network</strong>: Every host could be on a different physical location, but you’ll see them all in the same network. Even if they move physical location, it will still look the same to you.</li><li><strong>Private and encrypted: </strong>An external observer will only see SSL traffic from the client to the central server, meanwhile in reality you are probably encapsulating multiple different protocols (HTTP, SQL, DNS, etc)</li></ul><h4>Use cases</h4><ul><li><strong>Managed Services Providers</strong> can deploy the client software on their customer’s servers, avoiding costly hardware and staff to configure and maintain IPSec tunnels. It will also increase their customer’s security, exposing zero extra services on the servers.</li><li><strong>Developers </strong>willing to have their workstation connected to their servers for testing, deployment and management. Avoid exposing services to be brute-forced or exploited by external attackers.</li><li><strong>DevOps </strong>willing to architect and run applications using different hosting and cloud providers, thus unlocking different cost saving possibilities by using the best resources from each provider.</li><li><strong>Distributed / Nomad</strong> companies could have an intranet with their own laptops and distributed servers, and privately share documents and other information in the encrypted network.</li></ul><h4>Technical complexity</h4><p>If you really understand the architecture, it’s really not that difficult to get this solution up and running. It requires some networking knowledge, especially on the server side, and a bit of common sense. There’s an excellent guide on <a href="https://www.digitalocean.com/">Digital Ocean</a>’s site called <a href="https://www.digitalocean.com/community/tutorials/how-to-setup-a-multi-protocol-vpn-server-using-softether">how to setup a multiprotocol VPN server using SoftEther</a>. It takes a while, but if you’re careful you can get it up and running.</p><p>Some of you out there might stop reading here and jump to get your own SD-WAN running, but for the rest of you I thought I could help further, so I created a service to take away all the burden from setting up and maintaining one of these systems. I’ve also worked on making it super easy to get your first Linux and Windows machines in your network… Ladies and gentlemen, please welcome…</p><h4>Wormhole Network</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wTQDtsMLmnXGH8fOPXrLWg.png" /><figcaption>The logo shows how two isolated spaces are seamlessly connected through a worm hole :)</figcaption></figure><p><a href="https://wormhole.network/">Wormhole Network</a> simplifies the process both on client and server side. The servers are setup and maintained by me, meanwhile you’ve got control over the networks you create and the users/machines that can join your networks. I’ve made it super easy to go from nothing to have your first machine in the network.</p><p>If you have any privacy concerns, I’d like to let you know that I’ve got zero visibility over your traffic and you’re isolated over other customers.</p><p>Those are not all the good news. I’ve made sure you can try how easy and convenient is to use this system, so I have a free tier of the service where you can create one network (inside Wormhole are called hubs). No credit card required or any other data apart from your email and a password (the name is optional).</p><p><a href="https://wormhole.network/">Try it now!</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=205a701e2c46" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stop giving a fuck and be fucking honest]]></title>
            <link>https://medium.com/@pjperez/stop-giving-a-fuck-and-be-fucking-honest-fba86abcfd51?source=rss-7f8f99b120e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/fba86abcfd51</guid>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[honesty]]></category>
            <category><![CDATA[life-lessons]]></category>
            <dc:creator><![CDATA[Pedro Pérez]]></dc:creator>
            <pubDate>Sun, 03 Jan 2016 19:23:51 GMT</pubDate>
            <atom:updated>2016-01-03T20:44:09.859Z</atom:updated>
            <content:encoded><![CDATA[<p>I’m quite happy with my current life. I’ve got a great job at an amazing company, an intelligent and beautiful partner in life and we’re expecting a baby boy. We still have gaps to cover, like settling in our own house in the future, but we’re overall satisfied and undoubtedly happy.</p><p>It wasn’t always like that. In my 33 years of life I’ve lived different lives and in those lives I’ve been different men. I’ve worked hard to reinvent myself after every iteration. I look back and I see a different me two years ago, and another one three years ago… I’ve been growing as a person, but it has been the last few years when I really made a leap and really improved myself on different levels.</p><p>These are just some thoughts on what I think helped me and might help you too.</p><h4>The lack of confidence will kill your dreams</h4><p>As harsh as it sounds, your dreams are dreams because you haven’t been able to make them a reality: Asking that person out, changing jobs for the one you really like, going on sabbatical to travel South America or jumping from a fucking plane. Does any of that resonate?</p><p>There are going to be many obstacles in your way to your dreams. Financial obstacles are quite common, but there’s one single problem we all face too often: Lack of confidence. This is what probably stopped you from pursuing many of your dreams.</p><p>It stops you telling that person what you think of them. It stops you looking for a career change when unhappy. It stops you going to the gym, putting on those clothes or even showing up at some events. We all know how it feels, we all have been there at some point.</p><p><em>If I only was more confident, I would’ve…</em></p><h4>Actually, confidence is not the main problem</h4><p>Well, let me tell you one thing. You’re wrong. We’ve been wrong all along. Your problem is not with confidence, your problem is with giving a fuck about what other people think.</p><p>Do you need any proof of that? Just look at yourself: Do you behave equally online in social media than in person? What about online with your real name vs a nickname no one can trace back to you? Of course you don’t, but you’re still the same insecure human, right? So, what has changed? What’s different? The consequences look different, but they would actually be the same regardless of your level of anonymity.</p><h4>So you’re afraid of the consequences</h4><p>Well, welcome to the biggest club on this planet.</p><p>Here’s the next revelation: Most people don’t give a flying fuck about you. So, clearly, most of the times it doesn’t matter what do you do or say. Especially if you’re not perceived as someone with power or some sort of local influencer / guru. Fuck consequences, because there are none.</p><p>Actually that’s not entirely true, but unless you’re some sort of politician or your job is actually dependant on what the general public thinks about you, it applies.</p><h4>Wait, what?</h4><p>Listen, I used to care a lot about what would happen if e.g. I said no to my boss. Then I used to get angry because other people would make career progress with perceived less hard work than I did, or so I thought! I became frustrated and rather sooner than later frustration led to anger and burnout, so eventually I decided to sit back and learn.</p><p>How did others progress? These were some of my learnings:</p><ul><li>Choose your battles wisely.</li><li>Make sure you’re around when it’s time to shine.</li><li>Say no when there’s nothing to win and too much to lose.</li><li>And more importantly, <strong>stop giving a fuck</strong>.</li></ul><p>As long as you have a manager, you have to be easy to manage. What many of us get wrong is that we think easy means saying yes to everything and that’s actually a huge mistake.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*F0ChkYmGH4z3KCD7zO2i3w.gif" /><figcaption>Can you relate to this poor chap?</figcaption></figure><p>Being easy to manage means being brutally honest with your manager. If she’s asking you something, that means she needs that information to help you further. Make it fucking easy and don’t lie to please her or her boss. Be polite, there’s no need to fucking swear :) but tell the truth.</p><h4>Honesty as a Service</h4><p>If you’re honest, you will build trust with your manager and actually establish a healthy working relationship. She will be able to help you further and you will be able to help the company further, meaning your value will increase.</p><p>Managers prefer you to say no to a request and find someone who is available than saying yes if you’re really not. Instead of solving a problem, your lie is just postponing your managers problem, so they’ll have to face it again when they’re out of time. Not funny, isn’t it?</p><h4>Team work</h4><p>I’m a very empathic person, so I easily get anxious when a customer is in trouble. I do technical support, so my stress levels can go easily through the roof every day; if it wasn’t because I’ve learned to stop giving so many fucks about every single thing. I’ve learned to stop thinking I have to fix everything.</p><p>I know my trade and I’m good at it. I help my customers with all my skills and experience, but there could be situations out of my reach. Time difference, the need for different skills or actually if I’m busy helping other customers are obstacles that I fought in the past. Those were my dragons and they made me anxious, frustrated and angry; now I just work around them and move on. Am I busy? Sorry can’t help you, reach out to the team. Not in my skill-set? Can’t help, but here’s someone who can. Do you work while I sleep? Nope, can’t help you buddy; but my mates on your time zone will lend you a helping hand.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*SLmMLeAj6AAYVFo1gTulpQ.png" /></figure><p>Of course some things can only be done if you’re part of a team, but if you’re not you might want to think if you really need to take on that much work by yourself. If the answer is no, then don’t take it. If the answer is yes, then think again because something else must be wrong.</p><blockquote>Team work means I can go home and don’t give a fuck about work, because someone else is taking care of it.</blockquote><p>That is so liberating that I completely became a different man. I stopped giving a fuck and there were no bad consequences, but actually the opposite. My customers were happier, I started delivering better quality and my value inside the company increased. I did so good that I was promoted and my salary was a 50% bigger after a year. I also changed jobs afterwards, as part of my global domination plan… I mean, career development plan.</p><p>If you were to stop giving a fuck, you could sit back, think about the problems and actually solve them. You would become a better asset for your company and customers and, more important, a more balanced person. You would also learn to enjoy your free time with your friends and family.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*glfICjlP6gQ1Gy5Rd6ESJg.jpeg" /></figure><p>You will never be a 100% confident person, but you won’t worry more than needed.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fba86abcfd51" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>