shaw discarding certain packets (applies to all shaw customers)

[stringbeans]

http://www.boingboing.net/2004/11/11...soring_in.html

[Tux]

holy fuck. that would explainwhy soulseek upload speeds are crap (3kb/s) and why its gonna take me another 12 days (!!!) to finish downloading NFSU2 from bittorrent!!! (1.5KB/s wtf!) heres something else i found that supports this affecting bit torrent: http://209.123.109.175/forum/remark,...shaw~mode=flat

[dSl-DuDe]

GOOO telus! :p

[Electroflux]

It's reasons like these that make me glad I made a habit of running stuff on nonstandard ports.

I've been getting great speeds on uhh. PUBLIC DOMAIN COOKBOOKS on emule and others. 120k combined speed just yesterday.

[Crazy Dave]

nothing to do with what ports you are using. It can help playing with them...

meh... need more sleep to explain it better.

[Lee]

lol makes sense. EVERYTHING on my Shaw recently has been slow..

[dapimpstress]

yay for me cuz im NOT a shaw customer.. *giggle*

[neoh]

I don't have a problem. :)
I route all my packets individualy through a very unique iptable setup.

[BrownThug]

iiiits telus time....

[Dr. Doom]

http://www.ellacoya.com/solutions/
^^^
That be what they're using apparently.

[BrownThug]

done.

[Kraig]

Holy shit... keep us posted on this then!

[galaxie]

wow.
My computer at home is soooooo fucking slow at times, but I thought that it could just be that my cable is split two ways. Definitely gonna talk to my mom about this and see if she wants to look into switching. What a bunch of crap!

[neoh]

erm, well.
your computer being slow has nothing to do with shaw dropping packets.

[BrownThug]

LOL poor n00bs :(

[Electroflux]

Originally Posted by neoh

I don't have a problem. :)
I route all my packets individualy through a very unique iptable setup.

I have no problem and a very plain and crappy ruleset!
I need to find some of the old ones I was using that blocked all sorts of malformed packets/port 0, limited ICMP rates/etc.

[neoh]

kind of like this? ;P

iptables --new ICMP 2>/dev/null
iptables -A INPUT --proto icmp -j ICMP
iptables -A ICMP -p icmp --icmp-type echo-reply -j ACCEPT
iptables -A ICMP -p icmp --icmp-type destination-unreachable -j LOG
iptables -A ICMP -p icmp --icmp-type network-unreachable -j LOG
iptables -A ICMP -p icmp --icmp-type host-unreachable -j LOG
iptables -A ICMP -p icmp --icmp-type protocol-unreachable -j LOG
iptables -A ICMP -p icmp --icmp-type port-unreachable -j ACCEPT
iptables -A ICMP -p icmp --icmp-type fragmentation-needed -j DROP
iptables -A ICMP -p icmp --icmp-type source-route-failed -j LOG
iptables -A ICMP -p icmp --icmp-type network-unknown -j LOG
iptables -A ICMP -p icmp --icmp-type host-unknown -j LOG
iptables -A ICMP -p icmp --icmp-type network-prohibited -j LOG
iptables -A ICMP -p icmp --icmp-type host-prohibited -j LOG
iptables -A ICMP -p icmp --icmp-type TOS-network-unreachable -j LOG
iptables -A ICMP -p icmp --icmp-type TOS-host-unreachable -j LOG
iptables -A ICMP -p icmp --icmp-type communication-prohibited -j LOG
iptables -A ICMP -p icmp --icmp-type host-precedence-violation -j DROP
iptables -A ICMP -p icmp --icmp-type precedence-cutoff -j DROP
iptables -A ICMP -p icmp --icmp-type source-quench -j DROP
iptables -A ICMP -p icmp --icmp-type redirect -j DROP
iptables -A ICMP -p icmp --icmp-type network-redirect -j DROP
iptables -A ICMP -p icmp --icmp-type host-redirect -j DROP
iptables -A ICMP -p icmp --icmp-type TOS-network-redirect -j DROP
iptables -A ICMP -p icmp --icmp-type TOS-host-redirect -j DROP
iptables -A ICMP -p icmp --icmp-type echo-request -j LOG
iptables -A ICMP -p icmp --icmp-type router-advertisement -j DROP
iptables -A ICMP -p icmp --icmp-type router-solicitation -j DROP
iptables -A ICMP -p icmp --icmp-type time-exceeded -j LOG
iptables -A ICMP -p icmp --icmp-type ttl-zero-during-transit -j LOG
iptables -A ICMP -p icmp --icmp-type ttl-zero-during-reassembly-j LOG
iptables -A ICMP -p icmp --icmp-type parameter-problem -j LOG
iptables -A ICMP -p icmp --icmp-type ip-header-bad -j LOG
iptables -A ICMP -p icmp --icmp-type required-option-missing -j LOG
iptables -A ICMP -p icmp --icmp-type timestamp-request -j DROP
iptables -A ICMP -p icmp --icmp-type timestamp-reply -j DROP
iptables -A ICMP -p icmp --icmp-type address-mask-request -j DROP
iptables -A ICMP -p icmp --icmp-type address-mask-reply -j DROP
iptables -A ICMP -p icmp -j DROP

[BrownThug]

nice one.

[Gusto]

Originally Posted by neoh

I don't have a problem. :)
I route all my packets individualy through a very unique iptable setup.

How would this make a difference? If a server is sending packets back to you on a certain port, and Shaw is dropping the packets at their routers, then they will never hit your iptables to be manipulated in any way. I think we've had this conversation before. :)

[neoh]

we have had this conversation, damn you!
and will continue to conversation on msn!

[Electroflux]

Perhaps if you set up a tunnel to a computer with an unrestricted connection, and had p2p running over this you might get away from the filtering being done.

[Gusto]

Originally Posted by Electroflux

Perhaps if you set up a tunnel to a computer with an unrestricted connection, and had p2p running over this you might get away from the filtering being done.

Yeah, that'd definately work, but you're duplicating bandwidth which is a little wasteful.

[neoh]

damn straight it's a waste of bandwidth. We've come to the conclusion that using nonstandard ports to send data (like p2p/bt) seems to be overlooked, as it just seems to go after specific ports which is probably the case. They can't monitor every packet going to every port and check headers to all their customers.

They are basically just trying to get more bandwidth for the dollar by elminiating 50% of the p2p packets being transfered through shaw's routers.

[Mr.Wrong]

you guys are confusing the shit outta me.
does this affect browsing the internet/ using p2ps like soulseek and kazaalite/ DLin off mirc

[Mr.Wrong]

fuckers