Re: IP allocation for a client

I have static addresses being assigned from one of my boxen.  I do not have
the address listed in the pool assignments in pptpd.conf, rather only in the
chap-secrets..

My understanding from another user that had set this up previously was that
using multiple addresses in the chap-secrets file was to account for more
than one connection from the same user / password pair, otherwise only the
first address would be used.

The reason the address was not included in the pptpd.conf was similar to the
use of a dhcp-pool and an assignment outside of the pool allocation.

Hope this helps.


On Tue, Oct 4, 2011 at 3:41 AM, AT <[email protected]> wrote:

> Hi guys,
>
> I have an issue making PPTPd allocate correct IP address to the client
> machines. here is what I have in my configs:
>
> [root@lincoln ~]# cat /etc/pptpd.conf
> option /etc/ppp/options.pptpd
> #debug
> logwtmp
> connections 1024
> #delegate
> # we want pptpd to allocate the IPs not pppd
> localip 172.16.32.1
> remoteip 172.16.32.2-254,172.16.33.1-254,172.16.34.1-254,172.16.35.1-254
>
> [root@lincoln ~]# cat /etc/ppp/options
> lock
> 172.16.32.1:
>
> [root@lincoln ~]# cat /etc/ppp/options.pptpd
> name pptpd
> refuse-pap
> refuse-chap
> refuse-mschap
> require-mschap-v2
> require-mppe-128
> ms-dns 208.67.222.222
> ms-dns 8.8.8.8
> debug
> dump
> lock
> nobsdcomp
> novj
> novjccomp
> nologfd
>
> [root@lincoln ~]# cat /etc/ppp/chap-secrets
> # Secrets for authentication using CHAP
> # client        server  secret                  IP addresses
> someuser        *       somepass        172.16.32.9 172.16.32.11
> 172.16.32.10
>
> Now if I try to connect to the PPTPd server from two different
> machines using the same username 'someuser' they both are given
> 172.16.32.9 IP address.
>
> ppp0      Link encap:Point-to-Point Protocol
>          inet addr:172.16.32.1  P-t-P:172.16.32.9  Mask:255.255.255.255
>
> ppp1      Link encap:Point-to-Point Protocol
>          inet addr:172.16.32.1  P-t-P:172.16.32.9  Mask:255.255.255.255
>
> Obviously routing and network packet delivery does not work properly
> in this case. The system does not know how which interface to use to
> send the replies to 172.16.32.9.
>
> I was expecting PPTPd to allocate 172.16.32.9 to first connecting
> machine with username 'someuser' and 172.16.32.11 to another machine
> connecting with the same user name.
>
> Can anybody give an idea how do I make PPTPd allocate the necessary
> addresses?
> Or is there any way to route the traffic somehow for two pppX
> interfaces having the same remote IP address?
>
> Any input would be appreciated.
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2dcopy1
> _______________________________________________
> Poptop-server mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/poptop-server
>
>


-- 
Mark Grigsby
63613 S. Barview Rd
Coos Bay, OR. 97420
DID: 541-762-1171

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1

_______________________________________________
Poptop-server mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/poptop-server