By "keeping track", if you do a "show dhcp lease" it does suggest some kind of tracking mechanism:
Temp IP addr: 66.a.b.c for peer on Interface: Virtual-Access1571 Temp sub net mask: 255.255.255.0 DHCP Lease server: 199.d.e.f, state: 3 Bound DHCP transaction id: D98BA Lease: 259200 secs, Renewal: 129600 secs, Rebind: 226800 secs Next timer fires after: 14:19:22 Retry count: 0 Client-ID: bviper What's not clear to me is who handles DHCP renewals....if the router requests that from the external DHCP server and uses IPCP to pass that on to the PPPoA/E client, or the PPPoA/E client initates that and the router tracks it. Frank -----Original Message----- From: Eric Helm [mailto:[EMAIL PROTECTED] Sent: Thursday, October 18, 2007 4:26 PM To: [EMAIL PROTECTED] Cc: Duracom Lists; [email protected] Subject: Re: [c-nsp] PPPoE and DHCP Frank Bulk wrote: > For the record, I use an external DHCP server and it works just fine with > PPPoA/E. This is my config: > > interface Virtual-Template1 > ip unnumbered Loopback11 > ip helper-address 199.a.b.c > peer default ip address dhcp > ppp authentication pap > ppp ipcp dns 199.d.e.f 167.g.h.i > ppp ipcp unique-address > end > Interesting... so does the virtual template keep track of the dhcp leases and handle the DHCP client functions, such as renew and release, since the end station is using IPCP and has no a DHCP client functionality? /Eric _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
