Hank Moody

Members
 View Profile  See their activity

  • Posts

    10

  • Joined

  • Last visited

 Content Type 

Posts posted by Hank Moody

    [Plugin] Plex Streams

    in Plugin Support

    Posted

    hey dorgan, nice plugin! Found it through a screeny on /datahoaders

     

    I have similar problems as polishprocessors (p7) like I cannot get my server listed.

     

    Getting the token from plex stops the spinning wheel without a server listed; I have it under custom ip with port, tried /web and http.

     

    While signing in on plex I've seen that plex sees my server on zeus.home.arpa, tried it over the corresponding 10.1.30.0/24 network, no dice and still "There are currently no active streams"

    > /plugins/plexstreams/getServers.php?useSsl=1

    {"serverList":{"XXX":{"Name":"HERMES","Identifier":"XXX","Connections":[null]}}}

    I'm stuck, could we look into this? 🤪

    Wake on Lan for Virtual Machines for 6.1+

    in Plugin Support

    Posted

    Thanks for this missing piece of software! 

    I read the entire thread; I have only installed python2-2.7.18-x86_64-4.txz, have setup the default bridge (br1.30) in vm-manager and your pkg shows "running" - but nothing.

    The machine in case is a win10-vm which had it enabled as baremetal; as vm now there's no wol-option in the adapter-configuration within windows itself, and accessing the BIOS doesn't give me a wol-option, neither machine-type i440fx-4.2 nor q35-4.2.

    I'm trying to wake the machines up from the fw/pfsense directly, no dice.

     

    How could I troubleshoot furhter? Does the default vm-bridge have to be on the vlan where the vms sit i.e. br1.3 or on the general interface br1?

    Thanks for your time!

    [Support] spikhalskiy - ZeroTier

    in Docker Containers

    Posted · Edited by Hank Moody

    2 hours ago, Ford Prefect said:

    ...so, this has moved since last time.

    Nevertheless, this means that from inside your ZT-network, each ZT-client will have to use IP 192.168.191.2 as gateway for any host or network you would like to access via the ZT-docker.

    Do I have to toggle anything in the ZT-Clients or is this done via ZT-Central?
    TM9am0d.png

     

    Quote

    just to clarify...vlan-90 also resides somewhere in your network and this client will connect, when on a premise local to that network i.e. via WLAN to vlan-90 or will it use a VPN as well when abroad?

    This is a local vlan, every client when away would connect via ZT.

     

    Quote

    When abroad, what networks will it connect to simultaneously - vlan-90 via VPN *PLUS* ZT via zt-client or only one at a time?

    ^Only one at a time

     

    Quote

    When connected to vlan-90 only, do you wish it to be able to connect to plex as well?

    When I'm connected to vlan90 locally I have the fw-rules allowing me access to plex on vlan30

     

    Quote

    OK, this is the one parent, with a remote devioce that should be able to access plex, right?

    Exactly

     

    Quote

    Also: ZT is not doing NAT, so ZT clients will connect to any service with IPs from the 192.-168.191.0/24 range.

    So you want pfsense to allow traffic originating from 192.168.191.0/24 and destination 10.1.30.1 (plex)

    I tried my best, is this rule ok?
    Alias zt_net_plex = 192.168.191.0/24
    Alias media = 10.1.30.1

    I'm unable to ping plex over zerotier..:/

    HcZTREq.png

     

    Quote

    ...then, in ZT central add a single route to the plex host 10.1.30.1/32 with gateway 192.168.191.2 (which is your zt-docker).

    Note: since plex-docker and zt-docker do reside on the same unraid box, unraid (might) have a direct/local route available.

    See my next response, below.

    qlOJeQA.png

    Quote

    please Check the routes on unraid host (what is the output of "route -n" via command line)?

     

    We need to find out which path packets from zt-clients go when trying to reach plex and also which way return packets from plex go, trying to get back to a zt-client. Here the correct gateway is 10.1.100.201 (the "iunraid"-side/IP of your zt-docker). 

    All will depend on the routing table if unraid can identify the route/path locally or will use the default gateway (your pfsense).

    ExXgjpR.png

    FYI I'm using 3 eth-ports, whereas only port-1 is used/bridged for docker;
    - I have absolutely no clue where 172.17.0.0 and 192.168.122.0 come from (sweating a little bit..)


    Man, THANK YOU!! :) I owe you a lot

    [Support] spikhalskiy - ZeroTier

    in Docker Containers

    Posted · Edited by Hank Moody

     Sorry for not getting back any sooner, I really tried it a lot of times but can't get to the desired results; to recap: 

    On 3/23/2021 at 2:04 PM, Ford Prefect said:

    So 10.1.30.249 is the ZT-Client / the ZT-Docker IP on your unraid host?

    What network did you choose as transfer network in ZT central?

    The ZT-Node/docker resides on my unraid-box with a bridged-connection

    - 10.1.100.201 vlan-100

    - ZT-IP 192.168.191.2

     

     

    Quote

    Do you have another client, like a laptop and installed the ZT-client on it and are you able to connect and ping the 10.1.30.249 IP or any other IP on your VLAN3??

    Preferably from outside of your own network, via a 3G/4G connection or remote (W)LAN at a friend's or family place?

     

    This would be the first step you need to achieve.

    I have 3 ZT-Nodes

    - ZT-Docker on unraid

    --10.1.100.201 vlan-100

    --ZT 192.168.191.2

     

    - ZT-App on Windows

    --192.168.90.1 vlan-90 / Mobile 4G Hotspot

    --ZT 192.168.191.3

     

    - ZT-App on Android

    --Mobile 4G

    --ZT 192.168.191.4

     

    All on Version 1.6.5, Online, with Public-IP listed (wasn't the case when the zt-docker was in a vpn'd vlan);

    All devices can ping each other trough their ZT-IP with ping not higher than 128ms.

     

    Quote

    Zero-Tier is a LAN...in order to limit access to individual hosts in a network/LAN behind a zt-client, you should put the zt-docker in an additional, separate (V)LAN, different from VALN3 and let the firewall rules in your pfense decide which hosts are reachable/allowed from that zt-(V)LAN into your VLAN3.

    My Plex-Server on unraid

    - 10.1.30.1 vlan-30

     

    My ZT-Node on unraid

    --10.1.100.201 vlan-100

     

    pfSense let's pass traffic from vlan-100 to Plex-IP in vlan-30; this is now setup and working without problems. The ZT-docker can ping Plex.

     

    Quote

    Example (your zt-network IP in the range of 192.168.99.0/255.255.255.0):

     

    Your PFsense/VLAN3 (10.1.30.1) - zt-docker (10.1.30.249 + zt-net-ip 192.168.99.2) - zt-central - zt-client-Laptop (zt-net-ip 192.168.99.22 - LAN-IP 192.168.1.120) - remote LAN gateway (192.168.1.1)

     

    So, for the laptop to be able to reach your VLAN3, define (in ZT-central) the route to 10.1.30.0/24 with gateway=192.168.99.2 and of course the other path for returns (net 192.168.1.0/24 with gateway 192.168.99.22)

    But wait, this is only half of the story ;-)

     

    ...second half of the story:

     

    In order for IP packets to be able to reach in return from VLAN3 -net back to remote LAN 192.168.1.0/24, of course the router which is hosting VLAN3 needs to know the routes to zt-central (using the zt-client docker IP as gateway) as well.

    That means, your pfsense needs to be part of the game as well ;-)

    And should you wish the same for more hosts on the remote network and not just the laptop running zt-client, the remote router as well (which would form a true site2site connection)

     

    That is the proper way of doing it, I think and also easier to maintain, should things change.

     

    ...I hope I was able to shed same light to the story. However, I will/can not help with your pfsense...I am a Mikrotik person ;-)

    And here I'm stuck: In my desired scenario I'd like to have this one and only ZT-Node/docker to route all the other ZT-Nodes to my Plex instance; as much as I understand from your statements (marked bold) do I need to setup a route for every node I let into my private-sdn?

     

    In it's core all I want to accomplish is to use the ZT-Node on Unraid (vlan-100) let all other ZT-Nodes access Plex (vlan-30) without much more than confirming those ZT-Nodes in ZT-Central.

    Thanks for your help so far @Ford Prefect!

    Thanks a lot for reading so far

    [Support] spikhalskiy - ZeroTier

    in Docker Containers

    Posted · Edited by Hank Moody
    Tipo

    So I'm rereading this topic the 7th time in 7days with no end in sight. My main goal is to open Plex for friends with granular control.

     

    A handful of good friends are parents now too and as they discovered my Kids Video Collection (damn those VHS rips) they'd love to be able to give their kids those programs too instead of the utter BS that's running on TV nowadays.

     

    I have pfsense/baremetal running 12vlans and a 100/60 connection.

     

    VLAN 3 (10.1.30.0/24) is the Vlan where my Plex Servers reside (10.1.30.1 & 10.1.30.2). On the same Vlan there are 2 Steam Machines (10.1.30.40 & 10.1.30.41) I'd also like to 'share'.

     

    My ZT resides in above Vlan3 (10.1.30.249), and with this Docker I'd just want to share Plex/Steam.

     

    To my understanding it would be possible to use ZT for multiple Vlans, but for simplicity I'd rather start with one Vlan properly set-up 😅

     

    As said above I read the entire thread couple of times, especially the posts of @Ford Prefect

    about adding routes, but: I intend to only add certain hosts from the Vlan, not the entire network.

     

    Where do the routes have to go? Only ZT-Central? Or do I need to tweak pfsense/vlan-rules too?

     

    I'm at a loss and every help is much appreciated! Especially how the routes should look like as I had a HARD time setting pfsense up.. 🤣

     

    Kind regards,

    Hank

    PCIe Intel I350-T2 'Port Down' after reboot (bond+bridge)

    in Pre-Sales Support

    Posted · Edited by Hank Moody
    attachement/network-settings

    Hey guys,

    after having pretty much everything setup (for the 3rd time) I'm now definitely stuck.


    -nic1 onboard
    -nic2 I350
    -nic3 I350

     

    nic 1 got a static IP
    nic 2+3 are bond and bridged; switch is properly setup [switch:static-lag - unraid:round-robin]

     

    and this works until the server is rebooted, then the bond/I350-T2 won't come up automatically.

     

    I know of the concept of a server but however I can't always hookup a screen to start in the GUI to 'port-up'., and it's not the time yet for a kvm-switch.

     

     

    The host is temporarily in my home-office, but will move sooner or later, so I have to figure this out:

    There is a second card coming, the goal would be to bond all 5 together, and connect that to a 1/5/10G switch.

     

    So the cards are pcie_x2, fitted in a x1 slot, working perfectly:
    pc:pcie3_x1 / card:pcie2_x2
    breakdown:
    1 ethernet-port is at max. pulling 250MB/s (125MB/s upstream - 125MB/s downstream) so one card is pulling 0,5GB/s which is the max. of pci2_x1

     

    I'd like to achieve that the ports stay up due reboots. 10G card isn't a solution due to no available slots left.

     

    > In the mainboard-bios I deactivated network-boot (as I've read it here somewhere)
    > I saw that the Intel-I350 has a bios splash-screen /CTRL+S/ entered, couldn't uncheck the possibility to 'pxe-boot'.

    So now I may got a hint, could flashing the card be a thing?


    Has anybody input how I could proceed, what to try next?
    This is driving me nuts. (Tagged the title appropriately so whoever comes after me has a better time finding a solution) 

     

    Thanks in advance for any input! After this I'm sold to the pro-version

     

    PS: Will attach logs asap

     

    Kind regards

    screencapture-kaby-Settings-NetworkSettings-2021-02-18-19_09_59.png