I meant on the MT. As for radius, how does the radius get attributes set?
Are you just accessing the db directly? If you don't have access to the
radius server, it would be difficult as the send function is a manual
command. But you could always log into the MT and knock it off through CLI
or API.



On Wed, Jan 20, 2016 at 1:47 PM, Simon Westlake <[email protected]>
wrote:

> Because I might not have access to SSH/CLI on that RADIUS server if it's
> not a server I control. I'm trying to find a way that isn't reliant on
> Mikrotik as the NAS, seems like the disconnect packet is the right way.
> Looks like maybe it can be done using unlang or the rlm_perl/python modules
> to trigger based on some other event though.. still messing with it.
>
> On 1/20/2016 1:45 PM, Cameron Crum wrote:
>
> Why wouldn't it come from the radius you configured? Or why not add
> another ip as another radius that only accepts incoming requests if you
> don't want to use the regular radius? Alternatively, it can be done through
> cli on ssh or through the API.
>
> On Wed, Jan 20, 2016 at 1:41 PM, Simon Westlake <[email protected]>
> wrote:
>
>> Hmm, well after playing with it, it seems that Mikrotik doesn't like the
>> incoming RADIUS commands being sent unless it originates from the RADIUS
>> server it is configured to use, which makes life difficult. Is this the
>> solution everyone here is using to force a refresh of attributes?
>>
>> On 1/20/2016 12:52 PM, Simon Westlake wrote:
>>
>> That certainly sounds like the best solution. Thanks!
>>
>> On 1/20/2016 12:48 PM, Cameron Crum wrote:
>>
>> PPPOE can be dropped with an incoming radius command.
>>
>> On Wed, Jan 20, 2016 at 12:42 PM, Simon Westlake <[email protected]>
>> wrote:
>>
>>> How are you handling changes to your services today if you're using
>>> PPPoE?
>>>
>>> For example, let's say a customer is receiving specific attributes to
>>> set their speed, or IP address, or whether they should be redirected to a
>>> splash page. If you change one of these attributes, what is your current
>>> strategy for forcing a re-auth to update the attributes? Seems like it is
>>> pretty easy while you're on the phone with a customer to either login to
>>> your own gear and reauth the session, or tell them to reboot their router,
>>> or whatever their authenticated device is. But if they are disabled and
>>> they make a payment on a splash page, it seems like it would be likely to
>>> generate a service call if the splash page tried telling them to do
>>> something like reboot their router or radio.
>>>
>>> --
>>> Simon Westlake
>>> Skype: Simon_Sonar
>>> Email: [email protected]
>>> Phone: (702) 447-1247 <%28702%29%20447-1247>
>>> ---------------------------
>>> Sonar Software Inc
>>> The next generation of ISP billing and OSS
>>> https://sonar.software
>>>
>>>
>>
>> --
>> Simon Westlake
>> Skype: Simon_Sonar
>> Email: [email protected]
>> Phone: (702) 447-1247
>> ---------------------------
>> Sonar Software Inc
>> The next generation of ISP billing and OSShttps://sonar.software
>>
>>
>> --
>> Simon Westlake
>> Skype: Simon_Sonar
>> Email: [email protected]
>> Phone: (702) 447-1247
>> ---------------------------
>> Sonar Software Inc
>> The next generation of ISP billing and OSShttps://sonar.software
>>
>>
>
> --
> Simon Westlake
> Skype: Simon_Sonar
> Email: [email protected]
> Phone: (702) 447-1247
> ---------------------------
> Sonar Software Inc
> The next generation of ISP billing and OSShttps://sonar.software
>
>

Reply via email to