This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Yet another UPNP problem

Tags: None
(comma "," separated)
pcyanide
Registered Member
Posts
2
Karma
0

Yet another UPNP problem

Sat Nov 03, 2007 5:22 am
I just started using ktorrent, and it's really cool ! It reminds me uTorrent, and it also allows to kick of peers, which uTorrent designers will never agree :)

Honestly I prefer uTorrent style flags for peers (like DdUdI), so you look at a single column and know straight away what is going on with a peer.

I checked previous mails on similar UPNP pb, which were eventually solved, hopefully mine will be solved as well :)

I use ktorrent with Mandriva 2008, and my router is Netgear DG834G (ADSL). It is configured to enable UPNP and works OK with Windows. I also set up a "hardcoded" port in the router, and it works great with ktorrent (no complaints about incoming connections), but I would like it to work properly - through UPNP.

I start ktorrent and go to UPNP plugin config - the list of devices is completely empty. I press Rescan .... nothing happens. I turn off iptables to get ACCEPT for all policies (Windows won't survive, but Linux hopefully will!), but nothing changes.

Then I bring up wireshark, and repeat the procedure. I get a RED line saying:
192.168.0.5 239.255.255.250 SSDP M-SEARCH + HTTP/1.1

I apply 'port 1900' filter to wireshark and repeat.

When I start ktorrent, I see the SSDP request during ktorrent initialization, and it is blue (I assume that the request went through)! But again, when I go to UPNP plugin, the lines are always red.

Your help will be appreciated.
George
Moderator
Posts
5421
Karma
1

Sun Nov 04, 2007 12:19 pm
Just because wireshark puts something in red, doesn't mean it failed.

Anyway, your router should respond to the HTTP M-SEARCH, and it should periodically (every minute or so) broadcast it's presence by sending a NOTIFY to 239.255.255.250:1900 .

If you don't see any of these in wireshark, you have a problem, either with your router or your firewall.
pcyanide
Registered Member
Posts
2
Karma
0

Mon Nov 05, 2007 9:30 am
Well, that's another happy end. I upgraded the firmware and it works, the ports are listed and no more "triangle warning" ! Thanks.

BTW, how to tell which connections are remote, and which are local. ?
stoeptegel
Registered Member
Posts
1075
Karma
0

Mon Nov 05, 2007 4:25 pm
pcyanide wrote:BTW, how to tell which connections are remote, and which are local. ?


You can't in peerview, however you can check the "Authentication(S) to 201.235.155.38 : ok" messages. The (S) says that the connection was generated locally.


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot]