View previous topic :: View next topic |
Author |
Message |
Tzim
Joined: 19 May 2007 Posts: 3
|
Posted: Sat May 19, 2007 8:47 pm Post subject: Multiple LAN Interface |
|
|
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 |
|
|
miniupnp Site Admin
Joined: 14 Apr 2007 Posts: 1589
|
Posted: Mon May 21, 2007 12:21 pm Post subject: Re: Multiple LAN Interface |
|
|
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 |
|
|
miniupnp Site Admin
Joined: 14 Apr 2007 Posts: 1589
|
Posted: Wed May 23, 2007 10:02 am Post subject: |
|
|
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 |
|
|
Tzim
Joined: 19 May 2007 Posts: 3
|
Posted: Fri May 25, 2007 9:20 am Post subject: |
|
|
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 |
|
|
miniupnp Site Admin
Joined: 14 Apr 2007 Posts: 1589
|
Posted: Sat May 26, 2007 1:47 pm Post subject: |
|
|
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 |
|
|
miniupnp Site Admin
Joined: 14 Apr 2007 Posts: 1589
|
|
Back to top |
|
|
Tzim
Joined: 19 May 2007 Posts: 3
|
Posted: Sat May 26, 2007 5:37 pm Post subject: |
|
|
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 |
|
|
miniupnp Site Admin
Joined: 14 Apr 2007 Posts: 1589
|
Posted: Tue Sep 25, 2007 2:50 pm Post subject: |
|
|
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 |
|
|
miniupnp Site Admin
Joined: 14 Apr 2007 Posts: 1589
|
Posted: Fri Sep 28, 2007 9:34 am Post subject: |
|
|
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 |
|
|
|