[j-nsp] PPPoE to DHCP migration dhcp-local standalone....framed-route troubles.....ERX
Peter Krupl
peter.krupl at ventelo.dk
Wed Aug 16 05:43:29 EDT 2006
On Wed, Aug 16, 2006 at 09:13:06AM +0200, Peter Krupl wrote:
>> The dhcp client gets the ip address from radius, this works ok. If a
>> user connects with PPPoE the framed route Framed-Route =
>> "172.16.1.0/29 85.235.255.218 distance 21" get installed in the
>> routing table.
>> But not with DHCP. Any suggestions ?
>
>t's been a while since did this, but try changing the route to
>
>framed-Route = "172.16.1.0/29 0.0.0.0"
>
>I've seen a similar problem once, and the above fixed it. You
>shouldn't need a next-hop, since the router can safely assume the
>route should be installed to the new interface.
>
>
This does not seem to make any difference.
I wonder if it is possible to install a route for the dhcp client at all
?
But then again it seems like the ERX treats PPP and DHCP clients equal,
the routing table shows an access-internal route for the DHCP client...
The distance must be greater than 2 for any installed subscriber route,
as the access-internal route has a distance of 2, and he distance of a
route to
resolve another route must be better (less).
-------------------------------------PASTE------------------------------
--------------------
ERX01-BOR:default:i#sh ip route 85.235.255.219
Protocol/Route type codes:
I1- ISIS level 1, I2- ISIS level2,
I- route type intra, IA- route type inter, E- route type external,
i- metric type internal, e- metric type external,
O- OSPF, E1- external type 1, E2- external type2,
N1- NSSA external type1, N2- NSSA external type2
L- MPLS label, V- VRF, *- via indirect next-hop
Prefix/Length Type Next Hop Dst/Met Interface
------------------ --------- --------------- ----------
-----------------------
x.x.x.219/32 AccIntern 0.0.0.0 2/0 ATM2/1.1010
-------------------------------------PASTE------------------------------
--------------------
>--
>Terje Krogdahl
>
> All roads lead to Rome
> - A clearly confused router (R. Perlman)
###########################################
This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.f-secure.com/
More information about the juniper-nsp
mailing list