I've you seen my post or are you just ignoring it ? :)
-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
De la part de Angel L. Mateo
Envoyé : mardi 26 septembre 2006 08:34
À : freeradius-users@lists.freeradius.org
Objet : Re: Source IP address for proxy requests
El lun
On the active server (the one that have 192.168.1.1) you have to delete the
route that route packets through 192.168.1.2 for subnet 192.168.1.1/24 and
make sure there's a route through 192.168.1.1 for subnet 192.168.1.1/24.
This way, all connexion initiate from this box will have source address
192
]
[mailto:[EMAIL PROTECTED] De la part de Giuseppina Venezia
Envoyé : lundi 31 juillet
2006 16:26
À : FreeRadius users mailing
list
Objet : Re: ippool error
On 7/31/06, Sebastien
Cantos <[EMAIL PROTECTED]>
wrote:
I've something like this in the user file :
accounting {
…..
main_pool
….
Regards,
Sebastien.
De :
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] De la part de Giuseppina Venezia
Envoyé : lundi 31 juillet
2006 14:31
À : FreeRadius users mailing
list
Objet : Re: ippool error
On 7/31/06, Sebastien
Cantos <[EM
Yes it’s possible.
However you will have to store passwords in clear text format onto the ldap.
De :
freeradius-users-bounces+s.can[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] De la part de Giuseppina Venezia
Envoyé : lundi 31 juillet
2006 12:13
À : FreeRadius users mailing
list
Phil Mayers wrote:
> It would in theory be possible to save the key from the last walk, and
> next time we allocate an IP start from that key and wrap back around,
> which would allocate IPs in a more round-robin fashion.
Yes, that should be a solution. I was more thinking of adding a parameter
Hi,
I’ve noticed that rlm_ippool is nearly always
reassigning an IP address that has just been releasing for a new connexion.
This cause some TCP connexion problems because of the TIME_WAIT state.
Scenario:
1/ one device connects using source port 1024 (ppp)
and gets an IP address
7 matches
Mail list logo
