<div class="gmail_quote">On Thu, Jan 7, 2010 at 3:03 PM, Ashley M. Kirchner <span dir="ltr"><<a href="mailto:ashley@pcraft.com">ashley@pcraft.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
It will require some reconfiguring of either another subnet and packet forwarding, or configuring VLANs on the main switch the APs are on, or do some type of song and dance with WINS.</blockquote><div><br>It's not an either/or for those options. You have to do all of those. The VLANS will be on separate subnets and WINS is what will make Network Neighbor continue working as-is ( at least that is what another person said WINS will do ).<br>
<br>So the steps are:<br><br>1) set up vlans on your switch, for instance VLAN 101 and VLAN 102. Put the ports connected to your APs in VLAN 102 and the ports for your wired computers in VLAN 101.<br><br>2) You do have two options for connection the vlans to your Fedora router:<br>
<br><div style="margin-left: 40px;">2A) put a second nic in the Fedora box and put the port for one nic in VLAN 101 and the port for the other nic in VLAN 102. Configure iptables to allow routing between the two nics.<br>
<br>2B) use a single nic. Configure the port on the switch as a vlan trunk port. Configure the nic in Fedora as a vlan trunk for and set up a virtual interface for VLAN 101 and a virtual interface for VLAN 102. This is a little more complicated because you have to learn how to configure vlan trunking in Fedora, but it's really pretty easy. This is they way I would do it because it's more flexible. Configure iptables to allow routing between the two virtual interfaces.<br>
<br></div>3) Set up WINS on one of your servers. I would use a SAMBA server.<br><br>This is really a very standard set up and you'll learn things that you'll really need to eventually learn anyway as your network grows.<br>
</div></div>