Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 13 replies
  • Subscribers 4 subscribers
  • Views 14349 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

Multicast zwischen 2 Netzen

superfun2k23

Hi,

ich habe eine SG135 und nutze sie in Verbindung mit einer Fritzbox 6591.

Der Aufbau sieht wie folgt aus:

ETH0= WAN / Additional IP UTM 172.10.0.2 (Fritzbox 172.10.0.1 / WLAN 192.168.3.0/24)
ETH1-7= internes LAN 192.168.4.1 (192.168.4.0/24)

Alles funktioniert soweit, ich komme mit Geräten aus dem WLAN der Fritzbox 6591 ins lokale Ntz der UTM und auch zur Verwaltung auf die Fritzbox GUI.

Was nicht funktioniert:
1. Ich habe an der Fritzbox eine per FritzVPN verbundene 7490, in dieses Netzwerk komme ich nicht, weder aus dem lokalen Netz, noch dem WLAN (7490-Netzwerk 192.168.31.0/24)
2. Multicast zwischen 192.168.3.0/24 und 192.168.4.0/24 funktioniert nicht, da ich weder vom Handy aus SpotifyConnect nutzen kann, noch funktioniert bei Netflix die TV-Erkennung, da das Handy im Wlan eine 192.168.3.x bekommt und AVR und TV aber im 192.168.4.x hängen.

Ich habe schon versucht mit Mulicast PIM das zum laufen zu bekommen und für paar Sekunden war der AVR auch sichtbar, dann aber nicht mehr.. ich habe zusätzlich auf meinem PI, der auch PI-Hole und Nextcloud ist, noch AVAHI installiert für das Multicast und MDNS Reflector aktiviert. (IP des PI 192.168.4.3)

Kann mir jemand bei der Konfiguration des Multicast helfen? Ich bekomme im Log ständig Fehler, das Neighbor not found.

Außerdem wäre es cool, auch das entfernte Netzwerk aus dem FritzVPN zum laufen zu bekommen. :)



This thread was automatically locked due to age.
Parents
  • 0

     do you have an Idea whats the problem, when you look at the screenshots and logs?

  • 0 in reply to superfun2k23

    Well, if removing one of the PI-Hole RPs doesn't resolve this, I'd be tempted to re-image and restore a recent backup.

    I do think you should have someone (maybe you!) familiar with Pi-Hole and FritzBox look around in all three devices to see where multicast is dying.

    MfG - Bob (Bitte auf Deutsch weiterhin.)

     
    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

    I already tried the setup with only one PI-RP. No success.. but Pi-Hole itself has nothing to do with Multicast, as it is only DNS-Service, but the installed ahavi is working fine, it can detect spotifyConnect service on multicast, no matter if PI-RP is in LAN and AVR in WLAN or both in the same network.. it has to do with the UTM itself blocking it.. FritzBox can also is unlikely to cause the issue, because the UTM is setting the network up and manages IP´s via DHCP. the management-lan 172.10.0.0/24 also has nothing to do with LAN or WLAN

Reply
  • 0 in reply to BAlfson

    I already tried the setup with only one PI-RP. No success.. but Pi-Hole itself has nothing to do with Multicast, as it is only DNS-Service, but the installed ahavi is working fine, it can detect spotifyConnect service on multicast, no matter if PI-RP is in LAN and AVR in WLAN or both in the same network.. it has to do with the UTM itself blocking it.. FritzBox can also is unlikely to cause the issue, because the UTM is setting the network up and manages IP´s via DHCP. the management-lan 172.10.0.0/24 also has nothing to do with LAN or WLAN

