• Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

FredrikJL's Achievements


Newbie (1/14)



  1. I got this working and the macvlan issue remains solved a couple of weeks later. No crashes since I implemented this (on 11.5). Uptime is 3 weeks and counting or the first time ever. Sorry to hear that there seems to be problems for people to get this configured as described by @bonienl
  2. Make sure to have “IPv4 address assignment:” set to “none” for your eth1. (As well as for ipv6).
  3. This is what I did to fix my macvlan. Setting up/using ipvlan never worked for me
  4. As many people here I use (or try to use) Unraid to run a few SMB share with the purpose of backing up my MacBooks in a secure way. This has caused me much headache in the past. I've read countless posts here and there with limited success. I run a ASRock C2550D4I with two NICs. One is dedicated for Unraid and one for macvlans. So, no bonding. That's another story, but bonding and macvlans seems to be an issue. This is what works for me: Run the AFP variant of docker. This works ok, but there's a bit of an overhead with a docker, and the AFP branch of this one is stale. There's a much more maintained SMB version, but I never got that one to work properly. Just the regular SMB share in Unraid with Timemachine capabilities switched on (duh). The number two above is the big surprise for me, because I've been trying to make it work for a year with no success. Eventually I watched SpaceInvaderOne's video but had no success. But it gave me some inspiration and hope, since he clearly points out to remove any other extra SMB config that can intervene with Timemachine/SMB. My Unraid setup has been around for a long time and is probably full of my mistakes, semi-hacks and old upgrades. In order to get back to basics. I did the following: Took the array offline. Made a backup of everything in /boot/config Went into /boot/config/shares and removed all configs for old shares that aren't used anymore. Also removed their respective directories. I also removed all timemachine shares. (Some of the old backups where moved to other shares.) Removed everything from SMB-extras.conf according to SpaceInvaderOne's instructions. Completely deleted /boot/config/share.cfg to rid myself of any previous mistakes/hacks. Restarted with the array offline. With the array offline, checked the Settings page for SMB. Verified everything according to basic defaults and saved. This showed to be important, because now a new share.cfg file is created on /boot/config with the default settings. Cranked up the array. Created a new timemachine share, with no size limit as public. Tried to mount and use it for Timemachine. Success! Why did it work this time? I have no idea... Will it work on your machine? I have no idea. It works on my machine. But I was quite thorough when cleaning out old shares, tweaks, tunes and misconfigs. Take it for what it is. This might also work for you. Or not. share.cfg timemachine.cfg
  5. I've tried a bunch of different things to get rid of messages like this without any luck. I usually get one or two per day, as well as a random crash per week or so. Mar 2 22:21:04 Unraid kernel: WARNING: CPU: 1 PID: 7504 at net/netfilter/nf_conntrack_core.c:1208 __nf_conntrack_confirm+0xa5/0x2cb [nf_conntrack] Mar 2 22:21:04 Unraid kernel: Modules linked in: xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap macvlan xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs md_mod ipmi_devintf jc42 efivarfs ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc bonding tls igb intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel ast drm_vram_helper drm_ttm_helper ttm aesni_intel crypto_simd drm_kms_helper ipmi_ssif cryptd i2c_i801 intel_cstate joydev i2c_smbus drm input_leds backlight led_class agpgart syscopyarea sysfillrect sysimgblt i2c_algo_bit acpi_ipmi ahci fb_sys_fops i2c_core libahci ipmi_si button acpi_cpufreq unix [last unloaded: igb] Implemented the changes suggested above and no problems so far. Three days ago and counting... On an ASRock Rack C2750D4I that never gives my enough sleep.
  6. Sorry, I was referring to the App on Apple devices. Your comment sparked some troubleshooting on my end. The app IS in fact available in the EU (more precisely Sweden), as well as in the US and Canada. It is easily found on appstore in US and Canada. For some reason though, it cannot be found by searching in the Swedish app store. If you happen to search in your browser (by not using Google) you get the link to the appstore and ta-da, there it is, in the Swedish store as well. So there seems to be something fishy with AppStore, Sweden and this app. tl;dr It is available, just quite tricky to find. Thanks for a great little app!
  7. Hello @jbrodriguez! Thanks for a very useful plugin. I'd like to ask for two things. Can you publish the plugin in app store for European countries please? I can only find it in the US store. I don't know the reasoning behind it being inaccessible for EU users. Feel free to ask me (pm) questions on data privacy if that is an issue. I've quite a bit of experience with that. Suggestion: it would be a good thing to have a note on the Logs page if the user doesn't have the ControlR plugin installed or enabled. It took me a while to realize that this was a requirement for Logs to work. Thanks a bunch!
  8. Personally I first tried restarting unraid api. /etc/rc.d/rc.unraid-api restart Didn't do the trick though. So I checked connectivity to te mothership server using wget. That seemed to work. Then logged out of unraid My Serves account under Settings --> Management access, and then logged in again. That did the trick for me!
  9. I tinkered a bit with this script. The "original" quoted here, does a docker logs ClamAV which makes the script look at all logs, for all runs, ever (sort of). So if you actually had a virus, you'll end up alerting for that virus for all eternity, even tough you might have removed it. I updated the script to use: docker logs --since 23h ClamAV to just consider the latest 23 hours (or whatever you feel is reasonable). Personally I run the scan on a daily basis. My changes also modifies the severity level of the notification to 'alert' if a virus has been found. #!/usr/bin/php <? exec('/usr/local/emhttp/plugins/dynamix/scripts/notify -e "Antivirus Scan" -s "Antivirus Scan Started" -d "Antivirus Scan Started" -i "normal"'); exec('docker start ClamAV'); for ( ;; ) { $status = trim(exec("docker ps | grep ClamAV")); if ( ! $status ) break; sleep(60); } exec("docker logs --since 23h ClamAV 2>/dev/null",$logs); foreach ($logs as $line) { $virus = explode(" ",$line); if (trim(end($virus)) == "FOUND" ) { $infected .= "$line\n"; } } $level = "alert"; if ( ! $infected ) { $infected = "No infections found\n"; $level = "normal"; } exec('/usr/local/emhttp/plugins/dynamix/scripts/notify -e "Antivirus Scan" -s "Antivirus Scan Finished" -d '.escapeshellarg($infected).' -i '.escapeshellarg($level)); ?>