1812
Members
-
Joined
-
Last visited
Everything posted by 1812
-
I had this issue with this container and the other minos container. The only sort of solution was to log out and log back in. This resolved the webgui not responding about 50% of the time. I tried on several browsers to still the same. I got tired of that and now have mineos installed as a vm and it has zero issues and I've been frustration free.
-
check and make sure you didn't over provision the disk that the backup is located on (as in, make sure the physical disk has space available.) I ran into this issue by telling TM I wanted it that I wanted the backup to be XXX in size. And as it wrote to the disk (along with other shares) it filled the disk to the point where TM had no more space to write even though the share/setup said otherwise.
-
it isn't intended to be virtualized, so it assumes it is running on hardware and some sort of hardware GPU is present, either card/soldered or graphics via cpu. Yes, you can run it in VMware officially from apple, but it's not really built to do that in the same manner as windows.
-
is there a reason you want a different ip range? if there is no real reason than "just because" I'd just leave it all in the same network. I use to get fancy but simplicity is where I ended up these days. for a time I used the onboard gigabit for lan access for the rest of my network to my server and it worked well. Not collisions or other issues changing from 1gbe to 10gbe. (I've since purchased another mikrotik switch for my house and now run a 10gbe trunk line from this switch to that one.) whether or not the new pathway from your computer - 10gbe - CRS305 - 1gbe- gigabit switch will impact you negatively, it all depends on what the bandwidth going to the servers from the rest of the house is on the 1gbe line connecting them to it. If there is no traffic then you should see no slowdown. I run mine in swos. there seem to be no improvements in performance vs routeros from my early playing around it with it. and I'm not using vlans/layer3. it's a simpler interface that just works for me.
-
its a 10 dollar try it and find out! If it stopped after the fan, then heat would appear to be an issue.
-
I'll just stick them on the top and on the side (x marked in the pic below). they are operating within spec range, though towards the top end. Worst case I'm just making them more "Mad Max" themed in appearance. Best case I might get some longevity that I would have otherwise lost. If I have space in the switch I may add some to the sfp+ ports as well, as shown in the second picture denoted by a circle. too much? maybe, but also trying to keep myself busy and I don't see how it could hurt.
-
amazon has a few https://www.amazon.com/Heatsink-Cooling-Stepper-Regulators-Raspberry/dp/B07V9XDJNF/ref=sr_1_4?keywords=heat+sink+kit&qid=1585487921&s=electronics&sr=1-4 https://www.amazon.com/gp/product/B082RWXFR2/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 the flat area on my 10gbe rj45 transceiver is 15mmx13mm on top and 15mmx12mm on the side so I looked for kits that wold have something to fit there.. Shortly after posting that update, I rethought about which kit I bought, cancelled the 7 dollar one and went for the 16 dollar 100 piece kit because.... well, "sheltering in place" is going to become "put heat sinks on everything to fight boredom."
-
Over a year later and I've posted an update in the top post with my experience.
-
updated original thoughts/observations after 11 months of use.
-
I run a virtualized instance of an enterprise-grade firewall on my box. This keeps viruses and other nasties from penetrating my network and infecting my hardware. But at the same time, my friends with benefits can still gain access to my 9TB worth of Hard Disks for their pleasure. It may be hard to swallow, but taking the time to carefully setup your sever will pay dividends later with all that data going in and out, and in, and out.
-
I'll also try the 2 hp workstations I have and see what happens just for "fun." I never use GUI mode because I don't have a use case for it, but now I'm very interested!
-
(I'm reading through this pre-coffee), all very interesting because I run 2 ml30 g9's without issue but have never booted them into GUI mode. I will try it this weekend when one of them is not in use and try to confirm the behavior though I'm sure it will occur. I vaguely recall getting intermittent errors related to video output on one or two previous HP servers I've used Unraid on, but. I don't remember which ones specifically. I don't recall it causing shutdown issues either, but that doesn't mean its not a problem. iLo seems to rear an issue every now and then on Unraid but usually nothing this drastic.
-
I had this issue and resolved it by uninstalling the Nvidia driver, shutting down the vm, and then only passing through the video only, no audio, from the card. You may have to use acs functions to split your card into separate iommu groups. Upon restart, it works as expected minus GPU sound, but I'm using something else for that anyways so it wasn't a big deal. there may be a better way to resolve this though.
-
I think that use to be correct, but plex has gotten better at reading a RAM disk size. I use to use one exclusively until I started using the dvr, which needs a scratch disk the size of the recording (which is big for football games.) sometimes when setting up a RAM disk for the first time, plex may crash the stream filling it up, but then never exceeded it again. Sometimes it reads the size right the first time and there are no problems.
-
you are probably using vmxnet3. change to e1000-82545em
-
check if its changing your loader and nvram location to something not within the macinabox folder. I've noticed this behavior a few times causing what you describe. also make sure that you remove topology when you change core count (covered in the video)
-
No worries, I’m still twiddling my thumbs considering an AMD card for Catalina, and all the other fun that ensues by updating!
-
I get 500MB/s on high Sierra 10gbe via SMB which maxes out the ssd cache... doesn’t seem broken to me
-
This server's only job is hosing 2 vm's. After updating to RC9 I noticed higher cpu usage on cores that are normally very low and not used by VMs. Glances showed: I did have another computer conceded via smb to move a file over (compiling the RMRR patch) but even after disconnecting smb and shutting down the 2 VM's, high usage persisted. I don't recall seeing this on RC7 twins-diagnostics-20191210-1102.zip
-
updated from 6.8.0 rc2(?) to rc7. aside from it swiping my primary network adapter for the secondary (which wasn't plugged in) and failing to switch to an operational one, after that time I installed a windows 10 vm. following errors pop up: first is a network error with call trace. this occurs when the vm is using the bridge. Inside the vm I disabled the virtio bridge and used the solar flare 10g I have in it and these errors stopped. Dec 3 08:31:33 Backup kernel: e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang: Dec 3 08:31:33 Backup kernel: TDH <27> Dec 3 08:31:33 Backup kernel: TDT <7d> Dec 3 08:31:33 Backup kernel: next_to_use <7d> Dec 3 08:31:33 Backup kernel: next_to_clean <26> Dec 3 08:31:33 Backup kernel: buffer_info[next_to_clean]: Dec 3 08:31:33 Backup kernel: time_stamp <1000a35c2> Dec 3 08:31:33 Backup kernel: next_to_watch <27> Dec 3 08:31:33 Backup kernel: jiffies <1000a3d40> Dec 3 08:31:33 Backup kernel: next_to_watch.status <0> Dec 3 08:31:33 Backup kernel: MAC Status <80083> Dec 3 08:31:33 Backup kernel: PHY Status <796d> Dec 3 08:31:33 Backup kernel: PHY 1000BASE-T Status <3c00> Dec 3 08:31:33 Backup kernel: PHY Extended Status <3000> Dec 3 08:31:33 Backup kernel: PCI Status <10> Dec 3 08:31:35 Backup kernel: e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang: Dec 3 08:31:35 Backup kernel: TDH <27> Dec 3 08:31:35 Backup kernel: TDT <7d> Dec 3 08:31:35 Backup kernel: next_to_use <7d> Dec 3 08:31:35 Backup kernel: next_to_clean <26> Dec 3 08:31:35 Backup kernel: buffer_info[next_to_clean]: Dec 3 08:31:35 Backup kernel: time_stamp <1000a35c2> Dec 3 08:31:35 Backup kernel: next_to_watch <27> Dec 3 08:31:35 Backup kernel: jiffies <1000a4540> Dec 3 08:31:35 Backup kernel: next_to_watch.status <0> Dec 3 08:31:35 Backup kernel: MAC Status <80083> Dec 3 08:31:35 Backup kernel: PHY Status <796d> Dec 3 08:31:35 Backup kernel: PHY 1000BASE-T Status <3c00> Dec 3 08:31:35 Backup kernel: PHY Extended Status <3000> Dec 3 08:31:35 Backup kernel: PCI Status <10> Dec 3 08:31:38 Backup kernel: e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang: Dec 3 08:31:38 Backup kernel: TDH <27> Dec 3 08:31:38 Backup kernel: TDT <7d> Dec 3 08:31:38 Backup kernel: next_to_use <7d> Dec 3 08:31:38 Backup kernel: next_to_clean <26> Dec 3 08:31:38 Backup kernel: buffer_info[next_to_clean]: Dec 3 08:31:38 Backup kernel: time_stamp <1000a35c2> Dec 3 08:31:38 Backup kernel: next_to_watch <27> Dec 3 08:31:38 Backup kernel: jiffies <1000a4d40> Dec 3 08:31:38 Backup kernel: next_to_watch.status <0> Dec 3 08:31:38 Backup kernel: MAC Status <80083> Dec 3 08:31:38 Backup kernel: PHY Status <796d> Dec 3 08:31:38 Backup kernel: PHY 1000BASE-T Status <3c00> Dec 3 08:31:38 Backup kernel: PHY Extended Status <3000> Dec 3 08:31:38 Backup kernel: PCI Status <10> Dec 3 08:31:40 Backup kernel: e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang: Dec 3 08:31:40 Backup kernel: TDH <27> Dec 3 08:31:40 Backup kernel: TDT <7d> Dec 3 08:31:40 Backup kernel: next_to_use <7d> Dec 3 08:31:40 Backup kernel: next_to_clean <26> Dec 3 08:31:40 Backup kernel: buffer_info[next_to_clean]: Dec 3 08:31:40 Backup kernel: time_stamp <1000a35c2> Dec 3 08:31:40 Backup kernel: next_to_watch <27> Dec 3 08:31:40 Backup kernel: jiffies <1000a5540> Dec 3 08:31:40 Backup kernel: next_to_watch.status <0> Dec 3 08:31:40 Backup kernel: MAC Status <80083> Dec 3 08:31:40 Backup kernel: PHY Status <796d> Dec 3 08:31:40 Backup kernel: PHY 1000BASE-T Status <3c00> Dec 3 08:31:40 Backup kernel: PHY Extended Status <3000> Dec 3 08:31:40 Backup kernel: PCI Status <10> Dec 3 08:31:42 Backup kernel: e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang: Dec 3 08:31:42 Backup kernel: TDH <27> Dec 3 08:31:42 Backup kernel: TDT <7d> Dec 3 08:31:42 Backup kernel: next_to_use <7d> Dec 3 08:31:42 Backup kernel: next_to_clean <26> Dec 3 08:31:42 Backup kernel: buffer_info[next_to_clean]: Dec 3 08:31:42 Backup kernel: time_stamp <1000a35c2> Dec 3 08:31:42 Backup kernel: next_to_watch <27> Dec 3 08:31:42 Backup kernel: jiffies <1000a5d40> Dec 3 08:31:42 Backup kernel: next_to_watch.status <0> Dec 3 08:31:42 Backup kernel: MAC Status <80083> Dec 3 08:31:42 Backup kernel: PHY Status <796d> Dec 3 08:31:42 Backup kernel: PHY 1000BASE-T Status <3c00> Dec 3 08:31:42 Backup kernel: PHY Extended Status <3000> Dec 3 08:31:42 Backup kernel: PCI Status <10> Dec 3 08:31:43 Backup kernel: ------------[ cut here ]------------ Dec 3 08:31:43 Backup kernel: NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out Dec 3 08:31:43 Backup kernel: WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x161/0x1bb Dec 3 08:31:43 Backup kernel: Modules linked in: xt_CHECKSUM ipt_REJECT ip6table_mangle ip6table_nat iptable_mangle ip6table_filter ip6_tables vhost_net tun vhost tap xt_MASQUERADE iptable_filter iptable_nat nf_nat ip_tables xfs md_mod bonding e1000e sfc mdio wmi_bmof sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd glue_helper intel_cstate intel_uncore intel_rapl_perf i2c_i801 i2c_core ahci libahci mpt3sas isci libsas raid_class scsi_transport_sas wmi button [last unloaded: e1000e] Dec 3 08:31:43 Backup kernel: CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.3.12-Unraid #1 Dec 3 08:31:43 Backup kernel: Hardware name: Hewlett-Packard HP Z420 Workstation/1589, BIOS J61 v03.94 07/10/2018 Dec 3 08:31:43 Backup kernel: RIP: 0010:dev_watchdog+0x161/0x1bb Dec 3 08:31:43 Backup kernel: Code: 98 b1 00 00 75 39 48 89 ef c6 05 b5 98 b1 00 01 e8 f6 d5 fc ff 44 89 e9 48 89 ee 48 c7 c7 bb 06 db 81 48 89 c2 e8 0a c1 ac ff <0f> 0b eb 11 41 ff c5 48 81 c2 40 01 00 00 41 39 cd 75 95 eb 13 48 Dec 3 08:31:43 Backup kernel: RSP: 0018:ffffc900000fcea0 EFLAGS: 00010286 Dec 3 08:31:43 Backup kernel: RAX: 0000000000000000 RBX: ffff888bd2a54438 RCX: 0000000000000524 Dec 3 08:31:43 Backup kernel: RDX: 0000000000000001 RSI: 0000000000000002 RDI: 0000000000000247 Dec 3 08:31:43 Backup kernel: RBP: ffff888bd2a54000 R08: 0000000000000003 R09: 000000000001cd00 Dec 3 08:31:43 Backup kernel: R10: 0000000000000000 R11: 000000000000005c R12: ffff888bd2a5441c Dec 3 08:31:43 Backup kernel: R13: 0000000000000000 R14: ffff888bd8622080 R15: 0000000000000001 Dec 3 08:31:43 Backup kernel: FS: 0000000000000000(0000) GS:ffff888c0f640000(0000) knlGS:0000000000000000 Dec 3 08:31:43 Backup kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 3 08:31:43 Backup kernel: CR2: 00001480adc18b10 CR3: 000000000200a005 CR4: 00000000001626e0 Dec 3 08:31:43 Backup kernel: Call Trace: Dec 3 08:31:43 Backup kernel: <IRQ> Dec 3 08:31:43 Backup kernel: call_timer_fn.isra.0+0x12/0x6f Dec 3 08:31:43 Backup kernel: ? qdisc_put_unlocked+0x28/0x28 Dec 3 08:31:43 Backup kernel: expire_timers+0x7e/0x8d Dec 3 08:31:43 Backup kernel: run_timer_softirq+0x72/0x120 Dec 3 08:31:43 Backup kernel: ? __hrtimer_run_queues+0xc3/0x10b Dec 3 08:31:43 Backup kernel: ? ktime_get+0x44/0x95 Dec 3 08:31:43 Backup kernel: __do_softirq+0xc9/0x1d3 Dec 3 08:31:43 Backup kernel: irq_exit+0x47/0x86 Dec 3 08:31:43 Backup kernel: smp_apic_timer_interrupt+0x80/0x8b Dec 3 08:31:43 Backup kernel: apic_timer_interrupt+0xf/0x20 Dec 3 08:31:43 Backup kernel: </IRQ> Dec 3 08:31:43 Backup kernel: RIP: 0010:cpuidle_enter_state+0xe8/0x1f0 Dec 3 08:31:43 Backup kernel: Code: ff 45 84 ff 74 1d 9c 58 0f 1f 44 00 00 0f ba e0 09 73 09 0f 0b fa 66 0f 1f 44 00 00 31 ff e8 e1 43 ba ff fb 66 0f 1f 44 00 00 <45> 85 e4 0f 88 ea 00 00 00 49 63 cc be ff ff ff 7f 48 ba ff ff ff Dec 3 08:31:43 Backup kernel: RSP: 0018:ffffc90000087e90 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13 Dec 3 08:31:43 Backup kernel: RAX: ffff888c0f660ac0 RBX: ffffe8ffff27bf00 RCX: 000000000000001f Dec 3 08:31:43 Backup kernel: RDX: 0000000000000000 RSI: 000000002ac4fcf0 RDI: 0000000000000000 Dec 3 08:31:43 Backup kernel: RBP: ffffffff820584e0 R08: 000000e47c6036a7 R09: 000000e47a5e3354 Dec 3 08:31:43 Backup kernel: R10: 071c71c71c71c71c R11: 0000000000000020 R12: 0000000000000004 Dec 3 08:31:43 Backup kernel: R13: 000000e47c3003af R14: 000000e47c6036a7 R15: 0000000000000000 Dec 3 08:31:43 Backup kernel: cpuidle_enter+0x25/0x31 Dec 3 08:31:43 Backup kernel: do_idle+0x17e/0x1fc Dec 3 08:31:43 Backup kernel: cpu_startup_entry+0x18/0x1a Dec 3 08:31:43 Backup kernel: start_secondary+0x154/0x16f Dec 3 08:31:43 Backup kernel: secondary_startup_64+0xa4/0xb0 Dec 3 08:31:43 Backup kernel: ---[ end trace ffdb4b11edd93456 ]--- second is when the windows 10 vm sees high load/gaming on the cores Dec 3 11:11:56 Backup kernel: kvm_set_msr_common: 155 callbacks suppressed Dec 3 11:11:56 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:11:56 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:11:56 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:11:56 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:11:56 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:11:56 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:11:56 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:11:56 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:11:56 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:11:56 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:03 Backup kernel: kvm_set_msr_common: 5673 callbacks suppressed Dec 3 11:12:03 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:03 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:03 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:03 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:03 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:03 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:03 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:03 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:03 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:03 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:08 Backup kernel: kvm_set_msr_common: 77 callbacks suppressed Dec 3 11:12:08 Backup kernel: kvm [3974]: vcpu4, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:08 Backup kernel: kvm [3974]: vcpu4, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:08 Backup kernel: kvm [3974]: vcpu4, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:08 Backup kernel: kvm [3974]: vcpu4, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:08 Backup kernel: kvm [3974]: vcpu4, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:08 Backup kernel: kvm [3974]: vcpu4, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:08 Backup kernel: kvm [3974]: vcpu4, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:08 Backup kernel: kvm [3974]: vcpu4, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:08 Backup kernel: kvm [3974]: vcpu4, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:08 Backup kernel: kvm [3974]: vcpu4, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Now, I did not have a windows 10 vm on this computer before upgrading. the rIP problem has never occurred on the macOS video editing vm. I don't use the network bridge either for the macOS vm (10g card) so I can't be 100% sure the issues wouldn't have occurred before the update. But the server consistently throws the errors under the conditions listed above. Thanks! backup-diagnostics-20191203-1711.zip
-
remove the space after the coma for the last device id and reboot. you would have to check your scheduler and the logs to see what is happening at that time.... could be trim, could be anything.
-
Perhaps instead of “Remark”’the text should say “Reminder” because I thought I was doing it wrong and forwarding wasn’t working because it kept showing up....partly due to the explanation in the first post about auto UDP... (and maybe I didn’t read all the explanation very closely and it is clear?)
-
I played around with this today and got it going. Pretty cool! Faster than the built in VPN in sophos as too! Leaving the following info as I use sophos UTM 9 and it might help anyone else using this firewall and this service: Setup NAT forwarding for port forward to your server as demonstrated here and automatically create a firewall rule: Setup WireGuard per the instructions at the top of this thread. For basic server and Lan access, you are done. If you want VPN access to the internet from a peer/client: Use the VPN address/pool provide by the wireguard setup for clients to use starting at xxx.xx.xx.0 and add a masquerading rule to allow that pool to access External (WAN). That's it. A note though, the plugin still complains about this: Remark: configure your router with port forwarding of port 51820/UDP to 86.75.30.9 But everything still works. Don't know if its a bug or if it's sophos being sophos. Either way, thanks for the great feature!
-
I've found that when this happens, click and hold, then drag the mouse cursor to where you want to be, then click again. It's a pain, but "works"
-
I'm planning on running it again to build a new vm image this afternoon on another server. Maybe something went wonky for me during install, even though it "worked" first time through! Again, many thanks for this, it's pretty awesome!
