lists.freeradius.org
Sign In Sign Up
Manage this list Sign In Sign Up

Keyboard Shortcuts

Thread View

  • j: Next unread message
  • k: Previous unread message
  • j a: Jump to all threads
  • j l: Jump to MailingList overview
thread

Re:

Deepansha Gaur

30 Nov 2023 30 Nov '23
12:10 p.m.

Hi Mathias, Could you please confirm what logs do you need? Below are the radsniff and tcpdump outputs. root@test-freeradius:/home/dgaur# radsniff -i ens160 2023-11-30 10:07:07.548759 (1) Access-Request Id 67 ens160: 172.20.252.242:32778 -> 142.244.0.47:1812 +0.000 2023-11-30 10:07:12.748759 (1) ** norsp ** Access-Request Id 67 ens160: 172.20.252.242:32778 -> 142.244.0.47:1812 2023-11-30 10:07:17.567318 (2) Access-Request Id 68 ens160: 172.20.252.242:32778 -> 142.244.0.47:1812 +10.018 2023-11-30 10:07:22.767318 (2) ** norsp ** Access-Request Id 68 ens160: 172.20.252.242:32778 -> 142.244.0.47:1812 root@test-freeradius:/home/dgaur# tcpdump -eqnnntl -i ens160 port 1812 tcpdump: verbose output suppressed, use -v[v]... for full protocol decode listening on ens160, link-type EN10MB (Ethernet), snapshot length 262144 bytes a2:01:00:00:01:70 > 00:50:56:a2:64:59, IPv4, length 336: 172.20.252.242.32778 > 142.244.0.47.1812: UDP, length 294 a2:01:00:00:01:70 > 00:50:56:a2:64:59, IPv4, length 336: 172.20.252.242.32778 > 142.244.0.47.1812: UDP, length 294 a2:01:00:00:01:70 > 00:50:56:a2:64:59, IPv4, length 336: 172.20.252.242.32778 > 142.244.0.47.1812: UDP, length 294 a2:01:00:00:01:70 > 00:50:56:a2:64:59, IPv4, length 336: 172.20.252.242.32778 > 142.244.0.47.1812: UDP, length 294 "freeradius -X" and "/var/log/freeradius/radius.log" show nothing. Thanks. Regards, Deepansha Gaur On Thu, Nov 30, 2023 at 9:53 AM Mathias Maes < mathias.maes@maerlantatheneum.be> wrote:

...

Please post full logs as requested in the documentation. We have no idea what's going on now.

Op do 30 nov. 2023 17:51 schreef Deepansha Gaur <dgaur@ualberta.ca>:

...

Hi Team,

We are in the process of migrating from radiator to freeradius. I have a test freeradius server built on Ubuntu. When I am authenticating locally, radtest is successful. I added a wireless controller client and when I try to connect to the wifi using that client and freeradius authentication, it keeps failing. I see requests from the client to freeradius server but no response from freeradius. Below are the logs for reference: a2:01:00:00:01:70 > 00:50:56:a2:64:59, IPv4, length 336: WIRELESS_IP.32778

...

RADIUS_IP.1812: UDP, length 294 There's no response from the radius server.

Below are the firewall rules: nft add rule ip filter input udp dport 1812 counter accept nft add rule ip filter input udp dport 1813 counter accept

Please let me know if you need any further information. Thanks.

Regards, Deepansha Gaur - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

0 0
Reply
Sign in to reply online Use email software

Back to the thread

Back to the list

HyperKitty Powered by HyperKitty version 1.3.12.