bonienl

Community Developer
  • Posts

    10233
  • Joined

  • Last visited

  • Days Won

    65

Posts posted by bonienl

  1. 8 minutes ago, michaelmurfy said:

    I'm not fully confident this is the sole reason for the issues given the host is getting an IP

     

    IPv6 works a bit different and doesn't like loops (it is doing multicast).

     

    As I said, change the bonding mode for testing purposes, it will give you a better view what to look for.

     

  2. 9 minutes ago, michaelmurfy said:

    Yep - switch (Mikrotik) sure does and is working as expected.

     

    As a test you can change the bonding mode to "Active-Standby" as see if the NFS service is able to bind to the interface (this is new in 6.12.0)

     

    The error message you receive is because both sides of the bond are initially in different states and the bond acts as a layer 2 connection with one or more loops.

    It could be a timing issue (perhaps configurable), but I am not familiar with Mikrotik.

     

  3. How do you access the GUI, by name or by IP address?

    Try IP address and see if that makes a difference.

     

    I see in your configuration that you use IPv6 link local addresses for the DNS servers.

    I don't know if that works, the usual approach is to take the regular IPv6 address of your router (or alternatively one of the public IPv6 DNS servers from google or cloudflare)

     

  4. You have set up bonding with LACP, but it returns an error.

    Does your switch support LACP and is it properly configured?

     

    Jun 18 01:49:15 Pikachu kernel: br0: received packet on bond0 with own address as source address (addr:5c:ba:2c:25:c4:48, vlan:0)

     

    The network error is the reason for not accepting the IPv6 address.

  5. If you only complain but don't provide more detailed information (diagnostics), we can't do much.

    6.12.0 is a lot strickter and unfortunately people start to discover now incorrect settings from the past.

     

    NFS and IPv6 should work. Here is an extract from my log

     

    Jun 17 16:50:06 vesta root: Starting NFS server daemons:
    Jun 17 16:50:06 vesta root: /usr/sbin/exportfs -r Jun 17 16:50:06 vesta root: /usr/sbin/rpc.nfsd -u -s -H 10.0.101.11 -H 2a02:a448:32d5:101:xxxx:xxxx:xxxx:xxxx -H 10.253.0.1 -H 127.0.0.1 -H ::1 8 
    Jun 17 16:50:07 vesta root: /usr/sbin/rpc.mountd
    Jun 17 16:50:07 vesta kernel: NFSD: Using UMH upcall client tracking operations.
    Jun 17 16:50:07 vesta kernel: NFSD: starting 90-second grace period (net f0000000)

     

  6. On 5/29/2023 at 11:28 AM, Revan335 said:

    I can't move to unlimited Directory Level.

    For example /mnt/disk3/Backup_folder/Daten/user/Client move /mnt/disk1/Backup_folder/Daten/ ended there. I can't selected underlying directory level /user/ or /user/Client

     

    Thanks, made a fix.

     

    • Thanks 2