On Fri, Jul 24, 2009 at 2:19 PM, Joseph L. Casale<[email protected]> wrote: > The deployment I was planning earlier that referenced the 1u case > reco from everybody just got accelerated, the PIX that I was replacing > died:) > > I have a single wan(dhcp)(em0) and lan(192.168.0.1)(em1) interface, both > working > as expected. On the switch that the lan(192.168.0.1)(em1) interface is on, > there > is a tagged VLAN(3) I need access to, so I may forward external ports from the > wan to it, and write rules to allow certain ports access between the lan and > vlan(3). > > I set up a vlan(3) on my lan int(em1) in the assign menu, the switch is set to > untag traffic into the default lan, and allow tagged traffic into vlan(3). >
You should really tag everything if you're going to tag anything, for security reasons. > With my opt1 interface on a new subnet that matches vlan(3), how do I > configure it > now? > Not following what you mean. You'll need to assign the VLAN as an OPT interface. > I am kinda pressed as I have scads of people lined up wondering when > connectivity > will be restored and I hadn't finished figuring out how I was going to > migrate off > the pix, presently I had only been reading about the vpn config as I assumed > that > would be the most challenging:) > > Any help would be appreciated! > In a bind like this, it's probably in your best interest to see the link in the footer for support, I'd be glad to work with you immediately to get it all setup and working properly. Usually a good way to save yourself a lot of time, and your users a lot of frustration in this case since you had to make an emergency switch. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] Commercial support available - https://portal.pfsense.org
