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 

Multiple LAN Interface

 
Post new topic   Reply to topic    miniupnp.tuxfamily.org Forum Index -> miniupnpd Bugs
View previous topic :: View next topic  
Author Message
Tzim



Joined: 19 May 2007
Posts: 3

PostPosted: Sat May 19, 2007 8:47 pm    Post subject: Multiple LAN Interface Reply with quote

I don't really know if it's possible or not, but I'm using a 3 interface FreeBSD router (WAN, LAN and WLAN).

I don't want to bridge the WAN and WLAN interfaces, but then I have this problem :

I set 2 listening IP.

If I set the first listening address on the LAN IP, the wlan windows clients will see the device under network places but not under network connexions, and MSN won't be able to do any port mapping, while it's working for lan clients.

If I set the WLAN IP as the first, it's the oposite result.
How can I get UPnP working on both interfaces (again : without bridging) ?
Back to top
View user's profile Send private message
miniupnp
Site Admin


Joined: 14 Apr 2007
Posts: 1589

PostPosted: Mon May 21, 2007 12:21 pm    Post subject: Re: Multiple LAN Interface Reply with quote

Tzim wrote:
I don't really know if it's possible or not, but I'm using a 3 interface FreeBSD router (WAN, LAN and WLAN).

I don't want to bridge the WAN and WLAN interfaces, but then I have this problem :

I set 2 listening IP.

If I set the first listening address on the LAN IP, the wlan windows clients will see the device under network places but not under network connexions, and MSN won't be able to do any port mapping, while it's working for lan clients.

If I set the WLAN IP as the first, it's the oposite result.
How can I get UPnP working on both interfaces (again : without bridging) ?


I am in the same situation at home. WAN, WLAN and LAN.
The few windows machines I use are on the WLAN so I never tested the UPnP on the LAN with msn.
I have to check but I think that SSDP NOTIFY messages are sent only to the subnetwork of the 1st listening address.
Anyway It should not prevent SSDP M-SEARCH to work properly and Windows to detect the IGD. What Are the versions of MS Windows you tested with ?
Back to top
View user's profile Send private message Visit poster's website
miniupnp
Site Admin


Joined: 14 Apr 2007
Posts: 1589

PostPosted: Wed May 23, 2007 10:02 am    Post subject: Reply with quote

hum it seems not so easy to send a packet to multiple interfaces.
I think I need to do some deep modifications in the SSDP Notify code.
_________________
Main miniUPnP author.
https://miniupnp.tuxfamily.org/
Back to top
View user's profile Send private message Visit poster's website
Tzim



Joined: 19 May 2007
Posts: 3

PostPosted: Fri May 25, 2007 9:20 am    Post subject: Reply with quote

I use FreeBSD 6.2 and Windows XP x64 SP2.

The fact is : Windows DOES detect the device, it just not using it.
I'm just wondering if windows doesn't just ignore the IGD functionnalities because the upnpd doesn't announce itself in the same subnetwork... or, more likely, because the upnp-annouced address doesn't match with the default gateway.

I think that the SSDP module should announce the IP of the interface on wich it receives the M-SEARCH message to make it work with windows.
Back to top
View user's profile Send private message
miniupnp
Site Admin


Joined: 14 Apr 2007
Posts: 1589

PostPosted: Sat May 26, 2007 1:47 pm    Post subject: Reply with quote

Tzim wrote:
I use FreeBSD 6.2 and Windows XP x64 SP2.

The fact is : Windows DOES detect the device, it just not using it.
I'm just wondering if windows doesn't just ignore the IGD functionnalities because the upnpd doesn't announce itself in the same subnetwork... or, more likely, because the upnp-annouced address doesn't match with the default gateway.

I think that the SSDP module should announce the IP of the interface on wich it receives the M-SEARCH message to make it work with windows.

it would also mean listening for UPnP HTTP trafic on several interfaces.

Maybe the recent windows "security" feature to ignore IGD fuctionnalities if the address doesnt match the default gateway can be disabled. I'm trying to get more information about this.
_________________
Main miniUPnP author.
https://miniupnp.tuxfamily.org/
Back to top
View user's profile Send private message Visit poster's website
miniupnp
Site Admin


Joined: 14 Apr 2007
Posts: 1589

PostPosted: Sat May 26, 2007 2:25 pm    Post subject: Reply with quote

I found an interesting article :
http://support.microsoft.com/kb/821371
_________________
Main miniUPnP author.
https://miniupnp.tuxfamily.org/
Back to top
View user's profile Send private message Visit poster's website
Tzim



Joined: 19 May 2007
Posts: 3

PostPosted: Sat May 26, 2007 5:37 pm    Post subject: Reply with quote

miniupnp wrote:
Tzim wrote:
I use FreeBSD 6.2 and Windows XP x64 SP2.

The fact is : Windows DOES detect the device, it just not using it.
I'm just wondering if windows doesn't just ignore the IGD functionnalities because the upnpd doesn't announce itself in the same subnetwork... or, more likely, because the upnp-annouced address doesn't match with the default gateway.

I think that the SSDP module should announce the IP of the interface on wich it receives the M-SEARCH message to make it work with windows.

it would also mean listening for UPnP HTTP trafic on several interfaces.

Maybe the recent windows "security" feature to ignore IGD fuctionnalities if the address doesnt match the default gateway can be disabled. I'm trying to get more information about this.


I don't see that as a "security" feature. It's only logical for me that windows doesn't try to control a gateway that isn't it's gateway.
Back to top
View user's profile Send private message
miniupnp
Site Admin


Joined: 14 Apr 2007
Posts: 1589

PostPosted: Tue Sep 25, 2007 2:50 pm    Post subject: Reply with quote

I'm currently working on cleaning all that.
SSDP responses would be "customized" to each sub network so it should fix the problem
_________________
Main miniUPnP author.
https://miniupnp.tuxfamily.org/
Back to top
View user's profile Send private message Visit poster's website
miniupnp
Site Admin


Joined: 14 Apr 2007
Posts: 1589

PostPosted: Fri Sep 28, 2007 9:34 am    Post subject: Reply with quote

miniupnpd-1.0-RC9 support multiple LAN interface in a way that should fix all your problems !
_________________
Main miniUPnP author.
https://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 -> miniupnpd Bugs 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.