- #OPENWRT DHCP PACKET RECEIVED ON WHICH HAS NO ADDRESS SERIES#
- #OPENWRT DHCP PACKET RECEIVED ON WHICH HAS NO ADDRESS WINDOWS#
# Configure server mode and supply a VPN subnet # for OpenVPN to draw client addresses from. # Generate your own with: # openssl dhparam -out dh1024.pem 1024 # Substitute 20 if you are using # 2048 bit keys. key # This file should be kept secret # Diffie hellman parameters. # OpenVPN can also use a PKCS #12 formatted key file # (see "pkcs12" directive in man page). # Any X509 key management system can be used. Remember to use # a unique Common Name for the server # and each of the client certificates.
#OPENWRT DHCP PACKET RECEIVED ON WHICH HAS NO ADDRESS SERIES#
# See the "easy-rsa" directory for a series # of scripts for generating RSA certificates # and private keys. The server and all clients will # use the same ca file. Each client # and the server must have their own cert and # key file. # SSL/TLS root certificate (ca), certificate # (cert), and private key (key). # Non-Windows systems usually don't need this.
#OPENWRT DHCP PACKET RECEIVED ON WHICH HAS NO ADDRESS WINDOWS#
On XP SP2 or higher, # you may need to selectively disable the # Windows firewall for the TAP adapter. # Windows needs the TAP-Win32 adapter name # from the Network Connections panel if you # have more than one. # On most systems, the VPN will not function # unless you partially or fully disable # the firewall for the TUN/TAP interface. # On non-Windows systems, you can give # an explicit unit number, such as tun0. # If you want to control access policies # over the VPN, you must create firewall # rules for the the TUN/TAP interface. # Use "dev tap0" if you are ethernet bridging # and have precreated a tap0 virtual interface # and bridged it with your ethernet interface. # "dev tun" will create a routed IP tunnel, # "dev tap" will create an ethernet tunnel. You will need to # open up this port on your firewall. # Which TCP/UDP port should OpenVPN listen on? # If you want to run multiple OpenVPN instances # on the same machine, use a different port # number for each one.
Remember on # Windows to quote pathnames and use # double backslashes, e.g.: # "C:\\Program Files\\OpenVPN\\config\\foo.key" # Comments are preceded with '#' or ' ' # Which local IP address should OpenVPN # listen on? (optional) local a. # This config should work on Windows # or Linux/BSD systems. # OpenVPN also supports # single-machine single-machine # configurations (See the Examples page # on the web site for more info).
# This file is for the server side # of a many-clients one-server # OpenVPN configuration. # Sample OpenVPN 2.0 config file for # multi-client server.
0 kommentar(er)
