[nsp] ppp address negotiation

Adam Debus adam-lists at reachone.com
Thu Jul 1 11:40:23 EDT 2004


Hi Oliver,

    It turns out that I had a slight error in my radius configuration. I was
sending a Framed-IP-Address of 255.255.255.255 instead of 255.255.255.254.
It appears to have been accidentially changed about 6 months ago by somebody
here. I have no idea why things were still working before the upgrade, but
I'm not going to waste too much brain power on it :)

---
Adam Debus
Network Engineer, ReachONE Internet
adam at reachone.com

----- Original Message ----- 
From: "Oliver Boehmer (oboehmer)" <oboehmer at cisco.com>
To: "Adam Debus" <adam-lists at reachone.com>
Cc: <cisco-nsp at puck.nether.net>
Sent: Thursday, July 01, 2004 06:48
Subject: RE: [nsp] ppp address negotiation


Hi Adam,

I am unable to reproduce this behaviour with 12.2(24). When the client
connects and requests the same ip address (10.10.10.10) through IPCP (a
behaviour commonly seen), the LNS NACKs this and supplies an ip address
from the pool (182.168.221.1):

*Jul 16 04:10:55.815: Vi1 IPCP: I CONFREQ [REQsent] id 1 len 10
*Jul 16 04:10:55.815: Vi1 IPCP:    Address 10.10.10.10 (0x03060A0A0A0A)
*Jul 16 04:10:55.815: Vi1 AAA/AUTHOR/IPCP: Start.  Her address
10.10.10.10, we want 0.0.0.0
*Jul 16 04:10:55.815: Vi1 AAA/AUTHOR/IPCP: Reject 10.10.10.10, using
0.0.0.0
*Jul 16 04:10:55.815: Vi1 AAA/AUTHOR/IPCP: Done.  Her address
10.10.10.10, we want 0.0.0.0
*Jul 16 04:10:55.815: Vi1 IPCP: O CONFNAK [REQsent] id 1 len 10
*Jul 16 04:10:55.815: Vi1 IPCP:    Address 192.168.221.1
(0x030691FEDD01)

If you can reproduce this, can you please send "deb radius" and "deb ppp
neg" for this user so we can check what's going on.

oli

cisco-nsp-bounces at puck.nether.net <> wrote on Wednesday, June 30, 2004
8:10 PM:

> A few nights ago, we completed an upgrade to IOS 12.2(24) on
> our Cisco 7200
> VXR NPE-400.
>
> This router acts as the termination point for about 600 DSL customers
> running PPPoA.
>
> Now, when a customer signs on, if there is no static IP in the radius
> response, it will assign the same address that the customer
> had before, even
> if it is in use by another customer, or is not in the range
> from the "ip
> local pool". I tried executing the command "no ppp ipcp
> accept-address" but that seems to be the default, and has had no
> effect to how
> this is working.
>
> This is what my Virtual-Template looks like:
>
> interface Virtual-Template1
>  ip unnumbered Loopback0
>  ip route-cache flow
>  no logging event link-status
>  peer default ip address pool DSL
>  ppp authentication pap
>  ppp ipcp dns x.x.224.2 x.x.225.2
> !
> ip local pool DSL x.x.240.2 x.x.240.254
> ip local pool DSL x.x.241.129 x.x.241.254
>
> To give a real world example, a DSL has a static IP of
> x.x.242.1, after
> removing that static IP from radius and performing a "clear
> int vi" on the
> virtual-access interface, it logs out, logs back in, and receives the
> address x.x.242.1 instead of one of the addresses from the
> local pool. We
> also had an instance yesterday (which caused me to start
> looking at this)
> where two customers were active with the same ip address. It
> wasn't even
> checking to see if it was in use before assigning it.
>
> We have checked modem configurations, and none of the modems
> are set to have
> any address statically programmed, and rebooting the modem
> doesn't seem to
> fix the issue either.
>
> Does anyone have any thoughts or ideas as to what might be
> causing this and
> how to fix it?
>
> ---
> Adam Debus
> Network Engineer, ReachONE Internet
> adam at reachone.com
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/



More information about the cisco-nsp mailing list