Setting the flag --without-udpfromto inside debian/rules solved the
issue.
Probably debian/ubuntu testers added it in the default config because
they didn't test it with ipv6, I don't know.
Anyway now it works, thanks all for the help
-
List info/subscribe/unsubscribe? See
http://www.freeradi
I didn't enabled it but maybe the debian-build made it for me without
noticing it.
Anyway it's definetely the udpfromto problem. For debugging I just
forced the define of HAVE_AF_INET6 (that it was not defined and so made
udpfromto_init return -1) and now the code works.
Or better, there is a prob
D'AVELLA STEFANO wrote:
> Exactly the problem is in the udpfromto_init() call inside the
> listen_bind() function.
Then disable udpfromto. It is NOT enabled in the default build of the
server, so the only way you can run into this problem is if you enable a
non-standard feature.
Alan DeKok.
Exactly the problem is in the udpfromto_init() call inside the
listen_bind() function.
Inside this function the return value is set to be:
return setsockopt(s, proto, flag, &opt, sizeof(opt));
with the ipv6 address, it returns -1 (and after a couple of calls and
error logs, the program exits)
Ok I have traced where the problem is (of course it was in the actual
binding of the port).
Listen_init() calls listen_parse() that calls common_socket_parse().
Inside this function around line 510 of listen.c there is this line:
/*
* And bind it to the port.
*/
if (listen_bind(this) < 0)
I don't have selinux installed on the machine, the only installed
package about selinux is the shared library libselinux1, so
I don't think that is the problem. I am thinking that it is something
about the ipv6 config in ubuntu but I am not sure. What I am doing right
now is trying to backtrace t
No problem :)
Maybe a shot in the dark but is selinux enabled? check your logs to see if
any policies are blocking it or type 'echo 0 > /selinux/enforce' then try to
start it again.
--
Leigh
On Tue, Feb 10, 2009 at 3:19 AM, D'AVELLA STEFANO <
stefano.dave...@alcatel-lucent.com> wrote:
> Thanks
Thanks for the suggestion but of course I tried different ways to try to
grep the process :)
I just mentioned one of the command I used to make people understand
that I checked the process list :)
Still no clue about the problem anyway...
Try just 'ps -e|grep radius' that will catch freerad
Try just 'ps -e|grep radius' that will catch freeradius aswell as radiusd
which it is called on some.
--
Leigh
On Mon, Feb 9, 2009 at 12:02 PM, D'AVELLA STEFANO <
stefano.dave...@alcatel-lucent.com> wrote:
> *Be sure that no other freeradius is running and also that you have
> enough rights to
Be sure that no other freeradius is running and also that you have
enough rights to open such a port.
Look in your inet.d or similar to avoid that another service is run
instead of the planned freeradius.
Thanks for the quick answer. I have thought the same because also some
old mailing list po
Am 09.02.2009 um 17:17 schrieb D'AVELLA STEFANO:
Hello,
I am new to Freeradius. I am running Freeradius 2.1.0 on Ubuntu
8.10, built from source.
I have already read all the documentation I could find in the
config files and in the wiki.
The machine has two network interfaces, eth0 and e
Hello,
I am new to Freeradius. I am running Freeradius 2.1.0 on Ubuntu 8.10,
built from source.
I have already read all the documentation I could find in the config
files and in the wiki.
The machine has two network interfaces, eth0 and eth1, the first
configured with ipv4 and the second with i
12 matches
Mail list logo
