Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 15 replies
  • Subscribers 1 subscriber
  • Views 13583 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

SSDP (UDP 1900) over L2TP VPN Connection

busthead
Hello,

I wish to control my Sonos audio system remotely via iPhone.

I've configured and successfully connected to my Astaro via L2TP over IPSec. The iPhone is assigned 192.168.0.2 address from custom VPN Pool. This is the same subnet as my local home network on which the Sonos boxes reside.

I am able to ping my Sonos boxes from the iPhone when connected via VPN.

The Sonos app uses SSDP (UDP port 1900) to destination 239.255.255.250 (broadcast) to detect the Sonos boxes.

I ran Wireshark on my local network and was not able to see any SSDP traffic from the iPhone.

Thus, my question is, what is preventing SSDP packets originating from my iPhone from reaching my local network? 

Much thanks,
Scott


This thread was automatically locked due to age.
Parents
  • 0
    No, not confused, just ignorant by choice! [;)]

    Assigning an address within 'Internal (Network)' to a remote user works sometimes.  In this case, I suspect that all will work correctly if you'll just change the 'Pool network' back to 'VPN Pool (L2TP)' with 10.242.3.0/24.  If that doesn't solve the problem, then look at the Packet Filter and Intrusion Prevention logs.  If you still can't see the issue, then I'm out of guesses.

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Reply
  • 0
    No, not confused, just ignorant by choice! [;)]

    Assigning an address within 'Internal (Network)' to a remote user works sometimes.  In this case, I suspect that all will work correctly if you'll just change the 'Pool network' back to 'VPN Pool (L2TP)' with 10.242.3.0/24.  If that doesn't solve the problem, then look at the Packet Filter and Intrusion Prevention logs.  If you still can't see the issue, then I'm out of guesses.

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Children
No Data
Unfiltered HTML