• February 24, 2025, 06:02:22 AM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: DNS 320 HW b1->P2P Problem!  (Read 14679 times)

freeman74

  • Level 2 Member
  • **
  • Posts: 34
DNS 320 HW b1->P2P Problem!
« on: July 10, 2013, 07:40:52 AM »
Hi all,

i bought the DNS320 last week because i need a Bittorrent server 24hours active. MMMH... i'm thinking that this was a very bad idea...  ::) ::)

When i put in download some torrent (2 or 3 simoultaneous), randomly the p2p server crashes... the cpu is busy at 100%, i have verified that the p2p process is the problem.

In this situation (always), i have to reboot the nas to restore the normal p2p activity. I've tried to download a new firmware release but for B1 HW release i don't find any update!

Someone can help me?

thank you in advance
Freeman
Logged

albert

  • Level 5 Member
  • *****
  • Posts: 510
    • SoHo NAS Forum
Re: DNS 320 HW b1->P2P Problem!
« Reply #1 on: July 11, 2013, 08:47:48 AM »
What's your current firmware version?

AFAIK, the latest for h/w B1 should be 1.01b02.
Logged
D-Link DNS-320 rev A1 (FW: 2.05) [FFP-0.7]
PCI NAS-01G (FW: Encore ENNHD-1000 4.10)
PCI NAS-01G (FW: OpenNAS 1.9]

freeman74

  • Level 2 Member
  • **
  • Posts: 34
Re: DNS 320 HW b1->P2P Problem!
« Reply #2 on: July 11, 2013, 01:40:15 PM »
Quote from: albert on July 11, 2013, 08:47:48 AM
What's your current firmware version?

AFAIK, the latest for h/w B1 should be 1.01b02.

1.00, where can i find the latest version?

thx
Logged

albert

  • Level 5 Member
  • *****
  • Posts: 510
    • SoHo NAS Forum
Re: DNS 320 HW b1->P2P Problem!
« Reply #3 on: July 11, 2013, 08:50:04 PM »
Quote from: freeman74 on July 11, 2013, 01:40:15 PM
1.00, where can i find the latest version?

thx


PM for the URL as it's not allow to post "unofficial" firmware link here.
Logged
D-Link DNS-320 rev A1 (FW: 2.05) [FFP-0.7]
PCI NAS-01G (FW: Encore ENNHD-1000 4.10)
PCI NAS-01G (FW: OpenNAS 1.9]

freeman74

  • Level 2 Member
  • **
  • Posts: 34
Re: DNS 320 HW b1->P2P Problem!
« Reply #4 on: July 12, 2013, 02:30:35 PM »
Quote from: albert on July 11, 2013, 08:50:04 PM
PM for the URL as it's not allow to post "unofficial" firmware link here.

I've just updated the firmware (thank you Albert!), unfortunely the p2p problem is the same...

How many ways for factory i can do? I tried with the procedure explained within the manual without success.

Logged

albert

  • Level 5 Member
  • *****
  • Posts: 510
    • SoHo NAS Forum
Re: DNS 320 HW b1->P2P Problem!
« Reply #5 on: July 12, 2013, 10:43:10 PM »
Quote from: freeman74 on July 12, 2013, 02:30:35 PM
I've just updated the firmware (thank you Albert!), unfortunely the p2p problem is the same...

How many ways for factory i can do? I tried with the procedure explained within the manual without success.



If problem still persist after upgrading firmware, it probably there are no changes made to the P2P client in the new firmware release.

My personal advice is to switch to alternative BT client like Transmission, it save you a lot of headache and is widely used even for private site.
Logged
D-Link DNS-320 rev A1 (FW: 2.05) [FFP-0.7]
PCI NAS-01G (FW: Encore ENNHD-1000 4.10)
PCI NAS-01G (FW: OpenNAS 1.9]

freeman74

  • Level 2 Member
  • **
  • Posts: 34
Re: DNS 320 HW b1->P2P Problem!
« Reply #6 on: July 13, 2013, 12:55:02 AM »
Quote from: albert on July 12, 2013, 10:43:10 PM
If problem still persist after upgrading firmware, it probably there are no changes made to the P2P client in the new firmware release.

My personal advice is to switch to alternative BT client like Transmission, it save you a lot of headache and is widely used even for private site.

i've already installed Transmission client on my nas, but the results are the same. The CPU 100% and the downloads still blocked.

I've a strange problem in transmission.daemon.log (please see below a little part of it), when i start the transmission service, the log file grows until i stop the service. The crypto error repeats...

