All hell has broken loose on our network: I've got clients from all over phoning, wanting to know why their torrents have stopped working.

Since I installed 3.28 their uTorrent simply doesn't work anymore.

Is there a setting somewhere that I need to set to get them going again?

Did you put any p2p filters? I have alredy upgraded a bunch of routers and everything seems to be working very very well.

Nothing at all.

One of the reasons our clients love us is because they can do what they want with the bandwidth they buy. Nothing gets shaped or filtered.

Could be a million things. I suggest you give me winbox access to have a look-see. Skype: hypnologic

Eben, I'm using Free Download Manager that uses a built in torrent client and my downloads are fine on a RB532 running 3.28.

Hilton,

I need to get to the bottom of this...the TD5 needs a new thermostat fitted and it's a horrible job

Here are the basics of my network:

P4 with 1GB RAM and a 256MB CF card running ROS ver 3.28
ether1 - L2TP via ADSL to XDSL - Public IP
ether2 - IS uncapped fibre ADSL - Public IP
ether3 - IS uncapped satellite ADSL - Public IP
ether4 - Cisco 1601 - Telkom Diginet - Public IP
ether5 - RB433AH

RB433AH
ether1 - P4
ether2 - 8 port 3Com fibre switch - fibre optic network running to an estate with +/- 800 houses
ether3 - our office network
wlan1 - R5H backbone link to high site 1
wlan2 - R52H with 20dBi panel for local wireless
wlan3 - backbone link to high site 2

From there it spreads to cover everything from Gordon's Bay to the West Coast.

Torrents worked just fine on 3.27 but they just won't work on 3.28

I suspect it has something to do with NAT.

我在做“正确的”设备g, so an RB411 with IP address 192.168.89.250 in West beach can ping a NS5 with IP address 192.168.65.50 in Gordon's Bay (in less than 3ms).

All the NAT is done on the P4.

Update.

I've been working on and off on this during the day, trying various NAT solutions, but nothing wanted to work.

Eventually I got so frustrated that I switched the main machine off, let it sit for a couple of minutes and powered it back up.

Problem gone.

There's no rhyme nor reason for this.

So it was a hardware issue that affected the p2p traffic and not the other traffic ? hmmmvery very strange. You know, maybe it was caused bay the ghost of Elvis

This could be the 3.28 routes not working problem. I could check it for you if you are unable to pinpoint it.