package tcpip

  1. Overview
  2. Docs

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

License

mirage-tcpip is distributed under the ISC license.

Tags

org:mirage

Published: 10 Nov 2017

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

License

mirage-tcpip is distributed under the ISC license.

Dependencies (24)

  1. randomconv < "0.2.0"
  2. io-page-unix
  3. duration
  4. logs >= "0.6.0"
  5. lwt >= "3.0.0"
  6. fmt
  7. mirage-profile >= "0.5"
  8. ipaddr >= "2.2.0" & < "3.0.0"
  9. mirage-time-lwt >= "1.0.0"
  10. mirage-protocols-lwt >= "1.1.0" & < "1.3.0"
  11. mirage-protocols >= "1.1.0" & < "1.3.0"
  12. mirage-stack-lwt >= "1.0.0" & < "1.2.0"
  13. mirage-clock-lwt >= "1.2.0"
  14. mirage-random >= "1.0.0" & < "1.2.0"
  15. mirage-clock >= "1.2.0" & < "3.0.0"
  16. mirage-net-lwt >= "1.0.0" & < "2.0.0"
  17. mirage-net >= "1.0.0" & < "2.0.0"
  18. cstruct-lwt
  19. cstruct >= "3.0.2"
  20. rresult
  21. ppx_cstruct
  22. configurator build
  23. jbuilder >= "1.0+beta10" & < "1.0+beta18"
  24. ocaml >= "4.03.0"

Dev Dependencies (5)

  1. mirage-clock-unix with-test & >= "1.2.0" & < "2.0.0"
  2. pcap-format with-test
  3. alcotest with-test & >= "0.7.0"
  4. mirage-vnetif with-test & >= "0.4.0"
  5. mirage-flow with-test & >= "1.2.0" & < "2.0.0"

Used by (18)

  1. arp < "0.2.0"
  2. capnp-rpc-mirage < "0.8.0"
  3. caqti-mirage
  4. charrua-client < "0.9"
  5. charrua-client-lwt < "0.11.1"
  6. charrua-client-mirage < "0.10"
  7. charrua-core >= "0.9" & < "0.11.1"
  8. conduit = "0.10.0"
  9. frenetic >= "5.0.0" & < "5.0.5"
  10. git-mirage >= "2.0.0" & < "3.0.0"
  11. mirage-conduit >= "2.0.0" & < "2.2.0"
  12. mirage-dns < "2.6.0"
  13. mirage-nat < "1.1.0"
  14. mirage-qubes-ipv4 < "0.6"
  15. mirage-www >= "1.1.0"
  16. packet >= "0.4.0"
  17. tftp
  18. vpnkit >= "0.1.1"

Conflicts

None