Jump to content

[6.12.8 and 9] OS update mentions link, that does not work - Call traces and crashes related to macvlan

By DataCollector

· 425 views
  • Minor

Hello.

 

When i updated from 6.12.8 to 6.12.9  several days/weeks ago,  I saw the new update Dialogue.

There was the Problem "Call traces and crashes related to macvlan" mentioned and a link "If this affects you, see the alternate solution available since Unraid 6.12.4.
 https://account.unraid.net/server/6.12.4.md#fix-for-macvlan-call-traces

"

I followed the link and saw "404"

The Site was not found.

 

Okay, the people at Lime is smart and will see this themself.

 

Well, now I update to 6.12.10 und the same link is shown. I follow it.. and see "404".

 

I guess noone found this problem, so I  ask you: could you please fix that?

 

Thanks!

 

excuse my bad english. it is not my native language.

404Screenshot 2024-04-05 153207.png

    • User Feedback

    Recommended Comments

    Proficient

    bmartino1

    Members

    i have found that when these happen as ther are some seting that are set once to create the network.

     

    on the flash drive to delete the config file for netwrok only. This will recreate the network settings.

     

    issues are per client.

     

      

    On 11/29/2023 at 1:59 PM, bmartino1 said:

     

    This is the process:

     

    step 1: Connect a monitor to see boot process of unraid and get ip at boot.

     

    step 2: make a backup of the file before deleting the file for recover

     

    step 3 delete the file  /boot/config/network.cfg

    --Step 3.5 you should disable VM and docker before reboot

     

    Step 4 reboot

     

    Step 5 acquire unraid's new IP address

     

    Step 6 sign in to unraid

     

    Step 7 settings > network

    Folow https://docs.unraid.net/unraid-os/release-notes/6.12.4/ release notes for macvlan

    *Disable Bridging

     

    Example of my settings for macvlan:

    image.thumb.png.ca3ef7e3387d833bc74af0f1e9e75477.png

     

    step 8 reboot and check log / fix plug to see if you have any macvlan traces.

    step 8.5 enable VM and docker. before reboot and check again

     

    this will no use vhost@eth and or macvtap0@eth0 for the ip for the docker network for macvlan connections to and from the docker.

     

     

  • Quote

    • Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...