The Datanauts leap into a discussion about cloud exchanges with guest Mark Thiele. They talk about what an exchange is and how it addresses common challenges such as latency.
The post Datanauts 020: Understanding Cloud Exchanges appeared first on Packet Pushers.
The Datanauts leap into a discussion about cloud exchanges with guest Mark Thiele. They talk about what an exchange is and how it addresses common challenges such as latency.
The post Datanauts 020 – Understanding Cloud Exchanges appeared first on Packet Pushers.
Generating revenue is a surefire way to increase the value and influence of your IT work in your organization. Here's 6 tips to help get you started.
The post 6 Ways IT Pros Can Generate Revenue appeared first on Packet Pushers.
Generating revenue is a surefire way to increase the value and influence of your IT work in your organization. Here's 6 tips to help get you started.
The post 6 Ways IT Pros Can Generate Revenue appeared first on Packet Pushers.
GIT is a distributed VCS (Version Control System). In a few words, this means that is a system that allows you to keep track of changes made to a file. The files are stored on a server and each contributor has a local copy of them. Most of the times it’s used when dealing with software development environments, because there is usually a team that works on the same set of files. If it weren’t for GIT (or any other similar tool) everyone would probably overwrite changes that everyone else did to the code and madness would break loose. Still, if you’re not a code developer, you can use GIT to help you keep track of your own files, changes, etc. and keep your head clean!
First time I ran into GIT I had absolutely no idea what it was. For some time, until I had the time to ding into it, I had a note with commands and “what does it do” for each command. This is a “don’t do it like this”-like story. Most definitely, it’s a mistake to take this path because you’ll get to the point where you’ll screw things up so badly Continue reading
If you read this blog on a regular basis, you probably use the little tool called SSH, especially its ubiquitous and most popular implementation OpenSSH.
Maybe you’re savvy enough to only use it with public/private keys, and therefore protect yourself from dictionary attacks. If you do then you know that in order to configure access to a new host, you need to make a copy of a public key available to that host (usually by writing it to its disk). Managing keys can be painful if you have many hosts, especially when you need to renew one of the keys. What if DNSSEC could help?
CC BY 2.0 image by William Neuheisel
With version 6.2 of OpenSSH came a feature that allows the remote host to retrieve a public key in a customised way, instead of the typical authorized_keys file in the ~/.ssh/ directory. For example, you can gather the keys of a group of users that require access to a number of machines on a single server (for example, an LDAP server), and have all the hosts query that server when they need the public key of the user attempting to log in. This saves Continue reading
This post will briefly discuss the challenges of manually setting up MPLS-TE tunnels and how Auto Tunnels can lessen the burden of MPLS-TE tunnels.
One of the main challenges with traffic engineering and MPLS-TE is the number of tunnels that will be needed. To setup tunnels between all PE’s may not be a scalable solution. For a provider with 200 PE’s, 199 tunnels would have to be configured on each PE and that is if only one traffic class is used. This would mean that 39800 tunnels would be present in the network. If you then want to add a tunnel for voice at each PE you end up with 398 tunnels per PE and a total of 79600 tunnels.
Another option is to enable tunnels only on the P routers. If the number of P routers are 20, then each P router would need 19 tunnels and we would have 380 tunnels in total or 760 if adding an extra tunnel for voice. This is a much more reasonable number. It would require to enable LDP over the tunnels if MPLS L3VPNs are in use to have an end to end LSP. With the P to P tunnels we Continue reading
Software-defined networking is associated with both management and orchestration, but doesn't really address management.
This post is my follow-up on a recent discussion on twitter.
Working for a VAR (Value Added Reseller) is not always the glamours life some make it out to be.
Working as a consultant, what you are really doing, is being the CEO of your own service company.
What you are selling, is basically your own services. The fact that your paycheck is being signed by someone else doesnt/shouldnt really matter.
The customer is building a relationship with you, as much as the company you are working for.
On top of that, you are continually building rapor in the networking world, so in my opinion, I would rather leave the customer with a good solution, rather than having to stick with the insane budgets that sales people end up shaving a project down to, just to get the contract.
So what can you do to create the outcome that is beneficial for all parties concerned (The customer, Your employer and yourself)?
Well, what I have tried in the past, is try and emphasize the importance of leaving the customer with the right solution based on his/her requirements and constraints. This discussion should involve both the technical side of things, as Continue reading
Carrier Ethernet gets some SDN/NFV love.
Last autumn’s SDN roadtrip left me totally exhausted – at the moment it’s so bad that I can’t push myself to work on non-urgent things – but there are some conferences are that so awesome that I wouldn’t skip them no matter what.
Troopers 16 (March 14th – 18th in Heidelberg, Germany) is a must-go-to security conference. Past events were fantastic, and when Enno Rey asked me what I’d like to talk about this year it wasn’t hard to come up with three interesting topics:
Read more ...
On the heels of Juniper's firewall incident, programmers spot a hole in FortiOS.