If you haven't overridden it in the radius.cfg file, then its getting its
default ports from the /etc/services file
If you edit that file to have 1645 and 1646 instead of 1812 and 1813(?) and
restart radius, it should
bind to those ports.

You can also override the /etc/services file by adding to the radius.cfg
AuthPort    1645
AcctPort    1645

----- Original Message -----
From: "Lisa Goulet" <[EMAIL PROTECTED]>
To: "'Radiator@Open. Com. Au'" <[EMAIL PROTECTED]>
Sent: Monday, October 16, 2000 10:58 AM
Subject: (RADIATOR) RE: Proxy getting no reply


>
> Hello again,
>
> Here's a follow up question.
>
> Now I'm seeing on the console that the proxy server is sending on port
1645.
> Both servers are listening on 1812. Where is the sending port configured?
>
> Thanks again,
> Lisa
>
>
> > -----Original Message-----
> > From: Lisa Goulet
> > Sent: Monday, October 16, 2000 4:05 PM
> > To: Radiator@Open. Com. Au
> > Subject: Proxy getting no reply
> >
> >
> > Hello,
> >
> > I have a simple set up with one Radiator master and one proxy. When
> > testing with radpwtst I'm getting a "no reply".  I've double checked the
> > ip address, secret and the ports. I don't see much in the log files.
Here
> > are my configs:
> >
> > Proxy:
> >
> > Trace   4
> >
> > Foreground
> > LogStdout
> > LogDir          .
> > DbDir           .
> >
> >
> > # Handle everyone with RADIUS
> > <Realm DEFAULT>
> >         <AuthBy RADIUS>
> >                 AuthPort 1812
> >                 AcctPort 1813
> >                 Host xxx.xxx.xxx.xxx
> >                 Secret mysecret
> >                 CachePasswords
> >                 CachePasswordExpiry
> >         </AuthBy>
> > </Realm>
> >
> > Master radiator server:
> >
> > Trace   4
> >
> > Foreground
> > LogStdout
> > LogDir          .
> > DbDir           .
> >
> > AuthPort        1812
> > # AcctPort specifies the port to list on for accounting requests
> > AcctPort        1813
> >
> > <Client DEFAULT>
> >         Secret  mysecret
> >         DupInterval 0
> > </Client>
> >
> > # You can put additonal (or all) client details in your Radmin
> > # database table
> > # and get their details from there with something like this:
> > # You can then use the Radmin 'Add Radius Client' to add new
> > clients.
> > <ClientListSQL>
> >         DBSource        dbi:Pg:dbname=radmin;host=localhost
> >         DBUsername      radmin
> >         DBAuth          radmin
> > </ClientListSQL>
> >
> > # Handle everyone with RADMIN
> > <Realm DEFAULT>
> >         <AuthBy RADMIN>
> >                 # Change DBSource, DBUsername, DBAuth for your
> > database
> >                 # See the reference manual. You will also have to
> >                 # change the one in <SessionDatabse SQL> below
> >                 # so its the same
> >                 DBSource        dbi:Pg:dbname=radmin;host=localhost
> >                 DBUsername      radmin
> >                 DBAuth          radmin
> >
> >                 # You can add to or change these if you want, but
> > you
> >                 # will probably want to change the database schema
> > first
> >                 AccountingTable RADUSAGE
> >                 AcctColumnDef   USERNAME,User-Name
> >                 AcctColumnDef   TIME_STAMP,Timestamp,integer
> >                 AcctColumnDef
> > ACCTSTATUSTYPE,Acct-Status-Type,integer
> >                 AcctColumnDef
> > ACCTDELAYTIME,Acct-Delay-Time,integer
> >                 AcctColumnDef
> > ACCTINPUTOCTETS,Acct-Input-Octets,integer
> >                 AcctColumnDef
> > ACCTOUTPUTOCTETS,Acct-Output-Octets,integer
> >                 AcctColumnDef   ACCTSESSIONID,Acct-Session-Id
> >                 AcctColumnDef
> > ACCTSESSIONTIME,Acct-Session-Time,integer
> >                 AcctColumnDef
> > ACCTTERMINATECAUSE,Acct-Terminate-Cause,integer
> >                 AcctColumnDef   FRAMEDIPADDRESS,Framed-IP-Address
> >                 AcctColumnDef   NASIDENTIFIER,NAS-Identifier
> >                 AcctColumnDef   NASIDENTIFIER,NAS-IP-Address
> >                 AcctColumnDef   NASPORT,NAS-Port,integer
> >                 AcctColumnDef   DNIS,Called-Station-Id
> >
> >                 # This updates the time and octets left
> >                 # for this user
> >                 AcctSQLStatement update RADUSERS set
> > TIMELEFT=TIMELEFT-0%{Acct-Session-Time},
> > OCTETSINLEFT=OCTETSINLEFT-0%{Acct-Input-Octets},
> > OCTETSOUTLEFT=OCTETSOUTLEFT-0%{Acct-Output-Octets} where USERNAME='%n'
> >
> >                 # These are the classic things to add to each users
> >                 # reply to allow a PPP dialup session. It may be
> >                 # different for your NAS. This will add some
> >                 # reply items to everyone's reply
> >                 AddToReply Framed-Protocol = PPP,\
> >                         Framed-IP-Netmask = 255.255.255.255,\
> >                         Framed-Routing = None,\
> >                         Framed-MTU = 1500,\
> >                         Framed-Compression = Van-Jacobson-TCP-IP
> >         </AuthBy>
> > </Realm>
> >
> > <SessionDatabase SQL>
> >         # This database spec usually should be exactly the same
> >         # as in <AuthBy RADMIN> above
> >         DBSource        dbi:Pg:dbname=radmin;host=localhost
> >         DBUsername      radmin
> >         DBAuth          radmin
> >
> > </SessionDatabase>
> >
> > [Lisa Goulet]
>
> ===
> Archive at http://www.starport.net/~radiator/
> Announcements on [EMAIL PROTECTED]
> To unsubscribe, email '[EMAIL PROTECTED]' with
> 'unsubscribe radiator' in the body of the message.
>


===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.

Reply via email to