1 |
On Thu, Aug 13, 2020, at 5:03 PM, Grant Edwards wrote: |
2 |
> On 2020-08-13, Sid Spry <sid@××××.us> wrote: |
3 |
> > On Thu, Aug 13, 2020, at 4:33 PM, Grant Edwards wrote: |
4 |
> >> How does one hide a network interface from a badly-written application? |
5 |
> >> |
6 |
> >> I'm using Plex Media Server as a DVR, it it seems to have been written |
7 |
> >> by Windows programmers who assume that your computer exists for no |
8 |
> >> purpose other than running their program and their program alone. It |
9 |
> >> spews multicast and broadcast packets on all network interfaces |
10 |
> >> regardless of which interface you configure it to use. |
11 |
> >> |
12 |
> >> Is creating a network namespace that contains only the interfaces Plex |
13 |
> >> is allowed to use the best way to try to fix this problem? [Assuming |
14 |
> >> the developers won't do anything about it.] |
15 |
> > |
16 |
> > Yes, though you typically have to go out of your way to select a single |
17 |
> > interface. |
18 |
> |
19 |
> I'm not sure what "go out of your way" means in this context. I |
20 |
> assume I'd create a network namespace for Plex, and then use either |
21 |
> macvlan or ipvlan to share one of the physical interaces between the |
22 |
> root namespace and the Plex namespace. I'd like the 'lo' interfaces |
23 |
> to be shared as well, but I'm not sure that's possible. |
24 |
> |
25 |
|
26 |
Sorry, I meant go out of your way to select more than one interface. I'm |
27 |
genuinely confused anyone would ever do that let alone Plex. |
28 |
|
29 |
Yes, you're right (as far as I know). You might wish to see if Plex has a |
30 |
premade container built. I typically don't like them, but it will save you |
31 |
a fair bit of work if it exists. |