UDP

Library to send GELF messages to Graylog logging server. Supports plain-text, GELF messages and exceptions via UDP and TCP.

Provides support for asynchonous TCP, UDP, UNIX and SSL sockets.

This gem is a Logstash plugin required to be installed on top of the Logstash core pipeline using $LS_HOME/bin/logstash-plugin install gemname. This gem is not a stand-alone program

This gem is a Logstash plugin required to be installed on top of the Logstash core pipeline using $LS_HOME/bin/logstash-plugin install gemname. This gem is not a stand-alone program

A ruby Logger that sends UDP directly to a remote syslog endpoint

The net-ping library provides a ping interface for Ruby. It includes separate TCP, HTTP, LDAP, ICMP, UDP, WMI (for Windows) and external ping classes.

A pure-ruby growl notifier for UDP and GNTP growl protocols. ruby-growl allows you to perform Growl notifications from machines without growl installed (for example, non-OSX machines). What is growl? Growl is a really cool "global notification system originally for Mac OS X". You can receive Growl notifications on various platforms and send them from any machine that runs Ruby. OS X: http://growl.info Windows: http://www.growlforwindows.com/gfw/ Linux: http://github.com/mattn/growl-for-linux ruby-growl also contains a command-line notification tool named 'growl'. It is almost completely option-compatible with growlnotify. (All except for -p is supported, use --priority instead.)

Lightweight daemon to tail one or more log files and transmit UDP syslog messages to a remote syslog host (centralized log aggregation). Generates UDP packets itself instead of depending on a system syslog daemon, so it doesn't affect system-wide logging configuration.

Message sender that sends directly to a remote syslog endpoint (Support UDP, TCP, TCP+TLS)

