Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added section about non --net=host networking #88

Closed
wants to merge 1 commit into from
Closed

Added section about non --net=host networking #88

wants to merge 1 commit into from

Conversation

whi-tw
Copy link

@whi-tw whi-tw commented Jan 13, 2017

I've found I needed this, as all traffic was routing externally, causing havoc with stream quality and download caps.

--net=host is great, but I'm running openHAB on the same server, so this is a necessity.

This information comes from #36 but could probably do with being added to the readme.

I've found I needed this, as all traffic was routing externally. This information comes from #36
@LinuxServer-CI
Copy link
Contributor

Can an admin please whisper to jenkins to test this PR.

@sparklyballs
Copy link
Contributor

we've been discussing an overhaul of sorts on our README's en masse.

@ghost
Copy link

ghost commented Mar 29, 2017

Thank you for the instructions 👍

@lonix
Copy link
Contributor

lonix commented Apr 28, 2017

@sparklyballs I think this PR should be accepted in the interim. This info is very useful.

@lonix
Copy link
Contributor

lonix commented Nov 10, 2017

Is this PR just gonna linger for ever ?, at this point decline it, if you dont want it.
@sparklyballs

@LinuxServer-CI
Copy link
Contributor

Can an admin please whisper to jenkins to test this PR.

@bentech
Copy link

bentech commented Feb 27, 2018

Can't you just set your 'LAN Networks' under Settings->Server->Network?

e.g. '192.168.0.0/16'

@whi-tw
Copy link
Author

whi-tw commented Feb 27, 2018

Can't you just set your 'LAN Networks' under Settings->Server->Network?

e.g. '192.168.0.0/16'

For sure, that's a setting within Plex, but it doesn't have the same effect. Without customConnections, PMS isn't aware of the correct server IP - only the bridged IP.

As far as I can see, clients use this setting - it is the IP that they use to test if the server is local or not.

This setting is used in the official plexinc container and has been documented as a solution in another issue on this repo: #97

As this seems to be a confirmed issue, it could be an idea to do something along the lines of the 'official' container wrt handling this config modification using env vars.

@stefangordon
Copy link

stefangordon commented May 2, 2018

Oh, this information is hugely important and -net=host isn't always practical (not even possible on Docker For Mac). Why not merge it?

Been trying to figure this out for days.

@aptalca
Copy link
Member

aptalca commented Feb 27, 2019

I'm not in favor of encouraging users to manually edit their preferences.xml as that is managed by plex itself. If users want to go ahead and do it, they are taking that risk.

We are considering adding the plex claim token to enable server claiming in circumstances where net=host is not a possibility.

But we have been slammed with other work lately (multi-arch images, new pipeline for jenkins, rebasing to alpine 3.9 & ubuntu bionic, etc.)

@aptalca aptalca closed this Feb 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants