KatelynM

Members
 View Profile  See their activity

  • Posts

    6

  • Joined

  • Last visited

KatelynM's Achievements

Noob

Noob (1/14)

0

Reputation

  1. KatelynM
    Changed Status to Closed
  2. KatelynM
    Apparently will be solved with future update
  3. KatelynM
    To move my network to use 10./8 would require was more work then it's worth, I'd rather just manually editing the unraid network.cfg file in that case. I normally end up configuring though the UI as 172./8 and then manually changing the netmask in the network.cfg file to 255.240.0.0, I honestly just wish we had an option to just not use the drop down and enter our own for people who knew what they where doing, even if it was hidden under some 'Advanced' tab or something.
  4. KatelynM
    Is there a manual fix I could do to get it working until the release of Unraid the has the fix included comes out? I don't like the fact that I can't easily reboot my NAS because of this issue, though it's not like I reboot it often. My problem is I need a newer kernel because I need proper Intel Arc support, so downgrading isn't really an option. Once I get a response to this one way or the other I will mark it as solved, seeing as it's something that is known and will be fixed in the future. I will note this doesn't solve why it didn't work from the start, but I'm going to assume it's user error somehow at his point seeing as no one seems to be reporting the same problem.
  5. KatelynM
    I'm annoyed I have to manually edit my network.cfg file every time I need to make changes to my network config, all because /12 is not listed in the drop down box. Please add this, I'm sure I'm not the only one who uses the 172.16.0.0/12 private IP range.( netmask 255.240.0.0 ) Maybe not the proper location to ask, but on a related topic, am I the only one who noticed that broadcast isn't set either, it always defaults to 0.0.0.0 instead of what it's suppose to be, or is this done on purpose for some reason?
  6. KatelynM
    Description: Upon upgrading my home NAS from Unraid 6.12.6 to Unraid 6.12.8, my server lost all network connectivity, and I was unable to ping the network interface. Rebooting into safe mode didn't resolve the issue. I also upgraded the linux kernel back to 6.7.3 (latest stable from thor), which I was using to provide proper support to the Intel GPU in the server. That did not resolve the issue either. Digging further, I discovered that the ethernet interfaces weren't being bonded. I've begun using the following commands every time the server is restarted to restore it's network connectivity. ip link set down dev eth0 ip link set down dev eth1 ip link set master bond0 dev eth0 ip link set master bond0 dev eth1 I also found that I need to restart nginx after this for the web interface to come up. Steps to Reproduce: Server boot after upgrade to Unraid 6.12.8 Expected Results: Ethernet interfaces slaved to bond0. Actual Results: Ethernet interfaces up but not slaved to a bonded interface. The included diagnostics file was made after the kernel update and the commands listed above where done. I can reapply the update and make another one if is is needed that uses included kernel form Unraid 6.12.8, though, I do not think it is a kernel related issue. fairy-diagnostics-20240222-1655.zip