[OpenVPN home] [Date Prev] [Date Index] [Date Next]
[OpenVPN mailing lists] [Thread Prev] [Thread Index] [Thread Next]
Google
 
Web openvpn.net

[Openvpn-users] Re: One ip address per client


  • Subject: [Openvpn-users] Re: One ip address per client
  • From: larsbj@xxxxxxxxxxx (Lars Gullik Bjønnes)
  • Date: Thu, 20 Jan 2005 10:39:16 +0100
  • Cancel-lock: sha1:t3vFp7csNE/5y/8ZQYiyRfvP/Bw=

Mathias Sundman <mathias@xxxxxxxxxx> writes:

[repost, I seem to have some problem with the gmane interface]

| On Tue, 18 Jan 2005, Lars Gullik Bjønnes wrote:
>
>>
>> [This is a repost, but I never saw my message on the list. Sorry if
>> duplicate.]
>>
>>
>> Is it possible to have OpenVpn use only one ip per client instead of
>> four as it is now?
>>
>> I see that VTun sets up things like this:
>>
>> 133: tun0: <POINTOPOINT,MULTICAST,NOARP,UP> mtu 1450 qdisc pfifo_fast qlen 10
>>    link/ppp
>>    inet 172.16.31.1 peer 172.16.31.6/32 scope global tun0
>> 134: tun1: <POINTOPOINT,MULTICAST,NOARP,UP> mtu 1450 qdisc pfifo_fast qlen 10
>>    link/ppp
>>    inet 172.16.31.1 peer 172.16.31.4/32 scope global tun1
>>
>> ip rou sh
>> 172.16.31.6 dev tun0  proto kernel  scope link  src 172.16.31.1
>> 172.16.31.4 dev tun1  proto kernel  scope link  src 172.16.31.1
>
| Have a look at the --ifconfig-pool-linear option. Keep in mind that
| you loose Windows compatibility if you enable this though. Search the
| list archive for this option for discussions about this.

It is not clear to me that the same ip will be used on all tun
interfaces from this option.

I also wonder if it would be possible to use f.x. a /24 for net on the
interfaces, with individual statis routes in addition.

tun0:
172.16.31.1/24
tun1:
172.16.31.1/24

static routes:
172.16.31.6 dev tun0
172.16.31.4 dev tun1

And thus make it work on windows as well.


-- 
	Lgb

____________________________________________
Openvpn-users mailing list
Openvpn-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/openvpn-users