Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "DTPNet Support" <kristiadi_himawan@dtp.net.id>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Htb on trunked line
Date: Wed, 01 Oct 2003 23:40:18 +0000	[thread overview]
Message-ID: <marc-lartc-106505074030158@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106503280409228@msgid-missing>

Yah, A and C on different ip networks and also different vlan.

It's only example, in the real test i use zebra with a lot of vlan
interfaces and connect to some cisco switch.

And discover that some networks in different vlan can't reach, when i try to
see unreachable networks
using arp, i found uncomplete arp from it.

Until now i don't know why some vlans works fine but the others not.. :(

I think it's because arp, may be need to wait for long time before arp get
complete.
I try this just for half an hour.

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


> On Wed, 2003-10-01 at 15:39, Kristiadi Himawan wrote:
> > About your first option to plug the linux box to the switch and create
vlan
> > interfaces on it, i have try that before and the result some network
can't
> > reach because of arp uncomplete.
>
> Are A and C on different IP networks?  With routes to each other via the
> IPs on the subinterfaces on the linux box and they can arp for those
> IPs, I don't see where the arp issue would come from.
>
> > And the second option to put linux box between router and switch is the
> > better choice but i face new problem on it.
> > I already create transparent bridge (using eth0 and eth1) on the linux
box
> > and it's work.
> > But the problem occur when i try to shape the link using HTB or CBQ, the
> > filter always miss.
> > I will try your suggestion to bridge every vlan interfaces in the linux
box.
> > I hope this is the solution.
>
> Yeah we do this it works fine.  That is, with a bridge per VLAN.  If you
> want to share bandwidth amond the interfaces though, you need to set up
> IMQ, which I have not done.
>
> > > 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
> > >
> > > Ryan Goldberg wrote:
> > > 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.
>
>
>

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

  parent reply	other threads:[~2003-10-01 23:40 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 [this message]
2003-10-03  8:11 ` Kristiadi Himawan
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-106505074030158@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