Children
  • 0 in reply to superfun2k23

    What happens if you disable the other PI-RP?

    I was concerned that there were 8 different "102 Command failed Target" lines in the log above.  That makes me suspect a malfunction or an incompatibility in one of the other devices with UTM's PIM-SM.  Then again, I've never done multicast with anything other than a single Windows server as the PIM-SM RP Router, so maybe someone that's worked more with multicast could put a finger on the problem.

    MfG - Bob (Bitte auf Deutsch weiterhin.)

     
    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

    Ich habe den WLAN-PI-RP mit Anschluss wlan0 vom Raspberry abgeschaltet und zudem in den PIM-SM Einstellungen entfernt.
    Umgekehrt habe ich einfach beim LAN-PI-RP das LAN-Kabel abgesteckt und ihn auch aus den Einstellungen des PIM-SM entfernt,

    also so, das der jeweils entfernte auch nicht mehr per IP ansprechbar war.

    Also hast du das ganze mit einem Windows-Server in einem ähnlichem Umfeld schon funktionsfähig gehabt?

  • 0 in reply to superfun2k23

    Unser Labor:

     <== Es ist einige Jahre her - vielleicht /32 wäre nötig ???

    MfG - 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

    ich habs jetzt nach deinen "Vorgaben" umkonfiguriert und jetzt erhalte ich im Log folgenden Output:

    2023:02:05-20:41:58 utm-home xorp[19986]: [ WARNING xorp_pimsm4 PIM ] JoinDesired(*,G) = true: RP for group 224.0.1.187: not found
    2023:02:05-20:41:58 utm-home xorp[19986]: [ INFO xorp_rtrmgr:19986 RTRMGR rtrmgr/module_manager.cc:101 execute ] Executing module: static_routes (xorp_static_routes)
    2023:02:05-20:41:58 utm-home xorp[19986]: [ WARNING xorp_rtrmgr:19986 XrlFinderTarget obj/i686-pc-linux-gnu/xrl/targets/finder_base.cc:1135 handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "static_routes" does not exist or is not enabled.
    2023:02:05-20:41:58 utm-home xorp[19986]: [ WARNING xorp_rtrmgr:19986 RTRMGR rtrmgr/task.cc:215 xrl_done ] Failed to receive reply, code: 201 Resolve failed retries: 0 max_retries: 30
    2023:02:05-20:41:59 utm-home xorp[19986]: [ WARNING xorp_pimsm4 PIM ] JoinDesired(*,G) = true: RP for group 239.255.102.18: not found
    2023:02:05-20:41:59 utm-home xorp[19986]: [ INFO xorp_rtrmgr:19986 RTRMGR rtrmgr/module_manager.cc:101 execute ] Executing module: fib2mrib (xorp_fib2mrib)
    2023:02:05-20:41:59 utm-home xorp[19986]: [ WARNING xorp_rtrmgr:19986 XrlFinderTarget obj/i686-pc-linux-gnu/xrl/targets/finder_base.cc:1135 handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "fib2mrib" does not exist or is not enabled.
    2023:02:05-20:41:59 utm-home xorp[19986]: [ WARNING xorp_rtrmgr:19986 RTRMGR rtrmgr/task.cc:215 xrl_done ] Failed to receive reply, code: 201 Resolve failed retries: 0 max_retries: 30
    2023:02:05-20:42:00 utm-home xorp[19986]: [ INFO xorp_rtrmgr:19986 RTRMGR rtrmgr/task.cc:2242 run_task ] No more tasks to run
    2023:02:05-20:42:06 utm-home xorp[20018]: [ WARNING xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src = 192.168.4.5 dst = 239.255.255.250 len = 63: no RP address for this group
    2023:02:05-20:42:12 utm-home xorp[20018]: [ WARNING xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src = 192.168.4.5 dst = 239.255.255.250 len = 63: no RP address for this group
    2023:02:05-20:42:18 utm-home xorp[20018]: [ WARNING xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src = 192.168.4.5 dst = 239.255.255.250 len = 63: no RP address for this group
    2023:02:05-20:42:19 utm-home xorp[20018]: [ WARNING xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src = 192.168.4.6 dst = 239.255.255.250 len = 329: no RP address for this group
    2023:02:05-20:42:19 utm-home xorp[20018]: [ WARNING xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src = 192.168.4.6 dst = 239.255.255.250 len = 376: no RP address for this group
    2023:02:05-20:42:19 utm-home xorp[20018]: [ WARNING xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src = 192.168.4.6 dst = 239.255.255.250 len = 320: no RP address for this group
    2023:02:05-20:42:19 utm-home xorp[20018]: [ WARNING xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src = 192.168.4.6 dst = 239.255.255.250 len = 384: no RP address for this group
    2023:02:05-20:42:19 utm-home xorp[20018]: [ WARNING xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src = 192.168.4.6 dst = 239.255.255.250 len = 386: no RP address for this group
    2023:02:05-20:42:19 utm-home xorp[20018]: [ WARNING xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src = 192.168.4.6 dst = 239.255.255.250 len = 374: no RP address for this group
    2023:02:05-20:42:20 utm-home xorp[20018]: [ WARNING xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src = 192.168.4.6 dst = 239.255.255.250 len = 329: no RP address for this group
    2023:02:05-20:42:20 utm-home xorp[20018]: [ WARNING xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src = 192.168.4.6 dst = 239.255.255.250 len = 376: no RP address for this group
    2023:02:05-20:42:20 utm-home xorp[20018]: [ WARNING xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src = 192.168.4.6 dst = 239.255.255.250 len = 320: no RP address for this group
    2023:02:05-20:42:20 utm-home xorp[20018]: [ WARNING xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src = 192.168.4.6 dst = 239.255.255.250 len = 384: no RP address for this group
    2023:02:05-20:42:20 utm-home xorp[20018]: [ WARNING xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src = 192.168.4.6 dst = 239.255.255.250 len = 386: no RP address for this group
    2023:02:05-20:42:20 utm-home xorp[20018]: [ WARNING xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src = 192.168.4.6 dst = 239.255.255.250 len = 374: no RP address for this group
    2023:02:05-20:42:24 utm-home xorp[20018]: [ WARNING xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src = 192.168.4.5 dst = 239.255.255.250 len = 63: no RP address for this group
    2023:02:05-20:42:30 utm-home xorp[20018]: [ WARNING xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src = 192.168.4.5 dst = 239.255.255.250 len = 63: no RP address for this group
    2023:02:05-20:42:36 utm-home xorp[20018]: [ WARNING xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src = 192.168.4.5 dst = 239.255.255.250 len = 63: no RP address for this group
    2023:02:05-20:42:42 utm-home xorp[20018]: [ WARNING xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src = 192.168.4.5 dst = 239.255.255.250 len = 63: no RP address for this group
    wobei 192.168.4.5 mein TV ist (schätzungsweise Netflix, was da Multicast sucht?) und 192.168.4.6 (was der AVR mit SpotifyConnect ist)
    wie müsste ich die Group des RP anpassen, das die dazu passt?
  • 0 in reply to superfun2k23

    noch mehr Erkenntnisse:

    nachdem im Log folgende fehle Groups angemahnt wurden (2023:02:05-20:42:59 utm-home xorp[20018]: G) = true: RP for group 224.0.1.187/239.255.102.18: not found) habe ich sie erstellt:

    224.0.1.187
    239.255.102.18

    zusätzlich habe ich also diese beiden Groups angelegt und die fehlende 239.255.255.250

    nun spuckt das Log gar nichts neues mehr aus, die letzten Zeilen waren:

    2023:02:05-20:47:57 utm-home xorp[20018]: [ WARNING xorp_pimsm4 PIM ] JoinDesired(*,G) = true: upstream neighbor for RP 192.168.4.10 for group 239.255.255.250: not found
    2023:02:05-20:47:58 utm-home xorp[20018]: [ WARNING xorp_pimsm4 PIM ] JoinDesired(*,G) = true: upstream neighbor for RP 192.168.4.10 for group 224.0.1.187: not found
    2023:02:05-20:47:59 utm-home xorp[20018]: [ WARNING xorp_pimsm4 PIM ] JoinDesired(*,G) = true: upstream neighbor for RP 192.168.4.10 for group 239.255.102.18: not found
Unfiltered HTML