Archive

Category Archives for "Networking"

IDG Contributor Network: Getting data center managers & C-Suite on the same page for DCIM implementation

In any enterprise – large and small – bottom-line ROI is arguably the biggest factor driving business decisions. Whether switching from PCs to Macs, investing in new travel and expense management software or integrating data center solutions, every business unit, from HR to sales and IT, must prove the value that new processes and offerings will have on the enterprises’ bottom line. The problem? Getting buy-in from all business groups, from the C-Suite on down, can be a serious undertaking often halting or ceasing potential implementation. When it comes to the data center, no one knows this better than data center managers who must work tirelessly with C-Suite to showcase the value and benefits of next generations data center software solutions.To read this article in full or to leave a comment, please click here

Docker features for handling Container’s death and resurrection

Docker containers provides an isolated sandbox for the containerized program to execute. One-shot containers accomplishes a particular task and stops. Long running containers runs for an indefinite period till it either gets stopped by the user or when the root process inside container crashes. It is necessary to gracefully handle container’s death and to make … Continue reading Docker features for handling Container’s death and resurrection →

3 real-world examples of IoT rolled out in the enterprise

Buying into IoT comes with a wealth of benefits, but adopting heavy use of the internet of things means more than plugging in devices and waiting for the data to pour in; it means modifying network infrastructure to accommodate them.This is not a trivial consideration. If the network doesn’t adequately support all aspects of IoT, a company may be unable to take advantage of all that data and will fail to realize the return on investment it was hoping for.+Related: Feds consider tougher requirements for IoT security;  IoT Security for Health Care is in critical condition; What is IoT?+To read this article in full or to leave a comment, please click here

Worth Reading: The Coco Block Chain

Today I am proud to introduce the Coco Framework, an open-source system that enables high-scale, confidential blockchain networks that meet all key enterprise requirements—providing a means to accelerate production enterprise adoption of blockchain technology. Coco achieves this by designing specifically for confidential consortiums, where nodes and actors are explicitly declared and controlled. Based on these requirements, Coco presents an alternative approach to ledger construction, giving enterprises the scalability, distributed governance and enhanced confidentiality they need without sacrificing the inherent security and immutability they expect. —Mark Russinovich @ Azure

The post Worth Reading: The Coco Block Chain appeared first on rule 11 reader.

IDG Contributor Network: WANs, tunnels and tags are things of the past

It is probably safe to assume that private networking has been an afterthought. In fact, the Internet Engineering Task Force (IETF) document (RFC 1918) that created private network addresses that are “un-routable” was released years after BGP-4 and IPV6 were codified into standards.In order to join private networks to each other, wide area networks (WANs) emerged. Initially, the benefits obtained by WANs were just pure connectivity. Subsequent benefits accrued, including the belief that private networks were secure because addresses of servers and clients in the private address could not be reached from the public network unless a “translation” or rule was established. This, however, may no longer be the case.To read this article in full or to leave a comment, please click here

IDG Contributor Network: WANs, tunnels and tags are things of the past

It is probably safe to assume that private networking has been an afterthought. In fact, the Internet Engineering Task Force (IETF) document (RFC 1918) that created private network addresses that are “un-routable” was released years after BGP-4 and IPV6 were codified into standards.In order to join private networks to each other, wide area networks (WANs) emerged. Initially, the benefits obtained by WANs were just pure connectivity. Subsequent benefits accrued, including the belief that private networks were secure because addresses of servers and clients in the private address could not be reached from the public network unless a “translation” or rule was established. This, however, may no longer be the case.To read this article in full or to leave a comment, please click here

IDG Contributor Network: WANs, tunnels and tags are things of the past

It is probably safe to assume that private networking has been an afterthought. In fact, the Internet Engineering Task Force (IETF) document (RFC 1918) that created private network addresses that are “un-routable” was released years after BGP-4 and IPV6 were codified into standards.In order to join private networks to each other, wide area networks (WANs) emerged. Initially, the benefits obtained by WANs were just pure connectivity. Subsequent benefits accrued, including the belief that private networks were secure because addresses of servers and clients in the private address could not be reached from the public network unless a “translation” or rule was established. This, however, may no longer be the case.To read this article in full or to leave a comment, please click here

Brazil needs to involve all stakeholders in Internet governance

Last week the Brazilian government, through the Ministry of Science, Technology, Innovation and Communication, launched an open consultation as part of a process for reviewing the current structure and mission of the Brazilian Internet Steering Committee, the CGI.Br. 

[Note: Portuguese version of this post included below.]

An evaluation and review of a Governance mechanism is natural and something that should not call the attention of anybody.  The particularity here is that the announcement was unexpected, showing that the criteria to be used, the objectives of the review, and the process itself were not done in a multistakeholder manner.

Mr. Raúl Echeberría

All you need to know about Unix environment variables

Simply put, environment variables are variables that are set up in your shell when you log in. They are called “environment variables” because most of them affect the way your Unix shell works for you. One points to your home directory and another to your history file. One identifies your mail file while another controls the colors that you see when you ask for a file listing. Still another sets up your default search path.If you haven’t examined your environment variables in a while, you might be surprised by how many of them are configured. An easy way to see how many have been established in your account is to run this command: $ env | wc -l 25 The env command (or printenv) will list all of the enviroment variables and their values. Here’s a sampling:To read this article in full or to leave a comment, please click here

1 … 1,663 1,664 1,665 1,666 1,667 … 3,444