DHCP over PPP - or how to use sockets instead of BPF?

Sassy Natan sassyn at gmail.com
Thu May 13 13:36:09 UTC 2010


Thanks

I still fighting with this :-(

See the current status: on the DHCP Relay Aganet, which is the VPN client:

root at R2D2:/etc/default#  dhcrelay3  -i eth0 -i ppp0 -d 172.16.0.1
Internet Systems Consortium DHCP Relay Agent V3.1.2
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
ppp0: unknown hardware address type 512
Listening on Socket/ppp0
Sending on   Socket/ppp0
Listening on Socket/eth0
Sending on   Socket/eth0
Sending on   Socket/fallback
forwarded BOOTREQUEST for 00:1e:37:8c:37:a1 to 172.16.0.1
forwarded BOOTREQUEST for 00:1e:37:8c:37:a1 to 172.16.0.1
forwarded BOOTREQUEST for 00:1e:37:8c:37:a1 to 172.16.0.1
forwarded BOOTREQUEST for 00:1e:37:8c:37:a1 to 172.16.0.1


On the Server:
root at GW:/etc/dhcp3#  dhcpd3 -d -f ppp2 lan0
Internet Systems Consortium DHCP Server V3.1.2
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Wrote 0 leases to leases file.
Multiple interfaces match the same subnet: lan0 ppp2
Multiple interfaces match the same shared network: lan0 ppp2
ppp2: unknown hardware address type 512
Listening on Socket/lan0/172.16.0/24
Sending on   Socket/lan0/172.16.0/24
Listening on Socket/ppp2/172.16.0/24
Sending on   Socket/ppp2/172.16.0/24
Sending on   Socket/fallback/fallback-net
Can't create PID file /var/run/dhcpd.pid: Permission denied.
DHCPDISCOVER from 00:1e:37:8c:37:a1 via 172.17.0.1
DHCPOFFER on 172.17.0.10 to 00:1e:37:8c:37:a1 (sassyn) via 172.17.0.1
DHCPDISCOVER from 00:1e:37:8c:37:a1 (sassyn) via 172.17.0.1
DHCPOFFER on 172.17.0.10 to 00:1e:37:8c:37:a1 (sassyn) via 172.17.0.1
DHCPDISCOVER from 00:1e:37:8c:37:a1 (sassyn) via 172.17.0.1
DHCPOFFER on 172.17.0.10 to 00:1e:37:8c:37:a1 (sassyn) via 172.17.0.1
DHCPDISCOVER from 00:1e:37:8c:37:a1 (sassyn) via 172.17.0.1
DHCPOFFER on 172.17.0.10 to 00:1e:37:8c:37:a1 (sassyn) via 172.17.0.1


But then the client never get the package :-(



Does the IPv6 patch, will make the dhcp server work with ip v4 on the
client side?

IPCP, can u provide more info about this? I can't figure it out.


Do u know if someone did manage to solved it?
I found this, but still not working :-(

https://lists.isc.org/pipermail/dhcp-users/2009-June/009072.html


Thanks for the help!

Sassy




On Thu, May 13, 2010 at 4:29 PM, Patrik Lahti <plahti at qnx.com> wrote:
> On 12/05/10 05:58 PM, Sassy Natan wrote:
>>
>> Hi All
>>
>> Can u please tell me how can I make my DHCP server bind to a ppp
>> interface?
>>
>
> Hi,
>
> AFAIU, the ISC DHPC implementation does not support PPP interfaces today.
>
> On this thread in the email list (and a few other places) there has been
> discussion about how support for PPP interfaces can be introduced. It is a
> little complicated for various reasons, as you have read.
>
> However, the usual way to run IPv4 over PPP is *not* to use DHCPv4. Instead
> IPCP, which is part of PPP, is usually used to acquire an IPv4 address and
> various other configuration parameters such as DNS servers etc. I suggest
> you look into that option.
>
> The corresponding functionality is not present in IPv6CP, and instead you're
> supposed to use DHCPv6 on PPP interfaces. I have proposed a patch to ISC
> DHCP to enable DHCPv6 support on PPP interfaces.
>
> HTH,
> /P
>
>



More information about the dhcp-users mailing list