Page 7 of 7
Re: work units not sending. Also, idle not working properly
Posted: Mon Jun 02, 2014 7:52 am
by davidcoton
Two thoughts:
1) Is there any way to white-list certain IP addresses in the router? If so, can you identify and white-list the servers from which packets go missing?
2) Does the router have IP6 capabilities? Can you turn them off? There has been another report that having IP6 enabled has led to loss of IP4 routes to Stanford.
David
Re: work units not sending. Also, idle not working properly
Posted: Mon Jun 02, 2014 9:45 am
by Volnaiskra
I guess IP6 is already off:
I'm not sure about whitelists. Could you help me set it up? Do I put it on the inbound white list or outbound, or both?
Anyway, this is what the outbound page looks like:
And when I click the blue link for inbound firewall rules, it takes me here:
Re: work units not sending. Also, idle not working properly
Posted: Mon Jun 02, 2014 9:04 pm
by davidcoton
OK, well I'm not an expert on your router, but I can eliminate some things. It doesn't look like a port forwarding problem -- AFAIK that is for unsolicited incoming requests, not replies to your requests. I don't know for certain what Port Triggering is about -- BUT it has a default timeout of 20 min -- does that correspond to the time from the start of upload to when the final ack is due? I think it is saying that any dialogue that exceeds 20 mins will be blocked. So try increasing the port time-out to 30 mins, see if that fixes it. Or try ticking the box to disable. (There may be online help that explains this -- I may have misunderstood its purpose. If this doesn't help, st it back to enabled at 20 mins so we don't cause a problem elsewhere....
David
Re: work units not sending. Also, idle not working properly
Posted: Mon Jun 02, 2014 9:39 pm
by 7im
http://kb.netgear.com/app/answers/detai ... ggering%3F
"Port Triggering is an advanced feature that can be used for gaming and other Internet applications. It allows you to do port forwarding without setting a fixed PC."
Seems like you could disable this without issue.
Re: work units not sending. Also, idle not working properly
Posted: Mon Jun 02, 2014 10:45 pm
by davidcoton
So, maybe the default settings result in incoming acks being wrongly forwarded (or just lost) if they follow within 20 mins of another? Definitely try disabling it.
Thanks 7im for the search.
David
Re: work units not sending. Also, idle not working properly
Posted: Tue Jun 03, 2014 10:18 am
by Volnaiskra
davidcoton wrote:OK, well I'm not an expert on your router, but I can eliminate some things. It doesn't look like a port forwarding problem -- AFAIK that is for unsolicited incoming requests, not replies to your requests.
Is it possible that it's receiving replies from FAH that it mistakenly thinks are unsolicited?
Re: work units not sending. Also, idle not working properly
Posted: Tue Jun 03, 2014 10:43 am
by P5-133XL
It is possible. Normally, when an application sends out data NAT keeps track in a translation table so that any replies get routed back to the original application. The translation table only keeps the data for a relatively short interval but if something does reply then it is refreshed and continues refreshing till the interval expires and the connection is then closed. To my knowledge, there is no standard saying how long that entry has to remain and each router can choose it own minimum interval. If the entry is erased then the router will assume it is an unsolicited packet. Unsolicited blocked packets should be reported in your routers log.
That being said, the vast majority of routers do not have a problem erasing the entry prematurely.
Re: work units not sending. Also, idle not working properly
Posted: Tue Jun 03, 2014 11:27 am
by PantherX
Volnaiskra wrote:ok, well changing max-queue to 64 didn't do anything...
Reduce it to 5 and see what happens to see if the setting works or not.
Volnaiskra wrote:...Once the WUs reached exactly 10 (7 complete, 3 incomplete), FAH froze again, just like always. There were 10 work folders, from "00" to "09". I wonder if FAH has trouble correctly assigning new WU numbers above 09...
I do remember with 9 WUs (6 completed, 3 running), it worked fine. Thus, if you are certain of this issue, do provide the log file and a ticket will be opened if necessary.
Re: work units not sending. Also, idle not working properly
Posted: Thu Jun 05, 2014 9:36 am
by Volnaiskra
PantherX wrote:Volnaiskra wrote:...Once the WUs reached exactly 10 (7 complete, 3 incomplete), FAH froze again, just like always. There were 10 work folders, from "00" to "09". I wonder if FAH has trouble correctly assigning new WU numbers above 09...
I do remember with 9 WUs (6 completed, 3 running), it worked fine. Thus, if you are certain of this issue, do provide the log file and a ticket will be opened if necessary.
Ok, FAH has again frozen with exactly 10 work folders (00 to 09). That's the third time in a row. Here's my log file:
http://www.speedyshare.com/QxyMp/log.txt
PantherX wrote:Volnaiskra wrote:ok, well changing max-queue to 64 didn't do anything...
Reduce it to 5 and see what happens to see if the setting works or not.
I'll try that now
Re: work units not sending. Also, idle not working properly
Posted: Thu Jun 05, 2014 9:41 am
by Volnaiskra
P5-133XL wrote:It is possible. Normally, when an application sends out data NAT keeps track in a translation table so that any replies get routed back to the original application. The translation table only keeps the data for a relatively short interval but if something does reply then it is refreshed and continues refreshing till the interval expires and the connection is then closed. To my knowledge, there is no standard saying how long that entry has to remain and each router can choose it own minimum interval. If the entry is erased then the router will assume it is an unsolicited packet. Unsolicited blocked packets should be reported in your routers log.
That being said, the vast majority of routers do not have a problem erasing the entry prematurely.
What should I look for in the log (eg. which checkboxes should I check)? And should I post it here, so someone can make sense of it and see if there are unsolicited blocked packets?
Re: work units not sending. Also, idle not working properly
Posted: Fri Jun 06, 2014 2:57 am
by PantherX
Unfortunately, the link doesn't work for me. Can you please post it here within the Code Tags? If it is more that 6,000 characters, you split it up into multiple posts.
Re: work units not sending. Also, idle not working properly
Posted: Fri Jun 06, 2014 4:47 am
by bruce
PantherX wrote:...Can you please post it here within the Code Tags? If it is more that 6,000 characters, you split it up into multiple posts.
... and/or eliminate some messages which are repetitive and are unrelated to the problems
such as:
Code: Select all
02:59:24:WU01:FS01:0xa3:Completed 155000 out of 500000 steps (31%)
03:40:25:WU01:FS01:0xa3:Completed 160000 out of 500000 steps (32%)
04:33:57:WU01:FS01:0xa3:Completed 165000 out of 500000 steps (33%)
Re: work units not sending. Also, idle not working properly
Posted: Fri Jun 06, 2014 11:46 am
by Volnaiskra
PantherX wrote:
Unfortunately, the link doesn't work for me. Can you please post it here within the Code Tags? If it is more that 6,000 characters, you split it up into multiple posts.
It's 113k characters, so let me try another file-sharing service if you don't mind:
http://snk.to/f-cdniole5
Re: work units not sending. Also, idle not working properly
Posted: Sat Jun 07, 2014 12:26 am
by Volnaiskra
PantherX wrote:Volnaiskra wrote:ok, well changing max-queue to 64 didn't do anything...
Reduce it to 5 and see what happens to see if the setting works or not.
Yep, seems to do nothing, at least on this system. I changed it to 5, restarted PC and waited, and it's currently at 8 WU folders and still folding (there were only 4 initially).