Splynx radius authentication failed


#1

Hello, I have configured the mikrotik to be a PPPoE server, and to use Splynx as radius.
But everytime the pppoe clients tries to authenticate to the server, at server i see the log authentication failed. The username and password is correct, and the radius of splynx is configured with the same key as the mikrotik pppoe server. Please help me, thank you


#2

I have found similar problem and I think this is how I fixed it:

Check router clock is in sync with server
Check service/customer is active
Check radius Src Address field is same as external IP of NAS and no NAT and check your NAS IP in splynx routers config


#3

Splynx Radius configuration and troubleshooting


#4

Happens to me too. Then eventually connects like afer 10-30 tries.


#5

Check router clock is in sync with server
----Where to check the clock of splynx? It is web managed.

Check service/customer is active
----It is active

Check radius Src Address field is same as external IP of NAS and no NAT and check your NAS IP in splynx routers config
----It is configured correctly, i see sessions from mikrotik originating at the IP that is configured.
Also at Radius is the mikrotik nas configured

It seems like Splynx radius doesnt receive requests from mikrotik, but mikrotik i see that tries to make them.


#6

The Splynx server’s time is the Linux host servers time. Not sue how important this is but couldn’t hurt to make sure they are in sync.
You can get the current time by SSH into the server and type date


#7

Hello,
I have synchronized the clocks, but still the same.
From Splynx it says to start freeeradius, and below is the output
Thu Jun 29 07:25:24 2017 : Info: Ready to process requests
Thu Jun 29 07:25:32 2017 : Error: Ignoring request to auth address * port 1812 bound to server default from unknown client 160.119.127.250 port 44812 proto udp

Could you please help


#8

Hi, this error Thu Jun 29 07:25:32 2017 : Error: Ignoring request to auth address * port 1812 bound to server default from unknown client 160.119.127.250 port 44812 proto udp

Says that IP address of router is different than what is set in Splynx -> Router -> Host. So, I think it’s a NAT issue

Can you send us a ticket pls with teamviewer access and our engineers will help you to troubleshoot it.


#9

Hi,
The mikrotik that is serving as pppoe server is has a loopback public ip 160.119.127.250
[admin@PPPoE-Server] > ping 46.101.94.219 src-address=160.119.127.250
SEQ HOST SIZE TTL TIME STATUS
0 46.101.94.219 56 55 107ms
1 46.101.94.219 56 55 107ms
2 46.101.94.219 56 55 106ms

Also at Radius I have configured to have as source the same IP 160.119.127.250.
From Server Splynx i can ping the mikrotik
ping 160.119.127.250
PING 160.119.127.250 (160.119.127.250) 56(84) bytes of data.
64 bytes from 160.119.127.250: icmp_seq=1 ttl=54 time=106 ms
64 bytes from 160.119.127.250: icmp_seq=2 ttl=54 time=106 ms

So is not a matter of NAT i think.
This case is being followed by Jorge Gomis Castello with teamviewer, but till now is not resolved.
Please help us.

Thank you
Ernest


#10

This is NAT issue 100 % :slight_smile: I will connect to your teamviewer and show you


#11

the problem found, freeradius 3.0 is running. Splynx doesn’t work on 3.0 yet


#12

Thanks a lot for your support
We will downgrade to Debian 8 with radius 2.0 and check it.

Ernest


#13

Hello Alex,

any News for Debian9 / Freeradius3 support?

Heiko