Page 3 of 4
Posted: Mon Oct 21, 2013 9:53 am
esher wrote:so... is my emule client (office internet connection) banning my NL client (home internet connection) for 2 hours every morning?
It should not,
Neo should not change the hash if the off time was < 6 hours.
You should see in your eMule th euserhash of the NeoClient and see if it changes to often.
Posted: Mon Oct 21, 2013 10:22 am
i cannot find a way to make these clients connect, neither restarting emule side is helping. manual adding emule client as source produces nothing on both sides. no ban no rejection no connection at all. i'll try tonight. ty bye!
Posted: Mon Oct 21, 2013 5:36 pm
Tray using one of the static hash options.
Posted: Sat Oct 26, 2013 9:08 am
the random hash bug (random hash being set on each reatsrt and not only after >6h delay will be fixed in next release), i'm sorry for the inconvinience.
Posted: Sun Nov 03, 2013 9:45 pm
It is correct the ":ByteArray:"
string before real SUI String?
Posted: Sun Nov 03, 2013 10:39 pm
abel wrote:It is correct the ":ByteArray:" string before real SUI String?
Yes, :ByteArray: specifyed the encoding of the data fiels
Posted: Sat Nov 16, 2013 8:46 pm
can you overwrite the "Secure Hash" string with "Secure Static Hash" ? (same scheme already used for "Random Hash" and "Secure Random Hash")
Posted: Sat Nov 16, 2013 8:52 pm
ok, done on next release
Posted: Sat Nov 16, 2013 9:14 pm
Did esher solved his problem? I think there are no benefits using this feature (random sui hash) and I think we should discuss again about the default choice.
Posted: Sat Nov 16, 2013 9:25 pm
only for clearness, this is the summary for "Client Trackability" slider in the wizard:
Low (Minimized) = Secure Random Hash, No Torrent Trackers
Medium = Secure Random Hash, Torrent Trackers
High (Unrestricted) = Secure Static Hash, Torrent Trackers