Scheduled maintenance on Saturday, August 8th from 7am to 10am (UTC). Licensing registrations and key activations will be unavailable during this period. More info here.
We'd love to hear about it! Click here to go to the product suggestion community
I have a silly problem... maybe I'm wrong, but I don't know how to workaround that.
I have a device that discover the master device by 188.8.131.52:1900 multicast
The master device is in the Head office and this other device is here in the breach.
We are connected by IPSec IKEv2 (both by sophos v18) but the device don't see the master device.
I tried also Multicast route but nothing.Any suggest?
Could I extend the network mask? How?
How is the IPSec created? Policy-Based? Route-Based? 0.0.0.0?
How are you routing or how did you try routing?
In reply to Antonio Cienfuegos:
Brench sideLocal subnet:
Head side:Local subnet:
and both side Multicast routing enabled and setted.
On breanch side vs IPSecOn Head side vs Port4: 10.0.99.0
I think I did the righ configuration, but didn't work.
In reply to cyberguy:
The Multicast IP in the route should be 184.108.40.206. No idea if this will work though.
An alternative approach would be to enable and configure PIM.
In reply to ChrisKnight:
in the multicast route was 250...
I didi some test and edited in 255, but I tried both
220.127.116.11 and 18.104.22.168, nothing to do.