Greg,

Tell me exactly what you want to do and I will try to write up a doc for you and to contribute to the project.

I am only like a week or less into using PfSense but I think I get the basics enough to write something up. Even better, it may be pretty good since it will come through the eyes of a PfSense Newbie :)

Todd

--
Need A Toll Free Number That Follows You?
http://www.CallChasers.com

----- Original Message ----- From: "Greg Huggins" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, September 16, 2005 2:37 PM
Subject: RE: [pfSense-discussion] Optional NIC


Loved the Sesame Street comment!!  Never thought of the interface colors
in IPCOP like that.  Now that I have stopped laughing I guess from
reading your email that this is indeed possible to do what I want.

Do you know of a "how to" to do this so that I do not mess it up in
setting this up?

Thanks,



-----Original Message-----
From: Scott Ullrich [mailto:[EMAIL PROTECTED]
Sent: Friday, September 16, 2005 3:32 PM
To: [email protected]
Subject: Re: [pfSense-discussion] Optional NIC

On 9/16/05, Greg Huggins <[EMAIL PROTECTED]> wrote:
I am currently using IPCOP and have the RED - Wan, GREEN - Lan and
BLUE -
Wireless concept in my mind for referring to the various NICS.  In my
current IPCOP configuration I have my wireless AP and other computers
hooked
to the BLUE NIC and these computers cannot see the GREEN-Lan unless
rules
are made to allow the BLUE to see the GREEN but all on the BLUE NIC
can
access the internet.

Sounds like a sesame street firewall!?

Is this the same concept in pfSense?  If I have a 3 NIC setup can the
optional NIC (BLUE) see others on the BLUE and access the internet but
not
access computers on the GREEN-Lan side?

No, we expect our users to not be avvid watchers of sesame street
(unless you have kids of course).

All joking aside, we have the mandatory WAN and LAN interfaces and you
can add "Optional" interfaecs by visiting Assign interfaces.   You
could for instance add an optional interface to be an additional WAN,
routed subnet, etc.

Scott

Reply via email to