On Friday 19 January 2007 14:23, Scott Ullrich wrote:
> 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.
Did this change somewhere along the line?  I had this setup when using the 
earlier betas....

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

Should have been more clear.  This is what I was referring to change on the 
LAN rules.

> 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: [email protected]
> > > 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]

Reply via email to