LARTC - Feb 2002 - TC and Diffserv on IPv6

Hi all,

does somebody have experience with IPv6 traffic control?

I have tried different tools - but, none of them seemed to work the way 
it works with IPv4. Our project, Multi-Media-Conferencing, builds upon 
IPv6 and is intended to use Diffserv for supporting differentiated 
services requirements.
Is that feasible? At the moment we''re facing the following problems:

1.) Settings made using tc don''t have an effect on IPv6-traffic. (Is it
due to tc or to the kernel?)

2.) ip6tables does not support the TOS target or equivalent traffic 
class setting.

3.) mgen6 does not support traffic class marking.

4.) ping6 returns the message: "Flowinfo is not supported."


Thanks

viktor

On Tue, Feb 26, 2002 at 12:28:36AM +0100, Viktor Kemmet
wrote:
> Hi all,
> 
> does somebody have experience with IPv6 traffic control?
partly the same thing, partly not.

> 1.) Settings made using tc don''t have an effect on IPv6-traffic.
(Is it
> due to tc or to the kernel?)
tc filter won''t currently match ipv6, but tc commands will shape *all*
packets going out.
> 
> 2.) ip6tables does not support the TOS target or equivalent traffic 
> class setting.
but does it support --mark? If it does so, you can shape on that.
> 3.) mgen6 does not support traffic class marking.
> 
> 4.) ping6 returns the message: "Flowinfo is not supported."
Bug Alexey, i think he will care - tc filter should do ipv6.

Regards,

bert

-- 
http://www.PowerDNS.com          Versatile DNS Software & Services
http://www.tk                              the dot in .tk
http://lartc.org           Linux Advanced Routing & Traffic Control HOWTO

bert hubert wrote:
> On Tue, Feb 26, 2002 at 12:28:36AM +0100, Viktor Kemmet 
> wrote: 
> > Hi all,
> > 
> > does somebody have experience with IPv6 traffic 
> control? 
> 
> partly the same thing, partly not.
> 
> 
> > 1.) Settings made using tc don''t have an effect on 
> IPv6-traffic. (Is it  
> > due to tc or to the kernel?)
> 
> tc filter won''t currently match ipv6, but tc commands 
> will shape *all* 
> packets going out.
> 
Does that mean, I cannot use the tc filter command with IPv6?
How can I shape without filter?
The attached script "setup-01.tc.sh" works fine with v4. The traffic
is
shaped according to the qdisc tbf settings. 
With v6 these setting move all packets to the class, the prio-map maps 
the Best-Effort traffic to. 
Is this because the tc filter on the destination ports already fails?
  $TC filter replace $DEV parent 1:0 protocol ip prio 1 u32 \
    match ip dport $VIDEO_PORT 0xffff flowid 1:2
> > 
> > 2.) ip6tables does not support the TOS target or 
> equivalent traffic  
> > class setting.
> 
> but does it support --mark? If it does so, you can shape 
> on that. 
Yes, MARK seems to work ("Edge1new.sh").
  ip6tables -I OUTPUT -t mangle -p udp --destination-port 5001 \
    -j MARK --set-mark 1
  ip6tables -L OUTPUT -t mangle
... lists the desired settings. But again

  $TC filter add $EGDEV parent 1:0 protocol ip prio 4 handle 1 fw 
classid 1:1 

does not what it should.
What do you mean by shaping on fw-mark? Is that possible without using 
tc filter? 
> 
> > 3.) mgen6 does not support traffic class marking.
> > 
> > 4.) ping6 returns the message: "Flowinfo is not 
> supported." 
> 
> Bug Alexey, i think he will care - tc filter should do 
> ipv6. 
> 
> Regards,
> 
> bert
> 
viktor