But if push comes to shove you can use this setup, but you should assign
these routes thru radius. sometimes the portmaster will step on the above
static routes and remove them from the routing table, so useing radius to
assign temp routes will solve that problem.
>
>I did a traceroute and got:
>
>traceroute 209.20.190.14
>...
>bounces off every router within 1000 miles
>...
>209.20.130.197 my upstream provider line in to my pm3
>209.20.190.3 -> My PM3 (other pm3, not the one with the T1 but
> the pm3 that ...10 is connected to.
>**
>**
>** till it just times out.
You should get a loop if the user/network is not dialed in, the pm will
just use the default gateway if the user is not connected then of course
the gateway will send it back to the pm.
there are some tricks to fix that also. If you are interested just e-mail
me back.
If the user is dialed in then you have definite routeing problems in the
pm3 and should open a ticket with tech support.
>
>I was expecting it to at least have it go to ...10 then time out but
>it didn't.
>
>If I did a traceroute to ...10, I'd get :
>209.20.130.197
>209.20.190.3
>209.20.190.10
>
>as it should.
>
>I have a PM3 and want to avoid OSPF and BGB if possible.
>
>Thanks in advance,
>
>Ed
>
>RCIA <<Relatively Cheap Internet Access>>
>Redmond, WA
>-
>To unsubscribe, email 'majordomo@livingston.com' with
>'unsubscribe portmaster-users' in the body of the message.
>
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.