Config Examples

[Alex Bahoor]

Alen,

As other explained, when the port is set to 0, the daemon will take any port
dynamically. However, thanks to Tim, he cleared out my confusion, and I see
clearly the ports are in fact 1812 and 1813. 

udp 	0	0 *:radius		*:*
udp	0	0 *:radius-acct	*:*

So after all, it's not selecting random port numbers. Is this a bug?

Alex



-----Original Message-----
From: freeradius-users-bounces+alexbahoor=sbcglobal.net at lists.freeradius.org
[mailto:freeradius-users-bounces+alexbahoor=sbcglobal.net at lists.freeradius.o
rg] On Behalf Of Alan Buxey
Sent: Sunday, December 06, 2009 2:52 PM
To: FreeRadius users mailing list
Subject: Re: Config Examples

Hi,

> How rude! I can't believe highly professional people could be so
uncivilized
> on mail aliases. It's cowardly to hide behind the internet and insult
> people. Where is the moderator from all that?

hide behind? aliases?

i'm not sure where this paranoia comes from - we arent using aliases
or hiding who we are. anyway......

your initial question was about the config file and the values
in it.

if you choose the value '0' then this means freeradius will bind
to your chosen interface with the default RFC values - ie UDP 1812,
1813 and 1814  - you could just as well configure the value if you wanted.

all this talk of 'dynamic port assignment' is just confusing what the option
is, how it operates and WHY you would choose a different port. 

if you ran your daemon, and then used netstat with correct arguments you
would
clearly see that the daemon listens on the expected port and is happy for
clients - 
thats CLIENTS - to come from any source port - which is what clients do. ie
*:*

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

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4665 (20091206) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
 
 

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4665 (20091206) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com