At 02:54 PM 12/5/2009, Alex Bahoor wrote:
Ivan,
Imagine DNS uses dynamic port assignment instead of port 53? Guess what, no one would be able to use the internet. :-)
Alex
First, I believe you're trying to respond to me. Second, you're asking questions about which you don't apparently understand. What if I wanted to run my own implementation of DNS to do something bizarre? SSH on a different port than 22 (quite common)? A web server on port 88? Telnet on port 8000. I can do all of those things. And apache, bind, tftp, ftp, telnet, sshd (and really almost every service that assigns a port) all have the ability to change the default port. If I'm running my own services, I might want the ability to run them on non-standard ports. That's why there are defaults, AND the ability to change them. Rick
Rick, If I want to connect someonesWebServer.com, the only way I can do that is to map the name to an IP address. First thing, I would use my default DNS server which is served by my ISP to query the name. Because this is a puplic DNS server, there in on way in the world you set a private port number, and expect every user to query names in a broadcast form. The port must be 53 period. Similarly, when this DNS server does know not about someonesWebServer.com, he would have to go to the next level DNS on the Internet to query the name. That DNS server must be using 53 as well. This is a fundamental requirement on public networks setup. You can still change the ports on your private DNS server to any thing you want for security reasons. For that matter, Broadcasts queries by any local client would not be able to resolve names--all the client must be configured with its dns ip address so it avoid broadcast. Let me make it clear on public networks, and Internet, the only port you would see on any DNS server is the default (53), otherwise, internet would not be dynamic, and would be very clunky. And all DNS servers on the internet build their diarchy based on broadcast. I hope that help, Alelx -----Original Message----- From: freeradius-users-bounces+alexbahoor=sbcglobal.net@lists.freeradius.org [mailto:freeradius-users-bounces+alexbahoor=sbcglobal.net@lists.freeradius.o rg] On Behalf Of freeradius@corwyn.net Sent: Saturday, December 05, 2009 5:04 PM To: FreeRadius users mailing list; 'FreeRadius users mailing list' Subject: RE: Config Examples At 02:54 PM 12/5/2009, Alex Bahoor wrote:
Ivan,
Imagine DNS uses dynamic port assignment instead of port 53? Guess what, no one would be able to use the internet. :-)
Alex
First, I believe you're trying to respond to me. Second, you're asking questions about which you don't apparently understand. What if I wanted to run my own implementation of DNS to do something bizarre? SSH on a different port than 22 (quite common)? A web server on port 88? Telnet on port 8000. I can do all of those things. And apache, bind, tftp, ftp, telnet, sshd (and really almost every service that assigns a port) all have the ability to change the default port. If I'm running my own services, I might want the ability to run them on non-standard ports. That's why there are defaults, AND the ability to change them. Rick - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html __________ Information from ESET NOD32 Antivirus, version of virus signature database 4663 (20091205) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 4663 (20091205) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com
freeradius@corwyn.net wrote:
I hope that help,
It helps show you're not worth bothering with. Thanks.
...with a GMAME feed you can use your NNTP clients score file to solve this particular problem. :) Cheers -- Alexander Clouter .sigmonster says: I can't drive 55.
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? Alex -----Original Message----- From: freeradius-users-bounces+alexbahoor=sbcglobal.net@lists.freeradius.org [mailto:freeradius-users-bounces+alexbahoor=sbcglobal.net@lists.freeradius.o rg] On Behalf Of Alexander Clouter Sent: Sunday, December 06, 2009 3:10 AM To: freeradius-users@lists.freeradius.org Subject: Re: Config Examples freeradius@corwyn.net wrote:
I hope that help,
It helps show you're not worth bothering with. Thanks.
...with a GMAME feed you can use your NNTP clients score file to solve this particular problem. :) Cheers -- Alexander Clouter .sigmonster says: I can't drive 55. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html __________ Information from ESET NOD32 Antivirus, version of virus signature database 4663 (20091205) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 4663 (20091205) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com
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
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@lists.freeradius.org [mailto:freeradius-users-bounces+alexbahoor=sbcglobal.net@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
Alex Bahoor wrote:
As other explained, when the port is set to 0, the daemon will take any port dynamically.
This is not what the documentation says. It is not what people told you on this list.
However, thanks to Tim, he cleared out my confusion, and I see clearly the ports are in fact 1812 and 1813.
This was explained to you multiple times by multiple people.
udp 0 0 *:radius *:* udp 0 0 *:radius-acct *:*
So after all, it's not selecting random port numbers. Is this a bug?
Since you are not reading the documentation or the responses on this list, I don't see why you are asking questions. Alan DeKok.
Hi,
Alen,
you know my name - i dont mispell it in my emails :-(
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 *:*
there should be no confusion - netstat clearly describes what each column is and what is represents
So after all, it's not selecting random port numbers. Is this a bug?
it NEVER selects a random port - i dont know where you are getting this crazy idea from about dynamic random port if port = 0 please read the few lines above that option, ie # Port on which to listen. # Allowed values are: # integer port number (1812) # 0 means "use /etc/services for the proper port" port = 0 which bit of "0 means "use /etc/services for the proper port"" is not clear? if you've put some crazy value into /etc/services then that'd be your problem alan
You can still change the ports on your private DNS server to any thing you want for security reasons.
So, you say yourself that even in the case you are most fond of (DNS) changing "default" port is OK as na option. What was the problem with freeradius having the same option? Please stop trolling on this list. Ivan Kalik
participants (7)
-
Alan Buxey -
Alan DeKok -
Alex Bahoor -
Alexander Clouter -
freeradius＠corwyn.net -
Tim Sylvester -
tnt＠kalik.net