miniupnp.tuxfamily.org Forum Index miniupnp.tuxfamily.org
The forum about miniupnp and libnatpmp
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

port 1900 forwarding

 
Post new topic   Reply to topic    miniupnp.tuxfamily.org Forum Index -> miniupnpc Compilation/Installation
View previous topic :: View next topic  
Author Message
jbparker



Joined: 11 Feb 2008
Posts: 2

PostPosted: Mon Feb 11, 2008 5:32 pm    Post subject: port 1900 forwarding Reply with quote

I'd rather discuss this via email, if possible

I have a slightly odd WAN setup. I'm using OpenWRT with the WAN side
connected to my internal network. I do this because I don't want to mix the DHCP
domains. It's also simple.

In order to get my MusicPAL to see a music server, I think it needs to hear SSDP
multicasts (sent to port 1900). So, I think I need to forward them from the WAN
side to the wireless and back. I tried to use miniupnpd but I don't think it will do this
for me.

I did run the minissdpd, and it saw the broadcasts from the mediatomb I'm running
on the WAN side and it also saw the MusicPAL's broadcasts. But no reflecting.

I know a lot about multicast but nothing about SSDP. Am I correct in assuming that
if I reflect SSDP multicasts to port 1900 across from one port to the other, my upnp
device (the MusicPAL) will see the server?

thanks for any insights. or pointers to other places to ask...

-brad
Back to top
View user's profile Send private message
miniupnp
Site Admin


Joined: 14 Apr 2007
Posts: 1481

PostPosted: Tue Feb 12, 2008 9:54 am    Post subject: Reply with quote

Routing of multicast packets is done at kernel level.
I think you need to enable the multicast routing in the kernel and alter the routing table.
_________________
Main miniUPnP author.
http://miniupnp.tuxfamily.org/
Back to top
View user's profile Send private message Visit poster's website
jbparker



Joined: 11 Feb 2008
Posts: 2

PostPosted: Wed Feb 13, 2008 12:29 am    Post subject: Reply with quote

After your post I thought about multicast routing.

Back in the day I did a lot of multicast and multicast routing. I think my
named is in mrouted somewhere.

But I don't think that is what I need.

I have a NAT router. I think what i need is a cross between minissdpd and
miniupnpd.

I propose a daemon which like minissdpd, will collect advertisements. What I would add is the ability to respond to M-SEARCH queries from the internal 'database' of collected NOTIFYs.

This would allow a client on one side of the NAT to learn about something
on the other side (without the need for multicast routing). My assumption is that once it finds something it will then talk directly to it via TCP and then the normal NAT logic will make it all work.

Essentially an SSDP proxy.

minissdp is very close, but it does not answer queries. miniupnpd answers queries, but only for itself.

does that make more sense?
Back to top
View user's profile Send private message
miniupnp
Site Admin


Joined: 14 Apr 2007
Posts: 1481

PostPosted: Wed Feb 13, 2008 10:45 am    Post subject: Reply with quote

I think you are right, it should not be too difficult to make a SSDP proxy from current minissdpd code. The only thing to be carefull about would be not to answer on the same subnetwork.
_________________
Main miniUPnP author.
http://miniupnp.tuxfamily.org/
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic   Reply to topic    miniupnp.tuxfamily.org Forum Index -> miniupnpc Compilation/Installation All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group
Protected by Anti-Spam ACP
© 2007 Thomas Bernard, author of MiniUPNP.