[pfSense Support] Dual WAN, but only 1 default route...

2007-01-19 Thread Jaye Mathisen


I have a DSL connection wiht 32 static IP's, and a cable connection.

I have one very specific use for the cable connection and everythign else
goes over the DSL.

The Cable uses DHCP to assign IP's, and static is not an option for them.

My office subnet is NAT'd behind one of the 32 static IP's.  I want to continue
NAT'ing 99% of the traffic out that interface, and out the cable interface,
for the 1 connection to the 1 resource, I want it to be NAT'd, but use
the cable for outbound traffic.

The catch is, I don't want the cable DHCP info to over-write the default
route info that I have configured...

Can I do this?  Or am I perhaps not asking the question clearly?  Probably
the latter.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [pfSense Support] Help Me Plz

2007-01-19 Thread saidy
Can u tell me the step to do this. Thank you
  - Original Message - 
  From: Adam Van Ornum 
  To: support@pfsense.com 
  Sent: Wednesday, January 17, 2007 2:37 AM
  Subject: RE: [pfSense Support] Help Me Plz


  I've got an update for my situation, I was running the 12-23-2006 snapshot 
when I was having this problems but several days ago I updated to the 1-11-2007 
snapshot and its been running fine for about 4 days so far with only ~29 
processes running.





--
   Date: Mon, 15 Jan 2007 13:32:07 -0500
   From: [EMAIL PROTECTED]
   To: support@pfsense.com
   Subject: Re: [pfSense Support] Help Me Plz
   
   On 1/15/07, Adam Van Ornum [EMAIL PROTECTED] wrote:
   
I've had a similar issue on a machine I've been testing pfSense on (with 
512
MB ram). It'll run fine for a few days and then it will slow to a crawl 
and
I'll have to hard restart the machine to get it back up. When it comes 
back
up it will have that same message about the memory requirements.
   
Also, I've noticed that if I go into the shell (at any time, not just when
the above happens) and run top it'll show that around 500 processes are
running...is that normal?
   
   No, not at all.
   
   Scott
   
   -
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
   


--
  Get the Live.com Holiday Page for recipes, gift-giving ideas, and more. Check 
it out! 

Re: [pfSense Support] Dual WAN, but only 1 default route...

2007-01-19 Thread Robert Goley
I had a setup similar to this for a while.  Our cable company offers static 
IPs now.  You will need to setup the Cable connection as your WAN connection.  
If I remember correctly, this is the only interface you can setup using DHCP.  
You will add your DSL as OPT1 and use you NAT rules to define what traffic 
goes out over each connection based on your needs.  You will handle this with 
rules on the LAN interface for outgoing connections.  Because one of the 
connections is DHCP you will have to use this as a policy based dual  wan 
setup as it is labeled in the docs.

Robert

On Friday 19 January 2007 12:17, Tim Dickson wrote:
 Not quite sure what you are asking... but if I got it right:

 Setup everything like the DUAL WAN Manual shows
 Then set everything as the default gateway in your rules except for the
 IP you want to go out the cable... set that to the cable IP
 -Tim

 -Original Message-
 From: Jaye Mathisen [mailto:[EMAIL PROTECTED]
 Sent: Friday, January 19, 2007 12:47 AM
 To: support@pfsense.com
 Subject: [pfSense Support] Dual WAN, but only 1 default route...



 I have a DSL connection wiht 32 static IP's, and a cable connection.

 I have one very specific use for the cable connection and everythign
 else
 goes over the DSL.

 The Cable uses DHCP to assign IP's, and static is not an option for
 them.

 My office subnet is NAT'd behind one of the 32 static IP's.  I want to
 continue
 NAT'ing 99% of the traffic out that interface, and out the cable
 interface,
 for the 1 connection to the 1 resource, I want it to be NAT'd, but use
 the cable for outbound traffic.

 The catch is, I don't want the cable DHCP info to over-write the default
 route info that I have configured...

 Can I do this?  Or am I perhaps not asking the question clearly?
 Probably
 the latter.

 -
 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]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [pfSense Support] Dual WAN, but only 1 default route...

2007-01-19 Thread Scott Ullrich

This is partially incorrect.  There is no need to make the cable modem
the primary provider.   It should work with DHCP on the OPTX
interfaces as well.  I am running a Cable modem at my work now on OPT4
and it works fine.

But remember, the key is the gateway option in each firewall rule.
This is how you utilize multi-wan routing.

On 1/19/07, Robert Goley [EMAIL PROTECTED] wrote:

