You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I welcome the possibility to choose a specific network interface in the form:
source: udp://238.0.0.1:1234?interface=eth0
It is very good feature. Thank you very much.
When use only:
source: udp://238.0.0.1:1234
MediaMTX tries to get the source on all network interfaces.
However, perhaps the current behavior when the interface at the source is not defined should be different.
For example, the vlc uses the system routing table when choosing the interface at multicast.
Test with vlc:
test
$ vlc udp://@238.0.0.1:1234
$ ip maddr
...
2: eth0
inet 238.0.0.1
...
test
$ sudo ip route add 238.0.0.1/32 dev eth1
$ vlc udp://@238.0.0.1:1234
$ ip maddr
...
3: eth1
inet 238.0.0.1
...
I think that more tools in Linux behave like this (for example ffplay too: ffplay udp://238.0.0.1:1234).
vlc probably does something like this when choosing an interface:
$ ip route get 238.0.0.1
MediaMTX should respect the routing table just as vlc, ffplay and other tools do.
MediaMTX's current behaviour of trying to get video from all interfaces could then be set as follows:
source: udp://238.0.0.1:1234?interface=ALL
Although someone might be upset that it's a change in behavior.
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Which version are you using?
mediamtx_v1.12.2_linux_amd64.tar.gz
Which operating system are you using?
Linux amd64 standard
Describe issue
I welcome the possibility to choose a specific network interface in the form:
source: udp://238.0.0.1:1234?interface=eth0
It is very good feature. Thank you very much.
When use only:
source: udp://238.0.0.1:1234
MediaMTX tries to get the source on all network interfaces.
However, perhaps the current behavior when the interface at the source is not defined should be different.
For example, the vlc uses the system routing table when choosing the interface at multicast.
Test with vlc:
test
$ vlc udp://@238.0.0.1:1234
$ ip maddr
...
2: eth0
inet 238.0.0.1
...
test
$ sudo ip route add 238.0.0.1/32 dev eth1
$ vlc udp://@238.0.0.1:1234
$ ip maddr
...
3: eth1
inet 238.0.0.1
...
I think that more tools in Linux behave like this (for example ffplay too: ffplay udp://238.0.0.1:1234).
vlc probably does something like this when choosing an interface:
$ ip route get 238.0.0.1
MediaMTX should respect the routing table just as vlc, ffplay and other tools do.
MediaMTX's current behaviour of trying to get video from all interfaces could then be set as follows:
source: udp://238.0.0.1:1234?interface=ALL
Although someone might be upset that it's a change in behavior.
The text was updated successfully, but these errors were encountered: