VSCP & Friends Presentation Eindhoven
•Download as ODP, PDF•
0 likes•4,184 views
VSCP is a lightweight framework for IoT and M2M devices that includes a control protocol, tools, libraries, and autonomous node functionality. It allows for uniform unit discovery, configuration, data presentation, and firmware updates. The framework is designed to run on low-end hardware and supports many communication methods. It provides libraries and tools like VSCP Works for debugging and a lightweight daemon for a TCP/IP interface. The overall goal of VSCP is to make it easy to integrate smart devices in a common and scalable way.
Report
Share
Report
Share
Recommended
One to unite them all
This document introduces VSCP, an open framework for IoT and M2M devices that aims to provide:
1) A universal way to discover devices using globally unique IDs.
2) A common way to configure devices using a standardized register model.
3) A method for devices to interact and automatically react to information from each other.
4) A standardized way to remotely update firmware on all devices.
The framework also allows devices to communicate using many different protocols and aims to solve problems of inconsistent data formats, limited interoperability between devices, and dependence on single suppliers or protocols.
A black box gift for x-mas
The document describes a protocol called VSCP (Very Simple Control Protocol) that was created in 2000 to allow Internet of Things devices to communicate with each other regardless of differences in hardware or communication methods. VSCP defines common properties like identifiers and descriptions that each device must have to identify itself and share information. It also establishes standard ways for devices to send events, read/write properties, and update firmware over different connection types so that all IoT things can interact in a consistent, machine-readable manner. The goal was to make communication very simple for low-powered devices while providing an extensible framework.
Iot with-the-best & VSCP
The document discusses the Internet of Things (IoT) and how the Very Simple Control Protocol (VSCP) provides a standardized way to connect IoT devices. VSCP defines common formats for device discovery, messaging, configuration via registers, firmware updates, and security. It aims to abstract away device differences and provide interoperability through open specifications and tools like the VSCP daemon and VSCP Works for configuration and monitoring.
DEF CON 27 - NICOLAS OBERLI - poking the s in sd cards
This document discusses vulnerabilities in the password protection mechanism of some SD memory cards. It describes how SD cards implement password locking via the CMD42 command. On some cards from manufacturers like Transcend and Hama, the timing of the password verification process can be measured to determine individual password bytes via a side-channel attack. The document demonstrates this attack in practice and finds that cards from Sandisk were not vulnerable to this timing analysis approach. It concludes that while the vulnerability may not be very practical, it affects cards from several manufacturers.
Rig nitc [autosaved] (copy)
This document provides an overview of a workshop on basic robotics and embedded systems simulation. It discusses microcontrollers and some popular models like the AVR ATmega16. It describes the ATmega16's features like memory, I/O ports, timers and interfaces. It also explains concepts like I/O registers, binary-hexadecimal conversion, and using embedded C to code for the microcontroller. Examples provided include blinking an LED, pulse width modulation for LED contrast control, and motor speed control.
4a mdc-planificacin-1-161205221513
Este documento presenta el plan de estudios semestral para la asignatura de Informática en el cuarto nivel de la carrera de Medicina. La asignatura se extenderá de octubre de 2016 a marzo de 2017 e incluirá seis unidades temáticas sobre informática y software de oficina como Excel y Word. Habrá tres pruebas parciales y varias actividades virtuales evaluadas durante el semestre.
Ake hedman why we need to unite and why vscp is a solution to a problem
The world is «many», not «one», and it will always will be that way. Just as different cars drive on the same side of the road and adhere to the same rules, protocols and solutions in IoT and M2M must come to understandings that make them work beside each other and together.
What we see today is efforts on standardizing the «roads» while we really need to standardize on how we «travel» on them. This is really no different then what HTML did for hypertext in the past and which made the world wide web a success.
To take an example a temperature sent from a device must always be understood by a receiving device to be useful for it, which means it's coding and its unit must be coded in a standard way. Obvious to us all maybe, but not something the IoT/M2M standardizing groups work with today.
VSCP have solution for this and for device discovery, uniform configuration, self contained and serverless functionality, firmware updates and is free and open and will stay that way. It works equally well if communication is through a cable or over the air and it makes sure that the sender and the receiver understands each other.
In this presentation, Ake will pinpoint the problems and the trends and present one possible solution to the problem.
Åke Hedman, Maintainer, VSCP | Founder, Paradise of the Frog
Things You MUST Know Before Deploying OpenStack: Bruno Lago, Catalyst IT
Audience: Advanced
About: Real world lessons and war stories about Catalyst IT’s experience in rolling out an OpenStack based public cloud in New Zealand.
This presentation will provide tips and advice that may save you a lot of time, money and nights of sleep if you are planning to run OpenStack in the future. It may also bring some insights to people that are already running OpenStack in production.
Topics covered will include: selection of hardware for optimal costs, techniques that drive quality and service levels up, common deployment mistakes, in place upgrades, how to identify the maturity level of each project and decide what is ready for production, and much more!
Speaker Bio: Bruno Lago – Entrepreneur, Catalyst IT Limited
Bruno Lago is a solutions architect that has been involved with the Catalyst Cloud (New Zealand’s first public cloud based on OpenStack) from its inception. He is passionate about open source software, cloud computing and disruptive technologies.
OpenStack Australia Day - Sydney 2016
https://events.aptira.com/openstack-australia-day-sydney-2016/
Recommended
One to unite them all
This document introduces VSCP, an open framework for IoT and M2M devices that aims to provide:
1) A universal way to discover devices using globally unique IDs.
2) A common way to configure devices using a standardized register model.
3) A method for devices to interact and automatically react to information from each other.
4) A standardized way to remotely update firmware on all devices.
The framework also allows devices to communicate using many different protocols and aims to solve problems of inconsistent data formats, limited interoperability between devices, and dependence on single suppliers or protocols.
A black box gift for x-mas
The document describes a protocol called VSCP (Very Simple Control Protocol) that was created in 2000 to allow Internet of Things devices to communicate with each other regardless of differences in hardware or communication methods. VSCP defines common properties like identifiers and descriptions that each device must have to identify itself and share information. It also establishes standard ways for devices to send events, read/write properties, and update firmware over different connection types so that all IoT things can interact in a consistent, machine-readable manner. The goal was to make communication very simple for low-powered devices while providing an extensible framework.
Iot with-the-best & VSCP
The document discusses the Internet of Things (IoT) and how the Very Simple Control Protocol (VSCP) provides a standardized way to connect IoT devices. VSCP defines common formats for device discovery, messaging, configuration via registers, firmware updates, and security. It aims to abstract away device differences and provide interoperability through open specifications and tools like the VSCP daemon and VSCP Works for configuration and monitoring.
DEF CON 27 - NICOLAS OBERLI - poking the s in sd cards
This document discusses vulnerabilities in the password protection mechanism of some SD memory cards. It describes how SD cards implement password locking via the CMD42 command. On some cards from manufacturers like Transcend and Hama, the timing of the password verification process can be measured to determine individual password bytes via a side-channel attack. The document demonstrates this attack in practice and finds that cards from Sandisk were not vulnerable to this timing analysis approach. It concludes that while the vulnerability may not be very practical, it affects cards from several manufacturers.
Rig nitc [autosaved] (copy)
This document provides an overview of a workshop on basic robotics and embedded systems simulation. It discusses microcontrollers and some popular models like the AVR ATmega16. It describes the ATmega16's features like memory, I/O ports, timers and interfaces. It also explains concepts like I/O registers, binary-hexadecimal conversion, and using embedded C to code for the microcontroller. Examples provided include blinking an LED, pulse width modulation for LED contrast control, and motor speed control.
4a mdc-planificacin-1-161205221513
Este documento presenta el plan de estudios semestral para la asignatura de Informática en el cuarto nivel de la carrera de Medicina. La asignatura se extenderá de octubre de 2016 a marzo de 2017 e incluirá seis unidades temáticas sobre informática y software de oficina como Excel y Word. Habrá tres pruebas parciales y varias actividades virtuales evaluadas durante el semestre.
Ake hedman why we need to unite and why vscp is a solution to a problem
The world is «many», not «one», and it will always will be that way. Just as different cars drive on the same side of the road and adhere to the same rules, protocols and solutions in IoT and M2M must come to understandings that make them work beside each other and together.
What we see today is efforts on standardizing the «roads» while we really need to standardize on how we «travel» on them. This is really no different then what HTML did for hypertext in the past and which made the world wide web a success.
To take an example a temperature sent from a device must always be understood by a receiving device to be useful for it, which means it's coding and its unit must be coded in a standard way. Obvious to us all maybe, but not something the IoT/M2M standardizing groups work with today.
VSCP have solution for this and for device discovery, uniform configuration, self contained and serverless functionality, firmware updates and is free and open and will stay that way. It works equally well if communication is through a cable or over the air and it makes sure that the sender and the receiver understands each other.
In this presentation, Ake will pinpoint the problems and the trends and present one possible solution to the problem.
Åke Hedman, Maintainer, VSCP | Founder, Paradise of the Frog
Things You MUST Know Before Deploying OpenStack: Bruno Lago, Catalyst IT
Audience: Advanced
About: Real world lessons and war stories about Catalyst IT’s experience in rolling out an OpenStack based public cloud in New Zealand.
This presentation will provide tips and advice that may save you a lot of time, money and nights of sleep if you are planning to run OpenStack in the future. It may also bring some insights to people that are already running OpenStack in production.
Topics covered will include: selection of hardware for optimal costs, techniques that drive quality and service levels up, common deployment mistakes, in place upgrades, how to identify the maturity level of each project and decide what is ready for production, and much more!
Speaker Bio: Bruno Lago – Entrepreneur, Catalyst IT Limited
Bruno Lago is a solutions architect that has been involved with the Catalyst Cloud (New Zealand’s first public cloud based on OpenStack) from its inception. He is passionate about open source software, cloud computing and disruptive technologies.
OpenStack Australia Day - Sydney 2016
https://events.aptira.com/openstack-australia-day-sydney-2016/
Composing services with Kubernetes
1. Kubernetes services can be used to abstract external dependencies like databases and SaaS services, decoupling consumers from providers.
2. For databases, a service allows using a single-instance container database in test environments instead of a production cluster, without consumers needing different configurations.
3. For SaaS services, an ExternalName service type maps the service to the real URL in production but to a virtualization pod in tests, providing fake responses without consumers knowing.
IoT Story: From Edge to HDP
In order to share the project experience on IoT architecture and to make the project successful, we will explain the key points to be a hint from the practical experience point to avoid common common pitfalls in the IoT related project .
Building a Small DC
Building a Small DC, by Karl Brumund.
A presentation given at APRICOT 2016’s Network Infrastructure session on 24 February 2016.
Building a Small Datacenter
1. The document discusses building a small data center network for Dyn, focusing on lessons learned from two design iterations.
2. The first design used MPLS VPNs but had issues with routing and IPv6 support. The second design used virtual routing and forwarding with multiple routing tables to separate traffic and improve service mobility.
3. Key lessons included validating designs before deploying, automating network operations, and moving security policies to instances rather than the network to improve agility and isolate impacts.
A Kernel of Truth: Intrusion Detection and Attestation with eBPF
"Attestation is hard" is something you might hear from security researchers tracking nation states and APTs, but it's actually pretty true for most network-connected systems!
Modern deployment methodologies mean that disparate teams create workloads for shared worker-hosts (ranging from Jenkins to Kubernetes and all the other orchestrators and CI tools in-between), meaning that at any given moment your hosts could be running any one of a number of services, connecting to who-knows-what on the internet.
So when your network-based intrusion detection system (IDS) opaquely declares that one of these machines has made an "anomalous" network connection, how do you even determine if it's business as usual? Sure you can log on to the host to try and figure it out, but (in case you hadn't noticed) computers are pretty fast these days, and once the connection is closed it might as well not have happened... Assuming it wasn't actually a reverse shell...
At Yelp we turned to the Linux kernel to tell us whodunit! Utilizing the Linux kernel's eBPF subsystem - an in-kernel VM with syscall hooking capabilities - we're able to aggregate metadata about the calling process tree for any internet-bound TCP connection by filtering IPs and ports in-kernel and enriching with process tree information in userland. The result is "pidtree-bcc": a supplementary IDS. Now whenever there's an alert for a suspicious connection, we just search for it in our SIEM (spoiler alert: it's nearly always an engineer doing something "innovative")! And the cherry on top? It's stupid fast with negligible overhead, creating a much higher signal-to-noise ratio than the kernels firehose-like audit subsystems.
This talk will look at how you can tune the signal-to-noise ratio of your IDS by making it reflect your business logic and common usage patterns, get more work done by reducing MTTR for false positives, use eBPF and the kernel to do all the hard work for you, accidentally load test your new IDS by not filtering all RFC-1918 addresses, and abuse Docker to get to production ASAP!
As well as looking at some of the technologies that the kernel puts at your disposal, this talk will also tell pidtree-bcc's road from hackathon project to production system and how focus on demonstrating business value early on allowed the organization to give us buy-in to build and deploy a brand new project from scratch.
DevSecCon London 2019: A Kernel of Truth: Intrusion Detection and Attestation...
Matt Carroll
Infrastructure Security Engineer at Yelp
"Attestation is hard" is something you might hear from security researchers tracking nation states and APTs, but it's actually pretty true for most network-connected systems!
Modern deployment methodologies mean that disparate teams create workloads for shared worker-hosts (ranging from Jenkins to Kubernetes and all the other orchestrators and CI tools in-between), meaning that at any given moment your hosts could be running any one of a number of services, connecting to who-knows-what on the internet.
So when your network-based intrusion detection system (IDS) opaquely declares that one of these machines has made an "anomalous" network connection, how do you even determine if it's business as usual? Sure you can log on to the host to try and figure it out, but (in case you hadn't noticed) computers are pretty fast these days, and once the connection is closed it might as well not have happened... Assuming it wasn't actually a reverse shell...
At Yelp we turned to the Linux kernel to tell us whodunit! Utilizing the Linux kernel's eBPF subsystem - an in-kernel VM with syscall hooking capabilities - we're able to aggregate metadata about the calling process tree for any internet-bound TCP connection by filtering IPs and ports in-kernel and enriching with process tree information in userland. The result is "pidtree-bcc": a supplementary IDS. Now whenever there's an alert for a suspicious connection, we just search for it in our SIEM (spoiler alert: it's nearly always an engineer doing something "innovative")! And the cherry on top? It's stupid fast with negligible overhead, creating a much higher signal-to-noise ratio than the kernels firehose-like audit subsystems.
This talk will look at how you can tune the signal-to-noise ratio of your IDS by making it reflect your business logic and common usage patterns, get more work done by reducing MTTR for false positives, use eBPF and the kernel to do all the hard work for you, accidentally load test your new IDS by not filtering all RFC-1918 addresses, and abuse Docker to get to production ASAP!
As well as looking at some of the technologies that the kernel puts at your disposal, this talk will also tell pidtree-bcc's road from hackathon project to production system and how focus on demonstrating business value early on allowed the organization to give us buy-in to build and deploy a brand new project from scratch.
Add sale davinci
This document discusses embedded software development and image processing using the TI DaVinci platform. It provides an overview of the DaVinci SOC which includes both a GPP and DSP. It describes installing the necessary toolchain and software, setting up an NFS server, building the Linux kernel, cross-compiling programs, and provides an example of a simple image zooming application.
OVS and DPDK - T.F. Herbert, K. Traynor, M. Gray
The document discusses DPDK and software dataplane acceleration for Open vSwitch. It provides an overview of the OVS architecture and its evolution to integrate with DPDK. It shares one user's experience of initial challenges in using DPDK/OVS and improvements over time. Suggestions are made to improve areas like debugging, testing, documentation and training to enhance the usability of DPDK/OVS. Performance tuning techniques like using multiple threads are also briefly covered.
The internet of $h1t
I was asked to talk in front of Computer science students at the Bar-Ilan university about "what happens" when you don't care about writing "secured" or "safe" code. A perfect example for that, in my opinion, was the world of embedded computing AKA the IoT. I talked about the history of consumer embedded devices and showed a live demo of an 0day I found in one of the most popular routers in the country.
The advantages of Arista/OVH configurations, and the technologies behind buil...
Arista will put an emphasis on the technologies behind building and operating datacentres, and the reasons they give the results expected from them (varied traffic spike management, increasing bandwidth, end points and security), including very large-scale production environments.
SDN & NFV Introduction - Open Source Data Center Networking
This document introduces software defined networking (SDN) and network functions virtualization (NFV) concepts. It discusses challenges with traditional networking and how SDN and NFV address these by decoupling the control and data planes, centralizing network intelligence, and abstracting the underlying network infrastructure. It then provides examples of open source SDN technologies like OpenDaylight, Open vSwitch, and OpenStack that can be used to build programmable software-defined networks and virtualized network functions.
Network Virtualization & Software-defined Networking
This document introduces software defined networking (SDN) and network functions virtualization (NFV) concepts. It discusses challenges with traditional networking and how SDN and NFV address these by decoupling the control and data planes, making the network programmable through APIs, and virtualizing network functions. It then provides examples of open source SDN platforms like OpenDaylight, Open vSwitch, and OpenStack that enable building virtual networks and service chains.
Mellanox Approach to NFV & SDN
Presented by Eran Bello at the "NFV & SDN Summit" held March 2014 in Paris, France
Ideal for Cloud DataCenter, Data Processing Platforms and Network Functions Virtualization
Leading SerDes Technology: High Bandwidth – Advanced Process
10/40/56Gb VPI with PCIe 3.0 Interface
10/40/56Gb High Bandwidth Switch: 36 ports of 10/40/56Gb or 64 ports of 10Gb
RDMA/RoCE technology: Ultra Low Latency Data Transfer
Software Defined Networking: SDN Switch and Control End to End Solution
Cloud Management: OpenStack integration
Paving the way to 100Gb/s Interconnect
End to End Network Interconnect for Compute/Processing and Switching
Software Defined Networking
High Bandwidth, Low Latency and Lower TCO: $/Port/Gb
Introduction to WAMP, a protocol enabling PUB/SUB and RPC over Websocket
WAMP.ws is a powerful and flexible technology, but still misunderstood. These slides answer the most common questions.
Pluggable Infrastructure with CI/CD and Docker
The docker cluster ecosystem is still young, and highly modular. This presentation covers some of the challenges we faced deciding on what infrastructure to deploy, and a few tips and tricks in making both applications and infrastructure easily adaptable.
Network Automation - Interconnection tools
This document discusses tools for automating network interconnection and capacity planning decisions. It describes the complexity of manual processes and how automation can help by providing consistency, speed, ease of support, and compliance. NETCONF is presented as a standard for automating device configuration. Automating common tasks like adding ports and BGP sessions can help provision capacity based on traffic data. Total pluggability of providers is suggested to further streamline automation.
AnsibleFest 2019 - Greenfielding Network and Systems Automation in a Large an...
The year is 2019 and New York City has a very large public wifi and cellular network on the subway platforms and stations, however, it's all manually configured and maintained. This means we have carte blanche control over what and how we automate it. This talks aims to describe what it takes to bring automation to a network with over 15,000 devices and millions of daily users, including all of the pitfalls that came with it.
Monkey Server
Eduardo Silva is an open source engineer at Treasure Data working on projects like Fluentd and Fluent Bit. He created the Monkey HTTP server, which is optimized for embedded Linux and has a modular plugin architecture. He also created Duda I/O, a scalable web services stack built on top of Monkey using a friendly C API. Both projects aim to provide lightweight, high performance solutions for collecting and processing data from IoT and embedded devices.
Experiences with Microservices at Tuenti
Talk presented by Aarón Fas & Andrés Viedma at the JBcnConf 2015.
'Microservices' is one of the most popular buzzwords in the industry now, but are they really a step forward? Or they might be more a problem than a solution? When are they really helpful? How should they be addressed? What challenges will we face if we decide to implement a microservices based architecture?
One year ago, Tuenti moved from a monolithic PHP backend to a Java + PHP microservices architecture. In this talk, we'll share our experiences so far: how we addressed the change, how we implemented it, why we think it's been valuable for us (and how is that related to the company culture), why it might not be a good idea for your company / application and, mostly, what lessons we have learned from this experience.
Iot vupico-damien-contreras-2018-05-17-light-v3
Presentation used during SAP Tech days 2018 in Tokyo during a joint presentation between Hortonworks & Vupico represented by myself, what to think when implementing an IoT strategy. Why use Fog / Edge computing, showcased in a fun use case that I built: a cocktail machine built using raspberry pies with AndroidThings, cameras, TensorFlow lite, Mobilenet 1.0, peristaltic pumps and orchestrated by NiFi.
More Related Content
Similar to VSCP & Friends Presentation Eindhoven
Composing services with Kubernetes
1. Kubernetes services can be used to abstract external dependencies like databases and SaaS services, decoupling consumers from providers.
2. For databases, a service allows using a single-instance container database in test environments instead of a production cluster, without consumers needing different configurations.
3. For SaaS services, an ExternalName service type maps the service to the real URL in production but to a virtualization pod in tests, providing fake responses without consumers knowing.
IoT Story: From Edge to HDP
In order to share the project experience on IoT architecture and to make the project successful, we will explain the key points to be a hint from the practical experience point to avoid common common pitfalls in the IoT related project .
Building a Small DC
Building a Small DC, by Karl Brumund.
A presentation given at APRICOT 2016’s Network Infrastructure session on 24 February 2016.
Building a Small Datacenter
1. The document discusses building a small data center network for Dyn, focusing on lessons learned from two design iterations.
2. The first design used MPLS VPNs but had issues with routing and IPv6 support. The second design used virtual routing and forwarding with multiple routing tables to separate traffic and improve service mobility.
3. Key lessons included validating designs before deploying, automating network operations, and moving security policies to instances rather than the network to improve agility and isolate impacts.
A Kernel of Truth: Intrusion Detection and Attestation with eBPF
"Attestation is hard" is something you might hear from security researchers tracking nation states and APTs, but it's actually pretty true for most network-connected systems!
Modern deployment methodologies mean that disparate teams create workloads for shared worker-hosts (ranging from Jenkins to Kubernetes and all the other orchestrators and CI tools in-between), meaning that at any given moment your hosts could be running any one of a number of services, connecting to who-knows-what on the internet.
So when your network-based intrusion detection system (IDS) opaquely declares that one of these machines has made an "anomalous" network connection, how do you even determine if it's business as usual? Sure you can log on to the host to try and figure it out, but (in case you hadn't noticed) computers are pretty fast these days, and once the connection is closed it might as well not have happened... Assuming it wasn't actually a reverse shell...
At Yelp we turned to the Linux kernel to tell us whodunit! Utilizing the Linux kernel's eBPF subsystem - an in-kernel VM with syscall hooking capabilities - we're able to aggregate metadata about the calling process tree for any internet-bound TCP connection by filtering IPs and ports in-kernel and enriching with process tree information in userland. The result is "pidtree-bcc": a supplementary IDS. Now whenever there's an alert for a suspicious connection, we just search for it in our SIEM (spoiler alert: it's nearly always an engineer doing something "innovative")! And the cherry on top? It's stupid fast with negligible overhead, creating a much higher signal-to-noise ratio than the kernels firehose-like audit subsystems.
This talk will look at how you can tune the signal-to-noise ratio of your IDS by making it reflect your business logic and common usage patterns, get more work done by reducing MTTR for false positives, use eBPF and the kernel to do all the hard work for you, accidentally load test your new IDS by not filtering all RFC-1918 addresses, and abuse Docker to get to production ASAP!
As well as looking at some of the technologies that the kernel puts at your disposal, this talk will also tell pidtree-bcc's road from hackathon project to production system and how focus on demonstrating business value early on allowed the organization to give us buy-in to build and deploy a brand new project from scratch.
DevSecCon London 2019: A Kernel of Truth: Intrusion Detection and Attestation...
Matt Carroll
Infrastructure Security Engineer at Yelp
"Attestation is hard" is something you might hear from security researchers tracking nation states and APTs, but it's actually pretty true for most network-connected systems!
Modern deployment methodologies mean that disparate teams create workloads for shared worker-hosts (ranging from Jenkins to Kubernetes and all the other orchestrators and CI tools in-between), meaning that at any given moment your hosts could be running any one of a number of services, connecting to who-knows-what on the internet.
So when your network-based intrusion detection system (IDS) opaquely declares that one of these machines has made an "anomalous" network connection, how do you even determine if it's business as usual? Sure you can log on to the host to try and figure it out, but (in case you hadn't noticed) computers are pretty fast these days, and once the connection is closed it might as well not have happened... Assuming it wasn't actually a reverse shell...
At Yelp we turned to the Linux kernel to tell us whodunit! Utilizing the Linux kernel's eBPF subsystem - an in-kernel VM with syscall hooking capabilities - we're able to aggregate metadata about the calling process tree for any internet-bound TCP connection by filtering IPs and ports in-kernel and enriching with process tree information in userland. The result is "pidtree-bcc": a supplementary IDS. Now whenever there's an alert for a suspicious connection, we just search for it in our SIEM (spoiler alert: it's nearly always an engineer doing something "innovative")! And the cherry on top? It's stupid fast with negligible overhead, creating a much higher signal-to-noise ratio than the kernels firehose-like audit subsystems.
This talk will look at how you can tune the signal-to-noise ratio of your IDS by making it reflect your business logic and common usage patterns, get more work done by reducing MTTR for false positives, use eBPF and the kernel to do all the hard work for you, accidentally load test your new IDS by not filtering all RFC-1918 addresses, and abuse Docker to get to production ASAP!
As well as looking at some of the technologies that the kernel puts at your disposal, this talk will also tell pidtree-bcc's road from hackathon project to production system and how focus on demonstrating business value early on allowed the organization to give us buy-in to build and deploy a brand new project from scratch.
Add sale davinci
This document discusses embedded software development and image processing using the TI DaVinci platform. It provides an overview of the DaVinci SOC which includes both a GPP and DSP. It describes installing the necessary toolchain and software, setting up an NFS server, building the Linux kernel, cross-compiling programs, and provides an example of a simple image zooming application.
OVS and DPDK - T.F. Herbert, K. Traynor, M. Gray
The document discusses DPDK and software dataplane acceleration for Open vSwitch. It provides an overview of the OVS architecture and its evolution to integrate with DPDK. It shares one user's experience of initial challenges in using DPDK/OVS and improvements over time. Suggestions are made to improve areas like debugging, testing, documentation and training to enhance the usability of DPDK/OVS. Performance tuning techniques like using multiple threads are also briefly covered.
The internet of $h1t
I was asked to talk in front of Computer science students at the Bar-Ilan university about "what happens" when you don't care about writing "secured" or "safe" code. A perfect example for that, in my opinion, was the world of embedded computing AKA the IoT. I talked about the history of consumer embedded devices and showed a live demo of an 0day I found in one of the most popular routers in the country.
The advantages of Arista/OVH configurations, and the technologies behind buil...
Arista will put an emphasis on the technologies behind building and operating datacentres, and the reasons they give the results expected from them (varied traffic spike management, increasing bandwidth, end points and security), including very large-scale production environments.
SDN & NFV Introduction - Open Source Data Center Networking
This document introduces software defined networking (SDN) and network functions virtualization (NFV) concepts. It discusses challenges with traditional networking and how SDN and NFV address these by decoupling the control and data planes, centralizing network intelligence, and abstracting the underlying network infrastructure. It then provides examples of open source SDN technologies like OpenDaylight, Open vSwitch, and OpenStack that can be used to build programmable software-defined networks and virtualized network functions.
Network Virtualization & Software-defined Networking
This document introduces software defined networking (SDN) and network functions virtualization (NFV) concepts. It discusses challenges with traditional networking and how SDN and NFV address these by decoupling the control and data planes, making the network programmable through APIs, and virtualizing network functions. It then provides examples of open source SDN platforms like OpenDaylight, Open vSwitch, and OpenStack that enable building virtual networks and service chains.
Mellanox Approach to NFV & SDN
Presented by Eran Bello at the "NFV & SDN Summit" held March 2014 in Paris, France
Ideal for Cloud DataCenter, Data Processing Platforms and Network Functions Virtualization
Leading SerDes Technology: High Bandwidth – Advanced Process
10/40/56Gb VPI with PCIe 3.0 Interface
10/40/56Gb High Bandwidth Switch: 36 ports of 10/40/56Gb or 64 ports of 10Gb
RDMA/RoCE technology: Ultra Low Latency Data Transfer
Software Defined Networking: SDN Switch and Control End to End Solution
Cloud Management: OpenStack integration
Paving the way to 100Gb/s Interconnect
End to End Network Interconnect for Compute/Processing and Switching
Software Defined Networking
High Bandwidth, Low Latency and Lower TCO: $/Port/Gb
Introduction to WAMP, a protocol enabling PUB/SUB and RPC over Websocket
WAMP.ws is a powerful and flexible technology, but still misunderstood. These slides answer the most common questions.
Pluggable Infrastructure with CI/CD and Docker
The docker cluster ecosystem is still young, and highly modular. This presentation covers some of the challenges we faced deciding on what infrastructure to deploy, and a few tips and tricks in making both applications and infrastructure easily adaptable.
Network Automation - Interconnection tools
This document discusses tools for automating network interconnection and capacity planning decisions. It describes the complexity of manual processes and how automation can help by providing consistency, speed, ease of support, and compliance. NETCONF is presented as a standard for automating device configuration. Automating common tasks like adding ports and BGP sessions can help provision capacity based on traffic data. Total pluggability of providers is suggested to further streamline automation.
AnsibleFest 2019 - Greenfielding Network and Systems Automation in a Large an...
The year is 2019 and New York City has a very large public wifi and cellular network on the subway platforms and stations, however, it's all manually configured and maintained. This means we have carte blanche control over what and how we automate it. This talks aims to describe what it takes to bring automation to a network with over 15,000 devices and millions of daily users, including all of the pitfalls that came with it.
Monkey Server
Eduardo Silva is an open source engineer at Treasure Data working on projects like Fluentd and Fluent Bit. He created the Monkey HTTP server, which is optimized for embedded Linux and has a modular plugin architecture. He also created Duda I/O, a scalable web services stack built on top of Monkey using a friendly C API. Both projects aim to provide lightweight, high performance solutions for collecting and processing data from IoT and embedded devices.
Experiences with Microservices at Tuenti
Talk presented by Aarón Fas & Andrés Viedma at the JBcnConf 2015.
'Microservices' is one of the most popular buzzwords in the industry now, but are they really a step forward? Or they might be more a problem than a solution? When are they really helpful? How should they be addressed? What challenges will we face if we decide to implement a microservices based architecture?
One year ago, Tuenti moved from a monolithic PHP backend to a Java + PHP microservices architecture. In this talk, we'll share our experiences so far: how we addressed the change, how we implemented it, why we think it's been valuable for us (and how is that related to the company culture), why it might not be a good idea for your company / application and, mostly, what lessons we have learned from this experience.
Iot vupico-damien-contreras-2018-05-17-light-v3
Presentation used during SAP Tech days 2018 in Tokyo during a joint presentation between Hortonworks & Vupico represented by myself, what to think when implementing an IoT strategy. Why use Fog / Edge computing, showcased in a fun use case that I built: a cocktail machine built using raspberry pies with AndroidThings, cameras, TensorFlow lite, Mobilenet 1.0, peristaltic pumps and orchestrated by NiFi.
Similar to VSCP & Friends Presentation Eindhoven (20)
A Kernel of Truth: Intrusion Detection and Attestation with eBPF
A Kernel of Truth: Intrusion Detection and Attestation with eBPF
DevSecCon London 2019: A Kernel of Truth: Intrusion Detection and Attestation...
DevSecCon London 2019: A Kernel of Truth: Intrusion Detection and Attestation...
The advantages of Arista/OVH configurations, and the technologies behind buil...
The advantages of Arista/OVH configurations, and the technologies behind buil...
SDN & NFV Introduction - Open Source Data Center Networking
SDN & NFV Introduction - Open Source Data Center Networking
Network Virtualization & Software-defined Networking
Network Virtualization & Software-defined Networking
Introduction to WAMP, a protocol enabling PUB/SUB and RPC over Websocket
Introduction to WAMP, a protocol enabling PUB/SUB and RPC over Websocket
AnsibleFest 2019 - Greenfielding Network and Systems Automation in a Large an...
AnsibleFest 2019 - Greenfielding Network and Systems Automation in a Large an...
VSCP & Friends Presentation Eindhoven
- 1. VSCP – Very Simple Control Protocol A lot more than just a protocol
- 3. More?● A complete super lightweight framework for IoT/m2m ● Free and open to use. Open source, GPL, LGPL, freeware with possibility to buy commercial license ● Autonomous node functionality. ● Uniform unit discovery. ● Uniform unit configuration. ● Uniform data presentation. ● Uniform firmware update. ● A lot of tools and libs.
- 4. Lightweight ● Designed to do its job on low-end/low- bandwidth hardware. ● Scales from an AVR/PIC/ARM etc. to a full featured machines. ● Works on the media YOU like. Cable is your choice. Wireless to. ● A lot of free firmware examples on CAN, TCP/IP, Ethernet, RS-232,RS-485, GPRS, MiWI, 802.15.4...
- 5. ●Autonomous nodes ● No dependence on a master. ● Nodes just do there work. ● Internal decision matrix and registers makes them easy to configure in a common and easy way.
- 6. Uniform unit discovery ● Nodes inform you when they are first installed. ● Nodes tell you what they can do if you ask them. ● Nodes can even give you the manual if you want to read more about them. ● Nodes are identifiable in a globally unique way.
- 7. Uniform unit configuration ● Nodes will help you to configure them. ● If you are on an intelligent device the wizard will help you configure the little thing in an easy way. ● It has never been easier to configure complex things even at remote locations. And if you have done it once you know them all.
- 8. Uniform data presentation. ● VSCP events are well defined. ● You know if a temperature is coming your way and if it is set in Kelvin, Celsius or Fahrenheit. In fact that's true for everything your want to measure. ● Easy to adopt to dynamic environments.
- 9. A lot of tools and libs ● Libs and classes for easy access to functionality. ● VSCP Works a graphical tool for diagnostic, bootloading and other tasks. ● VSCP daemon a server workhorse. ● Many, many driver. CAN, SocketCAN, MQTT, TCP/IP links, XAP, Bluetooth... We can go on and on and on.
- 10. VSCP Works ● VSCP Works is mostly for developers ● Debug nodes and many useful tools. ● Logging ● Configuration and setup. ● Uniform firmware update. ● And more...
- 11. The VSCP Daemon ● Lightweight daemon. ● TCP/IP interface. ● HTML5 Web socket interface. ● WEB server ● Driver interface ● Scheduler. ● Central variable handling. ● And more...
- 12. next... ● We know you want beauty so you will give you that to. ● Good looking dynamic user interface components. ● Widgets on HTML5. Power & Looks. ● Communicate with hardware and/or VSCP daemon over web sockets ● Merlin a cross platform UI design tool.
- 14. VSCP & Friends We just want to change the world... http://www.vscp.org