>From: "Jyrki Kainulainen" <jyrki.kainulainen at datatie.fi> > >Another thing: When I set TNT System:permconn-update... = changed, and do >that refresh -a, all changed ATM connections will be put down and new >profiles asked from radius. After refresh, there are none of those changed >ATM connections up!. So, I do refresh -a command again and then one (1) >accounting start is sent, even there were many refreshed/changed ATM >connection profiles, and after that all connections are working. What's the >logic here?? We don't use permconns with our TNT, but we do use ATM permconns with a DSL Terminator 100. We find that equivalent to permconn-update... = changed in it is seriously broken. With Perm Conn Update=Changed, active profiles will be torn down at random and a random number will succeed in coming back up. The only fix is to set it to Perm Conn Update=All, which forces all permconns down when any are changed or added. Sometimes, a restart is necessary to get them all going again. I opened a ticket on the problem back in April but got nowhere. Granted, the TNT is a different (i.e. good) box than the Terminator, but they both run TAOS... -- Peter Lalor Infoasis plalor at infoasis.com http://www.infoasis.com/ "Where's my burrito?" -- Homer ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request at bungi.com To get FAQ'd: <http://www.nealis.net/ascend/faq>