Ports Search

Python library for working with the `Growl Notification Transport Protocol ( http://www.growlforwindows.com/gfw/help/gntp.aspx ) It should work as a dropin replacement for the older Python bindings.

libcloud is a client library for interacting with many of the popular cloud server providers. It was created to make it easy for developers to build products that work between any of the services that it supports.

Netlib is a collection of network utility classes, used by the pathod and mitmproxy projects. It differs from other projects in some fundamental respects, because both pathod and mitmproxy often need to violate standards.

Httping is like ping but for http-requests. Give it an url, and it will show you how long it takes to connect, send a request and retrieve the reply (only the headers).

Official command-line client for RIPE Atlas. RIPE Atlas is a global network of probes that measure Internet connectivity and reachability, providing an unprecedented understanding of the state of the Internet in real time.

The Inspector is an UPnP Device and Service analyzer, and a debugging tool, based on the Coherence DLNA/UPnP framework. Modeled loosely after the Intel UPnP Device Spy and Device Validator.

Service Location Protocol is an IETF standards track protocol that provides a framework to allow networking applications to discover the existence, location, and configuration of networked services in enterprise networks.

A very fast implementation of the xmlrpc spec for Python (written in C). It supports both blocking and non-blocking clients and servers on Windows and POSIX platforms. Version 0.8.1 is 100% compliant with the www.xmlrpc.com validator.

Getting network addresses from Python It's been irritating me for ages that it isn't possible to straightforwardly get the network address(es) of the machine you're running on from a Python program.

former QueSO home page <URL:http://www.apostols.org/projectz/queso/>: How we can determine the remote OS using simple TCP packets? Well, it's easy, they're packets that don't make any sense, so the RFCs don't clearly state what to answer in these kind of situations. Facing this ambiguous, each TCP/IP stack takes a different approach to the problem, and this way, we get a different response. In some cases (like Linux, to name one) some programming mistakes make the OS detectable. QueSO sends: 0 SYN * THIS IS VALID, used to verify LISTEN 1 SYN+ACK 2 FIN 3 FIN+ACK 4 SYN+FIN 5 PSH 6 SYN+XXX+YYY * XXX & YYY are unused TCP flags All packets have a random seq_num and a 0x0 ack_num.