Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "Kristiadi Himawan" <kristiadi_himawan@dtp.net.id>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Htb on trunked line
Date: Fri, 03 Oct 2003 08:11:42 +0000	[thread overview]
Message-ID: <marc-lartc-106516896632537@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106503280409228@msgid-missing>


I have try to create vlan from both side, eth0.106 and eth1.106 also br0.106
but why traffic from vlan 106 didn't enter into eth0.106,eth1.106,br0.106
although there's traffic.

Here's the interfaces statistic :

br0       Link encap:Ethernet  HWaddr 00:04:75:DA:26:34
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4101545 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:255233879 (243.4 Mb)  TX bytes:0 (0.0 b)

br0.106   Link encap:Ethernet  HWaddr 00:04:75:DA:26:34
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

eth0      Link encap:Ethernet  HWaddr 00:04:75:E9:58:B3
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2064270 errors:0 dropped:0 overruns:1 frame:0
          TX packets:2377003 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:152157356 (145.1 Mb)  TX bytes:342126806 (326.2 Mb)
          Interrupt:5 Base address:0xd800

eth0.106  Link encap:Ethernet  HWaddr 00:04:75:E9:58:B3
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

eth1      Link encap:Ethernet  HWaddr 00:04:75:DA:26:34
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2462723 errors:0 dropped:0 overruns:1 frame:0
          TX packets:1976909 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:348059246 (331.9 Mb)  TX bytes:146839806 (140.0 Mb)
          Interrupt:9 Base address:0xd880

eth1.106  Link encap:Ethernet  HWaddr 00:04:75:DA:26:34
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)


Here is tcpdump result from br0 :

14:47:00.374281 802.1Q vlan#106 P0 noc5.xxx.xxx.xx.33288 >
IP-160-227.xxx.xxx.xx.ssh: . ack 112 win 63712 <nop,nop,timestamp 9250021
146295576> (DF) [tos 0x10]
14:47:00.578201 802.1d config 8001.00:0a:b7:ea:fa:00.8002 root
8001.00:0a:b7:ea:fa:00 pathcost 0 age 0 max 20 hello 2 fdelay 15
14:47:00.579819 0:a:b7:ea:fa:2 > 1:0:c:cc:cc:cd snap ui/C len9
14:47:00.698593 802.1Q vlan#102 P7 1:0:c:cc:cc:cd > 0:a:b7:ea:fa:2 snap ui/C
len9
14:47:00.710374 802.1Q vlan#106 P7 1:0:c:cc:cc:cd > 0:a:b7:ea:fa:2 snap ui/C
len9
14:47:01.215717 802.1Q vlan#1 P2 CDP v2, ttl\x180s DevID 'sw2-customer-5thfl'
Addr (1): IPv4 192.168.2.6 PortID 'FastEthernet0/8' CAP 0x28[|cdp]

Any suggestion why ?


----- Original Message -----
From: "Ryan Goldberg" <rgoldber-list-lartc@bitburst.com>
To: "Kristiadi Himawan" <kristiadi_himawan@dtp.net.id>
Sent: Thursday, October 02, 2003 1:43 AM
Subject: Re: [LARTC] Htb on trunked line


> On Wed, 2003-10-01 at 13:41, Kristiadi Himawan wrote:
> > Dear All,
> >
> > I have configuration like this :
> >
> > DVB     Modem
> > |                |                                 ___Link A
> > \               /     trunk                    /
> > CiscoRouter ------------CiscoSwitch-------Link B
> >                                                  \___Link C
>
> Plug the linux box into the switch, set the link to dot1q, add
> subinterfaces on the linux box, set As and Cs routes to each other via
> the IPs on those subinterfaces, and do the shaping on those
> subinterfaces.  Should work no problem.
>
> Or are you trying to put the linux box in between the switch and
> router?  Then you'd have to talk dot1q to both devices and bridge each
> corresponding valn to each othter (e.g eth0.3 bridged with eth1.3) and
> do the shaping on those interfaces.  That should also work.
>
> Ryan
>
>
>
> I don't about trying to shape on a "raw" trunked link...
>
>

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2003-10-03  8:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-01 18:41 [LARTC] Htb on trunked line Kristiadi Himawan
2003-10-01 18:55 ` Steve Wright
2003-10-01 20:39 ` Kristiadi Himawan
2003-10-01 20:48 ` Kristiadi Himawan
2003-10-01 23:02 ` Ryan Goldberg
2003-10-01 23:40 ` DTPNet Support
2003-10-03  8:11 ` Kristiadi Himawan [this message]
2003-10-06 10:58 ` Ryan Goldberg
2003-10-07  2:54 ` Kristiadi Himawan

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=marc-lartc-106516896632537@msgid-missing \
    --to=kristiadi_himawan@dtp.net.id \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox