I have a customer authenticating on the MT PPPoE server.
We using radius pass the same ip each time to this customer.
Now the customer need an entire /29 to be routed over his static ip.
May I add a static route with its static (dinamic from the MT point of view) as gateway?
Thanks
Rosario
Add into radius database Framed-Route reply attribute for those customer. For example:
Framed-Route = a.b.c.d/27 0.0.0.0 1
may you explain the second and the third elemt of the reply?
The third should be the distance and the second?
I putted it into the reply message, the radius log tell me that this is passed to MT correctly, but I don’t see any dinamic rule added into the routing table.
Thanks
This attribute work for me for sure …
From RFC 2138:
5.22. Framed-Route
Description
This Attribute provides routing information to be configured for
the user on the NAS. It is used in the Access-Accept packet and
can appear multiple times.
A summary of the Framed-Route Attribute format is shown below. The
fields are transmitted from left to right.
0 1 2
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3
±±±±±±±±±±±±±±±±±±±±±±
| Type | Length | String…
±±±±±±±±±±±±±±±±±±±±±±
Type
22 for Framed-Route.
Length
= 3
String
The String field is one or more octets, and its contents are
implementation dependent. It is intended to be human readable and
MUST NOT affect operation of the protocol. It is recommended that
the message contain displayable ASCII characters from the range 32
through 126 decimal.
For IP routes, it SHOULD contain a destination prefix in dotted
quad form optionally followed by a slash and a decimal length
specifier stating how many high order bits of the prefix should be
used. That is followed by a space, a gateway address in dotted
quad form, a space, and one or more metrics separated by spaces.
For example, “192.168.1.0/24 192.168.1.1 1 2 -1 3 400”. The length
specifier may be omitted in which case it should default to 8 bits
for class A prefixes, 16 bits for class B prefixes, and 24 bits
for class C prefixes. For example, “192.168.1.0 192.168.1.1 1”.
Whenever the gateway address is specified as “0.0.0.0” the IP
address of the user SHOULD be used as the gateway address.
my fault sorry!
The subent assigned was inside a POOL. After I cencelled it from the ppol everything worked fine.
Thanks
Rosario