I had a setup similar to this for a while.  Our cable company offers static
IPs now.  You will need to setup the Cable connection as your WAN connection.
If I remember correctly, this is the only interface you can setup using DHCP.
You will add your DSL as OPT1 and use you NAT rules to define what traffic
goes out over each connection based on your needs.  You will handle this with
rules on the LAN interface for outgoing connections.  Because one of the
connections is DHCP you will have to use this as a policy based dual  wan
setup as it is labeled in the docs.

Robert

On Friday 19 January 2007 12:17, Tim Dickson wrote:
 Not quite sure what you are asking... but if I got it right:

 Setup everything like the DUAL WAN Manual shows
 Then set everything as the default gateway in your rules except for the
 IP you want to go out the cable... set that to the cable IP
 -Tim

 -Original Message-
 From: Jaye Mathisen [mailto:[EMAIL PROTECTED]
 Sent: Friday, January 19, 2007 12:47 AM
 To: support@pfsense.com
 Subject: [pfSense Support] Dual WAN, but only 1 default route...



 I have a DSL connection wiht 32 static IP's, and a cable connection.

 I have one very specific use for the cable connection and everythign
 else
 goes over the DSL.

 The Cable uses DHCP to assign IP's, and static is not an option for
 them.

 My office subnet is NAT'd behind one of the 32 static IP's.  I want to
 continue
 NAT'ing 99% of the traffic out that interface, and out the cable
 interface,
 for the 1 connection to the 1 resource, I want it to be NAT'd, but use
 the cable for outbound traffic.

 The catch is, I don't want the cable DHCP info to over-write the default
 route info that I have configured...

 Can I do this?  Or am I perhaps not asking the question clearly?
 Probably
 the latter.

 -
 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]

-
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] Dual WAN, but only 1 default route...

2007-01-19 Thread Tim Dickson
Apologies, should have been less vague in my descriptions...
I'm also using DHCP on my OPTX interface:
Rules look like...

*LAN net *   *   *   GATEWAY LAN -
WAN2

I had a hard time getting it to work at first and resetting the
modem/router/or switch in front of the firewall fixed it.  It was
holding on to the old MAC before the firewall was plugged in.
So to be safe... shutdown all your equip and unplug (be sure power is
drained completely) then power everything back on and you shouldn't have
a problem!
-Tim


-Original Message-
From: Scott Ullrich [mailto:[EMAIL PROTECTED] 
Sent: Friday, January 19, 2007 11:24 AM
To: support@pfsense.com
Subject: Re: [pfSense Support] Dual WAN, but only 1 default route...

This is partially incorrect.  There is no need to make the cable modem
the primary provider.   It should work with DHCP on the OPTX
interfaces as well.  I am running a Cable modem at my work now on OPT4
and it works fine.

But remember, the key is the gateway option in each firewall rule.
This is how you utilize multi-wan routing.

On 1/19/07, Robert Goley [EMAIL PROTECTED] wrote:
 I had a setup similar to this for a while.  Our cable company offers
static
 IPs now.  You will need to setup the Cable connection as your WAN
connection.
 If I remember correctly, this is the only interface you can setup
using DHCP.
 You will add your DSL as OPT1 and use you NAT rules to define what
traffic
 goes out over each connection based on your needs.  You will handle
this with
 rules on the LAN interface for outgoing connections.  Because one of
the
 connections is DHCP you will have to use this as a policy based dual
wan
 setup as it is labeled in the docs.

 Robert

 On Friday 19 January 2007 12:17, Tim Dickson wrote:
  Not quite sure what you are asking... but if I got it right:
 
  Setup everything like the DUAL WAN Manual shows
  Then set everything as the default gateway in your rules except for
the
  IP you want to go out the cable... set that to the cable IP
  -Tim
 
  -Original Message-
  From: Jaye Mathisen [mailto:[EMAIL PROTECTED]
  Sent: Friday, January 19, 2007 12:47 AM
  To: support@pfsense.com
  Subject: [pfSense Support] Dual WAN, but only 1 default route...
 
 
 
  I have a DSL connection wiht 32 static IP's, and a cable connection.
 
  I have one very specific use for the cable connection and everythign
  else
  goes over the DSL.
 
  The Cable uses DHCP to assign IP's, and static is not an option for
  them.
 
  My office subnet is NAT'd behind one of the 32 static IP's.  I want
to
  continue
  NAT'ing 99% of the traffic out that interface, and out the cable
  interface,
  for the 1 connection to the 1 resource, I want it to be NAT'd, but
use
  the cable for outbound traffic.
 
  The catch is, I don't want the cable DHCP info to over-write the
default
  route info that I have configured...
 
  Can I do this?  Or am I perhaps not asking the question clearly?
  Probably
  the latter.
 
 
-
  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]

 -
 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]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]