From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] CBQ to ASNs?
Date: Mon, 03 Dec 2001 01:44:09 +0000 [thread overview]
Message-ID: <marc-lartc-100734376903943@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100728645131774@msgid-missing>
On Sun, Dec 02, 2001 at 04:58:54PM +0100, Martin Devera wrote:
> > So: Can I do bandwidth management based on destination ASN?
>
> not yet. Only IPs. You will need to fetch data from BGP and use
> them to setup your qos filters.
>
> I can't invent another way ..
You might be able to use 'realms'. I think Zebra has some realms support.
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Software & Services
Trilab The Technology People
Netherlabs BV / Rent-a-Nerd.nl - Nerd Available -
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
prev parent reply other threads:[~2001-12-03 1:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-02 9:49 [LARTC] CBQ to ASNs? Jeff Warnica
2001-12-02 15:58 ` Martin Devera
2001-12-03 1:44 ` bert hubert [this message]
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-100734376903943@msgid-missing \
--to=ahu@ds9a.nl \
--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