I do this all the time and using a separate nic is simpler and easier to manage than an alias. Unless I am missing something, a vlan for this case is overkill.
------------------ Richard On Thu, Nov 18, 2010 at 4:13 PM, David Burgess <apt....@gmail.com> wrote: > On Thu, Nov 18, 2010 at 3:51 PM, fi...@7technw.com <fi...@7technw.com> > wrote: > > Another easy solution is to just add another nic. > > Not an option in this case. The OP described a wireless network where > the client subnet and management subnet exist on the same physical > network. You can't change that in this case, so your two options are > to separate them virtually (vlans) or just run them on the same > physical network. > > Yes, he could use another NIC and plug it into a switch along with the > first NIC and the wireless network, but this still doesn't separate > the two networks, and is no better than creating an alias on the > existing NIC. > > db > > --------------------------------------------------------------------- > To unsubscribe, e-mail: support-unsubscr...@pfsense.com > For additional commands, e-mail: support-h...@pfsense.com > > Commercial support available - https://portal.pfsense.org > >