EventMachine-LE (Live Edition) is a branch of EventMachine (https://github.com/eventmachine/eventmachine). This branch incorporates interesting pull requests that are not yet included in the mainline EventMachine repository. The maintainers of that version prefer to minimize change in order to keep the stability with already existing EventMachine deployments, which provides an impressive multi-platform base for IPv4 TCP servers (e.g., Web servers) that don't need good UDP or IPv6 support. This dedication to stability is helpful for production use, but can also lead to ossification. The present "Live Edition" or "Leading Edge" branch has its focus on supporting a somewhat wider use, including new Web servers or protocols beyond the HTTP Web. To provide even more focus, this branch is currently applying its energy towards Linux and Unix/BSD/OSX environments. Java reactor and pure Ruby reactor are for now removed in this branch, and Windows/Cygwin support is untested. This may very well change later, once interesting pull requests come in. EventMachine-LE draws from a number of dormant pull requests on the mainline version of EventMachine. New proposals will also directly come to EventMachine-LE and will be included once they are tested. This is not a "development branch", EventMachine-LE is ready for production, just beyond the focus of mainline EventMachine.

Simple methods for sending data to graphite over TCP or UDP

This library provides a Ruby interface to Google Cloud Print. cloudprint is a work in progress. I'll be adding documentation once all the basic GCP functionality is supported."

OverSIP is an async SIP proxy/server programmable in Ruby language. Some features of OverSIP are: - SIP transports: UDP, TCP, TLS and WebSocket. - Full IPv4 and IPv6 support. - RFC 3263: SIP DNS mechanism (NAPTR, SRV, A, AAAA) for failover and load balancing based on DNS. - RFC 5626: OverSIP is a perfect Outbound Edge Proxy, including an integrated STUN server. - Fully programmable in Ruby language (make SIP easy). - Fast and efficient: OverSIP core is coded in C language. OverSIP is build on top of EventMachine-LE async library which follows the Reactor Design Pattern, allowing thousands of concurrent connections and requests in a never-blocking fashion.

The LWES Light-Weight Event System is a framework for allowing the exchange of information from many machines to many machines in a controlled, platform neutral, language neutral way. The exchange of information is done in a connectless fashion using multicast or unicast UDP, and using self describing data so that any platform or language can translate it to it's local dialect.

Rather than streaming logs through a UDP connection this logger favors a simplier method: store things locally and retrieve them when your servers are not busy.

Super-Duper library to send syslog messages over UDP to logging server such as Graylog2. Supports Structured Data elements as defined by RFC 5424.

This is the simple REST client for Cloud Profiler API V2. Simple REST clients are Ruby client libraries that provide access to Google services via their HTTP REST API endpoints. These libraries are generated and updated automatically based on the discovery documents published by the service, and they handle most concerns such as authentication, pagination, retry, timeouts, and logging. You can use this client to access the Cloud Profiler API, but note that some services may provide a separate modern client that is easier to use.

Provides a class to access and control Urban Terror servers via RCON over UDP.

fluentd input/output plugin for tagged UDP message

API client for cloudpassage

Ruby client which uses UDP to communicate with a daemon which uses HTTP POST to communicate with a Web server

A Ruby library to interface with the PureCloud Platform API

A ruby Logger that sends UDP directly to a remote syslog endpoint

A generic abstraction layer for fire and forgetting measurements via UDP.

Steam Hlds Log Parser listens to UDP log packets sent by your (local or remote) HLDS game server, processes data and returns clean or/and translated and readable content that you can use for your website, irc channel, match live streaming, bots, database... Should work with all Steam HLDS based games, and has been mostly tested on Counter-Strike 1.6.

InfluxDB UDP Tracker built on Celluloid::IO

Rails syslog logger using TCP instead of UDP

A blogging framework that uses dropbox as it's storage engine

This input plugin allows you to collect incoming events over UDP instead of TCP

a lightweight udp server

Ruby Daemon collects statistics via UDP packets, stores them in Mongo, and then views them via a user friendly Sintra app.

Simple class for using UDP with Multicast

Sends JSON wrapped data via UDP packets to a given host.

Implements a gateway server to allow barebone basic sensor components to report state change updates as simple via TCP/UDP ports without the 'overhead' of the HTTP protocol. A power sensor for example might just broadcast a four byte floating point binary number once every second to an UDP port or an arduino board sends a UDP datagram whenever a button is pushed. You get the idea, this is how to bring embedded devices into the world of HTTP and Javascript...

Client and server modules to allow making REST HTTP requests over UDP

A minimal, zero dependencies, thread-safe Ruby gem to send metrics via UDP to InfluxDB.

Simple command-line server monitoring with a range of protocols: ICMP, TCP, UDP, HTTP/S, LDAP/S

Message sender that sends directly to a remote syslog endpoint (Support UDP, TCP, TCP+TLS)

Gem for transferring Active Support Instrumentation events to the InfluxDB database via UDP without boilerplate code.

Client library for accessing Fraudpointer REST API

# holepunch [](http://badge.fury.io/rb/holepunch) [](https://travis-ci.org/undeadlabs/holepunch) Holepunch manages AWS EC2 security groups in a declarative way through a DSL. ## Requirements - Ruby 1.9.3 or newer. ## Installation ```bash gem install holepunch ``` or in your Gemfile ```ruby gem 'holepunch' ``` ## Basic Configuration You need to provide your AWS security credentials and a region. These can be provided via the command-line options, or you can use the standard AWS environment variables: ```bash export AWS_ACCESS_KEY_ID='...' export AWS_SECRET_ACCESS_KEY='...' export AWS_REGION='us-west-2' ``` ## The SecurityGroups file Specify your security groups in a `SecurityGroups` file in your project's root. Declare security groups that you need and the ingresses you want to expose. You can add ingresses using `tcp`, `udp`, and `ping`. For each ingress you can list allowed hosts using group names or CIDR notation. ```ruby group 'web' do desc 'Web servers' tcp 80 end group 'db' do desc 'database servers' tcp 5432, 'web' end group 'log' do desc 'log server' tcp 9999, 'web', 'db', '10.1.0.0/16' end ``` An environment can be specified which is available through the `env` variable. This allows you to have custom security groups per server environment. ```ruby group "#{env}-web" group "#{env}-db" do tcp 5432, "#{env}-web" end ``` Your application may depend on security groups defined by other services. Ensure they exist using the `depends` method. ```ruby depends 'my-other-service' group 'my-service' do udp 9999, 'my-other-service' end ``` You may specify port ranges for `tcp` and `udp` using the range operator. ```ruby group 'my-service' do udp 5000..9999, '0.0.0.0/0' end ``` You can specify ping/icmp rules with `icmp` (alias: `ping`). ```ruby group 'my-service' do ping '10.0.0.0/16' end ``` It can be useful to describe groups of security groups you plan to launch instances with by using the `service` declaration. ```ruby service "#{env}-web" do groups %W( admin #{env}-log-producer #{env}-web ) end ``` ## Usage Simply navigate to the directory containing your `SecurityGroups` file and run `holepunch`. ``` $ holepunch ``` If you need to specify an environment: ``` $ holepunch -e live ``` You can get a list of security groups for a service using the `service` subcommand. ``` $ holepunch service -e prod prod-web admin,prod-log-producer,prod-web ``` You can also get a list of all defined services. ``` $ holepunch service --list ``` ## Testing You can run the unit tests by simply running rspec. ``` $ rspec ``` By default the integration tests with EC2 are not run. You may run them with: ``` $ rspec -t integration ``` ## Authors - Ben Scott (gamepoet@gmail.com) - Pat Wyatt (pat@codeofhonor.com) ## License Copyright 2014 Undead Labs, LLC. Licensed under the MIT License: http://opensource.org/licenses/MIT

To deliver a more Rubyesque experience when using the cloudpt API.

This input plugin allows you to collect incoming events over UDP

Capp is a packet capture library that wraps libpcap. Capp provides a simple API for capturing packets and automatically unpacks common packets (including Ethernet, IP, TCP, UDP and ICMP). Capp also cooperates with other threads better than other pcap wrapper libraries for ruby.

This library implements a server that emulates the functionality of the network connected Advantech ADAM-6050 digital IO module. Specifically the UDP protocol that the unit speaks has been reverse engineered. Since I don't have an actual device to test with the response messages from the server may differ from what they should be. It all works well enough for interfacing with Synology Surveillance Station which is the original intent.

CloudPI PaaS - Application Metric Client for ruby

A network server for distributing computations across different clients speaking TCP or UDP.

A simple UDP client for InfluxDB

event_shipper reads log files and sends each line in logstash JSON format via encrypted UDP to redis.

Sends and receives UDP packets in an OSC-compatable encoded format.