Re: [Efw-user] New efw 2.1.2 installation unable to OpenVPN

2007-12-06 Thread toby
for 210.x.x.x should be 255.255.255.248 and I do not > know where it is getting 192.168.1.1. > > Good news is we are getting closer :) > > Thanks, > > Toby > > On Dec 5, 2007 5:51 PM, compdoc <[EMAIL PROTECTED]> wrote: > > > Are you sure you'

Re: [Efw-user] New efw 2.1.2 installation unable to OpenVPN

2007-12-05 Thread toby
sure you've got the red and green nics connected correctly? > > > > > > *From:* [EMAIL PROTECTED] [mailto: > [EMAIL PROTECTED] *On Behalf Of *toby > *Sent:* Wednesday, December 05, 2007 4:12 PM > *To:* efw-user@lists.sourceforge.net > *Subject:* Re: [Efw-us

Re: [Efw-user] New efw 2.1.2 installation unable to OpenVPN

2007-12-05 Thread compdoc
Are you sure you’ve got the red and green nics connected correctly? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of toby Sent: Wednesday, December 05, 2007 4:12 PM To: efw-user@lists.sourceforge.net Subject: Re: [Efw-user] New efw 2.1.2 installation unable to OpenVPN No ports

Re: [Efw-user] New efw 2.1.2 installation unable to OpenVPN

2007-12-05 Thread Scott Silva
on 12/5/2007 3:12 PM toby spake the following: > No ports are blocked as this is a commercial T1 account. I have modem > connected to gigabit switch and devices needing public IPs are connected > to it and said devices are setup with static IPs from range given by > ISP. I will check to make sur

Re: [Efw-user] New efw 2.1.2 installation unable to OpenVPN

