All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andraz Sraka <a@aufbix.org>
To: lartc@vger.kernel.org
Subject: [LARTC] linux bridging vlans?
Date: Thu, 30 Mar 2006 00:43:05 +0000	[thread overview]
Message-ID: <1143679385.16301.17.camel@localhost> (raw)


[-- Attachment #1.1.1: Type: text/plain, Size: 1327 bytes --]

re

can somebody tell me what am I doing wrong (at this late night hour),
because vlan are not getting bridged at all.

   ifconfig eth0 0.0.0.0 up
   ifconfig eth1 0.0.0.0 up
   brctl addbr br0
   brctl addif br0 eth0
   brctl addif br0 eth1
   ifconfig br0 up
   vconfig add br0 X
   vconfig add br0 Y

X = vlan-ID (example: 222)
Y = vlan ID (example: 223)

 # brctl show
   bridge name     bridge id               STP enabled     interfaces
   br0             8000.00001a1a4c74       no              eth0
                                                          eth1



 # cat /proc/net/vlan/config
  VLAN Dev name    | VLAN ID
  Name-Type: VLAN_NAME_TYPE_RAW_PLUS_VID_NO_PAD
  br0.X       | X  | br0
  br0.Y       | Y  | br0



dmesg shows that:
br0: port 2(eth1) entering learning state
br0: port 1(eth0) entering learning state
br0: topology change detected, propagating
br0: port 2(eth1) entering forwarding state
br0: topology change detected, propagating
br0: port 1(eth0) entering forwarding state

but still no data is forwarded from one interface to another? Is there
any sysctl stuff, that I need to set up like 'ip_forwarding' when doing
routing? Is there something bridging parameter for forwarding or am I
misconfigured things above?

thanks and regards,
 Andraz

[-- Attachment #1.1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 196 bytes --]

[-- Attachment #1.2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 1903 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

             reply	other threads:[~2006-03-30  0:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-30  0:43 Andraz Sraka [this message]
2006-03-30  9:01 ` [LARTC] linux bridging vlans? m.innocenti
2006-03-30 13:24 ` Piotr Chytla

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1143679385.16301.17.camel@localhost \
    --to=a@aufbix.org \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.