Dear all
Since I have changed from latest Astaro to the first Sophos release I face a strange behaviour with particular audio streams (not all).
I have this stream http://87.98.219.160:20000 (Italian online radio Vicenza Radio Star).
It starts playing as expected but stops after one, maybe two minutes. Most of the time.
I do not have related errors in the logs nor does this occur with other streams.
I didn't care much and expected the failure at the Italian end until today, where Apples Facetime showed the very same behaviour: the connection was established for about one minute and then stopped. Its not behaving like a bandwidth issue: the quality (also for above issue) remain perfect until the sudden drop.
Sure, this too could be an issue at the other end... but it feels like at my end. Ahyes, stream caching/scanning is sure disabled in the firewall.
Does someone experience similar issues?
Kind regards
Oliver
p.s
I did follow-up on the below ideas with no result so far:
... so, new ideas are welcome :-)
Since I have changed from latest Astaro to the first Sophos release I face a strange behaviour with particular audio streams (not all).
I have this stream http://87.98.219.160:20000 (Italian online radio Vicenza Radio Star).
It starts playing as expected but stops after one, maybe two minutes. Most of the time.
I do not have related errors in the logs nor does this occur with other streams.
I didn't care much and expected the failure at the Italian end until today, where Apples Facetime showed the very same behaviour: the connection was established for about one minute and then stopped. Its not behaving like a bandwidth issue: the quality (also for above issue) remain perfect until the sudden drop.
Sure, this too could be an issue at the other end... but it feels like at my end. Ahyes, stream caching/scanning is sure disabled in the firewall.
Does someone experience similar issues?
Kind regards
Oliver
p.s
I did follow-up on the below ideas with no result so far:
- high memory or CPU consumption during streaming:
no - FW ignores "do not scan streams" setting for manually added rules:
not yet confirmed but my best guess - "unlucky" caching at recepient or Sophos Firewalls:
This might be an indicator. At least for the stream it is possible that the duration before the failure matches the receivers cache time.
... but why does the firewall then drop? That comes to my next guess. - Port ranges change to something of range after caching:
This could be but I didn't came further. My early investigations made me assume, that the ports change after the receivers cache was empty and needed to re-establish the connection. Although, the new port was within the allowed port range, the FW dropped it. This was visible in the logs. Unfortunately not reproducible right now. I didn't proceed with that guess as it does not happen to other streams.
(and I have never heard of such a setting of changing ports after an established connection)
... so, new ideas are welcome :-)