Actually in IP the source port is not of any significance EXCEPT that it
exist. On servers we *lock* applications to specific ports so that we
can find specific services AND utlize a server in several roles (web,
e-mail, radius, etc.). Typically on the client side the system starts
at port
There is no typical port used. Unless the application binds the
request to a specific port the OS picks for first available port. When
doing socket level programming it is best to leave it to the OS to pick
a port to send from (client side). The destination is fixed on a
specific port so
Thor Spruyt [EMAIL PROTECTED] wrote:
This doesn't say anything about which source port that is typically used in
case of a radius reply.
The reply comes FROM the port that the NAS sent the packet TO.
Alan DeKok.
-
List info/subscribe/unsubscribe? See
- Original Message -
From: Alan DeKok [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, June 27, 2004 3:17 PM
Subject: Re: Replies on port 1029
Thor Spruyt [EMAIL PROTECTED] wrote:
This doesn't say anything about which source port that is typically used
in
case of a radius
Thor Spruyt [EMAIL PROTECTED] wrote:
In other words: if your radius server is configured to listen on port 1812
it SHOULD sent replies FROM port 1812
And if it's listening on another port, then the situation is different.
Why such difficult answers to the original questions?
Because
:[EMAIL PROTECTED] On Behalf Of Paul
Hampson
Sent: Thursday, June 24, 2004 9:52 PM
To: [EMAIL PROTECTED]
Subject: RE: Replies on port 1029
From: Gary McKinney
Sent: Friday, 25 June 2004 3:13 AM
Brian,
That is the correct way for operation!
Radius Listens on Ports 1812 and 1813
From: Brian Andrus
Sent: Friday, 25 June 2004 4:01 PM
Well it is very odd to me. The proxy requests to me from another freeradius
are failing because the response is being sent back on a different port than
they were sent on.
What does the packet dumper say, at your end of the link?
--
What is failing? Is FreeRadius ignoring the response packets or do they not
arrive?
- Original Message -
From: Brian Andrus [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, June 25, 2004 8:00 AM
Subject: RE: Replies on port 1029
Well it is very odd to me. The proxy requests to me
Wha?? No it doesn't.
FTP opens a _second_ connection for data, but telnet and HTTP
both use the existing TCP
connection for data back to the client. And an IP connection
is defiened by five things:
(local address, local port, remote address, remote port, and
protocol (TCP)) These
Brian Andrus [EMAIL PROTECTED] wrote:
Well it is very odd to me. The proxy requests to me from another freeradius
are failing because the response is being sent back on a different port than
they were sent on.
You already said that, and I already responded, telling you how to
debug the
Check your /etc/services file. If a port is not specified in the radius
config, radius looks to /etc/services for the port. If none is
specified there then I guess it takes the first non-prevlidged port.
Mark C.
Brian Andrus wrote:
I have been using freeradius .9.1 for some time now. I have
:[EMAIL PROTECTED] On Behalf Of Mark
Coccimiglio
Sent: Thursday, June 24, 2004 12:46 AM
To: [EMAIL PROTECTED]
Subject: Re: Replies on port 1029
Check your /etc/services file. If a port is not specified in the radius
config, radius looks to /etc/services for the port. If none is specified
Brian Andrus [EMAIL PROTECTED] wrote:
And when I start freeradius up, it grabs 1812 and 1813 for listening. The
odd thing is that it seems to grab the first non-priviledged port for
sending out responses.
The server *should* send response FROM the port that the NAS sent
packets TO. If it
The Best,
Brian Andrus
Millenia Internet Services, Inc.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mark
Coccimiglio
Sent: Thursday, June 24, 2004 12:46 AM
To: [EMAIL PROTECTED]
Subject: Re: Replies on port 1029
Check your /etc/services file
From: Gary McKinney
Sent: Friday, 25 June 2004 3:13 AM
Brian,
That is the correct way for operation!
Radius Listens on Ports 1812 and 1813 ( for authentication and accounting
respectively) BUT responds back to the NAS on
the first non-priviledged port the system has available for
15 matches
Mail list logo
