Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Alexa Voice and Video Calling and Ring Video Doorbell + pfSense 2.3.4+

    Firewalling
    2
    2
    1.0k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • K
      khrystoph
      last edited by

      Hi All,

      I've now tried this with both pfSense 2.3.4 and 2.3.5-dev branch. Streaming works properly for things like Netflix, Amazon Prime Video, and DirecTV Now. However, since setting up my pfsense router, I have not been able to get INBOUND Amazon Alexa calls nor have I been able to view the video from my Ring Video doorbell or see events show up (ie. doorbell rings and motion events) in my account via my phone (out on public internet).

      Outbound Alexa calls, inbound Alexa calls over the wifi, and push notifications for the Ring doorbell all work (the push notifications part is strange since it never gets to the account as an event history item).

      Despite adding both inbound and outbound rules to allow tcp and udp ports for the Alexa service, it still throws errors like this one:
      Jul  3 01:10:30 pfSense filterlog: 126,16777216,,1499034557,ix0,match,block,in,4,0x0,,64,12896,0,DF,6,tcp,71,192.168.x.x,72.21.207.109,45182,443,31,PA,2731921050:2731921081,633785117,1506,,

      From what I can tell of reading this log, it's trying to reach out to Amazon EC2 (duh, Amazon Echo uses Amazon IPs to handle various skills, whether built-in or custom skill). It also looks like this is for SOME reason, being blocked for outbound…though, I wasn't aware of outbound traffic being blocked by pfsense.

      Does anyone have any clues/suggestions on why this may be happening? I think the Ring issue and the Amazon Echo issues are related...see, I made a pun about Related/Established. ;)

      1 Reply Last reply Reply Quote 0
      • DerelictD
        Derelict LAYER 8 Netgate
        last edited by

        Blocked PA traffic:

        https://doc.pfsense.org/index.php/Why_do_my_logs_show_%22blocked%22_for_traffic_from_a_legitimate_connection

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.