Archive

Category Archives for "Networking"

Evidence at the cost of trust: The trouble with the Department of Justice – DreamHost case

The social and economic benefits of the Internet cannot be realized without users’ ability to communicate and organize privately, and, where appropriate, anonymously. Data collection warrants must strike a balance to protect these benefits without impeding law enforcement’s ability to enforce the law. In recent weeks, the United States Department of Justice’s (DoJ) conflict with DreamHost, a website hosting service, has underscored the importance of this balance.

A week after the 2017 U.S. presidential inauguration, the DoJ issued a warrant to DreamHost to gather evidence for almost 200 cases related to violence that occurred during Inauguration Day protests. DreamHost had provided services to a website used to coordinate protests during the presidential inauguration.

The initial warrant was broad in scope; DreamHost stated that compliance would mean handing over records relating to 1.3 million IP addresses. This July, the DoJ went even further, issuing a new warrant asking for “Files, databases, and database records” regarding the website in question. DreamHost’s filing with the court specifies that the DoJ sought: the IP addresses of visitors to the website; which website pages were viewed by visitors; and a description of the software running on visitors’ computers.

The DoJ itself appears to Continue reading

NetDevOps: important idempotence

As more and more network engineers dive into network automation, the word idempotence keeps coming up. What is it? Why is it important? Why should we care? Idempotence is often described as the ability to perform the same task repeatedly and produce the same result. I want to demonstrate a super simple example of what this means.

If I am logged into a Linux box and want to add an IP address to the loopback address, I could use something simple like a sed command.

root@leaf01:mgmt-vrf:~# sed -i '/loopback/ a address 1.1.1.1/32' /etc/network/interfaces

This produces exactly what I want!
auto lo
iface lo inet loopback
        address 1.1.1.1/32
        address 10.0.0.11/32

I have appended the address 1.1.1.1/32 to the loopback interface stanza of the /etc/network/interfaces file. Now what happens if I run that same exact command again?

Running the command again produces the following output:
auto lo
iface lo inet loopback
        address 1.1.1.1/32
        address 1.1.1.1/32
        address 10.0.0.11/32

? That is not what I wanted. I performed the same task but instead of just leaving the file alone, since the 1.1.1. Continue reading

Evidence at the cost of trust: The trouble with the Department of Justice – DreamHost case

The social and economic benefits of the Internet cannot be realized without users’ ability to communicate and organize privately, and, where appropriate, anonymously. Data collection warrants must strike a balance to protect these benefits without impeding law enforcement’s ability to enforce the law. In recent weeks, the United States Department of Justice’s (DoJ) conflict with DreamHost, a website hosting service, has underscored the importance of this balance.

Mark Buell

This Mirai malware vaccine could protect insecure IoT devices

The hazard of unsophisticated and poorly secured Internet of Things (IoT) devices came to the front last year with the Mirai DDoS attack that involved nearly a million bots. Many of these devices remain a threat.Researchers have posed an original solution to the problem: Use the vulnerability of these devices to inject a white worm that secures the devices. It is an epidemiological approach that creates immunity with a vaccine by exposing the immune system to a weakened form of the disease.+ Also on Network World: How to improve IoT security + These devices are still a threat because some cannot be fixed because they have hard-coded back doors. Other insecure devices have software or firmware vulnerabilities that cannot be fixed because product designers did not include a software updates mechanism.To read this article in full or to leave a comment, please click here

This Mirai malware vaccine could protect insecure IoT devices

The hazard of unsophisticated and poorly secured Internet of Things (IoT) devices came to the front last year with the Mirai DDoS attack that involved nearly a million bots. Many of these devices remain a threat.Researchers have posed an original solution to the problem: Use the vulnerability of these devices to inject a white worm that secures the devices. It is an epidemiological approach that creates immunity with a vaccine by exposing the immune system to a weakened form of the disease.+ Also on Network World: How to improve IoT security + These devices are still a threat because some cannot be fixed because they have hard-coded back doors. Other insecure devices have software or firmware vulnerabilities that cannot be fixed because product designers did not include a software updates mechanism.To read this article in full or to leave a comment, please click here

RFC 8215: Local-Use IPv4/IPv6 Translation Prefix published

IPv6 BadgeRFC 8215 “Local-Use IPv4/IPv6 Translation Prefix” was recently published, reserving the IPv6 prefix 64:ff9b:1::/48 for local use within domains enabling IPv4/IPv6 translation mechanisms.

This allows the coexistence of multiple IPv4/IPv6 translation mechanisms in the same network, without requiring the use of a Network-Specific Prefix assigned from an allocated global unicast address space.

The well-known prefix 64:ff9b::/96 was originally reserved by RFC6052 for IPv4/IPv6 translation, but several new translation mechanisms such as those in RFCs 6146 and 7915 have subsequently been defined that target different use cases. It’s therefore possible that a network operator may wish to make use of several of these simultaneously, hence why a larger address space has been defined to accommodate this.

The shortest translation prefix being deployed in a live network was observed as being a /64, hence /48 was chosen as being on a 16-bit boundary whilst being able to accommodate multiple instances of /64.

If you’re interested in finding out more about IPv4/IPv6 translation mechanisms, there’s a few Deploy360 blogs on NAT64 and 464XLAT amongst others.

The post RFC 8215: Local-Use IPv4/IPv6 Translation Prefix published appeared first on Internet Society.

IDG Contributor Network: Seeing double: why IoT digital twins will change the face of manufacturing

If your organization is planning to leverage the Internet of Things (IoT) to gather data from products and systems, see how goods are performing in the field, enhance factory production, or any other reason, it needs to become familiar with the concept of the “digital twin.”A digital twin is a digital replica of a physical asset, process, or system that can be used for a variety of purposes. The digital representation of an object provides both the elements and the dynamics of how the object operates throughout its life cycle.The digital twin is intended to be an up-to-date and accurate replica of all elements of a physical object for which sensor data is available. Digital twins integrate technologies including artificial intelligence, machine learning, predictive analytics, and sensor telemetry to create digital clones of live and historical performance of physical machines and idealized digital simulation models that evolve based on the data collected from real-world instances.To read this article in full or to leave a comment, please click here

Abidjan Holds a Successful AfPIF 2017

Abidjan became the third West African city to hold the annual Africa Peering and Interconnection Forum (AfPIF), attracting top African and global players in the Internet ecosystem.

This year’s forum attracted 227 participants working in IXPs, ISPs, governments, content carriers, network providers, hardware providers, and software service providers among others. The meeting tool, which allows participants to discuss ways to exchange content, had 276 registered users who scheduled 170 meetings. Twenty networks introduced themselves during “Peering Introductions” session, held every day. This year there were 23 sponsors: Seacom, Liquid Telecom, Angonix, Angola Cables, De Cix, Linx, Adva, Afrinic, Akamai, Dolphin, Facebook, Flexoptix, France IX, Google, icolo.io, Main One, Netflix, Netnod, Yahoo, Medalion, MTN, Teraco, and ARTCI.

Getting more statistics

Research conducted by PCH reinforced the fact that most peering agreements have no formal agreement. The study done in 2016 found that 99 per cent of peering agreements in 148 countries were through a handshake. The study asked questions such as: are there formal agreements, is the peering arrangement symmetrical, is the content is IPv6 or IPv4, and what are the laws governing the agreement. Out of the 1,935,822 agreements, 49 percent comprised of matching peers, meaning it was easy Continue reading