RifleJock

Members
  • Content Count

    35
  • Joined

  • Last visited

Community Reputation

1 Neutral

About RifleJock

  • Rank
    Newbie
  • Birthday 11/08/1995

Converted

  • Gender
    Male
  • Location
    United States

Recent Profile Visitors

550 profile views
  1. So there is a big difference here... Your physical environment, and your virtual one. All things done within UnRAID are considered your virtual environment, and everything outside of that is considered your physicals. You can either setup UnRAID to have a L2 interface, of which you pass through as a bridge to your virtualized Palo Alto. (There wouldn't be much of a point in running a L2 within Palo if this is the case.) This will allow your Palo to communicate only on that physical L2 interface of UnRAID when trying to communicate with anything else on that same L2 interface in your physi
  2. https://www.youtube.com/watch?v=LkW3niAWAHs https://forums.unraid.net/topic/50882-guide-custom-vm-icons-automatically-downloaded-and-installed-to-unraid/ So, you have several physical interfaces in UnRAID, you can set these to their own VLAN in unraid, and then assign the bridge to Palo. You can also edit the xml I believe to be a different type of interface, rather than inet. Otherwise, just put a managed L2 switch next to your unraid box, and trunk your interfaces to Unraid.
  3. Not exactly, the most recent post made by me I believe is the only thing seen on unraid's forum about Palo setup process. One thing to mention, that might not have been mentioned before is the licensing, if you are going to make this a legit license, you MUST not remove the UUID in your xml file for the device, as Palo Licensing is near impossible to move once established. Save a copy of it somewhere.
  4. Nope, never did get this working. My USB ID's seem to be stable now however, and don't change at all. But the plugin still doesn't seem to ever detect any of the PSU's. -Jockie
  5. Let me first start off by describing the issue I face. I'm a hardware/networking kinda guy. I don't really know much when it comes to software/programming. In attempts to create my own user script, I faced numerous hurdles that I just simply don't know how to solve. Rather than creating a bandage for the issue I face, a simple resolve would be to create a simple fix to the already existing mechanics/programming that exists within the VM Settings of Unraid. Here's the concept of my script: When ran: 1. It would go to the variable for the default ISO storage path, of w
  6. So, I've got a bit of a weird situation. I do need assistance with setting this up as well. Not sure what I'm missing but I can't seem to figure out how to get the plugin to point to the correct device. Also, I happen to be running 3 AXi power supplies, thankfully all different wattage capabilities or I fear that might make things more complicated. Is there a way to setup multiple versions of this plugin to run at once so that I may monitor all three power supplies? By process of elimination, I unplugged one by one the usb to these PSU's to determine the correct device id.
  7. I re-downloaded a new instance of Version: 6.9.0-beta25 to my flashdrive after a clean wipe/reformat/reinstall. (also went through the website to re-register the flashdrive with the new install). I did some configuring and re-configuring, a few crashing and rebooting. At some point, not sure when. I think either I renamed my cache pool to nvme pool or it just strait up went missing. All my data and disks still exist fine. But I noticed after getting CA Fix Common Problems that the top alert stated that I wasn't using VMs share/dir on my cache drive. Looking into it further, I decided to d
  8. Hey jwiener3 and all others, As far as the perf: interrupt messages, I receive these as well, and the system seems to limit my login until it is done spitting those errors. Not sure if there are other processes still booting in the background. I'm assuming the "accessed a protected system..." is your banner/motd. As far as I know, those alerts don't actually cause any issues (that I have found). OH!!! Also, Update. Running Unraid 6.9.0-beta25. I'm now able to run much more interfaces. Currently running 25 (24 + mgmt). Addin
  9. Diagnostics Attached. dash-diagnostics-20200204-1721.zip
  10. Not sure why, but unraid seems to limit jumbo frame sizing to 9000. However, my 10gbe switched network is currently configured for 16k+ frame sizing in accordance to 802.3 Standards for 10gbe NICs. Looking to get that 99% efficiency in my file transfers. Is this a limitation of unraid?
  11. Changed Status to Open Changed Priority to Minor So, I've changed up the configuration. Eth0 is now br0 (10.1.0.0/24) DHCP and default shows correctly as 10.1.0.1 in both docker settings and interface settings. Eth1 is now br1 (10.1.10.0/24) DHCP and default shows correctly as 10.1.10.1 in both docker settings and interface settings. Eth2 (Disabled/unplugged and port down) is now br2 DHCP (no network associated, because its port down/unplugged). br1 is still not an option for docker containers whereas br0 is. I'll plug up eth2 later to see if br2 will sh
  12. So, the eth2 connection is disabled at the moment, (set to port down, as well as unplugged). The br1 pluggs into a Xfinity Business Modem/Router. The ports on the Modem/Router are basic switch ports, and there is a DHCP server that runs for basic networking connectivity within that network. However, there is a /29 network, of which the modem is also a part of. The modem acts as 96.x.x.134/29 (last useable address) and the 10.1.10.0/24 uses the 96.x.x.134 as the WAN address when being NAT'd. Plugged into the Xfinity Modem/Router is also an Asus GT5300 Wireless router, configured to us
  13. Tested with 6.8.2 as well. Here is the new diag. One thing to note, before manually adding my global network information. This shows correct default for docker setting. However, after editing the routing table to include the global addressing scheme, even if I remove the 10.1.10.1 information and re-add it... Docker settings shows incorrect default route for br1. I went ahead and removed the global default route. It's not really needed, since the unraid server doesn't have a global IP address assigned. (VM's will have global IP addresses, but they can s
  14. Version: 6.8.1 w/ NVIDIA drivers 440.44 In this example, br0 and br1 exist on my server, br1 spanning multiple interfaces, one of which is a 1gbe and another a 10gbe When reviewing my Docker Settings, I see IPv4 and IPv6 listings for both br0 and br1, as well as the custom added IPv4 for eth2 (which exist's within br1, but uses global network IP scheme) However, only br0 and eth2 show up as options (as well as bridge, host, and none) when creating a docker container... br1 missing!? One concern I have, is in the docker settings section. I've noticed that the gateway is listed