package tcpip
Install
Dune Dependency
Authors
Maintainers
Sources
sha256=7553df5fc7b1c969e76d8c8382f6e65ce95f47ad55aaf28969d248375371e1cf
md5=308a2972de7313b511e5de167882ba07
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):
- ETHERNET
- ARP
- 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.
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):
ETHERNET
ARP
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
API docs: http://docs.mirage.io/tcpip/index.html
License
mirage-tcpip is distributed under the ISC license.
Dependencies (25)
-
ocaml-migrate-parsetree
< "2.0.0" -
randomconv
< "0.2.0" - io-page-unix
- duration
-
logs
>= "0.6.0" -
lwt
>= "3.0.0" & < "5.0.0" - fmt
-
mirage-profile
>= "0.5" -
ipaddr
>= "2.2.0" & < "3.0.0" -
mirage-time-lwt
>= "1.0.0" -
mirage-protocols-lwt
>= "1.3.0" & < "1.4.0" -
mirage-protocols
>= "1.3.0" & < "1.4.0" -
mirage-stack-lwt
>= "1.2.0" & < "1.3.0" -
mirage-clock-lwt
>= "1.2.0" -
mirage-random
>= "1.0.0" & < "1.2.0" -
mirage-clock
>= "1.2.0" & < "3.0.0" -
mirage-net-lwt
>= "1.0.0" & < "2.0.0" -
mirage-net
>= "1.0.0" & < "2.0.0" - cstruct-lwt
-
cstruct
>= "3.0.2" -
rresult
>= "0.5.0" - ppx_cstruct
-
configurator
build -
jbuilder
>= "1.0+beta10" -
ocaml
>= "4.03.0"
Dev Dependencies (5)
-
mirage-clock-unix
with-test & >= "1.2.0" & < "2.0.0" -
pcap-format
with-test -
alcotest
with-test & >= "0.7.0" -
mirage-vnetif
with-test & >= "0.4.0" -
mirage-flow
with-test & >= "1.2.0" & < "2.0.0"
Used by (19)
-
arp
< "0.2.0" -
capnp-rpc-mirage
< "0.8.0" -
caqti-mirage
< "2.1.2" -
charrua-client
< "0.9" -
charrua-client-lwt
< "0.11.1" -
charrua-client-mirage
< "0.10" -
charrua-core
>= "0.9" & < "0.11.1" -
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
< "1.1.0" -
mirage-qubes-ipv4
< "0.6" -
mirage-www
>= "1.1.0" -
packet
>= "0.4.0" -
spoke
>= "0.0.3" - tftp
-
vpnkit
>= "0.1.1"
Conflicts
None