Fork of the TAP-Win32/Win64 driver of OpenVPN, aims to add IPv6 support.
C
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
amd64
i386
MAKEFILE
README
SOURCES
SOURCES.in
autodefs.h
common.h
constants.h
dhcp.c
dhcp.h
dhcpv6.c
dhcpv6.h
endian.h
error.c
error.h
hexdump.c
hexdump.h
instance.c
lock.h
macinfo.c
macinfo.h
mem.c
proto.h
prototypes.h
resource.rc
tapdrvr.c
types.h

README

The configuration format and some additional notes
--------------------------------------------------

       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                                                               |
      +                                                               +
      |                                                               |
      +                            Address                            +
      |                                                               |
      +                                                               +
      |                                                               |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      | Prefix Length |                   Reserved                    |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                              MTU                              |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                            Lifetime                           |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

- There can be many DHCPv6 servers in IPv6, so the packets should not be dropped
- Router address should not be set by DHCPv6, if there are routers present in the
  the VPN they should send their own router advertisements and prefixes
- The sent router advertisement has zero router lifetime to indicate no routing
- Same lifetime is set for both prefix and DHCPv6 acquired address, the client can
  renew the address at the time they wish, since T1 and T2 are both set to zero
- The MTU of the local network prefix can be configured through the interface,
  but it can not be higher than the adapter MTU or lower than 1280. It is also
  worth to notice that other advertised prefixes can have a different MTU, but in
  general this should not be a problem, because IPv6 uses path MTU discovery.
- DHCPv6 option buffers double the DHCPv4 buffers, because DHCPv6 options larger