> -----Original Message----- > From: Bill Marquette [mailto:[EMAIL PROTECTED] > Sent: 29 September 2005 15:49 > To: support@pfsense.com > Subject: Re: [pfSense Support] 802.11q vlans > > On 9/29/05, Dan Swartzendruber <[EMAIL PROTECTED]> wrote: > > i assumed he had all that correct, since he said > > he could see the traffic going into the pfsense > > port. i was going to ask the same question, > > myself. this has to be a config problem, as i'm using this exact same > setup. > > I agree, which is why I asked the obvious question :) Not everyone > realizes that marking a port with multiple vlans doesn't mean that > it's a tagged port, just that the machine on that port can see and > talk to each of the vlans (untagged). That of course would require > pfSesne to support real interface aliases - which we don't (and I'm > not yet convinced is required) > > --Bill > [alan walters] [alan walters] Just looking at this I can only tag to a specific vlan on each port. So port to is enabled for 802.11q on vlan 1-4 with vlan 1 as the tag but it allows untagged traffic to transit. Other ports have only onevlan on then and they are tagged.
There is traffic flowing into pfsense. Example a http request to the pfsense box comes in but does not go back. Dhcp receives a response from the client and sends it back an ip but it does not get there.?? Switch or pfsense???? Does anyone use 3com 3300XM switches with vlans? Will forward my xml still if you think it's pfsense it is a test lab box so there is nothing important on it. Regards Alan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
