Welcome, Guest. Please login or register.
Did you miss your activation email?
+  pfSense Forum
|-+  pfSense English Support» PPTP» max PPTP connections
Username:
Password:
 
 

Pages: [1]   Go Down
  Print  
Author Topic: max PPTP connections  (Read 6066 times)
0 Members and 1 Guest are viewing this topic.
moo
Newbie
*
Offline Offline

Posts: 14


View Profile
« on: December 23, 2005, 10:38:25 am »

can we only have 16 PPTP connections? we can't change the /28? or I'm missing something?

thanks
Logged
sullrich
Hero Member
*****
Offline Offline

Posts: 5135



View Profile WWW
« Reply #1 on: December 23, 2005, 12:59:23 pm »

http://article.gmane.org/gmane.comp.security.firewalls.pfsense.support/3920
Logged
moo
Newbie
*
Offline Offline

Posts: 14


View Profile
« Reply #2 on: December 23, 2005, 09:12:27 pm »

Ha, that's awesome!!!

thanks
Logged
wjoyce
Newbie
*
Offline Offline

Posts: 8


View Profile
« Reply #3 on: January 08, 2006, 04:39:33 pm »

Any plans to include making this configurable through the GUI?  For user friendlyness sake of course.   Grin
Logged
sullrich
Hero Member
*****
Offline Offline

Posts: 5135



View Profile WWW
« Reply #4 on: January 08, 2006, 05:00:28 pm »

Any plans to include making this configurable through the GUI?  For user friendlyness sake of course.   Grin

No, I doubt we'll expose these functions since not many ppl need them.  It's rather easy to edit config.xml and add the 2 lines.
Logged
wjoyce
Newbie
*
Offline Offline

Posts: 8


View Profile
« Reply #5 on: January 08, 2006, 05:08:06 pm »

I can respect that.  In the future, I plan on using the PPTP server to secure wireless captive portal clients.  I basically want to half the subnet I will use between the DHCP addresses and the PPTP addresses.
Logged
ssam
Jr. Member
**
Offline Offline

Posts: 26


View Profile
« Reply #6 on: February 21, 2006, 04:39:45 am »

i have a question here, i've added those 2 lines, and im using pptp for securing wifi too:) But when you go to the pptp option, the max pptp clients number is still on 16 (i think thats because the value is hardcoded?), and when i set the iprange, its still being calculated by the /28 range. Is it possible to change this somehow?
Logged
wjoyce
Newbie
*
Offline Offline

Posts: 8


View Profile
« Reply #7 on: February 21, 2006, 06:07:31 am »

i have a question here, i've added those 2 lines, and im using pptp for securing wifi too:) But when you go to the pptp option, the max pptp clients number is still on 16 (i think thats because the value is hardcoded?), and when i set the iprange, its still being calculated by the /28 range. Is it possible to change this somehow?

1.  Make sure your using the latest pfsense.
2.  add kern.ipc.maxpipekva="2514944" to /boot/loader.conf
3.  edit /etc/inc/globals.inc.  I am have been to set the values to what is below without experiencing any errors ONLY AFTER I did step 2.  I have not however tested it with 64 pptp concurrent clients. 

    "n_pptp_units" => 64,  /* this value can be overriden in pptp->n_pptp_units */
    "pptp_subnet" => 26,   /* this value can be overriden in pptp->pptp_subnet  */
4.  Note - Changes to /etc/inc/globals.inc are lost after every firmware upgrade.
« Last Edit: February 21, 2006, 06:22:49 am by wjoyce » Logged
ssam
Jr. Member
**
Offline Offline

Posts: 26


View Profile
« Reply #8 on: February 22, 2006, 01:20:27 am »

thanks a lot for this guide will try it!
Logged
ssam
Jr. Member
**
Offline Offline

Posts: 26


View Profile
« Reply #9 on: February 25, 2006, 05:46:00 am »

its working thanks, but im wondering what does this value mean? kern.ipc.maxpipekva="2514944" ?
Logged
wjoyce
Newbie
*
Offline Offline

Posts: 8


View Profile
« Reply #10 on: February 25, 2006, 06:52:18 am »

its working thanks, but im wondering what does this value mean? kern.ipc.maxpipekva="2514944" ?

I suggest you do a google search, I'm not an expert on kernal tuning.  I would assume ipc stands for interprocess communication and the kern.ipc.maxpipekva is some sort of buffer.
Logged
Pages: [1]   Go Up
  Print  
 
Jump to:  

 

Page created in 0.028 seconds with 20 queries.