2007-12-05 Thread toby
[mailto: > [EMAIL PROTECTED] *On Behalf Of *toby > *Sent:* Wednesday, December 05, 2007 3:36 PM > *To:* Kenton and Saundi Brown > *Cc:* Efw-user@lists.sourceforge.net > *Subject:* Re: [Efw-user] New efw 2.1.2 installation unable to OpenVPN > > > > Update: I added por

Re: [Efw-user] New efw 2.1.2 installation unable to OpenVPN

2007-12-05 Thread compdoc
bad, or the cabling is not correct. The ISP blocks those ports. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of toby Sent: Wednesday, December 05, 2007 3:36 PM To: Kenton and Saundi Brown Cc: Efw-user@lists.sourceforge.net Subject: Re: [Efw-user] New efw 2.1.2 installation unable

Re: [Efw-user] New efw 2.1.2 installation unable to OpenVPN

2007-12-05 Thread toby
Update: I added port 22 for external access and I cannot access public IP via SSH from outside of network. However, if I ssh into a server on LAN ( 192.168.1.0) going through Linksys router WAN (210.x.x.x) I can then SSH 210.x.x.x into efw box. The efw box has its own public IP as does the Linksys

Re: [Efw-user] New efw 2.1.2 installation unable to OpenVPN

2007-12-05 Thread toby
I have tried and i cannot connect. I am going to verify I have added port 22 for external access as comp-doc suggested. I thought I had made this change but we shall see. Toby. On Dec 4, 2007 11:08 AM, Kenton and Saundi Brown <[EMAIL PROTECTED]> wrote: > I do now if using an external dhcp will h

Re: [Efw-user] New efw 2.1.2 installation unable to OpenVPN

2007-12-04 Thread compdoc
You have to add port 22 in External Access to allow ssh directly. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of toby Sent: Monday, December 03, 2007 11:41 PM To: efw-user@lists.sourceforge.net Subject: Re: [Efw-user] New efw 2.1.2 installation unable to OpenVPN This is

Re: [Efw-user] New efw 2.1.2 installation unable to OpenVPN

2007-12-03 Thread toby
t; *From:* [EMAIL PROTECTED] [mailto: > [EMAIL PROTECTED] *On Behalf Of *toby > *Sent:* Monday, December 03, 2007 9:54 PM > *To:* [EMAIL PROTECTED] > *Cc:* efw-user@lists.sourceforge.net > *Subject:* Re: [Efw-user] New efw 2.1.2 installation unable to OpenVPN > > > > I fo

Re: [Efw-user] New efw 2.1.2 installation unable to OpenVPN

2007-12-03 Thread compdoc
. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of toby Sent: Monday, December 03, 2007 9:54 PM To: [EMAIL PROTECTED] Cc: efw-user@lists.sourceforge.net Subject: Re: [Efw-user] New efw 2.1.2 installation unable to OpenVPN I followed the KB and i still can't connect. I a

Re: [Efw-user] New efw 2.1.2 installation unable to OpenVPN

2007-12-03 Thread toby
I followed the KB and i still can't connect. I am not using EFW's DHCP server. Does that matter? I continue to get the same error messages that I posted earlier. " Mon Dec 03 21:51:43 2007 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity) Mon Dec 03

Re: [Efw-user] New efw 2.1.2 installation unable to OpenVPN

2007-11-30 Thread compdoc
? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of toby Sent: Friday, November 30, 2007 11:37 AM To: efw-user@lists.sourceforge.net Subject: Re: [Efw-user] New efw 2.1.2 installation unable to OpenVPN I am not allowing EFW to be DHCP server as I have another box doing that

Re: [Efw-user] New efw 2.1.2 installation unable to OpenVPN

2007-11-30 Thread toby
m missing > something. What do you think is the problem? Is it possible your broadband > router or ISP is blocking 1194? > > > > > > > > > > *From:* [EMAIL PROTECTED] [mailto: > [EMAIL PROTECTED] *On Behalf Of *toby > *Sent:* Friday, November 30, 2007 8:19 AM

Re: [Efw-user] New efw 2.1.2 installation unable to OpenVPN

2007-11-30 Thread compdoc
hat do you think is the problem? Is it possible your broadband router or ISP is blocking 1194? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of toby Sent: Friday, November 30, 2007 8:19 AM To: efw-user@lists.sourceforge.net Subject: Re: [Efw-user] New efw 2.1.2 installation

Re: [Efw-user] New efw 2.1.2 installation unable to OpenVPN

2007-11-30 Thread toby
> > > > > > > *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > *On Behalf Of *toby > > *Sent:* Thursday, November 29, 2007 10:02 AM > > *To:* efw-user@lists.sourceforge.net > > *Subject:* Re: [Efw-user] New efw 2.1.2 installation unable

Re: [Efw-user] New efw 2.1.2 installation unable to OpenVPN

2007-11-29 Thread toby
extra blank lines? They shouldn't be > there... > > > > > > > > *From:* [EMAIL PROTECTED] [mailto: > [EMAIL PROTECTED] *On Behalf Of *toby > *Sent:* Thursday, November 29, 2007 10:02 AM > *To:* efw-user@lists.sourceforge.net > *Subject:* Re: [Efw-user] Ne

Re: [Efw-user] New efw 2.1.2 installation unable to OpenVPN

2007-11-29 Thread compdoc
, November 29, 2007 10:02 AM To: efw-user@lists.sourceforge.net Subject: Re: [Efw-user] New efw 2.1.2 installation unable to OpenVPN Seriously, when I download cert from EFW web interface it saves as .pem automatically I did not have to rename it or anything. On Nov 29, 2007 10:57 AM, compdoc mailto:[EMAIL

Re: [Efw-user] New efw 2.1.2 installation unable to OpenVPN

2007-11-29 Thread toby
Seriously, when I download cert from EFW web interface it saves as .pem automatically I did not have to rename it or anything. On Nov 29, 2007 10:57 AM, compdoc <[EMAIL PROTECTED]> wrote: > When I save a cert from any efw, it gets a .cer file name extension. > How'd you get .pem? > > > > Heres m

Re: [Efw-user] New efw 2.1.2 installation unable to OpenVPN

2007-11-29 Thread toby
I just renamed it .pem :) On Nov 29, 2007 10:57 AM, compdoc <[EMAIL PROTECTED]> wrote: > When I save a cert from any efw, it gets a .cer file name extension. > How'd you get .pem? > > > > Heres my working client.ovpn: > > > > client > > float > > dev tap > > proto udp > > port 1194 > > remote xx

Re: [Efw-user] New efw 2.1.2 installation unable to OpenVPN

2007-11-29 Thread compdoc
When I save a cert from any efw, it gets a .cer file name extension. How’d you get .pem? Heres my working client.ovpn: client float dev tap proto udp port 1194 remote xxx.xxx.xxx.xxx resolv-retry infinite nobind persist-key persist-tun ca lasvegas.cer auth-user-pass pull comp-lzo Name the c