Re: Ingress shaping via connection marking, veths and network namespace

Linux Advanced Routing and Traffic Control

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Jan 6, 2014, at 10:29 AM, Alban Crequy <alban.crequy@xxxxxxxxxxxxxxx> wrote:

> Hi,
> 
> I'm replying to your discussion about ingress shapping via connection
> marking on: http://www.spinics.net/lists/lartc/msg22750.html
> 
> Have you managed to do it?
> 
> I'm trying to do the same thing: I don't control the Internet routers, I
> just have several downloads on my computer and I would like to give a
> guaranteed bandwidth to one of the downloads. The incoming packets
> themselves are undistinguishable from Netfilter (all downloads are on
> port 80 etc.) but the application requiring the guaranteed bandwidth
> could potentially be modified to mark the connection
> (setsockopt-SO_MARK).
> 
> So I have the same problem as you: incoming packets don't have any
> marking because the ingress-qdisc runs before Netfilter.

FWIW, the way I finally solved the problem was to not use SO_MARK at all, but rather choose the local source port when making the request, so that even though the incoming data is from the remote port 80, I could use a u32 match on the destination port of the incoming packets.

David

--
To unsubscribe from this list: send the line "unsubscribe lartc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [LARTC Home Page]     [Netfilter]     [Netfilter Development]     [Network Development]     [Bugtraq]     [GCC Help]     [Yosemite News]     [Linux Kernel]     [Fedora Users]
  Powered by Linux