.
Regards,
Tim
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
Yes that is possible, but locally managed.
I would prefer some SVN or git way.
Ah, gotcha. For those that have pfsense gold, there is the option to
take advantage of the pfsense-hosted autobackup solution. That said, the
config.xml file is just plain text; I imagine it would be fairly
It would be cool if pfSense supported a feature of this kind.
Diagnostics Backup/Restore Config History
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
.
--
Tim K
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
bridge, click 'Save'
-Traffic now flows
Keep in mind this scenario occurs both with and without VLAN's being involved,
and across a variety of NICs.
Most recent experience of this issue is on pfSense 2.2.2-RELEASE amd64 (full
install).
--Tim
___
pfSense
Tim Clarke
On 01/07/15 16:49, Vick Khera wrote:
On Wed, Jul 1, 2015 at 10:40 AM, Jon Gerdes gerd...@blueloop.net wrote:
Your first job is to establish a real baseline. That is: How fast can
you really move data between the two sites without any tunnels? You may
have to be creative with NATting
sound like using Proxy ARP would be the best choice. But
are there any disadvantages? What about performance?
Regards.
On 3/8/2015 7:42 AM, PiBa wrote:
Says it all:
https://doc.pfsense.org/index.php/What_are_Virtual_IP_Addresses
Which is better, that depends on what you need it to do.
Tim
Ed,
I like your idea with using 1:1 NAT but just one question; If you use
SSL with the certificate on the web server, will the 1:1 NAT mess with that?
Regards,
Tim
On 3/6/2015 9:52 PM, ED Fochler wrote:
Bridging will disable firewall and DHCP on modem, this should be expected.
If it works
Yes, I guess I want to know if the bridge is set up correctly when one
of the interfaces in the bridge has an IP address that is being used for
the NAT address for my internal LAN.
Regards,
Tim
On 3/6/2015 3:07 PM, WebDawg wrote:
On Fri, Mar 6, 2015 at 2:16 PM, Tim Hogan t...@hoganzoo.com
feature correctly. Any thoughts?
Thanks,
Tim
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
/16
label Block IPv4 link-local
Where on earth is that rule so I can remove the log option? Or is there
a setting that I missed somewhere?
Thanks,
Tim
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project
I was able to get vnstat to work by running the following commands
cd /var
mkdir lib
cd lib
ln -s /cf/conf/vnstat
After running those commands all of my previous data was available.
Regards,
Tim
On 1/25/2015 3:54 AM, Doug Lytle wrote:
Brian Caouette wrote:
Lightsquid and vnstat2 do
/havp.inc on line 604
This error occurs on top of the HAVP-config-pages.
Regards
Tim
Chris Buechler c...@pfsense.com hat am 24. Januar 2015 um 03:24 geschrieben:
Details on the blog:
https://blog.pfsense.org/?p=1546
___
pfSense mailing list
https
Thanks for your answer.
I did it. It was a missing rule on top of all other firewall rules without
setting a special gateway (*)
That did it.
Tim
Am 21. Januar 2015 12:57:02 MEZ, schrieb Christoph Hanle
christoph.ha...@leinpfad.de:
On 21.01.2015 11:28, 51537551.3:51537551.3 wrote:
LAN
!
---tim
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
, this is not desirable; the
traffic has to go down the VPN or not at all.
I can't get my head around a firewall rule (or other configuration)
which would achieve this. Any ideas?
Cheers,
---tim
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Or even better... ONLY put the two specific allow rules. PfSense blocks by
default so the rest will be blocked.
(And rules are top down)
This would be on the rules tab for the interface you are connecting from
(usually LAN)
On Sep 10, 2014 11:42 PM, Usama Ahmad u.us...@gmail.com wrote:
Hello
hardware. In your shoes, I would not be moving forward with
the current equipment.
--Tim
___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list
I'm getting destination host unreachable while trying to contact
packages.pfsense.org or www.pfsense.org. Traceroute gets as far as
fw1.pfmechanics.com. I've tried from a couple of different internet
connections with the same result.
Just wanting to check that I'm not being an idiot?
---tim
I'm getting destination host unreachable while trying to contact
packages.pfsense.org or www.pfsense.org. Traceroute gets as far as
fw1.pfmechanics.com. I've tried from a couple of different internet
connections with the same result.
Actually disregard this, connectivity now seems to be working
There was an issue with some production services at our datacenter,
everything should be back to normal now.
Thanks Jeremy, everything looks good now.
---t
___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list
issues, it looks like you made a friend on the list to take care
of the rest (offlist).
--Tim
___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list
...
Any ideas?
--Tim
___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list
it.
What type of NIC emulation is the KVM VM providing? e1000 would be best,
followed by virtio, then possibly rtl8139. Of course, that is coming from my
experience with using KVM via Proxmox VE, not KVM in a manual or 'cloud'
environment such as Profitbrick.
--Tim
PKI or even static keys).
Thanks!
--Tim
___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list
differ from stock
pfSense, but purely for educational reasons -- and I understand that
this could be considered as Netgate's IP.
---tim
___
List mailing list
List@lists.pfsense.org
http://lists.pfsense.org/mailman/listinfo/list
We just upgraded a box from 2.0.3 release to 2.1 release - and not sure
if it is related or coincidence but started having bizarre routing issue
post upgrade when using gateway groups.
Scenario
Dual WAN (em0 em1 drivers)
Quad LAN (igb0 and igb3 in use)
igb3 has multiple VLAN'd interfaces (5 -
rules
are legit for each of the interfaces, routing is correct, etc. With IPv4 this
is straight forward... :(
Thoughts?
--Tim
___
List mailing list
List@lists.pfsense.org
http://lists.pfsense.org/mailman/listinfo/list
DNS resolution in Alias lists work as I expect it to?
thanks for any info!
Tim
___
List mailing list
List@lists.pfsense.org
http://lists.pfsense.org/mailman/listinfo/list
for a new card. Suggestions? Can someone tell me a known
(guaranteed) working mPCIe interface card that works with pfSense? Use case is
simple indoor access point functionality as part of a SOHO firewall.
Thanks!
--Tim
___
List mailing list
List
- Original Message -
On Tue, Jan 22, 2013 at 11:24 AM, Tim Nelson tnel...@rockbochs.com
wrote:
I have two hosts in a CARP setup, working as expected for failover.
States are set to sync between the primary system and the secondary
system. However, when I look at the state table
the
state
MASTER
Fantastic! Do we have an ETA on 2.1 then? :D
--Tim
___
List mailing list
List@lists.pfsense.org
http://lists.pfsense.org/mailman/listinfo/list
11876 states, while the slave only
shows 244 states. Is this correct? Are the states sync'ed, but simply don't
show up on the secondary system until CARP failover happens? Thanks!
--Tim
___
List mailing list
List@lists.pfsense.org
http://lists.pfsense.org
that would show at the top of the
web GUI scrolling by, or other 'system level' or 'critical' issues?
Thoughts? Ideas?
Thanks!
--Tim
___
List mailing list
List@lists.pfsense.org
http://lists.pfsense.org/mailman/listinfo/list
- Original Message -
info here:
http://blog.pfsense.org/?p=676
And just in time for insert your holiday preferrence here! Fantastic! Thanks
for your amazing software, and brilliant work!
--Tim
___
List mailing list
List@lists.pfsense.org
clarification. It is what I found elsewhere, but wanted to
be sure. :)
Also, great idea on the OpenVPN connectivity pooling. I'll have to give that a
shot. Thanks!
--Tim
___
List mailing list
List@lists.pfsense.org
http://lists.pfsense.org/mailman/listinfo
- Original Message -
On 12/5/2012 10:11 AM, Tim Nelson wrote:
I've successfully setup 2x pfSense boxen with CARP. It is working
properly, with ~1 second failover. The following test scenarios
work well:
-Unplugging a link (WAN, LAN, etc)
-Causing system crash (kill -9 1
1950/2950 should also work. SCSI and PERC variants are both
functional.
Good to hear! Thanks for the input!
--Tim
___
List mailing list
List@lists.pfsense.org
http://lists.pfsense.org/mailman/listinfo/list
This is an old thread, and I'm sure you've figured it out... but your issue
is that you are still an routable address zones.
on a true WAN instance... that 192.168.*.* would NOT be routed, so need not
worry.
You can block the private address space with one of the toggle switches or
with rules if
or the power of the mind, instead favoring the most ludicrous
marketing brainwash/concept of our time... The Cloud. :/ Sorry, getting off
my soapbox now. /rant
--Tim
___
List mailing list
List@lists.pfsense.org
http://lists.pfsense.org/mailman/listinfo
on the
pfSense itself to bind to the virtual IP. If these installs are
upgraded
from 1.x.x it's quite possible this is why.
Ah yes, that makes sense. Thank you for the insight!
--Tim
___
List mailing list
List@lists.pfsense.org
http
doubles
the price to around £250 GBP.
Has anyone any suggestions for a 4-port alternative that's closer to
the
3-port cost?
If you really don't need the throughput of an additional physical NIC, a VLAN
capable switch will give you as many 'ports' as you need. :)
--Tim
is
The MRC is half of the 'regular fiber', but how much is your time worth trying
to make a broken implementation work?
--Tim
___
List mailing list
List@lists.pfsense.org
http://lists.pfsense.org/mailman/listinfo/list
[1], FreeBSD (base OS of pfSense) ran on the V100's as well. Just
another option for you to consider.
--Tim
[1] http://www.freebsd.org/relnotes/CURRENT/hardware/article.html#PROC-SPARC64
___
List mailing list
List@lists.pfsense.org
http
- Original Message -
Op 10 mei 2012, om 22:09 heeft Tim Nelson het volgende geschreven:
- Original Message -
I was not aware of the fact the OpenBSD runs natively on Sun Server
with SPARC architecture.
It's because i bought the V100 few months ago, so that's why i
, the
memories. :)
--Tim
___
List mailing list
List@lists.pfsense.org
http://lists.pfsense.org/mailman/listinfo/list
- Original Message -
- Original Message -
On Thu, Jan 12, 2012 at 1:00 PM, Tim Nelson tnel...@rockbochs.com
wrote:
Greetings-
I understand the functionality of the OpenVPN Status package from
the 1.x versions is now integrated into the 2.x versions.
*However
write the routing upon connecting.
-Tim
___
List mailing list
List@lists.pfsense.org
http://lists.pfsense.org/mailman/listinfo/list
- Original Message -
On Thu, Oct 13, 2011 at 16:03, Tim Nelson tnel...@rockbochs.com
wrote:
I would expect it to work this way also. However, I've removed the
OPT interfaces corresponding to the OpenVPN servers. Next, I've
added one rule to 'Allow all traffic, any protocol, any
up the interface IP address. It will then apply the rules
appropriately. My clue was seeing the OPT interfaces on the system dashboard as
up (green), but no IP assigned.
Thanks Jim and others for your helpful suggestions.
--Tim
___
List mailing list
are pointed straight
up(vertically), signal should be coming horizontally. This is an oversimplified
view, but roughly correct.
I'm not a wireless expert, but I hope these tips give you a few items to go
on for better performance.
Tim Nelson
Systems/Network Support
Rockbochs Inc.
(218)727-4332 x105
obvious problem so far (only apinger says, that it can't
ping the monitor-IP). Whatever monitor-IP I configure and do a routing
configuration for it, the gateway is first up and then goes offline
with the apinger error.
Any ideas? Help is really appreciated!
Regards, Tim
52 matches
Mail list logo