Re: [pfSense Support] pptp help!!
Chris Buechler escribió: On Tue, Nov 11, 2008 at 5:12 PM, Jostein Elvaker Haande <[EMAIL PROTECTED]> wrote: The good thing about PPTP is that basically any Windows installation He's talking (I believe) about a PPTP type Internet connection, not a PPTP server. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Commercial support available - https://portal.pfsense.org Yes, Yes, the connection, not a server -- Mikel Jimenez Fernandez Irontec, Internet y Sistemas sobre GNU/LinuX - http://www.irontec.com +34 94.404.81.82 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] Reflective routing ?
On Wed, Nov 12, 2008 at 6:50 AM, DLStrout <[EMAIL PROTECTED]> wrote: > All seems well on 1.2.1, but when testing 2.0Ax2 I > noticed one of the start up scripts hangs and > produces the below output. Not real sure how to > debug it and had to CTRL-C to get it to finally > finish booting up. I appears to be something w/ > the apinger function/piece of the startup process. > > The reflective routing piece works mint on > 1.2.1 but is still seems borked on 2.0. > > -- > output from system log after boot rc script hangs > and CTRL-C issued to release it. > -- > Nov 12 06:41:54 kernel: pflog0: promiscuous mode > disabled > Nov 12 06:41:54 sshlockout[42775]: sshlockout > starting up > Nov 12 06:41:54 sshlockout[42775]: sshlockout > starting up > Nov 12 06:41:54 init: /bin/sh on /etc/rc > terminated abnormally, going to single user mode > Nov 12 06:41:54 init: /bin/sh on /etc/rc > terminated abnormally, going to single user mode > Nov 12 06:41:42 apinger: command (touch > /tmp/filter_dirty) exited with status: 1 > Nov 12 06:41:42 apinger: Error while starting > command. > Nov 12 06:41:38 php: : Creating rrd update script > Nov 12 06:41:32 apinger: ALARM: wan(127.0.0.2) > *** down *** > Nov 12 06:41:29 kernel: ipfw2 (+ipv6) > initialized, divert loadable, nat loadable, > rule-based forwarding enabled, default to accept, > logging disabled > -- > > On Tue, Nov 11, 2008 at 8:31 PM, DLStrout <[EMAIL > PROTECTED]> wrote: >> Excellent .. is this change committed to both > 1.2.1 and 2.0 versions? >> 2.0 bug reports belong on the forum, not on the mailing list. I should remind you that it is a moving target and NOT ready for public testing where you will be disappointed. Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] second WAN on PPPOE
2008/11/12 Peter Todorov <[EMAIL PROTECTED]>: > Hello list, > I wonder is there a option to add second WAN (OPT) with PPPOE? pfsense 1.2. Not in 1.2, you have to do it on your modem for OPT WANs. In 2.0 that's an option. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Commercial support available - https://portal.pfsense.org
Re: Re: [pfSense Support] Reflective routing ?
Absolutely NOT disappointed at all, just pointing out an issue ... quite the contrary in fact, and I am as anxious as any to see some of the fantastic new features of 2.0 in a STABLE release. Really just try to provide some input into 2.0 from our prospective. So just so I have this straight .. (and hopefully it will enlighten other as well) ... any questions relating to 1.3/2.0 belong on the forum? Because I was told early on to post them to the list ... kind of mixed messages about where to post for what ... but no harm no foul. So, is the forum the desired endpoint for ALL 1.3/2.0 questions, bugs, etc. -- David L. Strout Engineering Systems Plus, LLC - Original Message - > > 2.0 bug reports belong on the forum, not on the mailing list. I > should remind you that it is a moving target and NOT ready for public > testing where you will be disappointed. > > Scott > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Commercial support available - https://portal.pfsense.org
Re: Re: [pfSense Support] Reflective routing ?
On Wed, Nov 12, 2008 at 1:11 PM, DLStrout <[EMAIL PROTECTED]> wrote: > Absolutely NOT disappointed at all, just pointing > out an issue ... quite the contrary in fact, and I > am as anxious as any to see some of the fantastic > new features of 2.0 in a STABLE release. Really > just try to provide some input into 2.0 from our > prospective. > > So just so I have this straight .. (and hopefully > it will enlighten other as well) ... any questions > relating to 1.3/2.0 belong on the forum? Because > I was told early on to post them to the list ... > kind of mixed messages about where to post for > what ... but no harm no foul. So, is the forum > the desired endpoint for ALL 1.3/2.0 questions, > bugs, etc. Yes. I do not want this list polluted with alpha / beta questions. Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Commercial support available - https://portal.pfsense.org
[pfSense Support] second WAN on PPPOE
Hello list, I wonder is there a option to add second WAN (OPT) with PPPOE? pfsense 1.2. Thank you in advance for answers. -- честността не е порок
Re: [pfSense Support] Reflective routing ?
All seems well on 1.2.1, but when testing 2.0Ax2 I noticed one of the start up scripts hangs and produces the below output. Not real sure how to debug it and had to CTRL-C to get it to finally finish booting up. I appears to be something w/ the apinger function/piece of the startup process. The reflective routing piece works mint on 1.2.1 but is still seems borked on 2.0. -- output from system log after boot rc script hangs and CTRL-C issued to release it. -- Nov 12 06:41:54 kernel: pflog0: promiscuous mode disabled Nov 12 06:41:54 sshlockout[42775]: sshlockout starting up Nov 12 06:41:54 sshlockout[42775]: sshlockout starting up Nov 12 06:41:54 init: /bin/sh on /etc/rc terminated abnormally, going to single user mode Nov 12 06:41:54 init: /bin/sh on /etc/rc terminated abnormally, going to single user mode Nov 12 06:41:42 apinger: command (touch /tmp/filter_dirty) exited with status: 1 Nov 12 06:41:42 apinger: Error while starting command. Nov 12 06:41:38 php: : Creating rrd update script Nov 12 06:41:32 apinger: ALARM: wan(127.0.0.2) *** down *** Nov 12 06:41:29 kernel: ipfw2 (+ipv6) initialized, divert loadable, nat loadable, rule-based forwarding enabled, default to accept, logging disabled -- On Tue, Nov 11, 2008 at 8:31 PM, DLStrout <[EMAIL PROTECTED]> wrote: > Excellent .. is this change committed to both 1.2.1 and 2.0 versions? > Yes. -- David L. Strout Engineering Systems Plus, LLC - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Commercial support available - https://portal.pfsense.org
[pfSense Support] Openvpn - same client ip with users.
Hi All, I would first like to thank the dev group on the great work with PFsense. Ive always been an avid fan of openBSD's pf implementation and to have such a frontend is fantastic. Going through the mailing list archive, I have not found a answer to the issue I am currently facing with OpenVPN impelementation. PFsense version: 1.2 I have setup the Openvpn with a remote range of 172.16.0.0/24. When connecting from one client, I would receive 172.16.0.6 and with another client with a different client certificate, would be assigned the same ip of 172.160.0.6. Config on the Openvpn server instance: Protocol UDP Dynamic IP - Yes Local port 1194 Address Pool - 172.16.0.0/24 Use static ip's - No Local network - 10.0.1.0/24 Remote network - nil Client to client vpn - no Cryto - BF-CBC (128bit) Auth - PKI LZO Compression - Yes The client .ovpn file is as follows: float port 1194 dev tun dev-node ovpn #proto tcp-client remote 1.2.3.4 1194 ping 10 persist-tun persist-key tls-client ca blah.crt cert user.crt key user.key ns-cert-type server comp-lzo pull verb 4 I have a feeling im missing something. Any help will be appreciated as I cannot seem to get my head around this. Best Regards, Ezat - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Commercial support available - https://portal.pfsense.org
