This is a fork of ENet, a reliable UDP networking library which still doesn't support IPv6 in 2024 (and ENet's author seems to dislike contributions).

So here's ENet with full support for dual-stack IPv4 / IPv6.

It supports additional features ENet lacks while staying true to its lightweight and simple spirit. It's also compatible with ENet protocol so its possible for ENet6 and ENet clients to connect and exchange packets.

Additional features include:

• Dual-stack IPv4/IPv6 support
• Callbacks for encryption
• A separate timed out disconnect event
• Packets acknowledge callbacks
• Added a C# binding (derived from the amazing https://github.com/nxrighthere/ENet-CSharp)

You can build this library using either XMake or CMake.

XMake has full support for all desktop and mobile platforms (plus a simpler syntax) so I would suggest to prefer it over CMake.

Build using xmake:

xmake

You can then install it using sudo xmake install (system-wide) or xmake install -o dest_folder

You can find precompiled binaries in the releases.

If you're using XMake, you can also simply use the enet6 packages from xmake-repo, for example:

add_rules("mode.debug", "mode.release")
add_requires("enet6")

target("my_project")
    add_files("src/main.c")
    add_packages("enet6")

This will make XMake download and compile enet6 on your computer and configure the compiler to have the right include dirs/link dirs/links so you can use it out of the box.

You can then generate Visual Studio projects, CMakeLists, or directly compile using xmake.

You can check the docs folder or read the official ENet tutorial.

Here are the key differences between the official library and this fork:

