This is a quick calculator I came up that I could use in the CCIE lab to translate between various IPv4 header QoS markings. As long as I could remember how to draw out the calculator, all I had to do was some basic math and I could translate between markings quite easily.
This post does not explain what the header fields are, why there’s so many or what the significance of one QoS value is over another. I’m making an assumption that the reader is already familiar with QoS concepts.
Here’s the calculator:
| x | x | x | x | x | x | x | x | |
|---|---|---|---|---|---|---|---|---|
| 128 | 64 | 32 | 16 | 8 | 4 | 2 | 1 | ToS |
| 32 | 16 | 8 | 4 | 2 | 1 | - | - | DSCP |
| 4 | 2 | 1 | 2 | 1 | - | - | - | DSCP AF values (AFxy) |
| 4 | 2 | 1 | - | - | - | - | - | IP Precedence |
| Enter 0 or 1 in each position |
Each column represents one bit from the Type of Service (ToS) field in the IPv4 header. The right-most column describes what each row is for. The very last row is meant to be filled in by us; it’s the input into the calculator.
As an example, let’s say we Continue reading
This vendor-written tech primer has been edited by Network World to eliminate product promotion, but readers should note it will likely favor the submitter’s approach.
All you have to do is read the headlines to know conventional IT security is failing. The number of security incidents among enterprises jumped 25% between 2011 and 2013, according to the 2014 PricewaterhouseCoopers “Global State of Information Security Survey.” And in the past 12 months, 96% of enterprises felt the sting of a cyberattack, according to the 2014 IDG Connect Cyber Defense Maturity Report.
The question is no longer if or when you will experience a significant security incident, but how well your processes and controls address detection, analysis and response. Without a real-time, independent and comprehensive view of endpoint status, organizations have an incomplete understanding of their IT risk, and it shows.
To read this article in full or to leave a comment, please click here
This vendor-written tech primer has been edited by Network World to eliminate product promotion, but readers should note it will likely favor the submitter’s approach.
Companies that sell products and services to consumers are collecting and storing massive volumes of customer data from not just POS, order management, customer service and e-commerce systems, but also mobile apps, social media feeds, online campaign forms and Web applications such as lead enrichment databases. As a result, new types of identity management systems have emerged to address the broader scale and risk of Web-based business processes and to give customers more control regarding how corporations use their data.
To read this article in full or to leave a comment, please click here
I bought a nearly new Snom IP phone on eBay, but it was getting autoprovisioned as a Vodafone device. I wanted to use it as a SIP phone on another provider’s network, so needed to get rid of this.
I’ll try to write down the steps I followed, but I tried quite a few things so there may be inaccuracies.
Basically this phone tries three ways to autoprovision itself:
1. Redirection – it goes to a host run by Snom, is redirected to a Vodafone host and autoprovisions from there.
2. PnP – I think this is where it multicasts for a configuration server.
3. DHCP – where it receives details of the configuraiton server from DHCP options it receives with its IP address.
Redirection is the first one it tries by default, so you need to stop this happening. Snom say on their forums that they can’t do this for Vodafone devices, which must be a legal thing between them and Vodafone, because they are able to do it for Snom phones that are auto-provisioned on other providers. In the latter case a simple request on the forums with the phone’s MAC address appears to be sufficient.