Am 25.07.2012 18:36, schrieb RB:
However, repeatedly firing off
fetch -q -o - http://checkip.dyndns.org | sed 's/^.*Current IP Address:
\(.*\)\/body.*$/\1/'
within the same minute doesn't error out, so it doesn't look like a limit
that's enforced by dyndns.
My only guess is that they're
Not sure if this is helpful to you at all, but I've looked at a possible
workaround for SSL and a lack of public IPs.
Host a virtualized pfsense box with a service provider (I'm using ARP
networks).
Get a /29 (or more as needed).
Set up a tunnel between the virtualized box and your local pfsense
On Thu, Jul 26, 2012 at 1:09 AM, Stefan Baur
newsgroups.ma...@stefanbaur.de wrote:
Still no luck. :-( Old IP shows up as red after the nightly IP change.
Crud, sorry to hear but unsurprised.
You mentioned a cron job for updating; are you hijacking pfSense built-in
functions for that or did
Hey Seth and Moshe,
I know that Varnish will be able to do most and Haproxy can definitely handle
the hostname to IP issue, but haproxy as far as I know won't do SSL you have to
have stunnel setup in front of it and it still requires the IP's set.
I was hoping that it could be done and I may
Hi Stefan,
On Thu, Jul 26, 2012 at 09:09:35AM +0200, Stefan Baur wrote:
Am 25.07.2012 18:36, schrieb RB:
However, repeatedly firing off
fetch -q -o - http://checkip.dyndns.org | sed 's/^.*Current IP Address:
\(.*\)\/body.*$/\1/'
within the same minute doesn't error out, so it doesn't look
Unfortunately the proxy route really wouldn't be an option. SNI support
isn't universal enough for that to work for us, and we can't mix different
client's sites on one certificate for business reasons. If either of those
were an option there would be no problem as we could just have a single
On Fri, Jul 27, 2012 at 2:44 AM, Stefan Baur
newsgroups.ma...@stefanbaur.de wrote:
Am 26.07.2012 22:45, schrieb Frank:
I'm not getting what you're trying to prove or disprove with that. Care to
explain? Fact is, triggering the update by refreshing the DynDNS page in
the WebGUI works.
Are
Am 26.07.2012 23:53, schrieb Nishant Sharma:
Are you running dual WAN setup with gateway failover by any chance?
Nope, single WAN, but in private IP space, as there is another router
above it.
-Stefan
___
List mailing list
List@lists.pfsense.org
Am 27.07.2012 01:16, schrieb Jeppe Øland:
On Thu, Jul 26, 2012 at 2:14 PM, Stefan Baur
newsgroups.ma...@stefanbaur.de wrote:
- what does your log say about dyndns?
Nothing that would look helpful:
check_reload_status: Updating all dyndns
is the only message containing the string dyn,
Hello
I have *2.0.1-RELEASE * (amd64) installed in a server that is behind a
cisco RV082 V03 router. I was asked to use openvpn to allow many vpn users
from the a single remote site. the problem is how should I configure the
openvpn behind a router if all the documentation I have found uses the
On Thu, Jul 26, 2012 at 4:25 PM, Stefan Baur
newsgroups.ma...@stefanbaur.de wrote:
There's got to be more in the log than just that!
Nope, there isn't... but...
Exactly from there:
Do me a favor and see if you maybe by accidend checked the disable
And GH, it seems that I hit that disable
My guess would be you need to forward whatever port you choose for OpenVPN
through the cisco to the pfSense box, and choose the appropriate public IP
when configuring the other end of the tunnel. (I'm assuming you're talking
about setting up a tunnel from one site to another, from your
Hello,
yes, Im forwarding all tcp traffic from ports 1190-1199 (openvpn uses 1194)
to the internal wan ip of openvpn but it is not reaching the pfsense box
and dont know why
Marcos Luna
On Thu, Jul 26, 2012 at 7:25 PM, Adam Stasiak pales...@gmail.com wrote:
My guess would be you need to
On Thu, Jul 26, 2012 at 9:46 PM, Marcos Luna marcos.l...@gmail.com wrote:
Hello,
yes, Im forwarding all tcp traffic from ports 1190-1199 (openvpn uses 1194)
OpenVPN generally uses UDP not TCP.
___
List mailing list
List@lists.pfsense.org
On Thu, Jul 26, 2012 at 11:51 AM, Peder Rovelstad
provels...@comcast.net wrote:
Just happened to see this today in my system logs. Does it mean something?
This is a home network with only about 6 active devices. The DHCP range is
only 192.168.100 - .110
Means your scope used to be
15 matches
Mail list logo
