Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 4 subscribers
  • Views 14669 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos, Logitech Media Server and SqueezeLite

TimBenkert

Hi guys,

 

I'm running Sophos UTM on a APU2C4 board with an inbuild Compex WLE600VX WLAN access point. My internal network is a bridge between the RJ45 connector at the APU board and the WLAN Access Point. The WLAN network is bridged into the AP LAN, which is the internal network. All further devices are connected to that internal Network.

On my Windows Server2012R2 the Logitech Media Server is installed. This is connected via a cable to the UTM. In my kitchen there is a Max2Play squeezelite player which is connected to the inbuild WLAN AccessPoint. 

From my Laptop I can reach web GUIs of Logitech Media Server and the Max2Play GUI of the player in the kitchen.

BUT: Player and Logitech Media Server don't find each other. This is usually done with autodiscovery, but it just doesn't work.

I tried firewall rules allowing all multicast adresses and all ports within the internal network. 

Any ideas how this issue could be solved? 

The UTM is doing only firewalling at the moment, no IPS, no webfiltering etc.

 

Regards

Tim



This thread was automatically locked due to age.
  • 0

    Ummm. Is the firewall log showing anything being blocked for:

    9000 TCP is used for the Web interface and streaming to Squeezebox players.
    9000 UDP is not used for anything.
    3483 TCP is the control channel for Squeezebox (display, IR, etc.)
    3483 UDP is used for SB->SlimServer discovery, and all control and streaming to the old SLIMP3 players.

     

    My house if full of these devices. Had them for years and love them! I'm listening to one now. Shame they are discontinued. Thanks goodness for the Rasp Pi

  • 0

    Does doing #1 in Rulz give you any clues?

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to Louis-M

    Hi Louis,

     

    sorry for my delayed response. 

    I checked the logs and allowed all that traffic. An additional firewall rule was necessary for that. Using the "log traffic" function I was able to see, that the traffic went through the firewall. 

    The problem is, that the destination IP address is a multicast address. This makes routing the connection a lot more difficult. Additionally, the behaviour ot the bridge is not clear to me. So I generated a second WLAN which I bound to a new virtual NIC. Now I hope to see more in the logs that I can use to further debug the problem and if necessary, I could start routing multicast connection attempts. Maybe this works.

     

    Regards

    Tim

  • 0 in reply to BAlfson

    Unfortunately this didn't help.

  • 0 in reply to TimBenkert

    That proves that you have a routing problem, Tim, certainly caused by multicasting.  Over the years, I've followed some threads on IPTV in the German Forum.  I don't remember seeing a solution other than having server and client in the same Ethernet segment.  Maybe Louis has a better answer for you.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson

    TBH, all of mine are on the same network. You might have to have a play with multicast due to the bridge:

    https://community.sophos.com/kb/en-us/115488

    Where is dhcp being served from? Is it you win2kr2 server? Are there any other drops occuring?

  • 0 in reply to Louis-M

    Ok, looks like a tricky thing to get that going. 

    I tried around a bit with multicasting and routing. It didn't work yet. I will keep you updated if get it going. I will have to read through the multicast documentation though.

     

    To answer your question: DHCP comes from the UTM. There are two servers; one for every network segment.

    Here is what I get from the Multicast PIM-SM log:

    2017:06:03-21:55:37 sophos xorp[19844]: [ TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 192.168.8.254 to 224.0.0.13 on vif wlan1
    2017:06:03-21:55:38 sophos xorp[19844]: [ TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 192.168.6.254 to 224.0.0.13 on vif br0
    2017:06:03-21:56:07 sophos xorp[19844]: [ TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 192.168.8.254 to 224.0.0.13 on vif wlan1
    2017:06:03-21:56:08 sophos xorp[19844]: [ TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 192.168.6.254 to 224.0.0.13 on vif br0
    2017:06:03-21:56:37 sophos xorp[19844]: [ TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 192.168.8.254 to 224.0.0.13 on vif wlan1
    2017:06:03-21:56:38 sophos xorp[19844]: [ TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 192.168.6.254 to 224.0.0.13 on vif br0
    2017:06:03-21:56:44 sophos xorp[19844]: [ TRACE xorp_fea:19819 MFEA fea/mfea_node.cc:1786 signal_dataflow_message_recv ] RX dataflow message: src = 192.168.6.52 dst = 239.255.255.250
    2017:06:03-21:56:44 sophos xorp[19844]: [ TRACE xorp_pimsm4 PIM ] RX DATAFLOW signal: source = 192.168.6.52 group = 239.255.255.250 threshold_interval_sec = 210 threshold_interval_usec = 0 measured_interval_sec = 210 measured_interval_usec = 0 threshold_packets = 0 threshold_bytes = 0 measured_packets = 0 measured_bytes = 0 is_threshold_in_packets = 1 is_threshold_in_bytes = 0 is_geq_upcall = 0 is_leq_upcall = 1
    2017:06:03-21:56:44 sophos xorp[19844]: [ TRACE xorp_pimsm4 PIM ] Delete MFC entry: (192.168.6.52, 239.255.255.250) iif = 0 olist = ...
    2017:06:03-21:56:44 sophos xorp[19844]: [ TRACE xorp_fea:19819 MFEA fea/mfea_mrouter.cc:1698 delete_mfc ] Delete MFC entry: (192.168.6.52, 239.255.255.250)
    2017:06:03-21:56:49 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:56:49 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:56:49 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:56:49 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 192.168.6.254 to 224.0.0.252
    2017:06:03-21:56:49 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:56:49 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 192.168.6.254 to 224.0.0.252
    2017:06:03-21:56:49 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:56:49 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:56:49 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:56:49 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:56:49 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.52 to 224.0.0.22 on vif br0
    2017:06:03-21:56:49 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.52 to 224.0.0.22 on vif br0
    2017:06:03-21:56:50 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 192.168.6.254 to 224.0.0.252
    2017:06:03-21:56:50 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:56:50 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 192.168.6.254 to 224.0.0.252
    2017:06:03-21:56:50 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:56:50 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 192.168.6.254 to 224.0.0.252
    2017:06:03-21:56:50 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:56:50 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:56:50 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:56:50 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:56:50 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:56:50 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:56:50 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.52 to 224.0.0.22 on vif br0
    2017:06:03-21:56:50 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.52 to 224.0.0.22 on vif br0
    2017:06:03-21:56:51 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 192.168.6.254 to 224.0.0.252
    2017:06:03-21:56:51 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:56:51 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:57:07 sophos xorp[19844]: [ TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 192.168.8.254 to 224.0.0.13 on vif wlan1
    2017:06:03-21:57:08 sophos xorp[19844]: [ TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 192.168.6.254 to 224.0.0.13 on vif br0
    2017:06:03-21:57:14 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 192.168.6.254 to 224.0.0.1
    2017:06:03-21:57:14 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 192.168.8.254 to 224.0.0.1
    2017:06:03-21:57:14 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_MEMBERSHIP_QUERY from 192.168.6.254 to 224.0.0.1 on vif br0
    2017:06:03-21:57:14 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_MEMBERSHIP_QUERY from 192.168.6.254 to 224.0.0.1 on vif br0
    2017:06:03-21:57:14 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_MEMBERSHIP_QUERY from 192.168.8.254 to 224.0.0.1 on vif wlan1
    2017:06:03-21:57:14 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_MEMBERSHIP_QUERY from 192.168.8.254 to 224.
    2017:06:03-21:57:14 sophos xorp[19844]: 0.0.1 on vif wlan1
    2017:06:03-21:57:15 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:57:15 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:57:17 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:57:17 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:57:18 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.254 to 224.0.0.22 on vif br0
    2017:06:03-21:57:18 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.254 to 224.0.0.22 on vif br0
    2017:06:03-21:57:23 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.8.254 to 224.0.0.22 on vif wlan1
    2017:06:03-21:57:23 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.8.254 to 224.0.0.22 on vif wlan1
    2017:06:03-21:57:23 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:57:23 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:57:37 sophos xorp[19844]: [ TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 192.168.8.254 to 224.0.0.13 on vif wlan1
    2017:06:03-21:57:38 sophos xorp[19844]: [ TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 192.168.6.254 to 224.0.0.13 on vif br0
    2017:06:03-21:57:52 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:57:52 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 192.168.6.254 to 224.0.0.253
    2017:06:03-21:57:52 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:57:52 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:57:52 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 192.168.6.254 to 224.0.0.252
    2017:06:03-21:57:52 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:57:52 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 192.168.6.254 to 224.0.0.252
    2017:06:03-21:57:52 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:57:52 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 192.168.6.254 to 224.0.0.253
    2017:06:03-21:57:52 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 192.168.6.254 to 224.0.0.252
    2017:06:03-21:57:52 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:57:52 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 192.168.6.254 to 224.0.0.253
    2017:06:03-21:57:52 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 192.168.6.254 to 224.0.0.252
    2017:06:03-21:57:52 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.52 to 224.0.0.22 on vif br0
    2017:06:03-21:57:52 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.52 to 224.0.0.22 on vif br0
    2017:06:03-21:57:52 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:57:52 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:57:53 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:57:53 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:57:53 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 192.168.6.254 to 224.0.0.253
    2017:06:03-21:57:53 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 192.168.6.254 to 224.0.0.252
    2017:06:03-21:57:53 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:57:53 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.10 to 224.0.0.22 on vif br0
    2017:06:03-21:57:53 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.52 to 224.0.0.22 on vif br0
    2017:06:03-21:57:53 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.6.52 to 224.0.0.22 on vif br0
    2017:06:03-21:57:54 sophos xorp[19844]: [ TRACE xorp_igmp MLD6IGMP ] Notify routing delete membership for (0.0.0.0, 224.0.0.253) on vif br0
    2017:06:03-21:58:07 sophos xorp[19844]: [ TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 192.168.8.254 to 224.0.0.13 on vif wlan1
    2017:06:03-21:58:08 sophos xorp[19844]: [ TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 192.168.6.254 to 224.0.0.13 on vif br0
    2017:06:03-21:58:30 sophos xorp[19844]: [ TRACE xorp_pimsm4 PIM ] TX PIM_ASSERT from 192.168.6.254 to 224.0.0.13 on vif br0
    2017:06:03-21:58:37 sophos xorp[19844]: [ TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 192.168.8.254 to 224.0.0.13 on vif wlan1
    2017:06:03-21:58:38 sophos xorp[19844]: [ TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 192.168.6.254 to 224.0.0.13 on vif br0
    2017:06:03-21:59:00 sophos xorp[19844]: [ TRACE xorp_fea:19819 MFEA fea/mfea_node.cc:1603 signal_message_recv ] RX kernel signal: message_type = 1 vif_index = 0 src = 192.168.6.52 dst = 239.255.255.250
    2017:06:03-21:59:00 sophos xorp[19844]: [ TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 0 src = 192.168.6.52 dst = 239.255.255.250
    2017:06:03-21:59:00 sophos xorp[19844]: [ TRACE xorp_pimsm4 PIM ] Add MFC entry: (192.168
    2017:06:03-21:59:00 sophos xorp[19844]: .6.52, 239.255.255.250) iif = 0 olist = ... olist_disable_wrongvif = OOO
    2017:06:03-21:59:00 sophos xorp[19844]: [ TRACE xorp_pimsm4 PIM ] Add dataflow monitor: source = 192.168.6.52 group = 239.255.255.250 threshold_interval_sec = 210 threshold_interval_usec = 0 threshold_packets = 0 threshold_bytes = 0 is_threshold_in_packets = 1 is_threshold_in_bytes = 0 is_geq_upcall = 0 is_leq_upcall = 1
    2017:06:03-21:59:00 sophos xorp[19844]: [ TRACE xorp_pimsm4 PIM ] Add dataflow monitor: source = 192.168.6.52 group = 239.255.255.250 threshold_interval_sec = 60 threshold_interval_usec = 0 threshold_packets = 0 threshold_bytes = 62914560 is_threshold_in_packets = 0 is_threshold_in_bytes = 1 is_geq_upcall = 1 is_leq_upcall = 0
    2017:06:03-21:59:00 sophos xorp[19844]: [ TRACE xorp_fea:19819 MFEA fea/mfea_mrouter.cc:1568 add_mfc ] Add MFC entry: (192.168.6.52, 239.255.255.250) iif = 0 olist = ...
    2017:06:03-21:59:07 sophos xorp[19844]: [ TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 192.168.8.254 to 224.0.0.13 on vif wlan1
    2017:06:03-21:59:08 sophos xorp[19844]: [ TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 192.168.6.254 to 224.0.0.13 on vif br0
     
     
    If I get that right, the Win2k12 server send the PIM_HELLO but nobody is answering. 
    I defined two PIM interfaces, one is the internal bridge, the second one is a WLAN which is bound to a seperate interface. The RendezvousPoint is the UTM address on the internal bridge.
    I created four routes:
    internal network -> internal bridge address
    internal network -> WLAN address
    WLAN network -> WLAN address
    WLAN network -> internal bridge address
     
    Something is still wrong, but let's see, maybe I can sort it out.

    Tim

     

  • 0

    Alright, got it working.

    First of all, I got rid of the bridge since it was causing trouble only. Now I have one network segment for LAN and one for WLAN. In both segements the UTM provides DHCP and DNS service. WINS is setup and all devices that are used regularly in the network have static mappings.

    The trick now was to get around the autodiscovery, which uses multicasting.

    What I did: In the Max2Play GUI under SqueezeLite->Advanced Options I added the start parameter -s <servername>. I tried that before but it didn't work. Reason was, that I put in -s <servername>:<port>. You have to leave out the portnumber and make sure, that the device Max2Play is running on can ping that servername. Than your are good to go.

     

    Multicast:

    My guess is, that the UTM cannot act as a Rendezvous Point. Since we have a subsription at work, I will open a support case and ask Sophos how to setup multicast the right way. Maybe autodiscovery is going to work than.


    Regards

    Tim

Unfiltered HTML