• 6.10rc1 Thunderbolt support


    Omri
    • Minor

    Hi

    Glad to see that Unraid is getting proper Thunderbolt support

    I have a few question about the support

    1.how do I authorizea device?

    for now I use 99-removable.rules in /etc/udev to remove security but it's not permanent and required after every boot.

    is there an equivalent to (for example) boltd/boltctl?

    2.I can manually use "ifconig thunderbolt0 IP up" to assign ip and activate the interface

    but it's still not showing under the gui "network settings"

    3.after doing the above manually, my Mac see Tower under system report

    but it won't connect even after giving the thunderbolt static ip in same subnet

    (tower is 192.168.1.1 and Mac is 192.168.1.2 which is different from my router pool)

    so in the end, network isn't working 

     

    attached unraid diagnostics, ifconfig output from tower and relevant mac settings

    Thanks

    any help/guide will be appreciated.

    382563002_ScreenShot2021-08-12at16_27_59.png.31878fcde7e1c292ac188d0d2ec3404c.png

    624550352_ScreenShot2021-08-12at16_31_30.png.f295973f1c0641903f1abf35670c95e8.png

    750936585_ScreenShot2021-08-12at16_32_28.png.9889f6784b6adb91bd511ea8d1129984.png

    tower-diagnostics-20210813-0903.zip




    User Feedback

    Recommended Comments



    @Omrifor point 1 you can create the file on flash.

     

    In the /boot/config/go

    cp file /etc/udev/rules.d/

    Chmod 644 on the file

    udevadm control --reload-rules

     

    Not sure on other points has dont haveTB. Its likely gui is looking for eth.

    Link to comment

    Hi

    I can bypass 1, by changing bios settings to not secure or by using what you suggested

    I can bypass 2 by editing network.cfg and adding this lines

    IFNAME[1]="thunderbolt0"

    IPADDR[1]="192.168.1.1"
    NETMASK[1]="255.255.255.0"

    USE_DHCP[1]="no"

    SYSNICS="2"

     

    but the end result is the same :(

    it looks fine on unraid end, but the mac won't connect

    when I boot the server with Ubuntu, it's immediately recognize the thunderbolt as network

    and the connection between the server and my mac is fine (almost twice as fast as 10GBE).

     

    Link to comment

    .. still 2 weeks before i can touch my System again, thats why i ask here is this problem solved or was the statement that "thunderbolt support" was added in 6.10 only hot air ?

    Link to comment

    My understanding is that Thunderbolt drivers were added so that people could try accessing certain devices from within Docker containers. No changes were made to the networking subsystem to support Thunderbolt nics within Unraid itself.

    Link to comment

    Well lets summarize the truth ...

    The "add on" Thunderbolt is wanted by just a few poeple who see the advantage of this technologie ( Hope more see the Light when USB4 ist final out)

    The developers of Unraid never realy looked into it, as the do not have the "Hardware" 

    Now they finaly added the driver but didnt connect the neccesary routes to the core.

     

    I can understand the developers.. is it fair and legit ?... i doubt.

    How they can "promote" it  but never ever tested it.  We enduser are there testers, Who paid for things that are not ready 😞

     

     

    Link to comment
    22 hours ago, Omri said:

    Thunderbolt is recognized, but can't seem to use it as network interface.

    @bonienl might be able to comment if this is something that can be remedied easily (or not) ?

    Link to comment

    From another thread where we are looking at getting QNAP 5Gb USB adapters working boniel has said that the device name needs to be eth*

     

    So we may be able to create udev rules to rename Thunder0 to eth10 for example. I havent look at the code for network pages as yet within the GUI so it may need to be there at reboot to create the network pages.

     

    I am awaiting for the QNAP device to arrive but we have created plugin to load the driver so I can test further. I dont have TB so cannot test anything.

     

    List the udev results for the adapter, i.e. for thunderbolt0 in this case.

     

    root@unraid:~# udevadm info -a -p /sys/class/net/eth2
    
    Udevadm info starts with the device specified by the devpath and then
    walks up the chain of parent devices. It prints for every device
    found, all possible attributes in the udev rules key format.
    A rule to match, can be composed by the attributes of the device
    and the attributes from one single parent device.
    
      looking at device '/devices/pci0000:00/0000:00:02.0/0000:06:00.0/net/eth2':
        KERNEL=="eth2"
        SUBSYSTEM=="net"
        DRIVER==""
        ATTR{carrier_changes}=="0"
        ATTR{testing}=="0"
        ATTR{carrier}=="0"
        ATTR{dev_id}=="0x0"
        ATTR{carrier_down_count}=="0"
        ATTR{proto_down}=="0"
        ATTR{address}=="f4:52:14:8b:46:21"
        ATTR{operstate}=="down"
        ATTR{link_mode}=="0"
        ATTR{dormant}=="0"
        ATTR{mtu}=="1500"
        ATTR{gro_flush_timeout}=="0"
        ATTR{carrier_up_count}=="0"
        ATTR{ifalias}==""
        ATTR{speed}=="-1"
        ATTR{netdev_group}=="0"
        ATTR{napi_defer_hard_irqs}=="0"
        ATTR{ifindex}=="14"
        ATTR{broadcast}=="ff:ff:ff:ff:ff:ff"
        ATTR{type}=="1"
        ATTR{dev_port}=="0"
        ATTR{phys_port_id}=="f4521403008b4621"
        ATTR{duplex}=="unknown"
        ATTR{addr_assign_type}=="0"
        ATTR{addr_len}=="6"
        ATTR{tx_queue_len}=="1000"
        ATTR{iflink}=="14"
        ATTR{flags}=="0x1003"
    
      looking at parent device '/devices/pci0000:00/0000:00:02.0/0000:06:00.0':
        KERNELS=="0000:06:00.0"
        SUBSYSTEMS=="pci"
        DRIVERS=="mlx4_core"
        ATTRS{mlx4_port2_mtu}=="4096"
        ATTRS{broken_parity_status}=="0"
        ATTRS{subsystem_device}=="0x0076"
        ATTRS{dma_mask_bits}=="64"
        ATTRS{mlx4_port1}=="eth"
        ATTRS{vendor}=="0x15b3"
        ATTRS{local_cpus}=="000f,ff000fff"
        ATTRS{class}=="0x020000"
        ATTRS{numa_node}=="0"
        ATTRS{max_link_width}=="8"
        ATTRS{msi_bus}=="1"
        ATTRS{device}=="0x1003"
        ATTRS{current_link_width}=="8"
        ATTRS{max_link_speed}=="8.0 GT/s PCIe"
        ATTRS{local_cpulist}=="0-11,24-35"
        ATTRS{mlx4_port2}=="eth"
        ATTRS{driver_override}=="(null)"
        ATTRS{d3cold_allowed}=="1"
        ATTRS{irq}=="28"
        ATTRS{revision}=="0x00"
        ATTRS{current_link_speed}=="8.0 GT/s PCIe"
        ATTRS{consistent_dma_mask_bits}=="64"
        ATTRS{mlx4_port1_mtu}=="4096"
        ATTRS{ari_enabled}=="1"
        ATTRS{enable}=="1"
        ATTRS{subsystem_vendor}=="0x15b3"
    
      looking at parent device '/devices/pci0000:00/0000:00:02.0':
        KERNELS=="0000:00:02.0"
        SUBSYSTEMS=="pci"
        DRIVERS=="pcieport"
        ATTRS{secondary_bus_number}=="6"
        ATTRS{subordinate_bus_number}=="6"
        ATTRS{aer_rootport_total_err_cor}=="0"
        ATTRS{broken_parity_status}=="0"
        ATTRS{subsystem_device}=="0x0e04"
        ATTRS{dma_mask_bits}=="32"
        ATTRS{vendor}=="0x8086"
        ATTRS{local_cpus}=="000f,ff000fff"
        ATTRS{class}=="0x060400"
        ATTRS{numa_node}=="0"
        ATTRS{max_link_width}=="16"
        ATTRS{aer_rootport_total_err_fatal}=="0"
        ATTRS{msi_bus}=="1"
        ATTRS{device}=="0x0e04"
        ATTRS{label}==" Onboard IGD"
        ATTRS{index}=="1"
        ATTRS{current_link_width}=="8"
        ATTRS{max_link_speed}=="8.0 GT/s PCIe"
        ATTRS{local_cpulist}=="0-11,24-35"
        ATTRS{driver_override}=="(null)"
        ATTRS{d3cold_allowed}=="1"
        ATTRS{irq}=="29"
        ATTRS{revision}=="0x04"
        ATTRS{current_link_speed}=="8.0 GT/s PCIe"
        ATTRS{consistent_dma_mask_bits}=="32"
        ATTRS{ari_enabled}=="0"
        ATTRS{enable}=="1"
        ATTRS{aer_rootport_total_err_nonfatal}=="0"
        ATTRS{subsystem_vendor}=="0x8086"
    
      looking at parent device '/devices/pci0000:00':
        KERNELS=="pci0000:00"
        SUBSYSTEMS==""
        DRIVERS==""
    
    E: IFINDEX=14
    E: INTERFACE=eth2
    E: SUBSYSTEM=net
    E: USEC_INITIALIZED=41094952

     

    Existing rule rules.

    root@unraid:~# cat /etc/udev/rules.d/70-persistent-net.rules 
    
    # PCI device 0x8086:0x1521 (igb)
    SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="ac:1f:6b:96:0b:7e", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
    
    # PCI device 0x8086:0x1521 (igb)
    SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="ac:1f:6b:96:0b:7f", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
    
    # PCI device 0x15b3:0x1003 (mlx4_core)
    SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="f4:52:14:8b:46:21", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"
    
    # PCI device 0x15b3:0x1003 (mlx4_core)
    SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="f4:52:14:8b:46:22", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3"
    root@unraid:~# 

     

    Create a udev rule, not sure if the kernel will be eth.

     

    root@unraid:~# cat /etc/udev/rules.d/71-persistent-net.rules 
    
    # Thunderbolt
    SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="02:1f:1e:cf:86:86", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth10"

     

    udevadm control --reload

    udevadm trigger --action=add --attr-match=address="02:1f:1e:cf:86:86"

    Edited by SimonF
    • Like 1
    • Thanks 1
    Link to comment

    Hello world,

    Thunderbolt on Unraid finaly works

    Device per Unraid connected -- works ! ( This weekend i will add my DIY TB4 to SAS to 24x 12TB HDD) to make my first Backup,  i will report here how it went !

    TB3/4 Networking working with 20GB Speed between Unraid and Windows !

     

    I super stoked about it, many thanks to the big support here !

     

    Thank u !

    • Like 1
    Link to comment
    Just now, Dtrain said:

    Hello world,

    Thunderbolt on Unraid finaly works

    Device per Unraid connected -- works ! ( This weekend i will add my DIY TB4 to SAS to 24x 12TB HDD) to make my first Backup,  i will report here how it went !

    TB3/4 Networking working with 20GB Speed between Unraid and Windows !

     

    I super stoked about it, many thanks to the big support here !

     

    Thank u !

    Cool, can you confirm actions you carried out?

     

     

    Link to comment

    Basicly followed ur instructions, and amended the Udev rules for removable disks and network, thats it.

     

    grafik.thumb.png.27a15386b36d5a698c1e0c476fbdb77e.png

    Edited by Dtrain
    • Like 1
    Link to comment

    Hi

    @SimonF @Dtrain

    I followed your post

    but can't seem to make it work

    here is my output for udevadm info -a -p /sys/class/net/thunderbolt0

     

    Udevadm info starts with the device specified by the devpath and then
    walks up the chain of parent devices. It prints for every device
    found, all possible attributes in the udev rules key format.
    A rule to match, can be composed by the attributes of the device
    and the attributes from one single parent device.
    
      looking at device '/devices/pci0000:00/0000:00:1b.4/0000:03:00.0/0000:04:00.0/0000:05:00.0/domain0/0-0/0-1/0-1.0/net/thunderbolt0':
        KERNEL=="thunderbolt0"
        SUBSYSTEM=="net"
        DRIVER==""
        ATTR{carrier_changes}=="0"
        ATTR{dev_id}=="0x0"
        ATTR{carrier_down_count}=="0"
        ATTR{proto_down}=="0"
        ATTR{address}=="02:1f:1e:cf:86:86"
        ATTR{operstate}=="down"
        ATTR{link_mode}=="0"
        ATTR{mtu}=="1500"
        ATTR{gro_flush_timeout}=="0"
        ATTR{carrier_up_count}=="0"
        ATTR{ifalias}==""
        ATTR{netdev_group}=="0"
        ATTR{napi_defer_hard_irqs}=="0"
        ATTR{ifindex}=="10"
        ATTR{broadcast}=="ff:ff:ff:ff:ff:ff"
        ATTR{type}=="1"
        ATTR{dev_port}=="0"
        ATTR{addr_assign_type}=="0"
        ATTR{addr_len}=="6"
        ATTR{threaded}=="0"
        ATTR{tx_queue_len}=="1000"
        ATTR{iflink}=="10"
        ATTR{flags}=="0x1002"
    
      looking at parent device '/devices/pci0000:00/0000:00:1b.4/0000:03:00.0/0000:04:00.0/0000:05:00.0/domain0/0-0/0-1/0-1.0':
        KERNELS=="0-1.0"
        SUBSYSTEMS=="thunderbolt"
        DRIVERS=="thunderbolt-net"
        ATTRS{prtcstns}=="0x00000003"
        ATTRS{prtcvers}=="1"
        ATTRS{prtcrevs}=="1"
        ATTRS{key}=="network"
        ATTRS{prtcid}=="1"
    
      looking at parent device '/devices/pci0000:00/0000:00:1b.4/0000:03:00.0/0000:04:00.0/0000:05:00.0/domain0/0-0/0-1':
        KERNELS=="0-1"
        SUBSYSTEMS=="thunderbolt"
        DRIVERS==""
        ATTRS{vendor_name}=="Apple Inc."
        ATTRS{maxhopid}=="15"
        ATTRS{vendor}=="0xa27"
        ATTRS{device}=="0xa"
        ATTRS{rx_lanes}=="1"
        ATTRS{rx_speed}=="20.0 Gb/s"
        ATTRS{unique_id}=="6f46b3a2-b973-4458-a3ff-b8193a7114b5"
        ATTRS{tx_lanes}=="1"
        ATTRS{tx_speed}=="20.0 Gb/s"
        ATTRS{device_name}=="Macmini8,1"
    
      looking at parent device '/devices/pci0000:00/0000:00:1b.4/0000:03:00.0/0000:04:00.0/0000:05:00.0/domain0/0-0':
        KERNELS=="0-0"
        SUBSYSTEMS=="thunderbolt"
        DRIVERS==""
        ATTRS{nvm_authenticate}=="0x0"
        ATTRS{vendor_name}=="ASUS"
        ATTRS{vendor}=="0x31"
        ATTRS{generation}=="3"
        ATTRS{device}=="0x5007"
        ATTRS{nvm_version}=="56.0"
        ATTRS{unique_id}=="cf030000-0070-740e-033a-832f2c337126"
        ATTRS{device_name}=="PROART Z490-CREATOR 10G"
    
      looking at parent device '/devices/pci0000:00/0000:00:1b.4/0000:03:00.0/0000:04:00.0/0000:05:00.0/domain0':
        KERNELS=="domain0"
        SUBSYSTEMS=="thunderbolt"
        DRIVERS==""
        ATTRS{boot_acl}==",,,,,,,,,,,,,,,"
        ATTRS{security}=="none"
        ATTRS{deauthorization}=="0"
        ATTRS{iommu_dma_protection}=="1"
    
      looking at parent device '/devices/pci0000:00/0000:00:1b.4/0000:03:00.0/0000:04:00.0/0000:05:00.0':
        KERNELS=="0000:05:00.0"
        SUBSYSTEMS=="pci"
        DRIVERS=="thunderbolt"
        ATTRS{power_state}=="D0"
        ATTRS{broken_parity_status}=="0"
        ATTRS{subsystem_device}=="0x8794"
        ATTRS{dma_mask_bits}=="64"
        ATTRS{vendor}=="0x8086"
        ATTRS{local_cpus}=="fff"
        ATTRS{class}=="0x088000"
        ATTRS{numa_node}=="-1"
        ATTRS{max_link_width}=="4"
        ATTRS{msi_bus}=="1"
        ATTRS{device}=="0x15eb"
        ATTRS{current_link_width}=="4"
        ATTRS{max_link_speed}=="2.5 GT/s PCIe"
        ATTRS{local_cpulist}=="0-11"
        ATTRS{driver_override}=="(null)"
        ATTRS{d3cold_allowed}=="1"
        ATTRS{irq}=="16"
        ATTRS{revision}=="0x06"
        ATTRS{current_link_speed}=="2.5 GT/s PCIe"
        ATTRS{consistent_dma_mask_bits}=="64"
        ATTRS{ari_enabled}=="0"
        ATTRS{enable}=="1"
        ATTRS{subsystem_vendor}=="0x1043"
    
      looking at parent device '/devices/pci0000:00/0000:00:1b.4/0000:03:00.0/0000:04:00.0':
        KERNELS=="0000:04:00.0"
        SUBSYSTEMS=="pci"
        DRIVERS=="pcieport"
        ATTRS{secondary_bus_number}=="5"
        ATTRS{power_state}=="D0"
        ATTRS{subordinate_bus_number}=="5"
        ATTRS{broken_parity_status}=="0"
        ATTRS{subsystem_device}=="0x8794"
        ATTRS{dma_mask_bits}=="32"
        ATTRS{vendor}=="0x8086"
        ATTRS{local_cpus}=="fff"
        ATTRS{class}=="0x060400"
        ATTRS{numa_node}=="-1"
        ATTRS{max_link_width}=="4"
        ATTRS{msi_bus}=="1"
        ATTRS{device}=="0x15ea"
        ATTRS{current_link_width}=="4"
        ATTRS{max_link_speed}=="8.0 GT/s PCIe"
        ATTRS{local_cpulist}=="0-11"
        ATTRS{driver_override}=="(null)"
        ATTRS{d3cold_allowed}=="1"
        ATTRS{irq}=="128"
        ATTRS{revision}=="0x06"
        ATTRS{current_link_speed}=="2.5 GT/s PCIe"
        ATTRS{consistent_dma_mask_bits}=="32"
        ATTRS{ari_enabled}=="0"
        ATTRS{enable}=="1"
        ATTRS{subsystem_vendor}=="0x1043"
    
      looking at parent device '/devices/pci0000:00/0000:00:1b.4/0000:03:00.0':
        KERNELS=="0000:03:00.0"
        SUBSYSTEMS=="pci"
        DRIVERS=="pcieport"
        ATTRS{secondary_bus_number}=="4"
        ATTRS{power_state}=="D0"
        ATTRS{subordinate_bus_number}=="109"
        ATTRS{broken_parity_status}=="0"
        ATTRS{subsystem_device}=="0x8794"
        ATTRS{dma_mask_bits}=="32"
        ATTRS{vendor}=="0x8086"
        ATTRS{local_cpus}=="fff"
        ATTRS{class}=="0x060400"
        ATTRS{numa_node}=="-1"
        ATTRS{max_link_width}=="4"
        ATTRS{msi_bus}=="1"
        ATTRS{device}=="0x15ea"
        ATTRS{current_link_width}=="4"
        ATTRS{max_link_speed}=="8.0 GT/s PCIe"
        ATTRS{local_cpulist}=="0-11"
        ATTRS{driver_override}=="(null)"
        ATTRS{d3cold_allowed}=="1"
        ATTRS{irq}=="16"
        ATTRS{revision}=="0x06"
        ATTRS{current_link_speed}=="8.0 GT/s PCIe"
        ATTRS{consistent_dma_mask_bits}=="32"
        ATTRS{ari_enabled}=="0"
        ATTRS{enable}=="2"
        ATTRS{subsystem_vendor}=="0x1043"
    
      looking at parent device '/devices/pci0000:00/0000:00:1b.4':
        KERNELS=="0000:00:1b.4"
        SUBSYSTEMS=="pci"
        DRIVERS=="pcieport"
        ATTRS{secondary_bus_number}=="3"
        ATTRS{power_state}=="D0"
        ATTRS{subordinate_bus_number}=="109"
        ATTRS{aer_rootport_total_err_cor}=="0"
        ATTRS{broken_parity_status}=="0"
        ATTRS{subsystem_device}=="0x8694"
        ATTRS{dma_mask_bits}=="32"
        ATTRS{vendor}=="0x8086"
        ATTRS{local_cpus}=="fff"
        ATTRS{class}=="0x060400"
        ATTRS{numa_node}=="-1"
        ATTRS{max_link_width}=="4"
        ATTRS{aer_rootport_total_err_fatal}=="0"
        ATTRS{msi_bus}=="1"
        ATTRS{device}=="0x06ac"
        ATTRS{current_link_width}=="4"
        ATTRS{max_link_speed}=="8.0 GT/s PCIe"
        ATTRS{local_cpulist}=="0-11"
        ATTRS{driver_override}=="(null)"
        ATTRS{d3cold_allowed}=="1"
        ATTRS{irq}=="124"
        ATTRS{revision}=="0xf0"
        ATTRS{current_link_speed}=="8.0 GT/s PCIe"
        ATTRS{consistent_dma_mask_bits}=="32"
        ATTRS{ari_enabled}=="0"
        ATTRS{enable}=="2"
        ATTRS{aer_rootport_total_err_nonfatal}=="0"
        ATTRS{subsystem_vendor}=="0x1043"
    
      looking at parent device '/devices/pci0000:00':
        KERNELS=="pci0000:00"
        SUBSYSTEMS==""
        DRIVERS==""
        ATTRS{waiting_for_supplier}=="0"

     

    I created /etc/udev/rules.d/71-persistent-net.rules

    Quote

    root@Tower:~# cat /etc/udev/rules.d/71-persistent-net.rules

    # Thunderbolt

    SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="02:1f:1e:cf:86:86", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth10"

     

    and still network doesn't work after these:

    udevadm control --reload

    udevadm trigger --action=add --attr-match=address="02:1f:1e:cf:86:86"

    any help will be appriciated

     

    Link to comment
    On 9/3/2021 at 6:37 PM, Omri said:

    any help will be appriciated

    how many nics do you have try eth3 instead of 10 if you dont have an eth3

    Link to comment

    Hi @SimonF

    I had it wrong before, didn't replace KERNEL=="eth* with KERNEL=="thunderbolt*

    now I get eth10/3 (doesn't seem to matter) in ifconfig and Unraid network settings

    I still can't get the connection to work though.

    with Ubuntu for example, I set static IP (different from my DHCP range)

    for example - server 192.168.1.2 an PC 192.168.1.3 and that's it

    now after setting it, no connection (can't ping either)

    I'm on mac (as you can see from the output before which is strange cause it's detecting my mac with 20GB/s link)

    Link to comment

    Just a little update

    on windows it's ( kind of) work

    I can establish 20gb/s link but the real transfer speed is ridiculous (less than 10mb/s)

    will continue testing

     

    Thanks

    Link to comment

    Another update

    when using Windows 10 - it doesn't matter if the device is eth* or thunderbolt*

    I can establish connection (shows as 20gb/s) but it's not reliable

    from pc to tower link is very slow, few mb/s

    from tower to pc it's not as fast as it should be but it's better +/- 4gb/s

    not matter if coping file or using iperf3 (one time as client and other as server)

    maybe it's a driver issue...

     

    when switching to mac os - still can't establish connection (although my mac is recognized in tower)

     

    tower booted with ubuntu instead of unraid:

    with windows same behaviour

    with mac os - full speed both ways

     

    out of ideas :)

     

     

     

     

    Link to comment

     

    looks like TB3/TB4 support is broken in rc2 again

    after reverted back to rc1 all works fine (again)

    Edited by Dtrain
    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.