Lost-Carrier Problem

[Sergen Çolak]

Hi Everyone,

The session is terminated when users do not use it for a while. In the radacct table, an attribute is formed as Lost-Carrier. Is there a way to extend this period?

I apologize for the bad english.

[Timothy White]

Hi Sergen

Under Coova Chilli Settings, you want to change "Default Session Idle
Time". However, this is any network activity from the computer. So if
you've not seen any packets from a modern computer in 10 minutes, they
are normally no longer connected. Modern OS's are very chatty and send
packets regularly.

Tim

> --
> This mailing list is for the Grase Hotspot Project http://grasehotspot.org
> ---
> You received this message because you are subscribed to the Google Groups
> "Grase Hotspot" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to grase-hotspo...@grasehotspot.org.
> To post to this group, send email to grase-...@grasehotspot.org.
> Visit this group at
> https://groups.google.com/a/grasehotspot.org/group/grase-hotspot/.
> To view this discussion on the web visit
> https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/d8a0febe-bb25-4661-9bdc-935060fd8f76%40grasehotspot.org.

[Sergen Çolak]

Hi Tim,

Thanks for the reply. I will try the parameter if it is okay, but what I want is a lost-carrier after 10 minutes when the user turns off the wifi connection. Can not we do it for 30 minutes or 1 hour, not 10 minutes?

I understand that idletimeout does not work for me.

Thank you.

23 Şubat 2018 Cuma 10:37:33 UTC+3 tarihinde Sergen Çolak yazdı:

[Timothy White]

Hi Sergen

We actually don't have any way to detect the difference between
someone turning off the Wifi, and not using a device. In theory, the
AP's know if we device is still connected, but we aren't the AP, we
don't have that data. Idletimeout is more critical to be low when
limiting people by time. That way, if they get disconnected, at the
most they'll use an extra "idletime" worth of time before they are
automatically logged out. If your users don't have time limits, then
you can increase the idletimeout much bigger.

Regards

Tim

> --
> This mailing list is for the Grase Hotspot Project http://grasehotspot.org
> ---
> You received this message because you are subscribed to the Google Groups
> "Grase Hotspot" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to grase-hotspo...@grasehotspot.org.
> To post to this group, send email to grase-...@grasehotspot.org.
> Visit this group at
> https://groups.google.com/a/grasehotspot.org/group/grase-hotspot/.
> To view this discussion on the web visit

> https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/cfbea15a-2d51-4ff9-a1f7-d7a1b2f8be72%40grasehotspot.org.

[Sergen Çolak]

Hello hello tim,

I have solved the Lost-Carrier problem. I did not make any changes to the idletimeout value while doing this. Idletimeout is disabled on the system. I got rid of the Lost-Carrier result after 600 seconds with the HS_LEASE parameter. I added this parameter to the chili config file.

To provide information. Thank you for your answers

23 Şubat 2018 Cuma 10:37:33 UTC+3 tarihinde Sergen Çolak yazdı:

Hi Everyone,