vlan without ip address

[saeedeh motlagh]

hi Nikos
yes i read it and thank you so much but my problem is not solved yet :(.
would you please tell me step by step how should i do to have a vlan
freebsd switch?

we have four freebsd system as end nodes and one freebsd system as a
switch. two of four systems should be the member of vlan10  and two others
should be the member of vlan11. consider that the range of ip address for
both vlan are the same (192.168.2.0). the ip addresses of vlan10 members
are: 192.168.2.28 and 192.168.2.29
the ip addresses of vlan11 members are: 192.168.2.150 and 192.168.2.151
thanks
yours

On Sat, Dec 24, 2011 at 9:38 PM, Nikos Vassiliadis <nvass at gmx.com> wrote:

> On 12/24/2011 4:09 PM, saeedeh motlagh wrote:
>
>> hi again and thanks for all your replies
>> i've reviewed all suggestions and tested them all but i still haven't
>> reached an exact answer to my own scenario.
>> if you don't mind i wanna try to explain it more in details.
>>
>> the simplest scenario is to configure a freebsd box to act as a switch.
>> this switch should act as a vlan switch, in case it has to support both
>> access ports and trunk ports.
>> as we know, when a switch supports vlan access ports, it will tag all
>> incoming packets from that access port with the related vlan id. in this
>> case, any node can be a member of our vlan by simply connecting it to
>> that access port; for sure this end node needs no additional vlan
>> configurations, cause its packets will be tagged by the attached switch
>> box.
>>
>> now my problem is that, i configure that freebsd box but it doesn't act
>> as expected. and the question is how to solve this problem...
>>
>> if more details are needed, my testing freebsd box contains four
>> gbethernet interfaces; we have four other end points, each connected to
>> one of those four interfaces. all these nodes are in the same network
>> but in two different vlans. now i wanna know how to configure my freebsd
>> box to act as a vlan  supported switch.
>>
>> i'm on a real force to find the answer ASAP so any suggestions would be
>> greatly appreciated.
>> yours
>>
>
> Hello,
>
> I have sent you a little template with the commands you should use.
> I don't think a can do more than that. The general advices apply:
> break the task in smaller pieces
> examine each port with tcpdump -e
> just connect two nodes on the freebsd switch and see what's going on
>
> HTH, Nikos
>