YouTube upload problems

[#1]

Hard to say without looking into it further. If you're able to leave your router on for a few days then I could get one of the faults guys here to do some digging?

[#2]

OK. Bearing in mind I have remote access disabled.

[#3]

Quote from: Razer

"interleaving ... only takes a day to remove again ... don't see any harm in trying": Hmm, my vague memory prevents me commenting specifically. ... but I'm going to be pretty [Censored] off if it impacts my already problematic gaming and if when I come to requesting it be removed again I get any of those problems my memory is currently vague about.

Great. Memory refreshed and it's as I feared. My connection has dropped twice in the last few minutes. Thanks to the interleaving being messed with my line has become erroneous and unstable.

[#4]

Quote from: Razer

OK. Bearing in mind I have remote access disabled.

That doesn't matter. It's the physical line itself that we'd be looking to test. It just needs to be in synch with the exchange.
Interleaving was off and your line was running in fast path mode. I switched it on. I switched it off on your request and it's now running in fast path mode again.
In summary, there's nothing supplier-side that's any different now to how it was before I applied interleaving.
Has the router been left on?

[#5]

On the face of it, nothing different. Correct. It's just funny how I have noted other members having problems with their connection when interleaving has been altered back and forth, and now I have too.
Yes, the router has been left on and will be left on.

[#6]

Thanks, I shall have somebody take a look.
Edit: There's a few disconnects on the line but it doesn't look particularly bad at present. Little/few errors at the time of testing. We've made a change on the Wholesale network to see if that helps and will monitor the line over the weekend/early next week. We'll run some more testing midweek.

[#7]

A few disconnects on the line - those occurring through the night to very early morning in the last couple of days were me gateway hopping. There were a few because I've been trying to leave it because you were supposed to be doing some testing and I wasn't sure if gateway hopping would interrupt some test that may have been going on at that moment. However, once you said I just need to leave the router synched, I hopped more readily. Over the last few days I have only noted three disconnections (including one resynch quoted below) that were not me. Other than that, my line doesn't drop as far as I can tell. You can check my connection chart (can't remember what you call it) and/or my data usage stats for the time I am active at the moment. If little/few errors has anything to do with any lack of activity from my end then cross referencing those stats will show it. This is the latest disconnection that wasn't me, so I assume it was either another instability drop or your testing:

Quote

Info Jul 26 13:15:21 FIREWALL event (1 of 1): deleted rules Warning Jul 26 13:15:20 PPP link up (Internet) [xx.xxx.xx.xxx] Info Jul 26 13:15:20 PPP CHAP Chap receive success : authentication ok Info Jul 26 13:15:20 PPP CHAP Receive challenge (rhost = PTN-AG03) Info Jul 26 13:15:19 PPP CHAP Receive challenge (rhost = bras-red7.gi-b) Info Jul 26 13:15:16 xDSL linestate up (ITU-T G.992.5; downstream: 22894 kbit/s, upstream: 1235 kbit/s; output Power Down: 20.7 dBm, Up: 12.4 dBm; line Attenuation Down: 17.0 dB, Up: 8.6 dB; snr Margin Down: 3.2 dB, Up: 6.6 dB) Info Jul 26 13:14:50 xDSL linestate down Info Jul 26 13:14:20 xDSL linestate down Info Jul 26 13:13:25 xDSL linestate down Warning Jul 26 13:13:02 PPP link down (Internet) [87.115.56.144] Info Jul 26 13:12:09 FIREWALL event (1 of 1): modified rules Info Jul 26 13:12:09 FIREWALL event (1 of 1): created rules Info Jul 26 13:12:09 xDSL linestate down

Over the weekend, early next week and mid-week. Hmm. That'll be Saturday, Sunday, Monday and Wednesday then.
Having already left my router on for several days I gotta say it Bob, can't help thinking this is just all part of the usual belief that 'it's the customer not leaving their router on so let's try and get him to leave it on' approach. I've already had plenty of debate and final acknowledgement that turning my router off and gateway hopping will have no effect upon my line functioning, so I hope that is not the real approach. Things have functioned for months the way I run it. Only got problems this month, as said, noted with YT uploads. I must say, however, that as I think about it, my gaming has been worse since this month over all, I just tried to adapt, thinking there was some other reason for it, so perhaps they are connected. It just went even more screwy when interleaving was turned on and it was impossible for me to adapt.

[#8]

YT uploads continue to be abortive and gaming is just diabolical (just like it was way back in January when I first started playing. If anything was done to my line/service to make gaming better when I first reported those problems can you check that and check if it has been reversed? I'm about ready to rip out my line and smash things up, frankly).

[#9]

We took interleaving off yeah?  Sounds like you've actually got a fault and it's those errors causing some of the problems.
Worth getting someone looking at it.

[#10]

Quote from: Razer

Having already left my router on for several days I gotta say it Bob, can't help thinking this is just all part of the usual belief that 'it's the customer not leaving their router on so let's try and get him to leave it on' approach.

Without the router being left on it makes remote testing very difficult (we can ascertain very little without the connection being in synch) and any drops whether instigated by yourself or otherwise muddy the waters when it comes to interpreting what's going on. I'm not saying you turning the router off is the cause of the problem.

Quote from: Razer

I've already had plenty of debate and final acknowledgement that turning my router off and gateway hopping will have no effect upon my line functioning, so I hope that is not the real approach.

Gateway hopping won't have an effect on your connection. Why are you doing it so frequently though? Our network has been very finely balanced of late so gateway hopping shouldn't have any noticeable impact on anything you're doing?

Quote from: Razer

YT uploads continue to be abortive and gaming is just diabolical (just like it was way back in January when I first started playing. If anything was done to my line/service to make gaming better when I first reported those problems can you check that and check if it has been reversed? I'm about ready to rip out my line and smash things up, frankly).

I wasn't party to the problems you reported back in January but if you've a link to a forum thread then I can check.

Quote from: Kelly

We took interleaving off yeah?  Sounds like you've actually got a fault and it's those errors causing some of the problems.

Interleaving was off to begin with. I applied and subsequently removed it. I've also arranged for your service to be placed on an elevated profile at our suppliers side so on paper your service is in a better place compared to what it was.

[#11]

Quote from: Kelly

We took interleaving off yeah?  Sounds like you've actually got a fault and it's those errors causing some of the problems. Worth getting someone looking at it.

Then it's been all this month because that's when I noticed things getting much worse. Gaming, as you know, has always been problematic for me, never being resolved.
Current router log:

Quote

Uptime: 3 days, 17:31:08 DSL Type: ITU-T G.992.5 Bandwidth (Up/Down) [kbps/kbps]: 1.235 / 22.894 Data Transferred (Sent/Received) [MB/MB]: 544,59 / 971,01 Output Power (Up/Down) [dBm]: 12,4 / 0,0 Line Attenuation (Up/Down) [dB]: 8,6 / 17,0 SN Margin (Up/Down) [dB]: 6,0 / 3,8 System Vendor ID (Local/Remote): TMMB / ---- Chipset Vendor ID (Local/Remote): BDCM / IFTN Loss of Framing (Local/Remote): 8 / 0 Loss of Signal (Local/Remote): 1 / 0 Loss of Power (Local/Remote): 0 / 0 Loss of Link (Remote): - Error Seconds (Local/Remote): 2.823 / 0 FEC Errors (Up/Down): 0 / 0 CRC Errors (Up/Down): 2 / 3.515 HEC Errors (Up/Down): 1 / 39.474

@ Bob. Thanks for your response, as usual.
I gateway hop because it usually (temporarily) helps with my gaming issues. I have been doing this since early this year when I first brought up issues with gaming. I am heavily hopping at the moment because the issues are massively increased, since this month, but especially since interleaving was turned on. They in fact became utterly ridiculous since then. The problem with YT occurred this month and at the same time I noticed an increase in problems with my game, but there have always been problems with it generally and with the upload aspect of speed tests. This is mentioned in my main thread opened in January here, from which I was just left hanging. As a result I have just tried to get on and manage with my gaming issues, coping by gateway hopping/switching my router settings off and on as mentioned in that thread whenever I got the errors appearing in my router log. There is some cross-referencing here.
I don't know how far back you can look over my connection history, but I can tell you that most of the disconnect/reconnects you may be able to see since about early in the year are done by me to gateway hop to temporarily cure the gaming problem. Where you see few d/r I am not gaming.
On paper my service may well be in a better place, but practically it is the worst it's ever been in terms of gaming (despite trying another push to get it sorted with this) and YT uploads.
Some recent examples of errors in router that cause me to switch settings and gateway hop. These are limited examples, from some of the time on some of the days only, of the same kind as mentioned in my original thread from January, only much worse.
Play for a bit, taking ages to get into a game and then when I do, play with terrible lag, until:

Quote

Error Jul 27 08:07:27 FIREWALL replay check (1 of 2): Protocol: ICMP Src ip: 216.240.146.139 Dst ip: 146.90.104.227 Type: Destination Unreachable Code: Port Unreacheable Error Jul 27 08:05:27 FIREWALL replay check (1 of 2): Protocol: ICMP Src ip: 216.240.146.139 Dst ip: 146.90.104.227 Type: Destination Unreachable Code: Port Unreacheable Error Jul 27 08:03:27 FIREWALL replay check (1 of 2): Protocol: ICMP Src ip: 216.240.146.139 Dst ip: 146.90.104.227 Type: Destination Unreachable Code: Port Unreacheable Error Jul 27 08:01:27 FIREWALL replay check (1 of 6): Protocol: ICMP Src ip: 216.240.146.139 Dst ip: 146.90.104.227 Type: Destination Unreachable Code: Port Unreacheable Error Jul 27 07:59:26 FIREWALL replay check (1 of 2): Protocol: ICMP Src ip: 216.240.146.139 Dst ip: 146.90.104.227 Type: Destination Unreachable Code: Port Unreacheable Error Jul 27 07:57:26 FIREWALL replay check (1 of 2): Protocol: ICMP Src ip: 216.240.146.139 Dst ip: 146.90.104.227 Type: Destination Unreachable Code: Port Unreacheable Error Jul 27 07:55:23 FIREWALL replay check (1 of 2): Protocol: ICMP Src ip: 216.240.146.139 Dst ip: 146.90.104.227 Type: Destination Unreachable Code: Port Unreacheable Error Jul 27 07:53:22 FIREWALL replay check (1 of 1): Protocol: ICMP Src ip: 216.240.146.139 Dst ip: 146.90.104.227 Type: Destination Unreachable Code: Port Unreacheable Error Jul 27 07:52:22 FIREWALL replay check (1 of 2): Protocol: ICMP Src ip: 216.240.146.139 Dst ip: 146.90.104.227 Type: Destination Unreachable Code: Port Unreacheable Error Jul 27 07:50:22 FIREWALL replay check (1 of 2): Protocol: ICMP Src ip: 216.240.146.139 Dst ip: 146.90.104.227 Type: Destination Unreachable Code: Port Unreacheable Error Jul 27 07:48:22 FIREWALL replay check (1 of 2): Protocol: ICMP Src ip: 216.240.146.139 Dst ip: 146.90.104.227 Type: Destination Unreachable Code: Port Unreacheable Error Jul 27 07:46:22 FIREWALL replay check (1 of 2): Protocol: ICMP Src ip: 216.240.146.139 Dst ip: 146.90.104.227 Type: Destination Unreachable Code: Port Unreacheable

So I gateway hop/switch router settings and play for a bit more, taking ages to get into a game and when I do, play with terrible lag.
Another day, play for a bit, taking ages to get into a game and when I do, play with terrible lag, until:

Quote

Error Jul 29 13:55:37 FIREWALL replay check (1 of 2): Protocol: ICMP Src ip: 216.240.146.139 Dst ip: 146.90.55.254 Type: Destination Unreachable Code: Port Unreacheable Error Jul 29 13:53:37 FIREWALL replay check (1 of 2): Protocol: ICMP Src ip: 216.240.146.139 Dst ip: 146.90.55.254 Type: Destination Unreachable Code: Port Unreacheable Error Jul 29 13:51:37 FIREWALL replay check (1 of 2): Protocol: ICMP Src ip: 216.240.146.139 Dst ip: 146.90.55.254 Type: Destination Unreachable Code: Port Unreacheable Error Jul 29 13:49:37 FIREWALL replay check (1 of 1): Protocol: ICMP Src ip: 216.240.146.139 Dst ip: 146.90.55.254 Type: Destination Unreachable Code: Port Unreacheable Error Jul 29 13:48:37 FIREWALL replay check (1 of 2): Protocol: ICMP Src ip: 216.240.146.139 Dst ip: 146.90.55.254 Type: Destination Unreachable Code: Port Unreacheable Error Jul 29 13:46:37 FIREWALL replay check (1 of 1): Protocol: ICMP Src ip: 216.240.146.139 Dst ip: 146.90.55.254 Type: Destination Unreachable Code: Port Unreacheable Error Jul 29 13:45:08 FIREWALL replay check (1 of 2): Protocol: ICMP Src ip: 216.240.146.139 Dst ip: 146.90.55.254 Type: Destination Unreachable Code: Port Unreacheable Error Jul 29 13:43:08 FIREWALL replay check (1 of 2): Protocol: ICMP Src ip: 216.240.146.139 Dst ip: 146.90.55.254 Type: Destination Unreachable Code: Port Unreacheable Error Jul 29 13:41:08 FIREWALL replay check (1 of 2): Protocol: ICMP Src ip: 216.240.146.139 Dst ip: 146.90.55.254 Type: Destination Unreachable Code: Port Unreacheable

Gateway hop/switch settings, play for a bit, taking ages to get into a game and when I do, play with terrible lag, until:

Quote

Error Jul 29 15:05:50 FIREWALL replay check (1 of 6): Protocol: ICMP Src ip: 216.240.146.139 Dst ip: 91.125.81.227 Type: Destination Unreachable Code: Port Unreacheable Error Jul 29 15:03:50 FIREWALL replay check (1 of 1): Protocol: ICMP Src ip: 216.240.146.139 Dst ip: 91.125.81.227 Type: Destination Unreachable Code: Port Unreacheable Error Jul 29 14:58:47 FIREWALL replay check (1 of 1): Protocol: ICMP Src ip: 216.240.146.139 Dst ip: 91.125.81.227 Type: Destination Unreachable Code: Port Unreacheable Error Jul 29 14:44:33 FIREWALL replay check (1 of 9): Protocol: ICMP Src ip: 216.240.146.139 Dst ip: 91.125.81.227 Type: Destination Unreachable Code: Port Unreacheable

And so on. Ad infinitum, ad nauseam.

[#12]

ICMP traffic from a dedicated (gaming?) server to your WAN IP address and the router's blocking it. Problem is, those logs aren't very verbose so it's anyone's guess as to why it's happening
Your router typically allows PING requests because I've just checked and had replies from it.

[#13]

Yeah, only when I enable ping (during gaming, and I was gaming when you pinged). Anyway, yes, I thought it was my router blocking it (yes, 216 ip is the game server) - even though I have ports forwarded and/or gaming mode enabled. Even get them if I 'disable' the firewall. Every router I've had from PN (all those whistlers) did the same.
EDIT:
Continuing to be seriously bugged by this.

Quote from: Bob

Problem is, those logs aren't very verbose so it's anyone's guess as to why it's happening

Yet again nobody, PN staff significantly included, knows exactly what the PN router log entries actually mean and so don't know exactly what to do to 'fix' them. I wish PN would make the effort to liaise with the maker to get some facts about these things and perhaps go to the effort of upgrading the firmware to make these things clear instead of tinkering with the firmware for other, less important things. That said, at least a thank-you to you for confirming what I have always suspected about those ICMP messages, that it IS the router blocking things. Perhaps PN should also go to the effort of taking that up with the maker, too, and maybe come to supplying a better router that actually does the job it's supposed to do. After having several routers from PN that all do the same (albeit at the moment it's worse than for a while), I can only conclude that all PN routers are faulty. I don't know, however, if the router is responsible for all these other errors on my 'line'. Any conclusions about those yet, Bob?

[#14]

I think all those logged ICMP destination unreachable packets are a symptom of some other problem, and not the problem in itself. Since you shouldn't receive any of them, I don't think it matters whether those ICMP packets get blocked or not.

[#15]

So you toggle the setting to enable/disable PING response on the WAN interface? Along with the gateway hopping that's something else I struggle to see the point in if I'm honest
Anyway, I concur with what ejs says. You're jumping to conclusions and assuming that the ICMP router entries are the cause of your problem. I very much doubt they are. We've thousands of people who use our router for gaming without any problems at all. Don't get me wrong, replacing the router with a third party model may resolve some of your problems (which is why I've suggested it) but there's practically zero chance you've been supplied with multiple faulty routers. Why not pick up a cheap router on eBay to help prove/disprove the theory? You can probably get one for peanuts.
We were waiting to see if the line elevation helped, which it doesn't seem to have. I'll get somebody to check again but if we don't see the errors (we didn't last time) then we may have to rethink the approach. Would be good to actually check your line whilst you're having the problem and whilst you're gaming. Is there ever an occasion when you're gaming during the working day and have problems?