I have several different services on my network that use UPnP, and none of them seem to work unless I disable the Firewall on my Fedora 14 desktops/laptops. Everything I've read says that I should be able to allow UDP on port 1900, but that doesn't seem to help. Can anyone tell me or point me to documentation about what I need to enable to let my Fedora 14 machines to see the services via UPnP?
Thanks Mike
On Mon, 2011-05-02 at 10:03 -0400, Mike Wohlgemuth wrote:
I have several different services on my network that use UPnP, and none of them seem to work unless I disable the Firewall on my Fedora 14 desktops/laptops. Everything I've read says that I should be able to allow UDP on port 1900, but that doesn't seem to help. Can anyone tell me or point me to documentation about what I need to enable to let my Fedora 14 machines to see the services via UPnP?
I also think I'm having trouble with UPnP. I posted a question a week or so ago:
http://lists.fedoraproject.org/pipermail/users/2011-April/395951.html
to which the answer was a deafening silence.
poc
Mike Wohlgemuth wrote:
I have several different services on my network that use UPnP, and none of them seem to work unless I disable the Firewall on my Fedora 14 desktops/laptops. Everything I've read says that I should be able to allow UDP on port 1900, but that doesn't seem to help. Can anyone tell me or point me to documentation about what I need to enable to let my Fedora 14 machines to see the services via UPnP?
UPnP stands for many different things. Which in particular are you trying to use?
IGP? Media server? Media render? etc.
On 05/02/2011 10:23 AM, Michael Cronenworth wrote:
Mike Wohlgemuth wrote:
I have several different services on my network that use UPnP, and none of them seem to work unless I disable the Firewall on my Fedora 14 desktops/laptops. Everything I've read says that I should be able to allow UDP on port 1900, but that doesn't seem to help. Can anyone tell me or point me to documentation about what I need to enable to let my Fedora 14 machines to see the services via UPnP?
UPnP stands for many different things. Which in particular are you trying to use?
IGP? Media server? Media render? etc.
As a starting point, I am attempting to discover services via SSDP. If I have the firewall enabled, and I run upnp-inspector, I see no services. No matter what combination of settings I have tried, I never see any services via upnp-inspector. If I disable the firewall and immediately rediscover services in upnp-inspector, I will instantly see my printers, my media server, etc. I wouldn't at all be surprised if the services didn't work without extra ports open, but I cannot even see them to attempt to use them.
Thanks Mike
On Mon, 2011-05-02 at 09:25 -0500, Michael Cronenworth wrote:
Michael Cronenworth wrote:
IGP?
I meant IGD. Internet Gateway Daemon.
In my case, I want my F14 machine to see my router in order to configure ports for torrents. It used to do this, now it doesn't. The torrent app (qbittorrent) says it can't find any UPnP/PMP-enabled routers. The router is a Cisco (Linksys) E1000 with UPnP capability, which is enabled.
poc
Mike Wohlgemuth wrote:
As a starting point, I am attempting to discover services via SSDP. If I have the firewall enabled, and I run upnp-inspector, I see no services. No matter what combination of settings I have tried, I never see any services via upnp-inspector. If I disable the firewall and immediately rediscover services in upnp-inspector, I will instantly see my printers, my media server, etc. I wouldn't at all be surprised if the services didn't work without extra ports open, but I cannot even see them to attempt to use them.
It looks like upnp-inspector not only listens[1] on UDP port 1900, but on two other randomized ports as well. One solution would be to have upnp-inspector use the new firewalld API in Fedora 15 to open up ports automatically. Another solution would be to allow high TCP/UDP ports (say, >30000).
[1] # netstat -anp | grep -i python
Patrick O'Callaghan wrote:
In my case, I want my F14 machine to see my router in order to configure ports for torrents. It used to do this, now it doesn't. The torrent app (qbittorrent) says it can't find any UPnP/PMP-enabled routers. The router is a Cisco (Linksys) E1000 with UPnP capability, which is enabled.
Have you tried other torrent clients? Deluge?
On 05/02/2011 12:57 PM, Michael Cronenworth wrote:
Mike Wohlgemuth wrote:
As a starting point, I am attempting to discover services via SSDP. If I have the firewall enabled, and I run upnp-inspector, I see no services. No matter what combination of settings I have tried, I never see any services via upnp-inspector. If I disable the firewall and immediately rediscover services in upnp-inspector, I will instantly see my printers, my media server, etc. I wouldn't at all be surprised if the services didn't work without extra ports open, but I cannot even see them to attempt to use them.
It looks like upnp-inspector not only listens[1] on UDP port 1900, but on two other randomized ports as well. One solution would be to have upnp-inspector use the new firewalld API in Fedora 15 to open up ports automatically. Another solution would be to allow high TCP/UDP ports (say,>30000).
[1] # netstat -anp | grep -i python
Ah! Thank you! That explains it. Now off to figure out why each individual application that I'm actually trying to use is having issues. Hopefully it will be as easy to figure out.
Thanks again Mike
On Mon, 2011-05-02 at 11:57 -0500, Michael Cronenworth wrote:
Mike Wohlgemuth wrote:
As a starting point, I am attempting to discover services via SSDP. If I have the firewall enabled, and I run upnp-inspector, I see no services. No matter what combination of settings I have tried, I never see any services via upnp-inspector. If I disable the firewall and immediately rediscover services in upnp-inspector, I will instantly see my printers, my media server, etc. I wouldn't at all be surprised if the services didn't work without extra ports open, but I cannot even see them to attempt to use them.
It looks like upnp-inspector not only listens[1] on UDP port 1900, but on two other randomized ports as well. One solution would be to have upnp-inspector use the new firewalld API in Fedora 15 to open up ports automatically. Another solution would be to allow high TCP/UDP ports (say, >30000).
[1] # netstat -anp | grep -i python
I have nothing called upnp-inspector in my system (F14), and nothing is listening on port 1900.
poc
On Mon, 2011-05-02 at 12:02 -0500, Michael Cronenworth wrote:
Patrick O'Callaghan wrote:
In my case, I want my F14 machine to see my router in order to configure ports for torrents. It used to do this, now it doesn't. The torrent app (qbittorrent) says it can't find any UPnP/PMP-enabled routers. The router is a Cisco (Linksys) E1000 with UPnP capability, which is enabled.
Have you tried other torrent clients? Deluge?
I just tried transmission, and its log file implies that UPnP/NAT-PMP was successful. Guess I'll focus on a possible bug in QB.
poc
On 05/02/2011 05:32 PM, Patrick O'Callaghan wrote:
I have nothing called upnp-inspector in my system (F14), and nothing is listening on port 1900.
We have two threads going on here. :)
upnp-inspector is a stand-alone application that can show all UPnP devices on your local network.
On Mon, 2011-05-02 at 20:18 -0500, Michael Cronenworth wrote:
On 05/02/2011 05:32 PM, Patrick O'Callaghan wrote:
I have nothing called upnp-inspector in my system (F14), and nothing is listening on port 1900.
We have two threads going on here. :)
That's my fault. Sorry about that but I didn't think it was too OT.
upnp-inspector is a stand-alone application that can show all UPnP devices on your local network.
I'll try installing it and see what it tells me.
poc
-
Michael Cronenworth -
Mike Wohlgemuth -
Patrick O'Callaghan