[23:50:44.890] Transmission 2.80 (14103) started (session.c:737)
[23:50:44.890] RPC Server Adding address to whitelist: 127.0.0.1 (rpc-server.c:828)
[23:50:44.890] RPC Server Adding address to whitelist: 192.168.*.* (rpc-server.c:828)
[23:50:44.891] RPC Server Serving RPC and Web requests on port 127.0.0.1:9091/transmission/ (rpc-server.c:1035)
[23:50:44.891] RPC Server Whitelist enabled (rpc-server.c:1039)
[23:50:44.891] RPC Server Password required (rpc-server.c:1042)
[23:50:44.891] DHT Generating new id (tr-dht.c:310)
[23:50:44.891] tr_crypto error:00000000:lib(0):func(0):reason(0) (crypto.c:342)
[23:50:44.891] tr_crypto error:00000000:lib(0):func(0):reason(0) (crypto.c:342)
[23:50:44.892] Using settings from "/mnt/HD/HD_a2/.transmission-daemon" (daemon.c:526)
[23:50:44.892] Saved "/mnt/HD/HD_a2/.transmission-daemon/settings.json" (variant.c:1217)
[23:50:44.892] transmission-daemon requiring authentication (daemon.c:546)
[23:50:44.892] Loaded 2 torrents (session.c:1976)
[23:50:44.892] Port Forwarding (NAT-PMP) initnatpmp succeeded (0) (natpmp.c:73)
[23:50:44.892] Port Forwarding (NAT-PMP) sendpublicaddressrequest succeeded (2) (natpmp.c:73)
[23:50:52.970] Port Forwarding Starting (port-forwarding.c:95)
[23:50:52.970] tr_crypto error:24064064:lib(36):func(100):reason(100) (crypto.c:115)
[23:50:52.970] tr_crypto error:24064064:lib(36):func(100):reason(100) (crypto.c:115)
[23:50:52.971] tr_crypto error:24064064:lib(36):func(100):reason(100) (crypto.c:115)
[23:50:52.971] tr_crypto error:24064064:lib(36):func(100):reason(100) (crypto.c:115)
[23:50:52.971] tr_crypto error:24064064:lib(36):func(100):reason(100) (crypto.c:115)
[23:50:52.971] tr_crypto error:24064064:lib(36):func(100):reason(100) (crypto.c:115)
[23:50:52.971] tr_crypto error:24064064:lib(36):func(100):reason(100) (crypto.c:115)
[23:50:52.971] tr_crypto error:24064064:lib(36):func(100):reason(100) (crypto.c:115)
[23:50:52.972] tr_crypto error:24064064:lib(36):func(100):reason(100) (crypto.c:115)
[23:50:52.972] tr_crypto error:24064064:lib(36):func(100):reason(100) (crypto.c:115)
[23:50:52.972] tr_crypto error:24064064:lib(36):func(100):reason(100) (crypto.c:115)
[23:50:52.972] tr_crypto error:24064064:lib(36):func(100):reason(100) (crypto.c:115)
[23:50:52.972] tr_crypto error:24064064:lib(36):func(100):reason(100) (crypto.c:115)
[23:50:52.972] tr_crypto error:24064064:lib(36):func(100):reason(100) (crypto.c:115)
[23:50:52.973] tr_crypto error:24064064:lib(36):func(100):reason(100) (crypto.c:115)
[23:50:52.973] tr_crypto error:24064064:lib(36):func(100):reason(100) (crypto.c:115)
[23:50:52.973] tr_crypto error:24064064:lib(36):func(100):reason(100) (crypto.c:115)
[23:50:52.973] tr_crypto error:24064064:lib(36):func(100):reason(100) (crypto.c:115)
[23:50:52.973] tr_crypto error:24064064:lib(36):func(100):reason(100) (crypto.c:115)
[23:50:52.973] tr_crypto error:24064064:lib(36):func(100):reason(100) (crypto.c:115)
[23:50:52.974] tr_crypto error:24064064:lib(36):func(100):reason(100) (crypto.c:115)
[23:50:52.974] tr_crypto error:24064064:lib(36):func(100):reason(100) (crypto.c:115)
[23:50:52.974] tr_crypto error:24064064:lib(36):func(100):reason(100) (crypto.c:115)
[23:50:52.974] tr_crypto error:24064064:lib(36):func(100):reason(100) (crypto.c:115)
[23:50:52.974] tr_crypto error:24064064:lib(36):func(100):reason(100) (crypto.c:115)
[23:50:52.974] tr_crypto error:24064064:lib(36):func(100):reason(100) (crypto.c:115)
[23:50:52.974] tr_crypto error:24064064:lib(36):func(100):reason(100) (crypto.c:115)
[23:50:52.975] tr_crypto error:24064064:lib(36):func(100):reason(100) (crypto.c:115)
[23:50:52.975] tr_crypto error:24064064:lib(36):func(100):reason(100) (crypto.c:115)
[23:50:52.975] tr_crypto error:24064064:lib(36):func(100):reason(100) (crypto.c:115)
[23:50:52.975] tr_crypto error:24064064:lib(36):func(100):reason(100) (crypto.c:115)
[23:50:52.975] tr_crypto error:24064064:lib(36):func(100):reason(100) (crypto.c:115)
[23:50:52.975] tr_crypto error:24064064:lib(36):func(100):reason(100) (crypto.c:115)
[23:50:52.976] tr_crypto error:24064064:lib(36):func(100):reason(100) (crypto.c:115)
[23:50:52.976] tr_crypto error:24064064:lib(36):func(100):reason(100) 
Logged

albert

  • Level 5 Member
  • *****
  • Posts: 510
    • SoHo NAS Forum
Re: DNS 320 HW b1->P2P Problem!
« Reply #7 on: July 13, 2013, 03:31:52 AM »
There is a known problem with DNS-320L, didn't expect this to occur with DNS-320 h/w B revision. Off hand I can't recall the workaround, will post the solution later.
Logged
D-Link DNS-320 rev A1 (FW: 2.05) [FFP-0.7]
PCI NAS-01G (FW: Encore ENNHD-1000 4.10)
PCI NAS-01G (FW: OpenNAS 1.9]

freeman74

  • Level 2 Member
  • **
  • Posts: 34
Re: DNS 320 HW b1->P2P Problem!
« Reply #8 on: July 13, 2013, 07:27:43 AM »
Quote from: albert on July 13, 2013, 03:31:52 AM
There is a known problem with DNS-320L, didn't expect this to occur with DNS-320 h/w B revision. Off hand I can't recall the workaround, will post the solution later.

This one?

http://forums.hardwarezone.com.sg/storage-clinic-119/d-link-dns-320l-3996991-9.html
Logged

albert

  • Level 5 Member
  • *****
  • Posts: 510
    • SoHo NAS Forum
Re: DNS 320 HW b1->P2P Problem!
« Reply #9 on: July 13, 2013, 10:20:51 AM »
Yes, this seem to be the one, I can't confirm at my end as mine is DNS-320 h/w rev A.
Logged
D-Link DNS-320 rev A1 (FW: 2.05) [FFP-0.7]
PCI NAS-01G (FW: Encore ENNHD-1000 4.10)
PCI NAS-01G (FW: OpenNAS 1.9]

freeman74

  • Level 2 Member
  • **
  • Posts: 34
Re: DNS 320 HW b1->P2P Problem!
« Reply #10 on: July 15, 2013, 01:29:23 AM »
Quote from: albert on July 13, 2013, 10:20:51 AM
Yes, this seem to be the one, I can't confirm at my end as mine is DNS-320 h/w rev A.

ok, all works fine. Transmission still running up to 48h without problems. The log file is empty of crypto errors. I've applied the change reported within your post.

i don't know if it's a coincidence, but also the p2p application now works fine. the cpu charge is normal and the download proceeds without freezing.   :o

Anyway thank you Albert for your support.

Freeman
Logged

tarta1974

  • Level 1 Member
  • *
  • Posts: 1
Re: DNS 320 HW b1->P2P Problem!
« Reply #11 on: July 24, 2013, 02:54:46 AM »
Hi all!
I've some problem with my nas dns320 rev b1 (firmware 1.00)
I would try to install new unofficial 1.01 firmware.
@ Albert and Freeman74: I've sent you a pm, I hope you can help me!
thanks in advance!


Logged

albert

  • Level 5 Member
  • *****
  • Posts: 510
    • SoHo NAS Forum
Re: DNS 320 HW b1->P2P Problem!
« Reply #12 on: July 24, 2013, 10:28:08 PM »
Quote from: tarta1974 on July 24, 2013, 02:54:46 AM
Hi all!
I've some problem with my nas dns320 rev b1 (firmware 1.00)
I would try to install new unofficial 1.01 firmware.
@ Albert and Freeman74: I've sent you a pm, I hope you can help me!
thanks in advance!

Check your PM.
Logged
D-Link DNS-320 rev A1 (FW: 2.05) [FFP-0.7]
PCI NAS-01G (FW: Encore ENNHD-1000 4.10)
PCI NAS-01G (FW: OpenNAS 1.9]

DarkDefender

  • Level 1 Member
  • *
  • Posts: 2
Re: DNS 320 HW b1->P2P Problem!
« Reply #13 on: August 07, 2013, 12:58:08 AM »
Hi, I'm a new user of a DNS-320_B1_HW and my P2P torrent crashes.

I read all this theme but I dont now how to solve it.

I have installed DNS-320_B1_FW.1.00b03 from de Taiwan link, but dont solve the problem.

I read this: 'http://forums.hardwarezone.com.sg/storage-clinic-119/d-link-dns-320l-3996991-9.html', but I dont now how to edit these files. I now that are Linux files, but I dont now how enter de NAS and edit them. I'm a W7 user.

And the last one, do you recommend me to install Transmission?
« Last Edit: August 07, 2013, 01:01:11 AM by DarkDefender »
Logged
Sorry for my English but I'm not English speaker