package tcpip

You can search for identifiers within the package.

in-package search v0.2.0

OCaml TCP/IP networking stack, used in MirageOS

Install

Dune Dependency

github.com Readme Changelog ISC License Edit opam file Versions (72)

Authors

Maintainers

A

anil@recoil.org

Sources

tcpip-v4.1.0.tbz

sha256=bf85f6341bfcfb4075868555cd2346c582f563f80383a2cb9ebcab5a1322dbdd

sha512=165f7ba7e55701b82926dab3fcdbff78de04e843cb8a6a1b155e85729ff9ce6ad91dc3dfea9f8ebc8bfcdbd3d3a18d37196ab5c0047c6a16c1b99c129dde9888

Description

mirage-tcpip provides a networking stack for the Mirage operating system. It provides implementations for the following module types (which correspond with the similarly-named protocols):

IP (via the IPv4 and IPv6 modules)
ICMP
UDP
TCP

Published: 08 Feb 2020

README

mirage-tcpip - an OCaml TCP/IP networking stack

mirage-tcpip provides a networking stack for the Mirage operating system. It provides implementations for the following module types (which correspond with the similarly-named protocols):

IP (via the IPv4 and IPv6 modules)
ICMP
UDP
TCP

Implementations

There are two implementations of the IP, ICMP, UDP, and TCP module types - the socket stack, and the direct stack.

The `socket` stack

The socket stack uses socket calls to a traditional operating system to provide the functionality described in the module types.

See the src/stack-unix/ directory for the modules used as implementations of the socket stack.

The socket stack is used for testing or other applications which do not expect to run as unikernels.

The `direct` stack

The direct stack expects to write to a device implementing the NETIF module type defined for MirageOS.

See the src/ directory for the modules used as implementations of the direct stack, which is the expected stack for most MirageOS applications.

The direct stack is the only usable set of implementations for applications which will run as unikernels on a hypervisor target.

Community

WWW: https://mirage.io
E-mail: mirageos-devel@lists.xenproject.org
Issues: https://github.com/mirage/mirage-tcpip/issues
API docs: http://docs.mirage.io/tcpip/index.html

License

mirage-tcpip is distributed under the ISC license.

Dependencies (26)

lru >= "0.3.0"
mirage-flow >= "2.0.0" & < "4.0.0"
ethernet >= "2.0.0" & < "3.0.0"
randomconv < "0.2.0"
duration
logs >= "0.6.0"
lwt-dllist
lwt >= "4.0.0"
fmt >= "0.8.0"
mirage-profile >= "0.5"
macaddr-cstruct
macaddr >= "4.0.0"
ipaddr >= "4.0.0"
mirage-time >= "2.0.0"
mirage-protocols >= "4.0.0" & < "5.0.0"
mirage-stack >= "2.0.0" & < "4.0.0"
mirage-random >= "2.0.0" & < "4.0.0"
mirage-clock >= "3.0.0"
mirage-net >= "3.0.0"
cstruct-lwt
cstruct >= "3.2.0" & < "6.1.0"
rresult >= "0.5.0"
result
ocaml >= "4.06.0"
dune-configurator
dune

Dev Dependencies

None

Used by (20)

arp < "0.2.0"
caldav
capnp-rpc-mirage >= "0.3.2" & < "0.8.0"
caqti-mirage < "2.1.2"
charrua < "1.2.2"
charrua-client-lwt >= "0.11.1" & < "0.12.0"
charrua-client-mirage >= "0.11.1" & < "0.12.0"
charrua-core >= "0.11.2"
conduit = "0.10.0"
frenetic >= "5.0.0" & < "5.0.5"
git-mirage >= "2.0.0" & < "3.0.0"
mirage-conduit >= "2.0.0" & < "2.2.0"
mirage-dns < "2.6.0"
mirage-nat >= "2.1.0" & < "2.2.5"
mirage-qubes-ipv4 >= "0.6" & < "0.8.3"
mirage-www >= "1.1.0"
packet >= "0.4.0"
spoke >= "0.0.3"
tftp
vpnkit >= "0.1.1"

Conflicts