At 03:15 AM 9/30/2005, you wrote:
[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.
Well, this is weird. I've got to believe it's a configuration
problem with your switch. If it weren't, I can't see how the packets
would exit the switch at all. BTW, my switch is such that each port
is associated with one and only one vlan, but I have to do this too:
1. put the pfsense port in both vlans (membership wise). don't know
how your switch does that.
2. change the ingress filtering so it won't drop by default packets
with a VID not matching the default one.
Not doing both of the above would cause your symptoms.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
