Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
mhammond1
New Contributor

SiriusXM Player won't stream through Fortigate 100F

We've been having issues getting a SiriusXM player to stream audio when connected to our network and Fortigate 100F and 200F firewalls running 7.2.12 build 1761 firmware. We have created a Firewall Policy for the device that Allows all traffic, with security profiles removed and no SSL inspection. DNS Helper has also been disabled for diagnostic purposes, and we are using external DNS (8.8.4.4 and 1.1.1.1). When checking Forward Traffic logs, we see no traffic being Denied, but the player will not stream audio. We verified the traffic for the device is using the Policy that has been created for it. When connecting the device to a wireless hotspot, the audio streams properly.

 

Below is a sample flow debug:

id=65308 trace_id=1 func=print_pkt_detail line=5813 msg="vd-root:0 received a packet(proto=6, x.x.x.x:35366->34.215.0.215:443) tun_id=0.0.0.0 from VLANx. flag [.], seq 288633703, ack 3087288262, win 1503"
id=65308 trace_id=1 func=resolve_ip_tuple_fast line=5901 msg="Find an existing session, id-0b663ace, original direction"
id=65308 trace_id=1 func=npu_handle_session44 line=1207 msg="Trying to offloading session from VLAN1833 to port13, skb.npu_flag=00000400 ses.state=00002204 ses.npu_state=0x00023094"
id=65308 trace_id=1 func=fw_forward_dirty_handler line=437 msg="state=00002204, state2=00004301, npu_state=00023094"
id=65308 trace_id=1 func=__ip_session_run_tuple line=3400 msg="SNAT x.x.x.x->y.y.y.y:35366"
id=65308 trace_id=1 func=np6xlite_hif_nturbo_build_vtag line=1229 msg="vtag->magic d153beef, vtag->coretag 84, vtag->vid 0
vtag->sip[0] 7a978d20, vtag->sip[1] 0, vtag->sip[2] 0, vtag->sip[3] 0
vtag->sport 9866, vtag->mtu 1500, vtag->flags 2, vtag->np6_flag 0x0, skb->npu_flag=0xc0c80"

1 Solution
mhammond1
New Contributor

Turns out the issue was Google DNS related, so switching the primary DNS to Cloudflare (1.1.1.1) resolved the issue.

View solution in original post

2 REPLIES 2
AEK
SuperUser
SuperUser

Does it use multicast?

AEK
AEK
mhammond1
New Contributor

Turns out the issue was Google DNS related, so switching the primary DNS to Cloudflare (1.1.1.1) resolved the issue.

Announcements
Check out our Community Chatter Blog! Click here to get involved
Labels
Top Kudoed Authors