On Wed, May 5, 2010 at 6:34 PM, drew Roberts <zotz...@gmail.com> wrote:
> On Wed, May 5, 2010 at 5:44 PM, Chris Buechler <cbuech...@gmail.com> wrote:
>> On Wed, May 5, 2010 at 3:03 PM, drew Roberts <zotz...@gmail.com> wrote:
>>> What I am looming to do is set up box with 3 nics. I want to bridge
>>> two of them but not assign IP addresses to those nics. I want to
>>> (possibly) set up an ip address in the third nic for management
>>> purposes.
>>>
>>> I want this to allow me to drop the box inline anywhere on a network
>>> using the two bridged nics and have traffic pass through the box
>>> without needing to change anything network wise. I want to be able to
>>> shape and possibly filter traffic passing the bridge.
>>>
>>> From my initial reading a week or two ago I thought pfsense would be
>>> able to do this for me. I brought up my first box with pfsense this
>>> morning but it seems to want ip addresses where I don't want to put
>>> any.
>>>
>>> Am I misunderstanding something, or is there a documented workaround
>>> that I can use to do what I want?
>>>
>>
>> In 1.2.x, LAN and WAN must have IPs. OPT interfaces can be left
>> IP-less by bridging them, or putting "none" into the IP address box.
>
> If that is the case, can I use LAN as the management interface, Do not
> give a nic to the WAN but define the IP for it. Give the two nic I
> want to bridge to OPT1 and OPT2?
>
> Is this expected to change in 2.x?
>

In 2.0 you don't have to set an IP on any interface (though if you set
them all to "none", you can't get in and change anything anymore of
course).

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