<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[mini-DLNA with multiple VLANs]]></title><description><![CDATA[<p dir="auto">pfSense version 2.4.3</p>
<p dir="auto">Hi,</p>
<p dir="auto">I have two VLANs, VLAN1 and VLAN2 each on their own subnet.</p>
<p dir="auto">On VLAN1 are a number of consumer devices, and on VLAN2 are a pair of NAS drives with mini-DLNA installed.  mini-DLNA uses two ports:</p>
<ul>
<li>
<p dir="auto">TCP 8200: I assume this is the direct media transfer port, and so we only need a rule on VLAN1 interface allowing TCP traffic to destination on VLAN2 subnet port 8200.</p>
</li>
<li>
<p dir="auto">UDP 1900: This is apparently the UPnP service discovery port.</p>
</li>
</ul>
<p dir="auto">The UDP is the part I don't understand how to configure.</p>
<ul>
<li>Do I need to allow port 1900 through the interface of VLAN1 and/or VLAN2?</li>
<li>Is the destination the subnet of the other VLAN, or the broadcast address (I believe this is 239.255.255.250)?</li>
<li>I thought a UDP broadcast could jump between subnets, is this the case?  If not, what do I need to do to permit it?</li>
<li>Some posts talk about IGMP, is this even required?  Do you not just need to permit the UDP broadcast?</li>
</ul>
<p dir="auto">Any help would be appreciated.</p>
<p dir="auto">Regards,<br />
Rob,</p>
]]></description><link>https://forum.netgate.com/topic/137276/mini-dlna-with-multiple-vlans</link><generator>RSS for Node</generator><lastBuildDate>Sun, 07 Jun 2026 08:02:51 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/137276.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 30 Oct 2018 12:12:16 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to mini-DLNA with multiple VLANs on Sun, 04 Nov 2018 22:56:15 GMT]]></title><description><![CDATA[<p dir="auto">You will neef IGMP proxy for 'discovery' to work. Unless you can use mDNS instead in which case try Avahi.</p>
<p dir="auto">Of coarse if you can enter the IP address of the NAS directly in the devices then you don't need either. But alas that's too easy for most manufacturers it seems.</p>
<p dir="auto">Steve</p>
]]></description><link>https://forum.netgate.com/post/802380</link><guid isPermaLink="true">https://forum.netgate.com/post/802380</guid><dc:creator><![CDATA[stephenw10]]></dc:creator><pubDate>Sun, 04 Nov 2018 22:56:15 GMT</pubDate></item></channel></rss>