[NEBULA] Accounting Stop values

yomismo

Hello all,

We are testing Zyxel Nebula with an external captive portal and external Radius authentication.

As I can see, Accounting Interim packets are sent every 60 seconds with Acct-Input-Octets and Acct-Output-Octets values:

User-Name = "38205631@XXXXX"
Framed-IP-Address = 172.16.40.169
Acct-Session-Id = "5C0FA66D"
Acct-Status-Type = Interim-Update
Acct-Authentic = RADIUS
NAS-IP-Address = 127.0.0.1
NAS-Port = 1787
NAS-Port-Type = Ethernet
Calling-Station-Id = "24-FD-52-XX-XX-XX"
Called-Station-Id = "60-31-97-XX-XX-XX:Nebula"
Acct-Session-Time = 61
Acct-Input-Octets = 105400
Acct-Output-Octets = 403250
Event-Timestamp = Dec 11, 2018 12:48:57.000000000 Hora estándar romance

But the Accounting Stop packet send those values as 0:

User-Name = "38205631@XXXXXX"
Acct-Session-Id = "5C0FA66D"
Acct-Status-Type = Stop
Acct-Authentic = RADIUS
NAS-IP-Address = 127.0.0.1
NAS-Port = 1787
NAS-Port-Type = Ethernet
Calling-Station-Id = "24-FD-52-XX-XX-XX"
Called-Station-Id = "60-31-97-XX-XX-XX:Nebula"
Acct-Session-Time = 504
Acct-Input-Octets = 0
Acct-Output-Octets = 0
Event-Timestamp = Dec 11, 2018 12:56:20.000000000 Hora estándar romance

Please let me know if there is anything I can do to help solve this issue. Or that is the way that Nebula works?

Thanks in advanced,

Zyxel_Freda

Hi @yomismo,

This issue will be resolved in next release in Jan. 2020.

Thanks.

Zyxel_Barney

Hi @yomismo

Thank you for providing us with detailed information!
We are able to observe similar results on our lab and are investigating the issue.

In the mean time, we would like to learn more about your deployment through private message.

Regards,
Barney Gregorio

Zyxel_Barney

Hi @yomismo

After further investigation, we found out that there was an issue with how the AP maintains it's wireless client information. We will improve this feature in the next official firmware release.

If you need a hot fix for this issue, then please contact me through private message.

Regards,
Barney Gregorio

yomismo

Hello Burney,

Could you please let me know if this bug is solved?

I am installing 2 real installations and I have same problem so I need to fix this issue.

Regards,

Zyxel_Freda

Hi @yomismo,

This issue will be resolved in next release in Jan. 2020.

Thanks.