From owner-freebsd-net@FreeBSD.ORG Mon Mar 5 04:31:47 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 239FD106564A for ; Mon, 5 Mar 2012 04:31:47 +0000 (UTC) (envelope-from bagadeh@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 6B2538FC13 for ; Mon, 5 Mar 2012 04:31:46 +0000 (UTC) Received: by bkcjc3 with SMTP id jc3so3767525bkc.13 for ; Sun, 04 Mar 2012 20:31:45 -0800 (PST) Received-SPF: pass (google.com: domain of bagadeh@gmail.com designates 10.205.132.141 as permitted sender) client-ip=10.205.132.141; Authentication-Results: mr.google.com; spf=pass (google.com: domain of bagadeh@gmail.com designates 10.205.132.141 as permitted sender) smtp.mail=bagadeh@gmail.com; dkim=pass header.i=bagadeh@gmail.com Received: from mr.google.com ([10.205.132.141]) by 10.205.132.141 with SMTP id hu13mr9455944bkc.87.1330921905409 (num_hops = 1); Sun, 04 Mar 2012 20:31:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=iQQgolIzsHF37ildfVzv//TfABs07Z7dMnoE4UPj3uU=; b=VGzqiendUcecmaPJJ4FiuXt0g+Q6OyYJnrg3uP5/qhTVnLe7XfB3b2SlTNaDQv1knd f4S0xcjcBWjtr70QVF7AIvbJeG3arjjN3uTRcH5Hw6hOP+7Y8D8osutI1EgIle+C5LuV V4LpPMfOMf3LeCZ+hjux4gXPEHZ1Dy0Z8TY6FnoRYRAg3HrJkdx3/48cXqXdVSxV8WfQ 362lqVu3AI+knLZDYBxKNJh54PvoHxfL0Fb1T6eaGuh0PxtcAyDwrbrxg54U+yZ9J96I vR/iM7LZk+txcSCroLu7Tmi5pHwZW/DlE6KOtG9YEIZR44ZfyToIAblDqqYCKGdTgA/J eu+w== MIME-Version: 1.0 Received: by 10.205.132.141 with SMTP id hu13mr7509095bkc.87.1330921905199; Sun, 04 Mar 2012 20:31:45 -0800 (PST) Received: by 10.204.167.139 with HTTP; Sun, 4 Mar 2012 20:31:44 -0800 (PST) In-Reply-To: <4f5344cc.51e4cc0a.522a.1a15@mx.google.com> References: <4f5344cc.51e4cc0a.522a.1a15@mx.google.com> Date: Mon, 5 Mar 2012 08:01:44 +0330 Message-ID: From: h bagade To: Rozhuk.IM@gmail.com Content-Type: multipart/mixed; boundary=000e0cdfd620621a5304ba7767f4 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net Subject: Re: problem with vlan interfaces tagging/untagging in a simulated switch box X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Mar 2012 04:31:47 -0000 --000e0cdfd620621a5304ba7767f4 Content-Type: text/plain; charset=ISO-8859-1 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 port) to go out of the box. it works fine. Then I tried to add another interface like eth0 which named eth2(vlan port) to be tagged vlan2 too. After that, I bridged eth0 and eth2 using ifconfig(as vlan ports are connected to each other on same vlan id). When traffic comes from eth0(system1) to the destination eth2(system2), all traffic also sent out eth1 which is not suitable! In the mentioned scenario, I don't want the traffic pass to the eth1. Is there any way that eth1 recognize which mac addresses don't belong to this box then sends the traffic out? I mean I want to send taraffic out of eth1 when the destination is not accessible via FreeBSD box so it should be sent out to be find out. On 3/4/12, rozhuk.im@gmail.com wrote: > > Use netgraph nodes. > > >> -----Original Message----- >> From: owner-freebsd-net@freebsd.org [mailto:owner-freebsd- >> net@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 >> >> Hi all, >> >> 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 the trunk port(or >> when it receives on vlan ports). >> The problem, I've encountered is that vlan interafaces on freebsd do >> tagging/untagging when the traffic is sourced/destined from/to them >> which in this case they should be assigned IP addresses. In other words >> they won't tag the traffic passing through their parent interface which >> I need to. >> >> In my case to be acting like a switch, interfaces on system won't have >> ip addresses and I need to tag the traffic coming from for example >> interface1 when passing through interfaceN(acting as trunk port). >> How could I reach this? would it be possible to use vlan interfaces to >> do so? >> >> I've tried many many ways to simulate the case but no success achieved! >> I'm really interested to find the proper solution for my config. >> >> Any comments or hints are really apperciated. >> _______________________________________________ >> freebsd-net@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-net >> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > > --000e0cdfd620621a5304ba7767f4--