• 6.12.0-rc4 "macvlan call traces found", but not on <=6.11.x


    sonic6
    • Solved Minor

    Hello,

     

    I got the following output in my syslog: https://pastebin.cloud-becker.de/5ede1251c0f8 (Diagnostic attached)

     

    I know, the general fix for this is using "ipvlan" instead of "mcvlan".

    But in my (and other people) case, this isn't an option.

    The AVM Fritzbox (7595 in my case) isn't compatible with ipvlan.

     

    I came from the latest 6.11.x stable without any problems, the same for 6.10.x .

     

    @alturismo got the same problem with 6.12.x, also when he was problemless on 6.11.x . Maybe he can post some more details from his setup.

     

    So I hope it is fixable, especially when version before run without this problem.

    unraid-1-diagnostics-20230429-1014.zip

    • Upvote 2



    User Feedback

    Recommended Comments



    This macvlan issue has been like that for a long time, for some users it started with v6.4, for others after upgrading to v6.5, then v6.6 and so on, with each new release some new users are affected.

     

    If using ipvlan is not an option try this if possible:

     

    Link to comment

    Don't get me wrong i don't wanna be one of this "mimimi-User" who is blaming on the Devs, but i think this is a huge problem, especially for german user. The AVM Fritzbox is very common in Germany. And i think the German-Unraid Community is one of the biggest?

     

    I am very thankful for Unraid and they (Community-)Devs. But you got only "workarounds", but we need a fix for that.

     

    -Don't use Custom Bride br0

    I need a dedicated IP for some Containers (Docker/LXC) for Traffic Management and Port Forwarding

     

    -Don't use Host Access

    Also needed for Bridged Container... (maybe i can handle it, putting all bridge Containers into a "custom user network"

     

    -Use ipvlan

    Isn't support by my Router (Fritzbox)

     

    -Use a second NIC.

    Can be a solution for me, but the most users doesn't have a second NIC onboard or the space for a second one.

     

    Again, please don't get me wrong, all in all i am very thankful for the development of Unraid which worked flawless till 6.12.x for me.

    • Upvote 1
    Link to comment

    If you want it fixed then you need to take it up with the genuine Linux developers, as they are the ones who do the Kernel, Drivers, and Networking Stacks.

     

    Unraid is merely small pieces added on top of that.

    Link to comment
    17 hours ago, sonic6 said:

    The AVM Fritzbox (7595 in my case) isn't compatible with ipvlan.

     

    -Use ipvlan

    Isn't support by my Router (Fritzbox)

     

    What exactly is the issue with your Fritzbox in your case?

    As far as I know there should be nothing on the router side which would prevent the use of ipvlan on the Unraid side.

     

    I also use Fritzboxes (7490 and in the last year 6690) with ipvlan since the feature was released since almost 2 years now without any problems.

    Link to comment

    Same problem here, I have never had call traces issues until this version, not in the previous versions, 6.11 6.10....

    I have been using unraid for a long time macvlan issues come and go with different versions, so for me is hard to believe that the problem is only with the kernel and the kernel developers fix it a break it again every few versions.

     

    I have attached my diagnostics in case it could be useful

     

     

    unraid-diagnostics-20230430-1009.zip

    Edited by L0rdRaiden
    Link to comment
    3 hours ago, greenflash24 said:

    What exactly is the issue with your Fritzbox in your case?

    In combination with "host access" the Port Forwarding etc got corrupted. AVM was contacted, and they said, that multiple IP from the same MAC address isn't support.

    To be fair, i am not very experienced with macvlan/ipvlan/linux, so i don't know if i am explained the problem valid to AVM.

     

    Maybe contacting from Unraid-Side, as a Developer-to-Developer can bring cearness into this?

    I am only "one of thousand user, with a special unique problem" in their eyes.

     

     

    Link to comment

    so, short update.

    @JorgeB

    todays morning my server crashed.

     

    the macvlan call trace was right after booting two days before. server runs without any problems from there for two days.

    when i tried opening the web gui i got messages from uptime-kuma and uptime-robot that the server becomes unresponsive. ssh, monitor/keyboard also didn't worked.

     

    anything to do next?

    Edited by sonic6
    Link to comment
    34 minutes ago, ChatNoir said:

    You should setup a syslog server and post it after the next crash.

    okay, i did.

    if this won't help, i can mirrow the syslog to my flashdrive in the next step.

    Link to comment

    I am not sure what is happening here, but it is not macvlan related.

     

    The call trace is network related and in the dhcp log there is this message

     

    May 02 06:56:09 [1130]: route socket overflowed (rcvbuflen 106496) - learning interface state
    May 02 06:56:09 [1130]: drained 123 messages

     

    Can you try in IPv4 only mode?

     

    • Like 2
    Link to comment

    Okay, this time IPv4 without Host Access.

     

    But what i noticed:

    image.thumb.png.ad688475977bde2d02cea06864390c23.png

     

    image.thumb.png.b10df300682fb6e06a09f4abfcdbdd5c.png

     

    image.thumb.png.727bd82f2590514eed4d3d9723818108.png

     

    Unraid itself and Dockers aren't pingable with ipv6, but the LXC Container is:

    PS C:\Users\domib> ping [fd00::99]
    
    Ping wird ausgeführt für fd00::99 mit 32 Bytes Daten:
    Antwort von fd00::99: Zeit<1ms
    Antwort von fd00::99: Zeit<1ms
    Antwort von fd00::99: Zeit<1ms
    Antwort von fd00::99: Zeit<1ms
    
    Ping-Statistik für fd00::99:
        Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
        (0% Verlust),
    Ca. Zeitangaben in Millisek.:
        Minimum = 0ms, Maximum = 0ms, Mittelwert = 0ms
    PS C:\Users\domib> ping wpad.fritz.box -6
    
    Ping wird ausgeführt für wpad.fritz.box [fd00::99] mit 32 Bytes Daten:
    Antwort von fd00::99: Zeit<1ms
    Antwort von fd00::99: Zeit<1ms
    Antwort von fd00::99: Zeit<1ms
    Antwort von fd00::99: Zeit<1ms
    
    Ping-Statistik für fd00::99:
        Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
        (0% Verlust),
    Ca. Zeitangaben in Millisek.:
        Minimum = 0ms, Maximum = 0ms, Mittelwert = 0ms
    PS C:\Users\domib> ping piholelxc.fritz.box
    
    Ping wird ausgeführt für piholelxc.fritz.box [192.168.0.11] mit 32 Bytes Daten:
    Antwort von 192.168.0.11: Bytes=32 Zeit<1ms TTL=64
    Antwort von 192.168.0.11: Bytes=32 Zeit<1ms TTL=64
    Antwort von 192.168.0.11: Bytes=32 Zeit<1ms TTL=64
    Antwort von 192.168.0.11: Bytes=32 Zeit<1ms TTL=64
    
    Ping-Statistik für 192.168.0.11:
        Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
        (0% Verlust),
    Ca. Zeitangaben in Millisek.:
        Minimum = 0ms, Maximum = 0ms, Mittelwert = 0ms
    PS C:\Users\domib> ping piholelxc.fritz.box -6
    Ping-Anforderung konnte Host "piholelxc.fritz.box" nicht finden. Überprüfen Sie den Namen, und versuchen Sie es erneut.

    Inside of the LXC runs keepalived with the "virtual_ipaddress" 192.168.0.99 and fd00::99

    unraid-1-diagnostics-20230502-1554.zip

    Link to comment
    2 minutes ago, JorgeB said:

    FYI all those pastebin links are locked, at least to me.

    oh damn... geoblock. sorry. nevermind it is only kernel cut off from syslog. must be also in the diagnostic, right?

    Link to comment
    1 hour ago, sonic6 said:

    Unraid itself and Dockers aren't pingable with ipv6

     

    To me that looks like a configuration or network setup error. The PC, when it has both IPv4 and IPv6 addresses should be able to reach the server.

     

    I am running pi-hole as a docker container on my server, pinging it from my pc just works fine

     

    C:\>ping -4 10.0.101.100
    
    Pinging 10.0.101.100 with 32 bytes of data:
    Reply from 10.0.101.100: bytes=32 time<1ms TTL=64
    Reply from 10.0.101.100: bytes=32 time<1ms TTL=64
    Reply from 10.0.101.100: bytes=32 time<1ms TTL=64
    Reply from 10.0.101.100: bytes=32 time<1ms TTL=64
    
    Ping statistics for 10.0.101.100:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum = 0ms, Average = 0ms
    
    C:\>ping -6 2a02:a448:32d5:101::100
    
    Pinging 2a02:a448:32d5:101::100 with 32 bytes of data:
    Reply from 2a02:a448:32d5:101::100: time<1ms
    Reply from 2a02:a448:32d5:101::100: time<1ms
    Reply from 2a02:a448:32d5:101::100: time<1ms
    Reply from 2a02:a448:32d5:101::100: time<1ms
    
    Ping statistics for 2a02:a448:32d5:101::100:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum = 0ms, Average = 0ms
    
    C:\>

     

    Note: for this there is no need to enable host access (Unraid itself is not involved in this communication)

     

    Link to comment
    1 hour ago, sonic6 said:

    so, after enabling "host access"

     

    In your latest diagnostics there is indeed a macvlan call trace.

    Since you don't need host access, better switch it off.

     

    Link to comment
    37 minutes ago, bonienl said:

    To me that looks like a configuration or network setup error. The PC, when it has both IPv4 and IPv6 addresses should be able to reach the server.

    In this Case i used the "IPv4 only" mode, like you suggested. But my LXC Container was pingable over IPv6... i was just wondering.

     

     

    26 minutes ago, bonienl said:

    Since you don't need host access, better switch it off.

    I am using both in my setup, br0 and host access.

     

    Edited by sonic6
    Link to comment
    2 minutes ago, sonic6 said:

    In this Case i used the "IPv4 only" mode, like you suggested. But my LXC Container was pingable over IPv6... i was just wondering.

     

    Sorry, I misunderstood. In IPv4 only mode it is normal that IPv6 does not work.

    Apparently the LXC container does its own thing independently of the Unraid settings, I guess it is created with both ipv4 and ipv6 enabled.

     

    The DHCP error related to IPv6 and network call trace, I saw last time are not there anymore.

    Your router is set up using DHCP for IPv6, can it be changed  to use SLAAC instead?

     

    7 minutes ago, sonic6 said:

    I am using both in my setup, br0 and host access.

     

    Why do you need host access?

     

    Link to comment
    21 minutes ago, bonienl said:

    Your router is set up using DHCP for IPv6, can it be changed  to use SLAAC instead?

    I am not sure. To be fair, i am not a IPv6 Professional :D

    But if i'm right, it should be enough deactivating the DHCPv6 function in my router: https://en.avm.de/service/knowledge-base/dok/FRITZ-Box-7590/573_Configuring-IPv6-in-the-FRITZ-Box/

     

    Should i use no DHCPv6 Server, or using the M- and/or O- Flag?

     

     

    21 minutes ago, bonienl said:

    Why do you need host access?

    I need br0 for IP-Based traffic- and port-management.

    And i'm using a Debian Container for remote access. When i disable host access, i can't reach all my containers from the Debian Container.

     

    Edited by sonic6
    Link to comment
    4 minutes ago, sonic6 said:

    But if i'm right, it should be enough deactivating the DHCPv6 function in my router

     

    The manual isn't very clear when disabling the DHCPv6 function, it will use only SLAAC.

    You can try, and it might be necessary to set a fixed DNSv6 server in your Unraid system. You can use the Google servers:

    2001:4860:4860::8888 and/or 2001:4860:4860::8844

     

    Link to comment
    4 minutes ago, bonienl said:

    The manual isn't very clear when disabling the DHCPv6 function, it will use only SLAAC.

    Looks like it should:

    image.thumb.png.082b77f6875a3779487d3eecaaebfc3d.png

     

    5 minutes ago, bonienl said:

    You can try, and it might be necessary to set a fixed DNSv6 server in your Unraid system.

    My pihole is reachable on ipv6 over fd00::99

    Link to comment



    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...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.