Ryan,
I know this is not your question but, my company setup Dynster.net for DDNS
needs. It's not built in to pfSense because we are trying to get info from devs
but, we do support a simple manual pfSense integration work around. It does
work.
Maybe it will help.
Andrew
On Monday,
I'm curious... Do you have packet captures. I'd want to see your RTP media. I'm
wondering if that is causing your issue.
Andrew K. Mitchell, MSISPM
Managing Member Senior Network Engineer
VoIPster Communications, LLC.
Toll-Free: (877) 378-1045 x2221
International: +1.502-694-3106 x2221
-
it from the console/SSH by running /etc/rc.update_bogons).
Moshe
Sent from mobile device; sorry for top-posting.
On Sep 28, 2014 10:26 AM, Chris Bagnall pfse...@lists.minotaur.cc wrote:
On 28 Sep 2014, at 12:19, Andrew Mitchell andrew.k.mitch...@att.net wrote:
My apologies. 192.40.140.0
] bogon networks
Have you tried pinging the IP from another machine not being routed through
your subnet?
On 9/29/2014 6:37 AM, Andrew Mitchell wrote:
Thanks for the info.
I've been working working on this all night on and off.
My questions to you guys is, does files.pfsense.org
, that protect
files/updates.pfsense.org. This should resolve your issue.
On 9/29/2014 6:37 AM, Andrew Mitchell wrote:
Thanks for the info.
I've been working working on this all night on and off.
My questions to you guys is, does files.pfsense.org and/or updates.pfsense.org
block bogon networks
My company has just recently been assigned it's own block from ARIN. We have a
handful of pfSense boxes we need to connect to from that block. I have noticed
we can't when Block bogon networks is enabled on the WAN interfaces.
Interestingly enough I also noticed that our block can't connect to
?
On Sep 28, 2014, at 5:59 AM, Andrew Mitchell andrew.k.mitch...@att.net
wrote:
My company has just recently been assigned it's own block from ARIN. We have
a handful of pfSense boxes we need to connect to from that block. I have
noticed we can't when Block bogon networks is enabled on the WAN
We have two independent facilities. One in Kansas City, MO and the other in
jacksonville, FL.
For the last two weeks or so, I have noticed something that seems odd.If I
traceroute from KC to updates.pfsense.org, here are my results:
1 dcna01.kc.voipster.org (192.40.140.1) 1.273 ms 0.468 ms
You can most certainly route VoIP traffic. I have an installation now 4500+
telephones between two locations. Open VPN works wonderful for this type of
traffic in my opinion because it's a connection overhead is extremely low even
with depression it's speeds are more than acceptable for what I
in the firewall on the destination side of the tunnel.
I can't figure out where I have gone wrong. I would appreciate any advise.
Thanks,
Andrew
On Mon, Jan 2, 2012 at 8:04 AM, John Busch jbusch...@gmail.com wrote:
On Thu, Dec 29, 2011 at 5:50 AM, Andrew Mitchell
andrew.mitch...@wdidata.net
I have quite a few pfSense boxes deployed. I have only run into this twice.
Once was a DDR2 clockspeed mismatch. The second was a bad memory module.
So, in both cases it was memory/hardware related.
Hope that helps.
Andrew
On Mon, Nov 14, 2011 at 4:16 AM, Hiren Joshi j...@moonfruit.com wrote:
Perhaps I am misunderstanding but could you setup a separate tunnel? Peer
to peer shared key as an example?
Andrew
On Tue, Dec 27, 2011 at 4:16 AM, Dave Warren li...@hireahit.com wrote:
Does anyone happen to know if pfSense (2.x)'s OpenVPN installation will be
willing to use saved
Doh! Found the issue... virtual_server/ was closed but never opened for
whatever reason. Works now!
Thanks,
Andrew
On Tue, Dec 27, 2011 at 3:31 AM, Andrew Mitchell
andrew.mitch...@wdidata.net wrote:
In the GUI, I do see the blank entry listed under both the Pools and
Virtual Servers tabs
I know. Sorry I misspoke. Thanks for the help though.
Andrew.
On Tue, Dec 27, 2011 at 10:09 AM, Vick Khera vi...@khera.org wrote:
On Tue, Dec 27, 2011 at 4:34 AM, Andrew Mitchell
andrew.mitch...@wdidata.net wrote:
Doh! Found the issue... virtual_server/ was closed but never opened
My fellow pfSensers,
Since I upgaded to 2.0.1, relayd fails to start reporting the following
error in System Logs:
The command '/usr/local/sbin/relayd -f /var/etc/relayd.conf' returned exit
code '1', the output was '/var/etc/relayd.conf:7: syntax error no
redirections, nothing to do unused
15 matches
Mail list logo
