You need to route that subnet to your TC on your border routers, but on
the TC itself, you route the subnet to the next hop, not the TC itself.
For example, we use un-numbered WAN interfaces on some ISDN stuff (NT
RAS can't do this) and assign the lowest number of the subnet as the IP
of the ISDN TA's ethernet. The RadiusNT entry looks like this:
user Password = "Blah"
User-Service = Framed-User,
Framed-Protocol = PPP,
Framed-Address = 188.8.131.52,
Framed-Route = "184.108.40.206/26 220.127.116.11 1"
When the user gets dialed in, the TC knows thier IP is 18.104.22.168.
It also dynamically adds the route to the subnet via the above IP. When
the user hands up, its all gone. Remember, you'll get a loop between the
TC and your border router when the connection isn't up.
PS, everyone needs to make sure they are posting to the @iea-software.com
domain and NOT the @emerald.iea.com domain. Starting next week we will be
sending an auto-responder to everyone who is sending to the @emerald.iea.com
domain, so update your address book now and save your the trouble later.
-- Dale E. Reed Jr. (email@example.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com