Prioritization for a specific website.
Prioritization for a specific website.
I am using centos 7 with squid (Transparent mode). This server is acting as Proxy server and I was wondering if there is any option that can help Prioritize a specific website?
Re: Prioritization for a specific website.
Implement QoS on your network?
Re: Prioritization for a specific website.
Yeah QOS. Can we do that with centOS?
-
- Posts: 2
- Joined: 2015/12/05 20:05:02
- Location: UK
Re: Prioritization for a specific website.
I'd love to give you a simple answer but actually, prioritisation is a pretty complex subject (particularly on the internet which is a bit like the "wild wild west")
DSCP marking is the most common way to indicate how a packet should be treated by routers on its way across the network.
See http://www.tldp.org/HOWTO/html_single/T ... s-iproute2 for more info.
DSCP marking is the most common way to indicate how a packet should be treated by routers on its way across the network.
- DSCP marks can be applied to transmitted packets by iptables (not sure if firewalld can also do it in CentOS7).
- DSCP marks work well in corporate networks but are sometimes stripped off or ignored by ISP's
- The meaning of DSCP marks are not always consistent across ISP's
- DSCP marks must be applied by both client and server to have them apply in both traffic directions
- See https://en.wikipedia.org/wiki/Differentiated_services
- RSVP requires the client to ask for a specific amount of bandwidth
- Routers on the way to the server may grant or reject the request (depending on how busy the network is)
- This mechanism is more likely to be used in corporate networks. It's very rare on the internet due to lack of co-operation across ISP's
See http://www.tldp.org/HOWTO/html_single/T ... s-iproute2 for more info.
Re: Prioritization for a specific website.
Actually more specifically, in the Internet, the priorities and so on made by intermediate carriers (i.e.: network operators) may not match yours (and often don't). As a made up example, if I'm a network operator and can send your data (you may or may not be my direct customer) down one of two different network paths, one is "quicker" but more expensive and the other is "slower" but cheaper, the data will probably end up going down the "slower" cheaper path (which may still match your required timings anyway), regardless what the QoS bits in your packet header say. There is absolutely nothing you can do about that. I guess you could enter into an agreement with your ISP and they enter into an agreement with their upstream ISP and so on, but that won't scale and would be very, very expensive to do.