mrbilky

Members
  • Posts

    460
  • Joined

  • Last visited

  • Days Won

    1

Report Comments posted by mrbilky

  1. 32 minutes ago, bonienl said:

    You have three times a default gateway "192.168.1.1" defined (eth0, eth1, eth2). This leads to asymmetric data transfers, and likely your firewall blocking things.

     

    Make sure only eth0 has a default gateway.

    Good eye sir that was the ticket!👍

  2. If they did it wasn't me I really thought it was my ISP so I took the drastic measure of resetting the router but then I rolled back to rc5 and all worked as normal then I updated again for shits and giggles to see if it was a hiccup but it went back to the errors reported I'm now on rc5 on my main server and rc6 on my other server with the only difference I see is the ip4 DNS server being google on the rc5 and the ip4 of the default gateway on rc6

  3. 10 minutes ago, cybrnook said:

    What do you have your dns settings set as?

    google but I didn't change it from rc5 to rc6 so it works on rc5 was I supposed to change it due to the upgrade? Funny thing to my other server an R710 is working fine with rc6 but the DNS is the routers DNS

  4. I may have spoke to soon for the 6.7.0 rc6 update I started having issues with dockers updating so I looked at fix common problems and it was complaining of these issues

    image.thumb.png.2743e7b220462bcf1613152541f0506f.pngScreen Shot 2019-03-27 at 6.32.29 PM

     

    so I rolled back to 6.7.0 rc5 and all seem to be good I updated dockers with no problem and FCP found no issue so I captured diags of before and after for those good at reading the tea leaves anyone else having anything like this? It actually affected Plex updating metadata thought that was weird I went so far as resetting my router but that was no help only rolling back corrected it

     

    homenas-diagnostics-20190327-2221.zip

    homenas-diagnostics-20190327-2228.zip

     

  5. 24 minutes ago, FreeMan said:

    Having just looked at CA for the first time in a while (my server is running fine and I don't fiddle with it much), here's what I said to Squid about all the new CA icons:

     

     

    I took a look at SpaceInvaderOne's video review of 6.7rc1 and I'll repeat my thoughts. The icon shapes are nice, but they're nothing but a sea of white. Again, I get that this is the latest trend in design, but it is, in my opinion a terrible one. There is considerably more cognitive load in mentally parsing the shapes when there is no color to help out. This is especially tough on those of us whose eyesight isn't quite as good as it used to be.

     

    There is a reason why modern IDEs all do syntax highlighting. This is an absolute God-send in comparison to the dark ages of working on a monochrome green or amber monitor! Just try disabling syntax highlighting in your modern IDE and see how hard that makes it - there's no good reason to go back.

     

    Again, I get that you're just following the "modern" trend, and I have tremendous appreciation for the incredible amount of work that goes into keeping the system updated with all the latest security patches and all the new features you're bringing to the table, but this is one trend I wouldn't mind missing out on. I'm sure that there will be a number of security patches in the 6.7 release, and I'd be remiss in skipping it just because of the UI design, but, based on what I've seen, I'd be tempted.

     

    And, yes, I really hate that my Android phone shows all my notification icons in white against a black background. When they allowed color there, I could tell at a glance if I had an orange text notification icon - now I have to analyze each one to see if it's the "new text message" shaped white square, among the sea of other white, essentially square, icons.

     

    </rant>

    I don't post much but I have to agree its harder to discern what icon your looking at, example would be unbalance or speedtest it just draws you to it when navigating both by its color and shape/image

    • Like 2