Jorge Pereira
Jorge Pereira
Get rid of the warning message. ``` InfoScreen.c:138:15: warning: misleading indentation; statement is not part of the previous 'if' [-Wmisleading-indentation] } if (mevent.y == LINES - 1) ^ InfoScreen.c:134:10: note:...
It fixes the below warnings. ``` clang -DHAVE_CONFIG_H -I. -DNDEBUG -pedantic -Wall -Wextra -std=c99 -D_XOPEN_SOURCE_EXTENDED -DSYSCONFDIR=\"/usr/local/etc\" -I"./linux" -rdynamic -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -g -O2 -MT linux/LinuxProcessList.o -MD -MP -MF $depbase.Tpo -c -o...
yep, I will take a look.
Hi @NorthFuture , Could you perform the tests using the latest code from https://github.com/FreeRADIUS/pam_radius ? e.g: ``` # git clone https://github.com/FreeRADIUS/pam_radius # cd pam_radius ``` For Debian... ``` # make...
@NorthFuture have you had a chance to validate? either way, it isn't an issue. just use the latest 2.0.1 from the HEAD.
@NorthFuture please, copy and paste the content of your `*.conf` file.
@NorthFuture exactly
That's is the problem. If you take a look at https://github.com/FreeRADIUS/pam_radius/blob/master/pam_radius_auth.conf#L47 you will see that for ipv6 we have some special config set. in your case. please try: ``` [my_radius_server]:31812...
@NorthFuture No worries, we are trying to figure out if it is a real issue or not. so, the next try is to configure like: IPv4 ``` 127.0.0.1:1812 mysecret 20...
@horaceou very hard to help without the `radiusclient.conf` even without the output of the `freeradius -X` and `radlogin -f /etc/radiusclient/radiusclient.conf`