1. Header files are in the enet6 folder instead of the enet folder (#include <enet6/enet.h>)
2. enet_host_create now takes a ENetAddressType as its first parameter. I suggest to use ENET_ADDRESS_TYPE_ANY on a server host (which will make it a dual-stack socket, able to handle IPv4 and IPv6). On a client host use either ENET_ADDRESS_TYPE_IPV4 or ENET_ADDRESS_TYPE_IPV6 depending on the ENetAddress you wish to connect to.
3. ENetAddress now has a type field, and its host field shouldn't be manipulated directly.
4. Peers disconnected by timing out now emit a ENET_EVENT_TYPE_DISCONNECT_TIMEOUT instead of a ENET_EVENT_TYPE_DISCONNECT

Examples:

ENetAddress address;
ENetHost* server;
/* Bind the server to the default localhost.     */
/* A specific host address can be specified by   */
/* enet_address_set_host (& address, type, "x.x.x.x"); */

/* use enet_address_build_any to configure a ENetAddress */
enet_address_build_any(ENET_ADDRESS_TYPE_IPV6, &address);
/* Default port set by enet_address_build_any is ENET_PORT_ANY which means a random port, this is not convenient for a server */
/* Bind the server to port 1234. */
address.port = 1234;
server = enet_host_create (ENET_ADDRESS_TYPE_ANY, /* either has to match address->type or be ENET_ADDRESS_TYPE_ANY to dual stack the socket */
                           & address /* the address to bind the server host to */, 
                           32      /* allow up to 32 clients and/or outgoing connections */,
                           2      /* allow up to 2 channels to be used, 0 and 1 */,
                           0      /* assume any amount of incoming bandwidth */,
                           0      /* assume any amount of outgoing bandwidth */);
if (server == NULL)
{
    fprintf (stderr, 
             "An error occurred while trying to create an ENet server host.\n");
    exit (EXIT_FAILURE);
}
...
...
...
enet_host_destroy(server);

ENetAddress address;
ENetEvent event;
ENetPeer* peer;
ENetHost* client;
/* Connect to some.server.net:1234. */
/* enet_address_set_host will resolve the target address using the target family */
/* if ENET_ADDRESS_TYPE_ANY is specified it will try to resolve using IPv6 if possible */
/* but may fallback on IPv4 */
enet_address_set_host (& address, ENET_ADDRESS_TYPE_ANY, "some.server.net");
address.port = 1234;
/* Initiate the connection, allocating the two channels 0 and 1. */

/* Create the enet host after resolving the address (allowing to create a IPv6 or IPv4 host) */
/* Using ENET_ADDRESS_TYPE_ANY type could also work but may fail on computers not supporting IPv6 at all */
client = enet_host_create (address.type,
                           NULL /* create a client host */,
                           1 /* only allow 1 outgoing connection */,
                           2 /* allow up 2 channels to be used, 0 and 1 */,
                           0 /* assume any amount of incoming bandwidth */,
                           0 /* assume any amount of outgoing bandwidth */);
if (client == NULL)
{
    fprintf (stderr, 
             "An error occurred while trying to create an ENet client host.\n");
    exit (EXIT_FAILURE);
}

peer = enet_host_connect (client, & address, 2, 0);    
if (peer == NULL)
{
   fprintf (stderr, 
            "No available peers for initiating an ENet connection.\n");
   exit (EXIT_FAILURE);
}
/* Wait up to 5 seconds for the connection attempt to succeed. */
if (enet_host_service (client, & event, 5000) > 0 &&
    event.type == ENET_EVENT_TYPE_CONNECT)
{
    puts ("Connection to some.server.net:1234 succeeded.");
    ...
    ...
    ...
}
else
{
    /* Either the 5 seconds are up or a disconnect event was */
    /* received. Reset the peer in the event the 5 seconds   */
    /* had run out without any significant event.            */
    enet_peer_reset (peer);
    puts ("Connection to some.server.net:1234 failed.");
}
...
...
...
enet_host_destroy(client);

Yes! You can connect to a regular enet server using a enet host created with the ENET_ADDRESS_TYPE_IPV4 address type (or ENET_ADDRESS_TYPE_ANY by using a IPv4-mapped IPv6). Regular enet clients can also connect to a enet6 host, if it was created using a ENET_ADDRESS_TYPE_ANY address type.

However, enet6 is not compatible with regular enet once encryption is enabled, for obvious reasons.

ENet received four pull requests to add IPv6 support between 2013 and 2019, and no one has ever been accepted or dismissed by ENet author which seems to just ignore the problem and keep ENet as a growing old library with no support for IPv6.

As a network programming teacher, I'm constantly running into issues like ENet only supporting IPv4 and other forks (like ENet-CSharp) solely relying on IPv6 which may not work on some network/computers.

This implementation aims to be an updated version of ENet, with IPv6 support and some other stuff I can use to teach network programming.

Feel free to use it.

Yes! Check the ipv6 branch which was used for my IPv6 pull request to ENet

ENet has been in version 1.x.y for 15+ years, I'm catching up (jk).

If you wish to use encryption, you need to set up enet_host_encrypt and pass an ENetEncryptor on both ends.

Since original ENet protocol can't be extended to support encryption, setting up an encryptor changes the protocol and breaks compatibility with regular ENet clients (this shouldn't be an issue as ENet does not support encryption at all anyway).

ENet6 will then call the encrypt callback before sending the packet, this callbacks works in a similar way to the compress callback (from compressor) except it receives the peer (allowing you to set a per-peer encryption key) and the callback can output more data than it receives. When receiving an encrypted packet, the decrypt callback will be called as well.

Note that the peer pointer will be NULL when connecting in the encrypt callback.

A common pattern is to enable encryption only connection (by sending a special packet), to do this:

1. Set up encryption callbacks on both ends (this is necessary because it changes the protocol) but make the encrypt callback return 0 for now (using a boolean in the peer data).
2. (Client) Connect to the server as usual.
3. (Client) Send a special packet to enable encryption (for better security, use an encrypted token which only the remote host can decrypt).
4. (Server) Enables encryption in the peer data, making packets encrypted from now.
5. (Client) When receiving an encrypted packet (in decrypt callback), enable encryption as well.
6. Encryption is now enabled on both server and client.

Check encryption example.