Hi all,
Zs wrote:
> Hi!
>
> Ha a Windows alatt OpenVPNGUI-t használsz, akkor az telepíti
> a Windowsos tun/tap drivert, amit az OpenVPN használ. Ennek
> a drivernek viszont tun alatt van egy nagyon komoly limitációja is:
> a felhúzott IP-nek ha a fene fenét eszik is, egy /30-as subnetbe kell
> esnie. A kapott 10.1.0.3-as IP cím egy /30-as subnet broadcastja,
> azzal tehát nem fog menni. A 169.254.168.68 viszont emlékezetem
> szerint az az IP, amit a Windows akkor húz fel, ha az interface-t UP-ba
> teszi és nem kap DHCP-vel IP-t...
>
> Honnan jön ez a 10.1.0.3-as IP? Nem lehetne ezt valami más IP-re
> felhúzni? pl. 10.1.0.1, 10.1.0.2, 10.1.0.5, 10.1.0.6, stb...
Nem artana ezt egy kicsit olvasgatni:
[...]
--topology mode
Configure virtual addressing topology when running in --dev tun
mode. This directive has no meaning in --dev tap mode, which always uses
a subnet topology.
If you set this directive on the server, the --server and
--server-bridge directives will automatically push your chosen topology
setting to clients as well. This directive can also be manually pushed
to clients. Like the --dev directive, this directive must always be
compatible between client and server.
mode can be one of:
net30 -- Use a point-to-point topology, by allocating one /30
subnet per client. This is designed to allow point-to-point semantics
when some or all of the connecting clients might be Windows systems.
This is the default on OpenVPN 2.0.
p2p -- Use a point-to-point topology where the remote endpoint of
the client's tun interface always points to the local endpoint of the
server's tun interface. This mode allocates a single IP address per
connecting client. Only use when none of the connecting clients are
Windows systems. This mode is functionally equivalent to the
--ifconfig-pool-linear directive which is available in OpenVPN 2.0 and
is now deprecated.
subnet -- Use a subnet rather than a point-to-point topology by
configuring the tun interface with a local IP address and subnet mask,
similar to the topology used in --dev tap and ethernet bridging mode.
This mode allocates a single IP address per connecting client and works
on Windows as well. Only available when server and clients are OpenVPN
2.1 or higher, or OpenVPN 2.0.x which has been manually patched with the
--topology directive code. When used on Windows, requires version 8.2 or
higher of the TAP-Win32 driver. When used on *nix, requires that the tun
driver supports an ifconfig(8) command which sets a subnet instead of a
remote endpoint IP address.
This option exists in OpenVPN 2.1 or higher.
[...]
Mindenki szamara ajanlom a subnet mode hasznalatat.
_________________________________________________
linux lista - [email protected]
http://mlf2.linux.rulez.org/mailman/listinfo/linux
