saeedeh motlagh writes:
| i think i have similar problem too. you want to have tagged and
| untagged traffic at the same time on the trunk port, right?
| in your topology the vlans and trunk port are bridged and the tagged
| traffic is passed through the trunk port and every thing works fine.
| the
Sorry my last post was sent out suddenly by pressing a key, I don't
yet know even which one! the compelete post is written down here.
let me explain my problem with this type of topology when I want to
simulate a switch like cisco
eth0 -+
|
let me explain my problem with this type of topology when I want to
simulate a switch like cisco
eth1 -+ --- bridge1 --- vlan9 --+-- eth0 --- trunk0
|
eth2 -+ --- bridge2 --- vlan8 --+
On 3/6/12, Peter Je
On 2012-Mar-06 09:15:57 +0330, h bagade wrote:
>On 3/6/12, Peter Jeremy wrote:
>> The following example diagram shows 3 distinct packet flows:
>> - packets tagged 5 in trunk1 and 6 in trunk0
>> - packets tagged 7 in trunk1 and 9 in trunk0
>> - packets tagged 8 in trunk0 and 10 in trunk2
>>
>>
On 3/6/12, Peter Jeremy wrote:
> Please don't top-post.
>
>
> OK. Sorry, I misunderstood what you were trying to achieve. I am
> using FreeBSD as a router rather than a switch. That said, I suspect
> your problem is that you are misunderstanding how VLAN tagging is
> applied. If a packet flows
Please don't top-post.
On 2012-Mar-05 13:30:36 +0330, h bagade wrote:
>on layer 2 switch, ports doesn't have ip addresses and traffic comming
>from a vlan port is tagged and pass through trunk port. this means
>that in our freebsd box which plays the role of switch, no interfaces
>should have ip
On 2012-Mar-04 10:01:07 +0330, h bagade wrote:
>I have problems with vlan interfaces on freebsd. I want to make my
>system like a switch with vlan ports and also a trunk port in
>conjuction with other switches. I thought that vlan interfaces would
>help me tagging traffic when traffic is going out
on layer 2 switch, ports doesn't have ip addresses and traffic comming
from a vlan port is tagged and pass through trunk port. this means
that in our freebsd box which plays the role of switch, no interfaces
should have ip addresses.
In your topology the em0 which plays the role of trunk port has
if you can not get the image, I've tried to draw text form here with commands:
##
[system 1]--#--[eth0]#
# |-- [hub0]--[vlan2] #
[system 2]
I've tried netgraph nodes too! but stuck on the next step and asked
the problem on this forum and received no answer:( my netgraph
scenario is described below:
I have designed a topology(attached) using netgraph to add vlan2
tag to the frames coming from eth0(vlan port) and send it to
eth1(trunk p
Use netgraph nodes.
> -Original Message-
> From: owner-freebsd-...@freebsd.org [mailto:owner-freebsd-
> n...@freebsd.org] On Behalf Of h bagade
> Sent: Sunday, March 04, 2012 3:31 PM
> To: freebsd-net
> Subject: problem with vlan interfaces tagging/untagging in a simulated
> switch box
>
11 matches
Mail list logo
