VPN server: associate IP addresses with users

[MajorTom]

I successfully installed a VPN server in my workplace, where it replaces a Win2k VPN server. It works quite well and my boss is very happy about Panther’s User management and monitoring functionalities.

But the old Win2k VPN server used to associate IP addresses with users, where Panther’s gives the users the next available IP address.

It shouldn’t be harmful, but an admin had the strange idea to hardcode some of the VPN-attributed IP’s in some scripts and now, some of them give funny results since they wait a static IP (files printed for an office actually print in another office, things like that).

Now, according to the article at https://www.afp548.com/Articles/Jaguar/vpnd.html (the article is for Jaguar, not Panther), it looks like one could associate IP addresses with users thanks to /etc/ppp/chap-secrets.

Problem is that after doing exactly what is told in this tutorial, VPN-attributed IP’s are still dynamic.

So what? Specs change between Jaguar and Panther? Panther Bug? Error between the chair and the keyboard?

Any hint is welcome!

[MajorTom]

MacTroll wrote:

IAlthough you could try adding a username/pass/ip combo into the flat file that doesn’t exist in Open Directory and see if after searching the “normal” places if it defaults to the file.

I just tried that (created an user in the flat file that didn’t exist in Open Directory), but it just ignored my /etc/chap-secrets file.

I begin to wonder if Apple really has thought about that. 😕

Any Open Directory wizard out there?

[Author]

Posts