Re: (ASCEND) Static routes via Radius (Max)

[nsupport@mail.idx.com.au (idx - nsupport)]

Hi,

Try to do a traceroute from the CISCO to the wan ip address (
Framed-IP-Address). If ok
  then connectivity is good, otherwise fix the connection first.
Then try and do a traceroute to one of the Routed IP addresses and see
where it fails. If 
  it stops at the wan ip address, then it may be a problem with the client
machine
  not forwarding from wan to lan and/or lan to wan. 

hope this helps.

best regards

At 01:02 PM 11/22/99 +1100, Roddy Strachan wrote:
>Hi,
>	We have a client who dials into us, we are also routing there
>Class C for them.  Now i have setup a Radius users entry to do this :
>
>username            Auth-Type = System
>                Service-Type = Framed-User,
>                Framed-Protocol = PPP,
>                Framed-IP-Address = 203.19.222.96,
>                Framed-Route = "203.55.197.0/24 203.19.222.96 1 n"
>                Session-Timeout = 14400,
>                Framed-Routing = Broadcast-Listen,
>
>Now as you can see from that, the IP they are given is 203.19.222.96, and
>I am routing the Class of 203.55.197.0 to their dialin IP.  WHen they
>connect to either of the maxes, I cant ping them from the termserv prompt
>on the max.  I have set a route up in our Cisco 4500
>ip route 203.55.197.0 255.255.255.0 203.19.222.96
>
>To tell it where to go.  I am not running RIP or any other routing
>protocol like that, here is the output from the 'radif' debug command from
>the max.
>
>RADIF: authenticating <4:username> with PAP
>RADIF 12:56:09> _radiusRequest: id 123, user name <5:username>
>RADIF: _radiusReq: challenge len = <0>
>RADIF: _radiusReq: socket 6 len 101 ipaddr 203.19.222.1 port 65534->1645
>RADIF:_radiusReq: id 123 <5:username>, starting timer (1 sec)
>RADIF: _radCallback: buf=B08826C0 from 203.19.222.1 1645
>RADIF: _radCallback, authcode = 2, id 123
>RADIF: _radCallback: id 123, killing timer
>RADIF: Authentication Ack
>RADIF: attribute 6, len 6, 00 00 00 02
>RADIF: attribute 7, len 6, 00 00 00 01
>RADIF: attribute 8, len 6, cb 13 de 60
>RADIF: attribute 22, len 35, 32 30 33 2e
>RADIF: raw route B079E420, cooked route B0838A30
>RADIF: processing framed route "203.55.197.0/24 203.19.222.96 1 n"
>RADIF: ip address 203.55.197.0, netmask 255.255.255.0
>RADIF: gateway address 203.19.222.96
>RADIF: metric 1
>RADIF: Adding cooked route B0838A20 to list
>RADIF: attribute 27, len 6, 00 00 38 40
>RADIF: attribute 10, len 6, 00 00 00 03
>RADIF:_freeInfoClassSess
>RADIF: radius type Acct ID = 157
>RADIF: _radiusAcctRequest: type 0 id 157, user name <5:username>
>RADIF: _radiusAcctReq: socket 9 len 109 IP 203.19.222.1 port 1027=>1646,
>ID=157
>RADIF:_freeInfoClassSess
>RADIF: _radCallback: processed acct server type=0
>
>Vice versa they cannot ping us etc, he is running a Linux box to route his
>ips etc.  I am not to sure if it is our end or his.  The only thing I
>could think on is maybe running RIP to see if that fixes it, apart from
>that I am stuck.
>ANy ideas?
>
>
>   ---------------------------------------------------------------------
>   Roddy Strachan                        Email - roddy@satlink.com.au
>   Network/Systems Administrator         ICQ   - 1987890
>   Satlink Internet Services             Ph.   - +61-3-9775-2600
>   www.straks.satlink.com.au             Fax.  - +61-3-9775-2456
>   ---------------------------------------------------------------------
>
>++ Ascend Users Mailing List ++
>To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
>To get FAQ'd:	<http://www.nealis.net/ascend/faq>
>


++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>