114
114
# out unless you are ethernet bridging.
115
115
;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100
117
# Configure server mode for ethernet bridging
118
# using a DHCP-proxy, where clients talk
119
# to the OpenVPN server-side DHCP server
120
# to receive their IP address allocation
121
# and DNS server addresses. You must first use
122
# your OS's bridging capability to bridge the TAP
123
# interface with the ethernet NIC interface.
124
# Note: this mode only works on clients (such as
125
# Windows), where the client-side TAP adapter is
126
# bound to a DHCP client.
117
129
# Push routes to the client to allow it
118
130
# to reach other private subnets behind
119
131
# the server. Remember that these
170
182
# all IP traffic such as web browsing and
171
183
# and DNS lookups to go through the VPN
172
184
# (The OpenVPN server machine may need to NAT
173
# the TUN/TAP interface to the internet in
174
# order for this to work properly).
175
# CAVEAT: May break client's network config if
176
# client's local DHCP server packets get routed
177
# through the tunnel. Solution: make sure
178
# client's local DHCP server is reachable via
179
# a more specific route than the default route
180
# of 0.0.0.0/0.0.0.0.
181
;push "redirect-gateway"
185
# or bridge the TUN/TAP interface to the internet
186
# in order for this to work properly).
187
;push "redirect-gateway def1 bypass-dhcp"
183
189
# Certain Windows-specific network settings
184
190
# can be pushed to clients, such as DNS
185
191
# or WINS server addresses. CAVEAT:
186
192
# http://openvpn.net/faq.html#dhcpcaveats
187
;push "dhcp-option DNS 10.8.0.1"
188
;push "dhcp-option WINS 10.8.0.1"
193
# The addresses below refer to the public
194
# DNS servers provided by opendns.com.
195
;push "dhcp-option DNS 208.67.222.222"
196
;push "dhcp-option DNS 208.67.220.220"
190
198
# Uncomment this directive to allow different
191
199
# clients to be able to "see" each other.