Author Archives: Russ
Author Archives: Russ
The post Worth Reading: The age of the GPU appeared first on 'net work.
A few of the papers, RFCs, and drafts I’m reading this week, along with a short description of each.
A Survey of Worldwide Censorship Techniques
draft-hall-censorship-tech-03
Censorship is a large problem on the Internet—but it’s often difficult to find any good description of the various ways censors can both find and block “offending” content. This draft is a short, readable overview of the various techniques actually seen in the wild, along with pointers to research about the techniques themselves, and instances where they’ve been used in the real world.
IPv6 Extension Headers and Packet Drops
draft-gont-v6ops-ipv6-ehs-in-real-world
One of the interesting features of IPv6 is its support for extension headers, which are variable length bits of information—metadata about the packet, for instance—that can be attached to a packet and processed by either the receiving host or forwarding devices along the way. Extension headers are useful, in that they allow IPv6 to be easily extended on the fly, rather than forcing the protocol designer to create a set of metadata “in stone.” Extension headers, however, are also controversial; how should an ASIC designer decide which ones to support in hardware, and how should extension headers that cannot be handled in hardware Continue reading
Deluged with an unprecedented amount of information available for analysis, companies in just about every industry are discovering increasingly sophisticated ways to make market observations, predictions and evaluations. Big Data can help companies make decisions ranging from which candidates to hire to which consumers should receive a special promotional offer. As a powerful tool for social good, Big Data can bring new opportunities for advancement to underserved populations, increase productivity and make markets more efficient. MarketWatch
The post Worth Reading: Big data and big trouble appeared first on 'net work.
The post Worth Reading: How to fight latency appeared first on 'net work.
The post Worth Reading: Windows WPAD attack appeared first on 'net work.
The post Worth Reading: IPv6 Link Local Addresses appeared first on 'net work.
Over my years as a network engineer, I’ve notice that the engineering job tends to be somewhat isolated (or isolating). Part of the reason is probably that there tend to be one or two network engineers at a single company, munged in with a lot of other IT folks who share some common ground (but not entirely), so there’s little chance to interact with others who are working on the same sorts of problem sets on a day to day basis. This tends to produce network engineers who are more attached to their vendor than they are to their “day job.” In fact, this tends to make the entire network engineering world, to the average network engineer, appear to be “not much more” than the vendors who show up on our doorsteps, the vendor specific trade shows we can attend, and what we read online. This is—how can I say this gently—??
This is an unhealthy situation for your career as a network engineer—and as a person.
What you need to do is build a network of other network engineers—a network network—so you can broaden your scope, keep your ear to the ground for changes, prepare for changes, have Continue reading
The post Worth Reading: Encryption is a red herring appeared first on 'net work.
The post Worth Reading: Privacy is disappearing appeared first on 'net work.
This week’s post was written by Johnny Britt over at FreedomPay. I’ve edited in some small places to add more information, etc., but I think Johnny needs to start blogging…
Once you have determined that AS-Path prepending can no longer help us what are our next steps? Routing is based on the longest matched prefix, this is true when BGP routes are being compared as well regardless of the AS-PATH. So one option you have is to split your address space into longer advertised prefixes and advertise a slice to each of our upstream providers. In Fig. 1, AS65000 splits its /44 IPv6 into 2 prefixes and advertises them out to AS65001 and AS65004 respectively. This forces half of AS65000 subnet traffic to flow inbound from one specific provider and we can combine both this technique and AS-Path prepending to give us more load sharing capabilities.
Using longer prefixes to direct traffic to a more preferred inbound link can take us a long way in creating the desired inbound traffic pattern. Sometimes there are scenarios where you may need to direct traffic at a more granular level.
But what if you don’t have the ability to create longer prefixes Continue reading
The post Worth Reading: Troubleshooting Cisco Remote Access appeared first on 'net work.
The post Worth Reading: Random number breakthrough appeared first on 'net work.
The post Worth Reading: Open Flow Tables and Vendor Hype appeared first on 'net work.
The post Worth Reading: Useful Utilities appeared first on 'net work.
The post Worth Reading: IP addresses are not telephone numbers appeared first on 'net work.
The post Worth Reading: Venezuela and ‘net Neutrality appeared first on 'net work.
The post Worth Reading: Automation, Robotics, and the Future appeared first on 'net work.
The Dynamic Host Configuration Protocol (DHCP) is widely used, and yet poorly understood. There are, in fact, a large number of options in DHCP—but before we get to these, let’s do a quick review of basic off-segment operation.
When the client, which has no IP address, sends out a request for configuration information, what happens? The Router, A, if it is configured to be a DHCP helper, will receive the packet and forward it to the DHCP server, which is presumably located someplace else in the network. The router generally knows what address to send the request to because of manual configuration—but how does the server know how to get the packet back to the original requester?
The helper—Router A in this case—inserts the IP address of the interface on which the request was received into the giaddr field of the DHCP packet. As boring as this might seem, this is where things actually get pretty interesting. It’s possible, of course, for a router to have an logical layer three interface that sits on a bridge group (or perhaps an IRB interface). The router obviously needs to be able to put more information in the DHCP request to handle this Continue reading
The post Worth Reading: DNS Privacy appeared first on 'net work.