Drew Lehman on 16 Aug 2012 13:39:09 -0700

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]


Ok, just for a heads up, I had to explicitly tag the ports for the pfsense and WAPs as being in the VLAN (so much for GVRP). That got the DHCP server to work. I added a rule to the VLAN virtual adapter to allow all access. With this I was able to get to the default VLAN, but not the Internet. I did some looking around and found out I had to add a route for that virtual adapter, even though I used the default gateway. Essentially I did this as the command prompt: route add -net netmask gw (the default gateway). I'm surprised I had to do this last step and that pfsense did not add a route by default for each new adapter.

On 8/16/2012 11:00 AM, John Kreno wrote:
He's saying that he's enabled a DHCP server on vlan 100, and he's
trying to get to clients on vlan 100 off of the Access Point. All of
that would be in the same broadcast domain, assuming that he has vlan
continuity through the switch.

Philadelphia Linux Users Group         --        http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug