William Bulley schrieb:
> According to Chris Buechler <cbuech...@gmail.com> on Mon, 01/12/09 at 11:44:
>   
>> On Mon, Jan 12, 2009 at 8:36 AM, William Bulley <w...@umich.edu> wrote:
>>     
>>> Second, I have one question:
>>>
>>>   "How does one set (and save) a default route (as in "route add default 
>>> 10.0.0.1")
>>>   from within pfSense?"
>>>       
>> On the WAN. The WAN interface needs to be the one facing the rest of
>> your network as it's the only one that can have the default gateway
>> (in 1.2.x). Though I think just plugging your gateway IP into the WAN
>> page will suffice regardless of whether it really resides on WAN.
>>     
>
> Thanks.
>
> Is this behaviour essential to pfSense?  It doesn't seem like it would
> be a FreeBSD requirement.  Maybe a future enhancement to pfSense may make
> multiple interfaces more "interchangeable" or "clone-like".  What if my
> sis0 interface on my 4801 died (unlikely, to be sure).  I would want to
> move to use a different (sis1 or sis2) interface.  It seems to me all the
> (like, ethernet) interfaces should have identical configuration choices.
>
> I say this as a newbie if only to avoid confusion with the "AccessPoint2"
> URL tutorial which made no mention of this feature/fact IIRC.  I will try
> your WAN suggestion above.  If this works, so be it.  I think this would
> mean that WAN (sis1) would become active (since it is disabled at present).
> That is the only unusual side-effect, but not a serious show stopper.
>
> Thanks again for your help.
>
> Regards,
>   


FreeBSD6 had no support for lagg(4). Though I think it may have been
MFCed to 6.4.
FreeBSD7 has.
Pfsense 1.2 was developed with FreeBSD6 in mind.

I don't know - maybe pfSense 2.0 will have support for lagg(4)?

I don't miss it - I only have one DSL line anyway ;-)



Rainer




---------------------------------------------------------------------
To unsubscribe, e-mail: support-unsubscr...@pfsense.com
For additional commands, e-mail: support-h...@pfsense.com

Commercial support available - https://portal.pfsense.org

Reply via email to