<div>Hi,</div>
<div> </div>
<div> I found a solution to my problem: I wanted to differentiate 2 kinds of VPN connections, but then i realized that what i wanted to do is differentiate 2 kind of group of users.</div>
<div> So i installed freeradius, pppd radius plugin, a postgresql database.</div>
<div> I created 2 groups in the radius, affected my users to 2 differents subnet and activating ippool in the radius it was working perfectly.<br> </div>
<div>Cheers,</div>
<div>Christophe.<br> </div>
<div><span class="gmail_quote">On 2/4/06, <b class="gmail_sendername">Paul Wouters</b> <<a href="mailto:paul@xelerance.com">paul@xelerance.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On Thu, 2 Feb 2006, Christophe Ngo Van Duc wrote:<br><br>> I had in the idea of differentiating 2 VPN connections based on the PSK
<br>> If I have PSK1 I use conn L2TP-PSK and L2TPD running at 1701 which affect<br>> ip in the range 192.168.1/24<br>> If I have PSK2 I use conn L2TP2-PSK and L2TPD running at 1700 which affect<br>> ip in the range
<a href="http://192.168.0.128/25"></b></font><font color="red"><b>MailScanner has detected a possible fraud attempt from "192.168.0.128" claiming to be</b></font> <font color="red"><b>MailScanner warning: numerical links are often malicious: 192.168.0.128/25</a><br>><br>> I have checked ipsec.conf it doesn't seems I can affect a PSK for a specific<br>> conn definition<br><br>That would not be a setting in ipsec.conf, but in
l2tpd.conf. IPsec still<br>happens on the same protocol (esp or espinudp)<br><br>I am not sure what you are trying to do. l2tp connections are distinguished<br>by a user/password, so why is that not good enough?<br><br>Paul
<br><br></blockquote></div><br>