ermmm

whereabouts in 
/usr/local/src/freeradius-server-3.0.0/raddb/sites-available/tls ?

Looing at file,there’s 



listen {
        ipaddr = *
        port = 2083
        type = auth

        # For now, only TCP transport is allowed.
        proto = tcp

        # Send packets to the default virtual server
        virtual_server = default

        clients = radsec
        tls {
…… 
}

clients radsec {
        client 127.0.0.1 {
                ipaddr = 127.0.0.1
                proto = tcp
                secret = testing123
        }
}

listen {
       ipaddr = 127.0.0.1
       port = 4000
       type = auth
}




On 7 Nov 2013, at 16:18, Alan DeKok <aland@deployingradius.com> wrote:

Alex Sharaz wrote:
Quick question about setting up radsec and FR3. When I was playing with RADSEC and Radiator, a permanent link was established between two radsec endpoints ( had radsec/ipv4 -> Ubuntu VM out in the cloud and then radsec/ipv6 -> Radiator on OS X machine at home). Should FR do this as well, or does it just establish a connection whenever it needs one?

 The server establishes connections only when needed.

Had some sort of success with radsecproxy and FR3 but then FR3 complained about exceeding max client connections (>16)

 That's why the config files are editable.  You can change that.  See
the "listen" section of raddb/sites-available/tls.

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