| View previous topic :: View next topic |
| Author |
Message |
newbie95
Joined: 08 Dec 2009 Posts: 1
|
Posted: Tue Dec 08, 2009 2:04 pm Post subject: Http proxy NOT in transparent mode + QOS working with it |
|
|
Because i need to address the zeroshell proxy in my browser. (default PC gateway can not be zeroshell in my network config ,so transparent mode can't work in this case) ! javascript:emoticon(' ')
QOS doesn't seem to work when http proxy is enable ?!. javascript:emoticon(' ')
regards. |
|
| Back to top |
|
 |
ppalias
Joined: 17 Dec 2008 Posts: 1151 Location: Athens, Greece
|
Posted: Tue Dec 08, 2009 2:23 pm Post subject: |
|
|
| It depends on the rules of the QoS and the interface you apply them. When you have a proxy server, traffic originates from the ZS itself. |
|
| Back to top |
|
 |
atheling
Joined: 24 Sep 2009 Posts: 212
|
Posted: Tue Dec 08, 2009 7:08 pm Post subject: |
|
|
| ppalias wrote: | | It depends on the rules of the QoS and the interface you apply them. When you have a proxy server, traffic originates from the ZS itself. |
The QoS queues are associated with the output interface.
But in 1.0beta12, Zeroshell puts the tagging into the mangle table in the FORWARD chain within iptables. So traffic from the router itself is not tagged for QoS. Without the tagging the traffic will go into a default queue level at the interface.
I submitted a patch to Fulvio that moves that QoS tagging to the mangle POSTROUTING chain so that traffic from the router as well as user traffic from the LAN are properly tagged for QoS. (That wasn't actually the reason I made that change but it had that effect. The reason for my change was so that I could have QoS and network balancing at the same time). |
|
| Back to top |
|
 |
|