[pfSense Support] How to move usage date (RRD graph data) to new box?
Hi All, can somebody help me here? I'm replacing the current pfSense box (2800-Athlon desktop w/ 3 D-Link GBit NICs) with a Acrosser AR-B1662 based 19 box (4 build-in NICs). I don't want to loose the usage data of the old box, but still a fresh install will tidy up old unused config date etc... So my question is where is the usage data displayed in the RRD graphs stored? would it be enough to simply copy that data across?? Thanks! Holger
Re: [pfSense Support] How to move usage date (RRD graph data) to new box?
On 6/14/06, Holger Goetz [EMAIL PROTECTED] wrote: can somebody help me here? I'm replacing the current pfSense box (2800-Athlon desktop w/ 3 D-Link GBit NICs) with a Acrosser AR-B1662 based 19 box (4 build-in NICs). I don't want to loose the usage data of the old box, but still a fresh install will tidy up old unused config date etc... So my question is where is the usage data displayed in the RRD graphs stored? would it be enough to simply copy that data across?? On the old box: tar cvPzf /root/rrddata.tgz /var/db/rrd/ Copy /root/rrddata.tgz off the box using exec.php Copy the rrddata.tgz to the new box and use exec.php to upload, it will end up in /tmp/ Now do: mkdir -p /var/db/rrd tar xvPzf/tmp/rrddata.tgz -C /var/db/rrd Done! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] How to move usage date (RRD graph data) to new box?
Thanks Scott! That worked well - even though i used scp to copy the file across the boxes :-) Also on this place a big THANK YOU for your and all the contributors efforts making pfSense as good as it is!! Cheers, Holger On Wed, 2006-06-14 at 11:41 -0400, Scott Ullrich wrote: On 6/14/06, Holger Goetz [EMAIL PROTECTED] wrote: can somebody help me here? I'm replacing the current pfSense box (2800-Athlon desktop w/ 3 D-Link GBit NICs) with a Acrosser AR-B1662 based 19 box (4 build-in NICs). I don't want to loose the usage data of the old box, but still a fresh install will tidy up old unused config date etc... So my question is where is the usage data displayed in the RRD graphs stored? would it be enough to simply copy that data across?? On the old box: tar cvPzf /root/rrddata.tgz /var/db/rrd/ Copy /root/rrddata.tgz off the box using exec.php Copy the rrddata.tgz to the new box and use exec.php to upload, it will end up in /tmp/ Now do: mkdir -p /var/db/rrd tar xvPzf/tmp/rrddata.tgz -C /var/db/rrd Done! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[pfSense Support] Direct traffic out over a second gateway / WAN?
Hi! We have a requirement to divert certain traffic out of our building (via pfsense) on a different route than that of our main ADSL feed. This is so we can present a different IP to the destination host we're connecting to from that of our main office IP. Is there a reasonably straightforward way in pfsense to rule that; If destination = xxx.xxx.xxx.xxx then use gateway xxx.xxx.xxx.xxx instead of default so effectively traffic heading for a specific destination leaves the building via a different route / external address? Thanks in advance, Steve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] Direct traffic out over a second gateway / WAN?
On 6/14/06, Steve Harman [EMAIL PROTECTED] wrote: Hi! We have a requirement to divert certain traffic out of our building (via pfsense) on a different route than that of our main ADSL feed. This is so we can present a different IP to the destination host we're connecting to from that of our main office IP. Is there a reasonably straightforward way in pfsense to rule that; If destination = xxx.xxx.xxx.xxx then use gateway xxx.xxx.xxx.xxx instead of default so effectively traffic heading for a specific destination leaves the building via a different route / external address? Yes, simply create a firewall rule for the desired traffic and set the gateway in the advanced section of the firewall rule. It's really that easy :) Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] Direct traffic out over a second gateway / WAN?
What needs to be done to set the specific IP address that is seen/used for the traffic? For example, using a static arp address instead of the main interface address. Robert On Wednesday 14 June 2006 12:51, Scott Ullrich wrote: On 6/14/06, Steve Harman [EMAIL PROTECTED] wrote: Hi! We have a requirement to divert certain traffic out of our building (via pfsense) on a different route than that of our main ADSL feed. This is so we can present a different IP to the destination host we're connecting to from that of our main office IP. Is there a reasonably straightforward way in pfsense to rule that; If destination = xxx.xxx.xxx.xxx then use gateway xxx.xxx.xxx.xxx instead of default so effectively traffic heading for a specific destination leaves the building via a different route / external address? Yes, simply create a firewall rule for the desired traffic and set the gateway in the advanced section of the firewall rule. It's really that easy :) Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] Direct traffic out over a second gateway / WAN?
On 6/14/06, Robert Goley [EMAIL PROTECTED] wrote: What needs to be done to set the specific IP address that is seen/used for the traffic? For example, using a static arp address instead of the main interface address. Nothing needs set. Setup the 2nd wan and start passing traffic. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[pfSense Support] Minor bug?
This might have been noticed by the devs already, but I wasn't sure where to check, so I am asking here... On the Firewall: Rules: Edit page, Source section, the Type drop-down includes choices for LAN address and WAN address; should it not also include however many OPTx address interfaces you have? ~Brian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] Minor bug?
Most likely. However this is not something we can fix for 1.0. This type of change could break other areas, and we have had enough breakage for this release cycle. Please create a ticket on CVSTRAC and we will get this fixed for 1.1. On 6/14/06, Brian Neufeld [EMAIL PROTECTED] wrote: This might have been noticed by the devs already, but I wasn't sure where to check, so I am asking here... On the Firewall: Rules: Edit page, Source section, the Type drop-down includes choices for LAN address and WAN address; should it not also include however many OPTx address interfaces you have? ~Brian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[pfSense Support] squid w/trans proxy and fw rules
Hi all, I'm having a little trouble with figuring out how firewall rules that would block port 80 interact with squid when the transparent proxying feature is enabled. If I put a simple block from x.x.x.x to any port 80 type rule in, the user still has access to the web via squid. What's the proper way to do this? Also if anyone wants to give me a freebie, I'm on beta 4 and would like to get current. Does this require a full upgrade, or can I use the cvs sync method? I've kind of fallen behind on where things are going these days, but I'd like to give the new squid packages a spin. Thanks, Charles - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
