Lines Matching defs:tun
41 #include "tun.h"
93 if (is_dev_type (dev, dev_type, "tun"))
109 return "tun";
146 * If !tun, make sure ifconfig_remote_netmask looks
149 * If tun, make sure ifconfig_remote_netmask looks
153 ifconfig_sanity_check (bool tun, in_addr_t addr, int topology)
157 if (tun)
160 msg (M_WARN, "WARNING: Since you are using --dev tun with a point-to-point topology, the second argument to --ifconfig must be an IP address. You are using something (%s) that looks more like a netmask. %s",
380 bool tun = false;
383 tun = false;
385 tun = true;
387 msg (M_FATAL, "Error: problem with tun vs. tap setting"); /* JYFIXME -- needs to be caught earlier, in init_tun? */
389 return tun;
393 * Init tun/tap object.
423 bool tun = false;
431 tun = is_tun_p2p (tt);
448 (tun ? GETADDR_RESOLVE : 0)
496 if (!tun)
508 if (tun)
561 * Platform specific tun initializations
627 bool tun = false;
644 tun = is_tun_p2p (tt);
662 if (!tun)
691 if (tun) {
731 if (tun)
774 if (tun)
867 if (!tun && tt->topology == TOP_SUBNET)
869 /* Add a network route for the local tun interface */
885 * On OpenBSD, tun interfaces are persistent if created with
891 if (tun)
951 if (tun)
975 * NetBSD has distinct tun and tap devices
1007 msg( M_INFO, "no IPv6 support for tun interfaces on NetBSD before 4.0 (if your system is newer, recompile openvpn)" );
1024 msg (M_INFO, "NOTE: Tried to delete pre-existing tun/tap instance -- No Problem if failure");
1028 if (tun)
1064 /* Add a network route for the local tun interface */
1065 if (!tun && tt->topology == TOP_SUBNET)
1095 if (tun)
1130 /* Add a network route for the local tun interface */
1131 if (!tun && tt->topology == TOP_SUBNET)
1161 if (tun)
1200 msg (M_FATAL, "Error: When using --tun-ipv6, if you have more than one TAP-Windows adapter, you must also specify --dev-node");
1263 msg (M_WARN, "NOTE: explicit support for IPv6 tun devices is not provided for this OS");
1286 /* on NetBSD, tap (but not tun) devices are opened by
1400 node = "/dev/net/tun";
1411 * Process --tun-ipv6
1422 * Figure out if tun or tap device
1434 msg (M_FATAL, "I don't recognize device %s as a tun or tap device",
1439 * Set an explicit name, if --dev is not tun or tap
1441 if (strcmp(dev, "tun") && strcmp(dev, "tap"))
1445 * Use special ioctl that configures tun/tap device with the parms
1697 dev_node = "/dev/tun";
1698 dev_tuntap_type = "tun";
1714 msg (M_FATAL, "I don't recognize device %s as a tun or tap device",
1773 /* Assign ppa according to the unit number returned by tun device */
1789 /* Assign ppa according to the unit number returned by tun device */
2018 /* tun(4): "If the device was created by opening /dev/tunN, it will be
2030 /* only *TAP* devices need destroying, tun devices auto-self-destruct
2042 /* setup command, close tun dev (clears tt->actual_name!), run command
2052 openvpn_execve_check (&argv, NULL, 0, "OpenBSD 'destroy tun interface' failed (non-critical)");
2116 * NetBSD before 4.0 does not support IPv6 on tun out of the box,
2119 * NetBSD 4.0 and up do, but we need to put the tun interface into
2158 /* the current way OpenVPN handles tun devices on NetBSD leads to
2165 /* only tun devices need destroying, tap devices auto-self-destruct
2177 /* setup command, close tun dev (clears tt->actual_name!), run command
2187 openvpn_execve_check (&argv, NULL, 0, "NetBSD 'destroy tun interface' failed (non-critical)");
2295 /* tun(4): "These network interfaces persist until the if_tun.ko module is
2299 * so, to avoid lingering tun/tap interfaces after OpenVPN quits,
2315 /* setup command, close tun dev (clears tt->actual_name!), run command
2325 openvpn_execve_check (&argv, NULL, 0, "FreeBSD 'destroy tun interface' failed (non-critical)");
2465 * If IPv6 is configured, and the tun device is closed, the IPv6 address
2466 * configured to the tun interface changes to a lingering /128 route
2946 err = "must exist within the same 255.255.255.252 subnet. This is a limitation of --dev tun when used with the TAP-WIN32 driver";
2954 err = "cannot use the first or last address within a given 255.255.255.252 subnet. This is a limitation of --dev tun when used with the TAP-WIN32 driver";
2974 printf ("On Windows, point-to-point IP support (i.e. --dev tun)\n");
4728 msg (M_FATAL, "ERROR: --dev tun also requires --ifconfig");
4759 msg (M_FATAL, "ERROR: The TAP-Windows driver rejected a DeviceIoControl call to set Point-to-Point mode, which is required for --dev tun");