1 |
On 2020-08-13, Sid Spry <sid@××××.us> wrote: |
2 |
> On Thu, Aug 13, 2020, at 4:33 PM, Grant Edwards wrote: |
3 |
>> How does one hide a network interface from a badly-written application? |
4 |
>> |
5 |
>> I'm using Plex Media Server as a DVR, it it seems to have been written |
6 |
>> by Windows programmers who assume that your computer exists for no |
7 |
>> purpose other than running their program and their program alone. It |
8 |
>> spews multicast and broadcast packets on all network interfaces |
9 |
>> regardless of which interface you configure it to use. |
10 |
>> |
11 |
>> Is creating a network namespace that contains only the interfaces Plex |
12 |
>> is allowed to use the best way to try to fix this problem? [Assuming |
13 |
>> the developers won't do anything about it.] |
14 |
> |
15 |
> Yes, though you typically have to go out of your way to select a single |
16 |
> interface. |
17 |
|
18 |
I'm not sure what "go out of your way" means in this context. I |
19 |
assume I'd create a network namespace for Plex, and then use either |
20 |
macvlan or ipvlan to share one of the physical interaces between the |
21 |
root namespace and the Plex namespace. I'd like the 'lo' interfaces |
22 |
to be shared as well, but I'm not sure that's possible. |
23 |
|
24 |
> Have you filed a bug report? Can you link to it? |
25 |
|
26 |
People have been complaining to upstream devs about this for years, |
27 |
and nothing's been done. I posted a question the Plex forum about it, |
28 |
but I doubt anybody will pay any attention. (Plex doesn't seem to use |
29 |
any sort of bug reporting or tracking system). |
30 |
|
31 |
-- |
32 |
Grant |