danb35 / freenas-iocage-plex

Scripted installation of Plex Media Server in a FreeNAS jail
GNU General Public License v3.0
56 stars 9 forks source link

On a LAGG with a load of VLANS #9

Closed r3m0dul8 closed 4 years ago

r3m0dul8 commented 4 years ago

Anyway I can use this but on a LAGG port that directly connects to VLANs and not to a physical network adapter?

Get this error:

Untitled

r3m0dul8 commented 4 years ago

Have also tried modifying the line in plex-jail.sh

INTERFACE="vnet0"

to reflect my bridge for the vlan I want it to sit on and it couldn't start the vnet as there was an issue with what I had done to it

r3m0dul8 commented 4 years ago

Untitled Sorry, forgot to add the screenshot

r3m0dul8 commented 4 years ago

Also, tried installing on the native LAGG physical adapter it it still refuses to work :( Untitled

thorsteneb commented 4 years ago

When you manually create a jail, what options do you use to do that? Checkboxes, interfaces chosen, values, vlan, and so on.

It's quite possible the script needs changes to become vlan-aware.

r3m0dul8 commented 4 years ago

Untitled Untitled1 Untitled2

Last one shows the vlan ID it is attached to through a bridge that sits on the LAGG port

This was taken from a active working plex server in TrueNAS 12.1

Hope this helps (sorry for delay)

thorsteneb commented 4 years ago

It helps. This will take a bit of testing. The script doesn't support DHCP; does your network allow static IPs?

In the meantime, you can just manually create a jail, run pkg install plexmediaserver and sysrc plexmediaserver_enable="YES", mount in your media, and you are up and running.

If so desired, you could also create an external dataset to hold your configuration data, rsync -ha those metadata over from the current jail, run 'mkdir /config' in the new jail, mount the external dataset there, and then as a last step point Plex to that location with sysrc plexmediaserver_plexpass_support_path="/config"

r3m0dul8 commented 4 years ago

Hi

I'm using a PfSense firewall and it doesn't play well with static IP's - a lot of faffing around to get them working and as I control all network traffic through this, I'd rather just keep it super simple.

Unless there is a way that I can get the MAC address before, then I can add and assign the IP before the jail connects to the network.

danb35 commented 4 years ago

I'm using a PfSense firewall and it doesn't play well with static IP's

Nonsense, pfSense plays perfectly well with static IPs (I know, I'm using it). Just leave some space in your DHCP reservation range (so rather than giving it a range of .2 to .254, give it a range of .100 to .250). You can set static IPs in .2 to .99.

r3m0dul8 commented 4 years ago

I'm using a PfSense firewall and it doesn't play well with static IP's

Nonsense, pfSense plays perfectly well with static IPs (I know, I'm using it). Just leave some space in your DHCP reservation range (so rather than giving it a range of .2 to .254, give it a range of .100 to .250). You can set static IPs in .2 to .99.

Granted, so my question would be does setting said static IP range accommodate acme certs and internal DNS assignment?

I've just got too many IP addresses to remember and I prefer to use DNS resolver internally over remembering IPs, they just look so much more fancy too lol

I mean, fair point but is it really so hard to get the script to use DHCP?

thorsteneb commented 4 years ago

Enabling DHCP in the script is likely not too difficult. In the meantime, you can very easily do what the script does manually, that’ll be quicker than trying to get the script to work in your specific environment.

danb35 commented 4 years ago

does setting said static IP range accommodate acme certs and internal DNS assignment?

Of course it does. ACME certs aren't affected in the least, and I have no idea where that question would even come from. Internal DNS assignments are trivial--go to Services -> DNS resolver and add host overrides as needed.

r3m0dul8 commented 4 years ago

No worries, I'll just stick to the official plug-in. Seems to work fine and without needing to assign anything manually.

I did try to run the commands independently but it didn't want to work - it's why I reported it. Will try what you originally suggested next time (if) I have to do a re-install as I really like the idea to have all the metadata and settings saved elsewhere to prevent having set everything back up again.

Thanks again for the suggestions, even if I didn't quite get round to using it, heard many good things about your repo so wanted to give it a whirl.