View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0012839 | MMW v4 | DLNA/UPnP | public | 2015-09-01 22:52 | 2016-09-25 19:28 |
| Reporter | peke | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | assigned | Resolution | open | ||
| Target Version | 5.0.0 | ||||
| Summary | 0012839: DLNA/UPnP Settings: We should add Subnet Mask as additional check for LAN access | ||||
| Description | There is the reports where LAN uses 192.168.0.x IP address space and WLAN 192.168.1.x IP address space. This is set in DHCP server to simple separate WLAN users from LAN without more complicated hardware and router settings (VLAN space) where DHCP serve 255.255.255.0 subnet mask. Result is that WLAN (WiFi) devices do not see MM server on LAN and MM rejects them as external access. This can be easilly avoided if MMW server have subnet mask check where setting 255.255.254.0 instead of 255.255.255.0 will classify all WiFi devices as in LAN without exposing MM to internet by enabling '[x] Accept external IPs' | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
Peke, can you elaborate, from your description it looks that this needs to be splitted into more possible issues. Re the external (public) address detection. From what I see in our code the 192.168.1.x IP is never considered as external IP so MM should not reject it. I guess this must be a test error? Re server visibility: If an UPnP control point device does not see the MM server on the LAN then it is an issue with SSDP auto discovery. e.g. UPnP is disabled on the router or the device is connected to another router (access point). Another case is that MM server is using IP from another network interface when serving links/metadata, this can be changed in Options -> Media Sharing -> <Server> -> IP combo box. I believe that the choice "Automatic" works fine (because it auto-sets the IP of the interface from which the request is coming), but if it does not work for some reason then changing to the IP of corresponding interface should work fine. I also noticed that some media servers (like Mezzmo) solves this by running as many Mezzmo servers as interfaces, i.e. in my case there are 3 Mezzmo servers running each with IP of corresponding interface (192.168.204.1, 192.168.0.12, 169.254.211.185), but I don't know another server acting like this, the others mostly use the same as MM, i.e. some kind of "Automatic" IP. |
|
|
Haven't seen many reports recently to make full example. I've never found out why windows is assigning Devices within LAN into Internet zone, lowering priority to do more investigation. |
