Problems with Bitcomet

[pietronik]

Hi,
I'm Italian, so I'm sorry for my bad English.
I'm a new user of Look'n'stop and I found it really great!
I use Bitcomet as P2P client and I've configurated it but I can't connect to DHT network. I think that LnS close a port necessary to connect with DHT.
Can somebody Help me, please!
Thanks

[Frederic]

Hi,

I suppose BitComet is a BitTorrent client. If this is the case then you can import some rules from the following import file:
http://www.looknstop.com/En/rules/rules.htm#BitTorrent

Regards,

Frederic

[pietronik]

I've already imported that rule but DHT network don't work!

[Frederic]

What is DHT ? (sorry for my ignorance ??? )

Do you have some alerts in the Look 'n' Stop logs ?

Frederic

[snowbound]

-{ Quote: "What is DHT ? (sorry for my ignorance ??? )

" }-
I would asumme it is this?

http://wiki.bitcomet.com/help/DHT_Network_in_BitComet



snowbound

[pietronik]

The log gives me a lot of signalation for stateful packet inspection but, also, if I disable SPI, DHT doesn't connect.
What is the real function of SPI?

[pietronik]

-{ Quote: "I would asumme it is this?

http://wiki.bitcomet.com/help/DHT_Network_in_BitComet



snowbound" }-


Yes,is it!

[Martin Aston]

Bitcomet uses a single port for its connections. I think it is 26472, look it up in the program options (and look in the LnS log to see if the port that Bitcomet needs is being blocked). You'll have to allow this port in LnS in order to make Bitcomet work. That should do the trick.
Good luck.

[Martin Aston]

Ooops, you were asking about DHT. Forget my previous answer.

[Frederic]

-{ Quote: "The log gives me a lot of signalation for stateful packet inspection but, also, if I disable SPI, DHT doesn't connect.
What is the real function of SPI?" }-
So the problem is not only the TCP SPI (SPI stands for Stateful Packet Inspection, it detects packets that are not belonging to an allowed open connection and drop them).

After you disabled the TCP SPI, was the log clearer with some other alerts ?

Frederic

[zoes]

hi,pietronik

I think your trouble nothing with LNS.

I using Bt with DHT,it works well.

[Name]

I'm getting the same alerts if I enable SPI WHILE BitComet is running (DHT doesn't matter). If I enable SPI BEFORE starting BitComet everything is working fine.

Oh well, maybe that's normal...

[pietronik]

So, if L'n's isn't the problem what I can do to make DHT fully working?

[Name]

Like Martin said before, in BitComet goto Options->Preferences->Connection, look up your listening port, make sure it's enabled and add a rule (protocol: "TCP or UDP"(!), "Source / Destination:" "TCP/UDP : port" "Equals" <your port>) in LnS internet filtering. Make sure the rule is somewhere above the "Block all other TCP packets"-rule.

BTW, the rule posted earlier does not work with BitComet (uses different port).

Most torrents aren't configured to use the DHT network by default yet. So for now you have to enable DHT manually for almost every task: right click it, Properties->Advanced, check "Enable Public DHT Network".

[pietronik]

I've configurated the UDP rule in this way:

[Name]

Do the following changes:

IP protocollo: "TCP or UDP"
TCP/UDP : porta (left side!): uguale a <your port>
TCP/UDP : porta (right side): tutti

You only need that one rule for BitComet to function completely.

Again make sure it's somewhere above the "block all other TCP"-rule.