Hello,
I have PFsense snapshot 27-3-2007, but when I click save on the RIP routed
package the system shows a WARNING message saying:
Warning: fopen(/usr/local/pkg/routed.xml): failed to open stream: No such
file or directory in /etc/inc/xmlparse.inc on line 158 Error: could not open
XML input
Thanks, I'll check out the RIP issue.
--Bill
On 4/5/07, Samer Chaer [EMAIL PROTECTED] wrote:
Hello,
I have PFsense snapshot 27-3-2007, but when I click save on the RIP routed
package the system shows a WARNING message saying:
Warning: fopen(/usr/local/pkg/routed.xml): failed to open
stream:
I´m using ipsec to connect three branch offices. There is a issue with the
firewall described below:
I´m not allowing output traffic from LAN subnet to WAN, so I disabled the
default LAN rule Default LAN - any, however disabling this rules causes
LAN subnet not reach the ipsec tunnels. After
On 4/5/07, Diego Morato [EMAIL PROTECTED] wrote:
I´m using ipsec to connect three branch offices. There is a issue with the
firewall described below:
I´m not allowing output traffic from LAN subnet to WAN, so I disabled the
default LAN rule Default LAN - any, however disabling this rules causes
Fixed, check the next snapshot in a couple hours. The last embedded
build that I see has a date of 2007-Apr-04 03:12:30, you'll want
something after that (in the process of building now).
--Bill
On 4/5/07, Samer Chaer [EMAIL PROTECTED] wrote:
Hello,
I have PFsense snapshot 27-3-2007, but
Dear Bill,
did you fix the rip down after pfsense restart problem?
thanks,
Samer.
On 4/5/07, Bill Marquette [EMAIL PROTECTED] wrote:
Fixed, check the next snapshot in a couple hours. The last embedded
build that I see has a date of 2007-Apr-04 03:12:30, you'll want
something after that
On 4/5/07, Samer Chaer [EMAIL PROTECTED] wrote:
Dear Bill,
did you fix the rip down after pfsense restart problem?
Good point, probably not. I'll check it out in a couple hours.
--Bill
-
To unsubscribe, e-mail: [EMAIL
Scott,
Ok. Thank you very much. Each tab on Firewall Rules page control the
traffic incoming on each corresponding interface.
--
Diego
- Original Message -
From: Scott Ullrich [EMAIL PROTECTED]
To: support@pfsense.com
Sent: Thursday, April 05, 2007 1:44 PM
Subject: Re: [pfSense
Using a soekris 4801 with 1.0.1 of pfsense on a single WAN connection,
works just fine.
I want to add another WAN connection to OPT1, but I don't want failover,
or load balancing, I have 1 application that needs to route traffic out
the new connection.
I can specify the destination IP for any
I don't have thos config, but i could imagine it works with the gateway option
(select a gateway different than default)
Perhaps it might be necessary to define a pool or else fort hat...
Just try a bit :-)
Regards, Martin
-Ursprüngliche Nachricht-
Von: Jaye Mathisen [mailto:[EMAIL
http://doc.pfsense.org/index.php/Multi-Wan/Load-Balancing
Holger
-Original Message-
From: Fuchs, Martin [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 05, 2007 11:13 PM
To: support@pfsense.com
Subject: AW: [pfSense Support] OK, I think this is simple...
I don't have thos config, but
Yeah, I read that. But I don't want load balancing or failover.
Logging in via shell shows the routing is set right, in that the
default route is still WAN.
# netstat -rn
Routing tables
Internet:
DestinationGatewayFlagsRefs Use Netif Expire
default
Just leave off the steps for creating the pools and skip straight to setting
your LAN rules. All you should have to do to send the traffic for the one
application is define a couple of rules based on either source IP on the LAN,
Destination IP, or destination ports that application uses. you
Been struggling for quite a few hours today trying to get some IPSEC
tunnels established over the OPT interface.
WAN = 216.211.25.114 (PPPoE DSL)
OPT1 = 24.109.252.249 (static IP)
pfSense Version: 1.0.1-SNAPSHOT-03-27-2007 built on Thu Apr 5 18:16:29
EDT 2007
I've got a VPN tunnel on the
I have a customer with a setup that sounds very similar to what you are
describing. They have 2 WAN type connections. The first is an SDSL
line that is used for IPSEC and other general WAN stuff. The second is
an ADSL line that they use to feed their proxy server/content filter.
They don't
15 matches
Mail list logo
