CGRateS Radius processing

[tyc...@gmail.com]

Good day,

I am facing a challenge with cgrates not processing radius requests.

I see the information coming via Ngrep but it seems cgrates not showing any events.

Please find config below.

Processing is working when using MikroTik, but failing when coming from different sources, may there be something I am missing.

Regards

[Alexandru Tripon]

Hi Ty,

Please post the CGRateS version you are using( the output of `cgr-engine -version` command).

Also in your configuration, all the request processors have a filter so the reason why there are no events on the CGRateS side may be because of this.

To further debug this please add to the back of the list a new request processor with `*dryrun` and `*log` flags and no filters.

After please post the CGRateS syslog when there are no events from our side.

Thanks,

Trial97

--
You received this message because you are subscribed to the Google Groups "CGRateS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cgrates+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cgrates/45935fb5-165c-4e8b-bf46-249ca5bcec7an%40googlegroups.com.

[tyc...@gmail.com]

Hello Trail97

1. Please find below the results of cgrates version check

[root@andromeda ~]# cgr-engine -version

CGR...@v0.10.2

2. *log tag was already present, but upon your advise added *dryrun and commented out filters.

Still facing same problem, have attached syslog and current config

Regards and Thank you

[Alexandru Tripon]

Hi Ty,

There are no logs related to the RadiusAgent in the syslog you posted so please make sure the following:

- that your `cgr-engine` is running( did not panic in any way)

- the radius package arrives at the port CGRateS listen to

This is because even if the package doesn't match any request processor you should still view a log related to it.

Testing your config found that there are some issues with it:

- the `*authorize` flag is used on master only. For v0.10 you should use the `*auth` flag

- in the v0.10 the `*variable` is not supported in the reply fields please use `*composed` instead

Please update your configuration and retest making sure that the packet arrives at CGRateS.

Thanks,

Trial97

To view this discussion on the web visit https://groups.google.com/d/msgid/cgrates/460bae3e-9945-4e9f-922b-abcfec1b8ebdn%40googlegroups.com.

[tyc...@gmail.com]

Hello Trail97

Relating to suggested corrections, had implemented below 

1. switched CGRateS version from v0.10 to "CGR...@v0.11.0~dev-20210414062129-1aa33a2c687e"

2. ensured that cgr-engine had no panics present at any point during testing

3. radius package reaching server (shared pcap)

Have also shared below the updated config and pcap. there are currently no events in syslog to share related to RadiusAgent (this is where I am stuck)

Thank you for your help. 

Regards,

Ty

[Alexandru Tripon]

Hi Ty,

I retested on the mentioned version with the given configuration by extracting a package from the pcap and sending it to CGRateS.

The logs from the requests processors were displayed correctly on the syslog.

Please make sure that you the packages arrive at the address CGRateS listens to.

You could also check the stdout of cgr-engine command to see if there are some logs regarding the radius avps.

Thanks,

Trial97

To view this discussion on the web visit https://groups.google.com/d/msgid/cgrates/3f63359b-89c4-4bbb-9518-08fbd6f6226fn%40googlegroups.com.