DLNA with multi VLAN



  • Hello community,

    My config:

    pFSense 2.4.4p3
    192.168.10.254 (VLAN 10)
    192.168.20.254 (VLAN 20)

    OMV NAS (miniDLNA server)
    192.168.10.253

    TVs
    192.168.20.x

    I tried the IGMP proxy and PIMD, but none of them worked. Can someone show me a working setting (screenshot)?

    Thanks,
    Joc



  • Hello,

    I have been fighting the same problem, for at least two years spending many many hours and
    ……. I did not manage :( :(
    My hope is that the recent release of the PIMD package brings the solution.

    My network is just as yours divided in a couple of VLAN's

    To mention here:

    • Incomming interface
    • 192.168.1.0/24 PC's, HIFI-receivers etc.
    • 192.168.2.0/24 Servers e.g. Twonky Media Server
    • 192.168.3.0/24 IoT-devices
      All vlan's/subnets hosted by pfSense 2.4.4. release-3. With Avahi and PIMD installed.

    pfSense is also used as DHCP and DNS-server. The whole network is IPV6 enabled (so preferable that should work as well).

    Avahi (mDNS) is not relevant here and is turned off.
    IGMP-proxy should be turned off, since at this moment it is "replaced by" PIMD

    IMHO I opened all relevant ports:

    • IMCP (IPV6)

    • SSDP 1900, 2869 (microsoft), 5000 (old)

    • 9000 Twonky

    • 1901 Upnp-Response

    • netbios is blocked (for security reasons)

    Today I was testing again with PIMD using following settings:

    general

    • bind to none (to be secure)
    • loglevel info (during testing)
    • Interval 8 (to speed up detection)
    • timeout 29 (to speed up detection)
      interfaces
    • enabled the three mentioned lan's
    • no BSR-Candidates
    • no RP-Candidates
    • 192.168.1.1 as RP address

    status and logs show that there is something happening between PIMD and computers

    from the logs e.g.
    Mar 17 14:01:02 pimd[50054]: Send PIM ASSERT from 192.168.116.1 for group 239.255.255.250 and source 192.168.1.2

    status e.g.
    PIMD Routes
    Virtual Interface Table ======================================================
    Vif Local Address Subnet Thresh Flags Neighbors


    3 192.168.1.1 192.168.1 1 DR NO-NBR
    6 192.168.116.1 192.168.2 1 DR NO-NBR
    7 192.168.14.1 192.168.3 1 DR NO-NBR
    10 192.168.1.1 register_vif0 1

    Vif SSM Group Sources

    Multicast Routing Table ======================================================
    ----------------------------------- (*,G) ------------------------------------
    Source Group RP Address Flags


    INADDR_ANY 224.0.1.1 192.168.1.1 WC RP
    Joined oifs: ...........
    Pruned oifs: ...........
    Leaves oifs: ...l.......
    Asserted oifs: ...........
    Outgoing oifs: ...o.......
    Incoming : ..........I

    TIMERS: Entry JP RS Assert VIFS: 0 1 2 3 4 5 6 7 8 9 10
    0 30 0 0 0 0 0 0 0 0 0 0 0 0 0
    ----------------------------------- (S,G) ------------------------------------

    TIMERS: Entry JP RS Assert VIFS: 0 1 2 3 4 5 6 7 8 9 10
    135 50 0 0 0 0 0 0 0 0 0 0 0 0 0
    Source Group RP Address Flags


    192.168.116.33 239.255.255.250 192.168.1.1 SPT CACHE SG
    Joined oifs: ..........j
    Pruned oifs: ...........
    Leaves oifs: ...l..ll...
    Asserted oifs: ...........
    Outgoing oifs: ...o..oo..o
    Incoming : ......I....

    TIMERS: Entry JP RS Assert VIFS: 0 1 2 3 4 5 6 7 8 9 10
    135 50 0 0 0 0 0 0 0 0 0 0 0 0 0
    --------------------------------- (,,G) ------------------------------------
    Number of Groups: 3
    Number of Cache MIRRORs: 6

    So there defitively something going on ………… but in the end ……. it is not working :( :( :(

    If someone has a working configuration ………. please help !!!!!!!

    Sincerely,

    Louis



  • Hello,

    I should have added that I have another problem which might or might not be related
    .

    The may be related problem is, that I can not see SMB-shares (SMB3) present in other VLAN's.

    Note that there is not any problem to access those shares via IP-address or host-name or domain-name. But dispite lots and lots of hours of reading and testing, I did not manage to have those shares visible (in e.g. windows network).

    I tried lots of things using all kind of test tools like wireshark, but it simply does not work ……

    Note that for security reasons SMB1 is turned off and "of course" I also tested with a disabled windows firewall.

    I need a solution for that problem as well !!!

    But …… it might be …… that the fact that the SMB-shares are not visable ….. are related to the fact that the media server is not visible …… even when using PIMD

    Sincerely,

    Louis


  • LAYER 8 Global Moderator

    @louis2 said in DLNA with multi VLAN:

    have those shares visible (in e.g. windows network).

    Windows network browser has never worked across vlans.. Back from windows 3.11 days.. For you to see stuff on different vlans in windows network browser you would need to run wins server.

    There is no reason to fix that - its not broken.. Never was - just access shares via their fqdn..


Log in to reply