Kenneth Grady wrote:
Oh I get it. I'm a proxy to an unknown home server and should shut it
off, unless I want to proxy requests to somewhere else.
As I understood, you don't want to proxy... but you want another radius
server to proxy requests to you.
If you uncomment all proxy items in your conf
Oh I get it. I'm a proxy to an unknown home server and should shut it
off, unless I want to proxy requests to somewhere else.
On Fri, 2004-11-12 at 10:57, Kenneth Grady wrote:
> Then why would I be listening on port 1814? if it's a source port?
> just to see if someone is trying to break in?
>
>
Kenneth Grady <[EMAIL PROTECTED]> wrote:
> Then why would I be listening on port 1814? if it's a source port?
> just to see if someone is trying to break in?
When run in debug mode, the server prints out which ports it's
listening on, and why. usually:
1812 is for incoming Access-Request pac
Then why would I be listening on port 1814? if it's a source port?
just to see if someone is trying to break in?
On Fri, 2004-11-12 at 10:36, Thor Spruyt wrote:
> Kenneth Grady wrote:
> > I think I can use port 1812, but thought that 1814 was designed for
> > just
> > this sitation.
>
> Port 1814
Kenneth Grady wrote:
I think I can use port 1812, but thought that 1814 was designed for
just
this sitation.
Port 1814 is used as source port if your server sends packets to another
radius server (functioning as proxy).
In your case, the remote radius server should send authentication packets to
I have a freeradius server running authorizing via LDAP and
authenticating via Kerberos (very nice). We want to have an outside
company (outside our firewall) provide access to our users world wide. I
looked at proxy and didn't see much that I needed to do on my home
server save add the radius serv
6 matches
Mail list logo
