<div dir="ltr"><div class="gmail_quote">2011/7/3 Arie Skliarouk <span dir="ltr"><<a href="mailto:skliarie@gmail.com">skliarie@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi,<div class="im"><br><br>On Sun, Jul 3, 2011 at 08:02, shimi <span dir="ltr"><<a href="mailto:linux-il@shimi.net" target="_blank">linux-il@shimi.net</a>></span>
wrote:<br><blockquote style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex" class="gmail_quote">If you want, prior to calling them, to combat them with their own
weapon, thankfully there's a UDP protocol that probably no ISP would
want to degrade; Try switching to port 53 :-)<br></blockquote><br></div>I think that would not work as I observe frequent name server errors at exactly same periods (I am using Google's free DNS servers 8.8.8.8 and 8.8.4.4). Hmm, need to switch to the local DNS servers...<br>
<br clear="all"><br></blockquote><div><br>If that's the case, it wouldn't, probably. If your ISP does not provide you with the ability to use the yellowpages of the Internet, I would have switched an ISP _yesterday_... (but would have tried to call them and ask them to rectify the problem first, as everybody deserves a chance... maybe they just "got it wrong"...). <br>
<br>If they don't solve the problem and that causes you to switch an ISP, I would also complain to the MOC. As a general rule, I would record such phone calls, and trick the other side to admit that they're messing with your traffic... sometimes they would decline that they're "delibaretly stopping/dropping traffic", but would admit that "we prioritize HTTP for better service", which implies the former, obviously, as this is a zero-sum game.<br>
<br>Of course, you can go Geoffrey's way, and use VPN over port 80 (probably what they favor their traffic for), affecting your performance, security (no hidden VPN server anymore...), etc, and wait until the next thing your ISP fights you, _their customer_, with. OK, try 443 first, as this is less likely to be messed up by Deep Packet Inspection machines on the way, and Transparent HTTP Proxies. However, it might be that only 80 is favored in their QoS box... as I have seen a few years ago in the ISP I'm using...<br>
<br>-- Shimi<br></div></div><br></div>