Looking for others that can reproduce this. I'm running Radius 2.0, and
ComOS 3.5 on all our PM2e's. When authenticating a user with multiple
Framed-Route entries, if the last Framed-Route is the very last entry in the
RADIUS response packet, that route does not get added to the PM's dynamic
routes.
More specifically, let me pin down an entry (with appropriate fields
censored):
(userid) Password = "(password)", NAS-Port-Type = Async
User-Service = Framed-User,
Framed-Protocol = PPP,
Framed-Address = 207.30.C.D,
Framed-Netmask = 255.255.255.255,
Framed-Route = "207.30.C.E/32 207.30.C.D 1",
Framed-Route = "207.30.C.F/32 207.30.C.D 1",
Framed-Route = "207.30.C.G/32 207.30.C.D 1"
Yes, I intended to route singular IPs; he's running an OS that allows .255
netmasks on all interfaces. :) Anyway, this user dials in and has all the
correct routes on an Ascend MAX, but is missing the 207.30.C.G route on a
PM2e. I can work around this by adding another field (I'm using Framed-MTU)
to the end of the entry--the PM2e then has all three extra routes--but that
should be unnecessary.
This happens with RADIUS 2.0, 1.16, and Ascend's RADIUS 9702something.
Seems the PM2e may be forgetting a portion of the packet... :)
=====
== Todd Vierling (Personal tv@pobox.com; Business tv@iag.net) Foo-bar-baz! ==
== System administrator/technician, Internet Access Group, Orlando Florida ==
== Dialups in Orange, Volusia, Lake, Osceola counties - http://www.iag.net ==