Who is agent 'Lavf/56.36.100' ?

[keijo]

I have that user-agent popping in an out my dnas every few seconds, from a few different IPs across Europe. It connects for 1 second and closes right away.

Anyone to shed some light?

TIA

keijo.-

[dopelabs]

libavfilter

anyone with vlc or ffmpeg or mpv or IINA or any other tool that relies on libavfilter.

its prob just something to grab metadata and/or test to see if the stream is up.

[keijo]

Thank you, dopelabs. Your response is blazing fast and straight to the bone.

What puzzles me is that it connects using SHOUTcast 1, and the same IPs ring: 2 connections from Belgium and the Netherlands, 3 from Switzerland, and 1 host that belongs to (allegedly) a German-ish UnityMedia.

Anyway, I'll let it be, since it's not causing any serious harm, just curious if there was any info about them.

Regards,
keijo.-

[djSpinnerCee]

lavf ua is also sometimes the tunein.com app...

[dopelabs]

I have found that tune in usually includes their name in the user agent... I have all kinds of 'revolving door' connections to my streams. people have players embedded in multiplayer games that trigger on proximity to the in game object where the player is embedded.. in this use case, its a car stereo, which as the car moves, and becomes within ear shot of other players in the game, it forces their machine to tune into the stream server.. as you can imagine as people drive around heavily populated areas, its almost like a mass flood of tune ins followed immediately by timeouts. its kind of clever, but could have been implemented in a much nicer way by having the game server act as a local proxy for any in game streams, thus the players only need to use the existing connection to the server, and its only a single connection from the game server to my stream. buuuut thats in a perfect world.

you shouldn't be seeing different geo location data for a single client ip. if you are, and your sure its the same ip, id like to investigate further because that could be a bug.

for the most part, unless they are using Winamp, your not going to see many v2 protocol connections to a v2 dnas... basically dnas v2 and the protocol v2 came out and there was an overwhelming lack of encoders and streaming tools developed for the v2 protocol that the DNAS implemented a bunch of stuff to still support v1 encoders and broadcasting tools...