07-29-2005 06:24 AM - edited 02-21-2020 01:53 PM
Hi Folks,
we are having problems using VitalQIP with VPN-Concentrator to asign IP-Addresses to VPN-Clients: VitalQIP dosen't care about DHCP Option 61 (Client identifier) and the VPN-Concentrator using only his MAC-Address when sending the Discovery/Request.
Anyone got workaround/fix/tip??
http://www.lucent.com/products/solution/0,,CTID+2020-STID+10439-SOID+1456-LOCL+1,00.html
08-04-2005 06:46 AM
I would suggest inspecting the DHCP configuration itself.
08-04-2005 10:52 PM
it's not a problem of the dhcp configuration on the VPN-Concentrator - using an ISC DHCPd version 3.0.1 everything is fine. The problem is, QIP doesn't care about the Client Identifier.
01-11-2006 01:26 PM
How did you ultimately fix this problem? I've had the same scenario & have had it for more than a year now. I've noticed, after a lot of observation, DHCP discovers begin failing after the last (sequential) address in the scope has been assigned, even though there should be more than enough leases available. I've been confused for a long time on this one!
01-13-2006 02:20 AM
Actually I didn't fix the Problem.
The Problem is, VitalQIP is NOT RFC COMPLAINT! (at least regarding the DHCP Option 61 issue)
AFAK our customer bought a patch/modification for the DHCP-Server to overcome this issue. - So blaim lucent, thier Product is not RFC complaint, although they say so.
01-13-2006 07:09 AM
Thanks - I'm giving up & have decided to use an internal pool of addresses. Bummer!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide