Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(ASCEND) Static routes to an ATMP tunnel
When playing with ATMP stuff, I encountered the following
problem:
I defined the following profile in RADIUS, for the mobile node
connecting the foreign agent:
foo Password = "ascend-rules"
User-Service = Framed-User,
Framed-Protocol = PPP,
Framed-Routing = None,
Framed-Address = 172.16.1.1,
Framed-Netmask = 255.255.255.0,
Framed-Route = "172.16.2.0/24 172.16.1.1 1",
Ascend-Idle-Limit = 600,
Ascend-Home-Agent-IP-Addr = 10.0.0.1,
Ascend-Home-Agent-Password = "home-max",
Ascend-Home-Agent-UDP-Port = 5150
Once foo is connected to the FA, I see a route for 172.16.1.0/24
with gateway tunnel0 on the Home agent, but nothing about
172.16.2.0/24.
sh ip route gives:
172.16.1.0/24 - tunnel0 ? 100 2 3 5
I tried to add static routes for 172.16.2.0/24 on FA and/or HA,
but it doesn't help.
(a traceroute to 172.16.2.x stops after the HA with * * *, when
the mobile node -172.16.1.1- should answer).
Of course, a traceroute to 172.16.1.1 works perfectly.
It seems the tunnel is not usable as a real interface, as it is
with a GRE tunnel on a Cisco.
This is quite ennoying, and doesn't help when building intranet,
as the static routing flexibilty is quite decreased.
Is this a normal behaviour, or a bug ?
Is there a solution, or can we expect this will be solved soon ?
--
David Ponzone / ISDnet
Pager: +33 (0)6 06 41 82 45 Cell: +33 (0)6 60 61 21 63
Email: david@isdnet.net
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.shore.net/~dreaming/ascend-faq>
or <ftp://ftp.shore.net/members/dreaming/ascend-faq.txt>
Follow-Ups: