cancel
Showing results for 
Search instead for 
Did you mean: 

IWF cache

bonzo888
Newbie
Posts: 1
Registered: 12-04-2012

IWF cache

I have a problem accessing various hosting sites,, gettin a  conection was reset error.
Plusnet said it was an IWF cache problem and would impliment a fix
fix done according to plusnetr but no difference made,
nothing about this problem is mentiones anywhere
what I would like to know is how I get someone at plusnet to find out what the problem actually is and to fix it.
11 REPLIES
Community Veteran
Posts: 4,979
Thanks: 376
Fixes: 16
Registered: 10-06-2010

Re: IWF cache

Problems accessing certain websites sometimes affects some plusnet gateways but not others, so you may be able to sidestep the problem by switching gateways (disconnect and reconnect from your router's web interface).
Can you give any examples of the inaccessible sites?
Community Veteran
Posts: 5,472
Thanks: 292
Fixes: 4
Registered: 11-08-2007

Re: IWF cache

It can also be a sign of having the MTU settings of your equipment being configured incorrectly.
cbcadmin
Grafter
Posts: 184
Thanks: 1
Registered: 14-02-2012

Re: IWF cache

I just got this note on my questions page. :-
"Needs adding to IWF cache update."
In response to "telnet postimage.org 80" working on some Plusnet connections but not others.
It appears to be working on all now, so looks as if someone has fixed it. Smiley
Keef - Sheerness Kent UK - Sky via Technicolor TG582N

Previously - EE, New Call Telecom/Fuelbroadband, Plusnet, Virgin/NTL/Bell Cable, Crosswinds, IC24, FreeOnlineNet, X-Stream, Totalise, Freeserve, Force9, TescoNet, AOL, Freenetname, Pipex, E7

===========
Community Veteran
Posts: 4,979
Thanks: 376
Fixes: 16
Registered: 10-06-2010

Re: IWF cache

Not on ptn-ag04!
traceroute -T -p 80 postimage.org
traceroute to postimage.org (46.229.160.181), 30 hops max, 60 byte packets
1  192.168.0.1 (192.168.0.1)  2.437 ms  9.575 ms  10.010 ms
2  lo0-central5.ptn-ag04.plus.net (195.166.130.83)  41.790 ms  44.974 ms  46.314 ms
3  84.93.253.83 (84.93.253.83)  28.085 ms  30.494 ms  31.551 ms
4  po4.ptn-gw01.plus.net (212.159.1.138)  33.888 ms  35.031 ms  37.374 ms
5  tun0.ptn-gw01.plus.net (212.159.2.101)  41.141 ms  42.084 ms  46.668 ms
6  vl69.ptw-gw02.plus.net (212.159.3.253)  47.087 ms  44.823 ms  39.379 ms
7  po4.ptn-gw01.plus.net (212.159.1.138)  40.923 ms  24.285 ms  23.841 ms
8  tun0.ptn-gw01.plus.net (212.159.2.101)  25.712 ms  24.039 ms  25.991 ms
9  vl69.ptw-gw02.plus.net (212.159.3.253)  24.668 ms  23.466 ms  23.268 ms
...
22  po4.ptn-gw01.plus.net (212.159.1.138)  29.332 ms  30.281 ms  29.910 ms
23  tun0.ptn-gw01.plus.net (212.159.2.101)  30.668 ms  30.727 ms  30.145 ms
24  vl69.ptw-gw02.plus.net (212.159.3.253)  30.019 ms  30.484 ms  29.902 ms
25  po4.ptn-gw01.plus.net (212.159.1.138)  28.467 ms  29.608 ms  30.045 ms
26  tun0.ptn-gw01.plus.net (212.159.2.101)  29.866 ms  30.164 ms  29.983 ms
27  vl69.ptw-gw02.plus.net (212.159.3.253)  30.419 ms  29.855 ms  29.134 ms
28  po4.ptn-gw01.plus.net (212.159.1.138)  30.333 ms  29.088 ms  29.377 ms
29  tun0.ptn-gw01.plus.net (212.159.2.101)  29.730 ms  47.780 ms  48.752 ms
30  vl69.ptw-gw02.plus.net (212.159.3.253)  30.328 ms  31.852 ms  30.710 ms

And fiddling with the MTU makes no difference.
Community Veteran
Posts: 19,099
Thanks: 434
Fixes: 21
Registered: 31-08-2007

Re: IWF cache

Quote from: purleigh
It can also be a sign of having the MTU settings of your equipment being configured incorrectly.

I think that the way you've said that may be misinterpreted. The whole network should be capable of working with a default MTU of 1500.
Community Veteran
Posts: 4,979
Thanks: 376
Fixes: 16
Registered: 10-06-2010

Re: IWF cache

Unfortunately you can't control every network between you and the destination, so you might have to work around things that both have a lower MTU and block automatic MTU detection.
Community Veteran
Posts: 19,099
Thanks: 434
Fixes: 21
Registered: 31-08-2007

Re: IWF cache

I think we should be careful not to take this thread off-topic, the other thread is more relevant for that (MTU) discussion.
kmilburn
Grafter
Posts: 902
Thanks: 2
Registered: 30-07-2007

Re: IWF cache

Quote from: ejs
 4  po4.ptn-gw01.plus.net (212.159.1.138)  33.888 ms  35.031 ms  37.374 ms
5  tun0.ptn-gw01.plus.net (212.159.2.101)  41.141 ms  42.084 ms  46.668 ms
6  vl69.ptw-gw02.plus.net (212.159.3.253)  47.087 ms  44.823 ms  39.379 ms
7  po4.ptn-gw01.plus.net (212.159.1.138)  40.923 ms  24.285 ms  23.841 ms
8  tun0.ptn-gw01.plus.net (212.159.2.101)  25.712 ms  24.039 ms  25.991 ms
9  vl69.ptw-gw02.plus.net (212.159.3.253)  24.668 ms  23.466 ms  23.268 ms
...

And fiddling with the MTU makes no difference.

Given the apparent routing loop between po4, tun0 and vl69,  the MTU is irrelivant.
VileReynard
Seasoned Pro
Posts: 10,676
Thanks: 211
Fixes: 9
Registered: 01-09-2007

Re: IWF cache

It works for me - but badly!
Quote
traceroute postimage.org
traceroute to postimage.org (213.174.142.28), 30 hops max, 60 byte packets
1  ROUTER (192.168.1.1)  1.902 ms  1.889 ms  17.254 ms
2  lo0-central7.pcl-ag03.plus.net (195.166.130.120)  33.924 ms  35.461 ms  35.455 ms
3  84.93.251.179 (84.93.251.179)  178.297 ms  178.293 ms  178.859 ms
4  tun0.pcl-gw01.plus.net (212.159.2.105)  178.852 ms  179.726 ms  179.717 ms
5  flowers2.servers.plus.net.uk (212.159.2.98)  50.795 ms  50.787 ms  52.157 ms
6  xe-11-1-0.edge3.London2.Level3.net (212.187.201.209)  66.755 ms  64.916 ms  65.480 ms
7  ae-0-11.edge4.London2.Level3.net (4.69.200.126)  42.667 ms  30.571 ms  31.337 ms
8  ae-3-3.ebr1.London1.Level3.net (4.69.141.189)  35.388 ms  35.384 ms  39.529 ms
9  ae-59-114.csw1.London1.Level3.net (4.69.153.126)  40.775 ms ae-58-113.csw1.London1.Level3.net (4.69.153.122)  42.694 ms ae-59-114.csw1.London1.Level3.net (4.69.153.126)  53.329 ms
10  ae-1-51.edge3.London1.Level3.net (4.69.139.73)  46.324 ms  49.383 ms  31.384 ms
11  IPTRIPLEPLA.edge3.London1.Level3.net (212.113.15.22)  31.826 ms  32.694 ms  32.687 ms
12  6-5.r0.101.dc5.eq.ash.va.us.iptp.net (91.194.117.159)  115.267 ms  114.898 ms *
13  ah.r0.101.eq.ash.va.us.iptp.net (98.158.98.254)  113.602 ms  112.417 ms  112.780 ms
14  213.174.142.28 (213.174.142.28)  113.336 ms  114.049 ms  113.768 ms

Community Veteran
Posts: 1,136
Thanks: 2
Registered: 30-07-2007

Re: IWF cache

I see the internal routing loop
root@ncc1701:~# tcptraceroute -p 80 postimage.org
traceroute to postimage.org (46.229.160.183), 30 hops max, 60 byte packets
1  skynet.avatastic.co.uk (10.0.1.1)  1.684 ms  1.014 ms  0.944 ms
2  lo0-central2.ptw-ag03.plus.net (195.166.128.48)  46.117 ms  27.400 ms  33.801 ms
3  gi1-16-321.ptw-gw01.plus.net (84.92.3.216)  37.765 ms  32.067 ms  50.790 ms
4  ae4.ptw-cr01.plus.net (195.166.129.36)  26.768 ms  43.103 ms  39.762 ms
5  te9-4.ptn-gw01.plus.net (195.166.129.33)  54.771 ms  35.146 ms  55.760 ms
6  tun0.ptn-gw01.plus.net (212.159.2.101)  39.636 ms  40.478 ms  28.789 ms
7  vl69.ptw-gw02.plus.net (212.159.3.253)  44.738 ms  41.626 ms  39.767 ms
8  po4.ptn-gw01.plus.net (212.159.1.138)  69.788 ms  24.958 ms  28.825 ms
9  tun0.ptn-gw01.plus.net (212.159.2.101)  40.751 ms  27.324 ms  53.667 ms
10  vl69.ptw-gw02.plus.net (212.159.3.253)  41.415 ms  62.607 ms  21.729 ms
11  po4.ptn-gw01.plus.net (212.159.1.138)  26.837 ms  48.425 ms  40.770 ms
12  tun0.ptn-gw01.plus.net (212.159.2.101)  26.802 ms  56.904 ms  22.951 ms
13  vl69.ptw-gw02.plus.net (212.159.3.253)  50.645 ms  23.377 ms  27.082 ms
14  po4.ptn-gw01.plus.net (212.159.1.138)  56.822 ms  29.249 ms  34.727 ms
15  tun0.ptn-gw01.plus.net (212.159.2.101)  27.801 ms  45.363 ms  25.815 ms
16  vl69.ptw-gw02.plus.net (212.159.3.253)  44.771 ms  25.273 ms  24.354 ms
17  po4.ptn-gw01.plus.net (212.159.1.138)  40.743 ms  22.309 ms  26.763 ms
18  tun0.ptn-gw01.plus.net (212.159.2.101)  55.784 ms  23.209 ms  25.783 ms
19  vl69.ptw-gw02.plus.net (212.159.3.253)  52.790 ms  26.258 ms  28.785 ms
20  po4.ptn-gw01.plus.net (212.159.1.138)  44.761 ms  28.503 ms  46.342 ms
21  tun0.ptn-gw01.plus.net (212.159.2.101)  32.079 ms  28.283 ms  68.780 ms
22  vl69.ptw-gw02.plus.net (212.159.3.253)  22.759 ms  25.089 ms  52.759 ms
23  po4.ptn-gw01.plus.net (212.159.1.138)  28.793 ms  56.935 ms  29.069 ms
24  tun0.ptn-gw01.plus.net (212.159.2.101)  28.778 ms  68.841 ms  25.788 ms
25  vl69.ptw-gw02.plus.net (212.159.3.253)  40.857 ms  28.467 ms  30.763 ms
26  po4.ptn-gw01.plus.net (212.159.1.138)  58.731 ms  26.285 ms  46.766 ms
27  tun0.ptn-gw01.plus.net (212.159.2.101)  98.290 ms  37.936 ms  36.654 ms
28  vl69.ptw-gw02.plus.net (212.159.3.253)  58.763 ms  43.100 ms  31.151 ms
29  po4.ptn-gw01.plus.net (212.159.1.138)  31.414 ms  27.471 ms  56.775 ms
30  tun0.ptn-gw01.plus.net (212.159.2.101)  28.801 ms  49.212 ms  29.757 ms
root@ncc1701:~#

via ptw-ag03
F9 member since 4 Sep 1999
F9 ADSL customer since 27 Aug 2004
DLM manages your line the same way DRM manages your rights.
Look at all the pretty graphs! (now with uptime logging!)
Community Gaffer
Community Gaffer
Posts: 13,006
Thanks: 792
Fixes: 70
Registered: 04-04-2007

Re: IWF cache

Quote from: Keeef
I just got this note on my questions page. :-
"Needs adding to IWF cache update."
In response to "telnet postimage.org 80" working on some Plusnet connections but not others.
It appears to be working on all now, so looks as if someone has fixed it. Smiley

It's not been fixed yet.

Bob Pullen
Plusnet Products Team
If I've been helpful then please give thanks ⤵