Limy

Members
  • Content count

    56
  • Joined

  • Last visited

Community Reputation

4 Neutral

About Limy

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    edm.ab.ca

Recent Profile Visitors

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

  1. So I have been running my system since Wednesday of last week and I no longer have any call traces on macvlan. I may try the next suggestion and place 192.168.19.xxx with a DHCP pool on br4. Right now, I’m very happy that I can eliminate the call traces.
  2. Limy

    Couldn't register serial port

    I get roughly the same error when I boot unRaid. I haven’t delved into it.
  3. Limy

    Network Issue

    Windows 10 has a firewall. You may have to turn that off.
  4. Well I'm glad my odometer doesn't go up like my cache otherwise I would need a new vehicle a lot sooner
  5. So basically, nothing to be concerned about.
  6. I thought I would throw this out, to see if anyone else is seeing the same thing. Ever since I setup my unRaid server (early this spring) , I have seen a large number of writes on my SSD cache drives. Currently, it has only been running for 2 days, 15 hours and these are the current values: Granted, I do have the following on the cache drives: I have two VM's and a few dockers running. I also have the trim plugin Dynamic SSD Trim. I'm just wondering if it's normal to see that high number of writes or maybe I have something setup wrong. Thanks for any feedback.
  7. Okay, thanks for clarifying. BTW with my current setup no call traces so far with broadcast messages and macvlan. I should note that one other change I adopted from @ken-ji‘s setup, is that I also setup the Network Protocol to IPv4 + IPv6 for both the interface and the VLAN which I cannot really see that resolving any issue. I just thought I should mention it.
  8. Thanks @ken-ji and @bonienl. Well, after reading what you wrote, I’m wondering if there is some sort of bug / glitch that caused br4.34 to be available only after I setup a pool on br4. At any rate on my system br0 192.168.19.xxx is my main unsaid network. I have some dockers running on that which are operating in bridge mode. So @bonienl are you inferring that in the Docker Settings a pool should always be assigned otherwise Docker is running a DHCP server and is competing with my routers DHCP server? By the way, ever since I setup br4 as shown in my earlier post, my system has totally settled down. I’m not actually using 192.168.2.xxx in my system / router at all. I’m going to leave my system going for a couple more days to see if the call traces are resolved. If so, I can do some more experimenting.
  9. Hi ken-ji, Posting that helped a lot and I was able to figure out my issue. Apparently I needed to assign a pool to br4 as well in order for br4.34 to be available. So my docker settings now look as follows: Just out of curiosity, are you actually using 192.168.2.XXX for anything in your system. Or did you just set this up for isolation. Thanks for you help. I will see if this rids me of the call traces.
  10. Hi ken-ji, Can you be a bit more specific. When I set IPv4 address assignment: to None on my example VLAN 34, I cannot then start the dockers and br4.34 is no longer available. Thanks.
  11. Okay, I think I will try that. I decided to update to 6.5.3 and 2 hours later I got another call trace. That could be the reason for the macvlan broadcast call traces.
  12. Limy

    unRAID OS version 6.5.3 available

    Upgraded from 6.5.1-rc2. So far no observed issues. Thanks limetech.
  13. So I finally decided that using ( br0 which unraid runs on ) with VLAN's is not a good idea for me. Since I have more ethernet adapters on my server, I decided to use eth4 and put all my docker VLAN's on that. It's fairly early, but I'm pretty sure that I have gotten rid of my call traces. One note, you have to set interface IPv4 address assignment to None. If you don't do that, unraid will assign an arbitrary ip address. But the bigger problem especially with my network is that you will constantly loose and regain an ip address on the main VLAN interface from the dhcp server. This would occur randomly between 15 minutes to two hours. So my final setup for the VLAN is as follows: And I have a docker pool setup as: Hope this helps anyone with VLAN problems. I will report my results back after a few days.
  14. I’m looking forward to trying it. Thanks.
  15. So anyone able to get to the bottom of this. I did install tcpdump, but honestly, if I start only one docker i.e. Plex running on br0.34, it takes 2 days to start getting call traces. As soon as I stop the docker container the traces stop. Obviously not many people are coming across this problem or are not running vlans. Apparently there is one fix to vlans and bonding (broadcast) in kernel 4.14.42 as shown at this link: https://www.systutorials.com/linux-kernels/498439/linux-4-14-42-release/ Another VLAN fix in 4.14.44: https://www.systutorials.com/linux-kernels/498875/linux-4-14-44-release/ Lots of VLAN fixes in 4.14.45: https://www.systutorials.com/linux-kernels/500298/linux-4-14-45-release/ Basically until this gets resolved my VLAN is pretty much useless. Call traces will eventually kill my server.

Copyright © 2005-2018 Lime Technology, Inc.
unRAID® is a registered trademark of Lime Technology, Inc.