SMB Performance Woes

R

Rakkzi

New Member
Mar 25, 2026
4
0
1
I've been working on setting up a high performance NAS to host storage for some VMs/LXCs and Windows PCs, and while I'm able to get 200k+ IOPS on the Windows PCs through the 56G Infiniband link, for some reason my Proxmox node is only getting 6000.. (according to fio):
proxmox FIO.png

I'm using fstab to mount the share via the Windows Server's Infiniband interface IP (i.e. \\169.254.81.150\sharename). I tried hooking in a 40GBe link directly between the Proxmox and the Windows Server, but I haven't been able to get it to work correctly, ping is telling me the host isn't reachable (the 40G interface IP on the windows machine; 169.254.82.151), but if I use ping with the -I command and specify the 40G interface, it works just fine.

I tried to do some SMB Multichannel stuff but I have no idea how to make it work on Proxmox, looked into mounting via hostname and handling that with DNS but mainly due to the aformentioned issue I'm having where it can't "normally" reach the 40G Ethernet interface (and being somewhat lost/over my head) I ended up giving up on it.
Diagram of my network topology:
NetworkDiagram.png
The 40Gbe / multichannel was mostly just to try troubleshooting the connection since there's not any tools (iperf doesn't work very good for RDMA ime) for testing connection performance of IB between windows and linux, but disabling the IB interface on proxmox and setting the fstab mount point to the 40Gbe interface (169.254.82.151) still doesn't mount/ping. The subnets being different was on account of reading that it was recommended for SMB multichannel on linux. I also wanted to use it as a backup bridge in case I can't use IB in a VM.

I tested the SRIOV (ETH Only) performance in a Ubuntu VM, it was able to talk over the 40Gbe to the windows server out of the box, but also showed similarly bad results:
Screenshot 2026-03-29 094654.png
(sanity tested on windows 11 client immediately after and it's still showing 240k+ IOPS)

RDMA Link shows both being Active with Link up on both the proxmox host and the VM:
1774783396122.png
1774792882088.png

I know this is a lot of text, but tl;dr - how do I figure out where my network IOPS are going between proxmox and the Windows Server?
Any help is much appreciated in advance <3
 
Hi,

The issue with pinging is normal - I mean 169. are link local addresses and the stack doesn't know which interface to use unless you specify it explicitely.

Given that the Ubuntu VM with SR-IOV also gets bad IOPS, but Windows clients are fine, the problem is almost certainly that Linux's CIFS/SMB Direct implementation isn't activating RDMA, and you're bottlenecking on TCP processing or kernel SMB overhead. The rdma mount option + vers=3.1.1 + cache=none combo is the first thing to try.

Can you share your current fstab entry and the output of cat /proc/fs/cifs/DebugData? That'll make the diagnosis much more precise.
 
psalkiewicz said:
Hi,

The issue with pinging is normal - I mean 169. are link local addresses and the stack doesn't know which interface to use unless you specify it explicitely.

Given that the Ubuntu VM with SR-IOV also gets bad IOPS, but Windows clients are fine, the problem is almost certainly that Linux's CIFS/SMB Direct implementation isn't activating RDMA, and you're bottlenecking on TCP processing or kernel SMB overhead. The rdma mount option + vers=3.1.1 + cache=none combo is the first thing to try.

Can you share your current fstab entry and the output of cat /proc/fs/cifs/DebugData? That'll make the diagnosis much more precise.
Click to expand...

Gotcha, the ping issue with the link local addresses makes sense. Should I just assign static IPs to the interfaces, then? I was getting conflicting information about that + subnets.

I tried adding rdma + vers=3.1.1 + cache=none, but it didn't seem to make a difference.

Current ftsab entry: //169.254.81.150/Vault /mnt/lxc_shares/Vault cifs _netdev,x-systemd.automount,noatime,cache=none,rdma,vers=3.1.1,multichannel,max_channels=4,nobrl,uid=100999,gid=100990,dir_mode=0770,file_mode=0770,username=[share username],password=[share password],iocharset=utf8 0 0

I did notice it's saying the server has no multichannel support in journalctl:
1775879325307.png


and the output of cat /proc/fs/cifs/DebugData:

Code: 
Display Internal CIFS Data Structures for Debugging
---------------------------------------------------
CIFS Version 2.56
Features: DFS,FSCACHE,SMB_DIRECT,STATS,DEBUG,ALLOW_INSECURE_LEGACY,CIFS_POSIX,UPCALL(SPNEGO),XATTR,ACL,WITNESS
CIFSMaxBufSize: 16384
Active VFS Requests: 0

Servers:
1) ConnectionId: 0x2 Hostname: 169.254.81.150
ClientGUID: 80690519-C6F9-A949-AACC-1D4945E25CEB
SMBDirect (in hex) protocol version: 100 transport status: 2
Conn receive_credit_max: ff send_credit_target: ff max_send_size: 554
Conn max_fragmented_recv_size: 100000 max_fragmented_send_size: 100000 max_receive_size:554
Conn keep_alive_interval: 7270e00 max_readwrite_size: 1ff000 rdma_readwrite_threshold: 1000
Debug count_get_receive_buffer: 583e8 count_put_receive_buffer: 582e9 count_send_empty: 14c3
Read Queue count_reassembly_queue: 0 count_enqueue_reassembly_queue: 582e4 count_dequeue_reassembly_queue: 582e4 reassembly_data_length: 0 reassembly_queue_length: 0
Current Credits send_credits: ff receive_credits: fe receive_credit_target: ff
Pending send_pending: 0
Receive buffers count_receive_queue: 0
MR responder_resources: 10 max_frmr_depth: 1ff mr_type: 0
MR mr_ready_count: 20 mr_used_count: 0
Number of credits: 8190,1,1 Dialect 0x311
Server capabilities: 0x30006f
RDMA
TCP status: 1 Instance: 1
Local Users To Server: 4 SecMode: 0x1 Req On Wire: 0 Net namespace: 4026531833
In Send: 0 In MaxReq Wait: 0
Compression: no built-in support
Encryption: Negotiated cipher (AES128-GCM)

        Sessions:
        1) Address: 169.254.81.150 Uses: 1 Capability: 0x30006f Session Status: 1
        Security type: RawNTLMSSP  SessionId: 0x16870f400006d
        User: 100999 Cred User: 0

        Extra Channels: 3

                Channel: 2 ConnectionId: 0x3
                Number of credits: 8190,1,1 Dialect 0x311
                TCP status: 1 Instance: 1
                Local Users To Server: 1 SecMode: 0x1 Req On Wire: 0
                In Send: 0 In MaxReq Wait: 0 Net namespace: 4026531833

                Channel: 3 ConnectionId: 0x4
                Number of credits: 8190,1,1 Dialect 0x311
                TCP status: 1 Instance: 1
                Local Users To Server: 1 SecMode: 0x1 Req On Wire: 0
                In Send: 0 In MaxReq Wait: 0 Net namespace: 4026531833

                Channel: 4 ConnectionId: 0x5
                Number of credits: 8190,1,1 Dialect 0x311
                TCP status: 1 Instance: 1
                Local Users To Server: 1 SecMode: 0x1 Req On Wire: 0
                In Send: 0 In MaxReq Wait: 0 Net namespace: 4026531833

        Shares:
        0) IPC: \\169.254.81.150\IPC$ Mounts: 1 DevInfo: 0x0 Attributes: 0x0
        PathComponentMax: 0 Status: 1 type: 0 Serial Number: 0x0
        Share Capabilities: None        Share Flags: 0x30
        tid: 0x1        Maximal Access: 0x11f01ff

        1) \\169.254.81.150\Vault Mounts: 2 DevInfo: 0x20020 Attributes: 0xc700ee
        PathComponentMax: 255 Status: 1 type: DISK Serial Number: 0xbc92c893
        Share Capabilities: None Aligned, Partition Aligned, SSD, TRIM-support, Share Flags: 0x800
        tid: 0x5        Optimal sector size: 0x1000     Maximal Access: 0x1f01ff


        Server interfaces: 4    Last updated: 226 seconds ago
        1)      Speed: 56Gbps
                Capabilities: rdma rss
                IPv4: 169.254.81.150
                Weight (cur,total): (4,56)
                Allocated channels: 4
                [CONNECTED]

        2)      Speed: 40Gbps
                Capabilities: rdma rss
                IPv4: 169.254.82.151
                Weight (cur,total): (0,40)
                Allocated channels: 0

        3)      Speed: 1Gbps
                Capabilities: rss
                IPv4: 192.168.50.247
                Weight (cur,total): (0,1)
                Allocated channels: 0

        4)      Speed: 1Gbps
                Capabilities: rss
                IPv6: fe80:0000:0000:0000:ad46:1233:b1f5:35fa
                Weight (cur,total): (0,1)
                Allocated channels: 0


        MIDs:
--

2) ConnectionId: 0x1 Hostname: 169.254.81.150
ClientGUID: 536907F8-6B82-3D48-A40B-CD8995788A24
Number of credits: 8190,1,1 Dialect 0x311
Server capabilities: 0x300067
TCP status: 1 Instance: 1
Local Users To Server: 2 SecMode: 0x1 Req On Wire: 0 Net namespace: 4026531833
In Send: 0 In MaxReq Wait: 0
Compression: no built-in support
Encryption: Negotiated cipher (AES128-GCM)

        Sessions:
        1) Address: 169.254.81.150 Uses: 1 Capability: 0x300067 Session Status: 1
        Security type: RawNTLMSSP  SessionId: 0x168540400007d
        User: 0 Cred User: 0

        Shares:
        0) IPC: \\169.254.81.150\IPC$ Mounts: 1 DevInfo: 0x0 Attributes: 0x0
        PathComponentMax: 0 Status: 1 type: 0 Serial Number: 0x0
        Share Capabilities: None        Share Flags: 0x30
        tid: 0x1        Maximal Access: 0x11f01ff

        1) \\169.254.81.150\Vault Mounts: 1 DevInfo: 0x20020 Attributes: 0xc700ee
        PathComponentMax: 255 Status: 1 type: DISK Serial Number: 0xbc92c893
        Share Capabilities: None Aligned, Partition Aligned, SSD, TRIM-support, Share Flags: 0x800
        tid: 0x5        Optimal sector size: 0x1000     Maximal Access: 0x1f01ff


        Server interfaces: 4    Last updated: 865 seconds ago
        1)      Speed: 56Gbps
                Capabilities: rdma rss
                IPv4: 169.254.81.150
                Weight (cur,total): (1,56)
                Allocated channels: 1
                [CONNECTED]

        2)      Speed: 40Gbps
                Capabilities: rdma rss
                IPv4: 169.254.82.151
                Weight (cur,total): (0,40)
                Allocated channels: 0

        3)      Speed: 1Gbps
                Capabilities: rss
                IPv4: 192.168.50.247
                Weight (cur,total): (0,1)
                Allocated channels: 0

        4)      Speed: 1Gbps
                Capabilities: rss
                IPv6: fe80:0000:0000:0000:ad46:1233:b1f5:35fa
                Weight (cur,total): (0,1)
                Allocated channels: 0


        MIDs:
--

        2) Address: 169.254.81.150 Uses: 1 Capability: 0x300067 Session Status: 1
        Security type: RawNTLMSSP  SessionId: 0x16871e4000031
        User: 0 Cred User: 0

        Shares:
        0) IPC: \\169.254.81.150\IPC$ Mounts: 1 DevInfo: 0x0 Attributes: 0x0
        PathComponentMax: 0 Status: 1 type: 0 Serial Number: 0x0
        Share Capabilities: None        Share Flags: 0x30
        tid: 0x1        Maximal Access: 0x11f01ff

        1) \\169.254.81.150\Vault Mounts: 1 DevInfo: 0x20020 Attributes: 0xc700ee
        PathComponentMax: 255 Status: 1 type: DISK Serial Number: 0xbc92c893
        Share Capabilities: None Aligned, Partition Aligned, SSD, TRIM-support, Share Flags: 0x800
        tid: 0x5        Optimal sector size: 0x1000     Maximal Access: 0x1f01ff


        Server interfaces: 4    Last updated: 865 seconds ago
        1)      Speed: 56Gbps
                Capabilities: rdma rss
                IPv4: 169.254.81.150
                Weight (cur,total): (1,56)
                Allocated channels: 1
                [CONNECTED]

        2)      Speed: 40Gbps
                Capabilities: rdma rss
                IPv4: 169.254.82.151
                Weight (cur,total): (0,40)
                Allocated channels: 0

        3)      Speed: 1Gbps
                Capabilities: rss
                IPv4: 192.168.50.247
                Weight (cur,total): (0,1)
                Allocated channels: 0

        4)      Speed: 1Gbps
                Capabilities: rss
                IPv6: fe80:0000:0000:0000:ad46:1233:b1f5:35fa
                Weight (cur,total): (0,1)
                Allocated channels: 0


        MIDs:
--

Witness registrations:
 
Looks like RDMA isn't actually being used for data - mr_used_count: 0 means SMB Direct's RDMA memory registration engine has never been used. The connection negotiated RDMA/SMBDirect successfully, but actual I/O is falling back to regular TCP sends over the IB link. You're getting IB's bandwidth but at TCP latency/CPU overhead — hence the ~6K IOPS.

Connection 1 has 4 channels allocated, all on the 56G IB interface. The 40GbE interface shows Allocated channels: 0 on both connections — consistent with the routing issue you described. Connection 2 (used by LXCs based on the multiple sessions) only has 1 channel. So multichannel is negotiated but all channels are on one interface, and RDMA data path isn't engaging.

Code: 
Encryption: Negotiated cipher (AES128-GCM)


Both connections are encrypted. On Windows clients, AES-NI handles this in the network stack nearly for free. On Linux/CIFS, this is done in software and at high IOPS it becomes a serious CPU bottleneck. This alone can explain 200K→6K. It's easy to verify - just check cpu stats during the fio run. Except for the cpu usage I think that might be the reason why RDMA doesn't kick. I guess that software encryption excludes the use of RDMA. The best try is to disable encryption on the Windows side and give it a try again. Verify the CPU usage before and after and mr_used_count in the DebugData (if it's >0 it means that rdma kicked in).

Code: 
powershell# Check current setting
Get-SmbShare -Name "Vault" | Select EncryptData
Get-SmbServerConfiguration | Select EncryptData, RejectUnencryptedAccess

# Disable per-share 
Set-SmbShare -Name "Vault" -EncryptData $false

# Also ensure server-global isn't forcing it
Set-SmbServerConfiguration -EncryptData $false -RejectUnencryptedAccess $false

Regarding the ip addressing on the IB network - I would always assign private ip addressess to IB links instead of relying on link-local. Unless you have a very good reason for that (some rare device uses link local and cannot be changed). Link local addresses are unreliable, conflicts happen, compatibility issues, there are always problems with routing and I see no benefit of using them at all.

Please change it because it hurts my eyes when I see smb share on \\169.254 :-)
 
  • Like
Reactions: Johannes S
Thank you so much for your help! I got a pretty major breakthrough today!

The CPU was barely getting touched at all (<5%) while running FIO, so I tried changing the encryption but noticed it was already false, turned off the RejectUnencryptedAccess but that didn't change anything..
Debug is still saying it's negotiating AES128-GCM somehow even after this
1776019028218.png

However! While I was poking around, I noticed some interesting errors in journalctl:
1776019088246.png
The event=rejected and mention of a failed port stood out to me, so I thought to myself... "what if the windows server's defender firewall is blocking the RDMA port..", so I turned off the firewall to test, and look what happened:
1776023210588.png
It's beautiful..

I thought I was totally set and done, but after deleting the test file and re-running FIO, it dropped back down again to what it was before. :(
It seems like running FIO with a pre-existing test file (overwriting it?) gets me the full 200k+, but deleting it + running the test again runs badly (until I repeat the test with a test file already there).

I ran the debugger while doing a FIO test, and the mr_used_count went up to 20! Running it without an active test showed 0. (same results with a pre-existing test file and creating a new one)

Shortened the Server ConnectionId bits to fit in the character limit:
Code: 
Display Internal CIFS Data Structures for Debugging
---------------------------------------------------
CIFS Version 2.56
Features: DFS,FSCACHE,SMB_DIRECT,STATS,DEBUG,ALLOW_INSECURE_LEGACY,CIFS_POSIX,UPCALL(SPNEGO),XATTR,ACL,WITNESS
CIFSMaxBufSize: 16384
Active VFS Requests: 132

Servers: 
1) ConnectionId: 0x2 Hostname: 169.254.81.150 
ClientGUID: C409C044-1A66-D84C-8127-0C7C0F039EFF
SMBDirect (in hex) protocol version: 100 transport status: 2
Conn receive_credit_max: ff send_credit_target: ff max_send_size: 554
Conn max_fragmented_recv_size: 100000 max_fragmented_send_size: 100000 max_receive_size:554
Conn keep_alive_interval: 7270e00 max_readwrite_size: 1ff000 rdma_readwrite_threshold: 1000
Debug count_get_receive_buffer: 2e531e count_put_receive_buffer: 2e521f count_send_empty: 95025
Read Queue count_reassembly_queue: b2 count_enqueue_reassembly_queue: 2e521a count_dequeue_reassembly_queue: 2e521a reassembly_data_length: 0 reassembly_queue_length: 0
Current Credits send_credits: f9 receive_credits: ff receive_credit_target: ff
Pending send_pending: 1 
Receive buffers count_receive_queue: 0 
MR responder_resources: 10 max_frmr_depth: 1ff mr_type: 0
MR mr_ready_count: 0 mr_used_count: 20
Number of credits: 8157,1,1 Dialect 0x311
Server capabilities: 0x30006f
RDMA 
TCP status: 1 Instance: 1
Local Users To Server: 4 SecMode: 0x1 Req On Wire: 33 Net namespace: 4026531833 
In Send: 1 In MaxReq Wait: 0
Compression: no built-in support
Encryption: Negotiated cipher (AES128-GCM)

        Sessions: 
        1) Address: 169.254.81.150 Uses: 1 Capability: 0x30006f Session Status: 1 
        Security type: RawNTLMSSP  SessionId: 0x1689ec8000069
        User: 100999 Cred User: 0

        Extra Channels: 3 

                Channel: 2 ConnectionId: 0x3
                Number of credits: 8157,1,1 Dialect 0x311
                TCP status: 1 Instance: 1
                Local Users To Server: 1 SecMode: 0x1 Req On Wire: 33
                In Send: 1 In MaxReq Wait: 0 Net namespace: 4026531833 

                Channel: 3 ConnectionId: 0x4
                Number of credits: 8157,1,1 Dialect 0x311
                TCP status: 1 Instance: 1
                Local Users To Server: 1 SecMode: 0x1 Req On Wire: 33
                In Send: 0 In MaxReq Wait: 0 Net namespace: 4026531833 

                Channel: 4 ConnectionId: 0x5
                Number of credits: 8156,1,1 Dialect 0x311
                TCP status: 1 Instance: 1
                Local Users To Server: 1 SecMode: 0x1 Req On Wire: 34
                In Send: 0 In MaxReq Wait: 0 Net namespace: 4026531833 

        Shares: 
        0) IPC: \\169.254.81.150\IPC$ Mounts: 1 DevInfo: 0x0 Attributes: 0x0
        PathComponentMax: 0 Status: 1 type: 0 Serial Number: 0x0
        Share Capabilities: None        Share Flags: 0x30
        tid: 0x1        Maximal Access: 0x11f01ff

        1) \\169.254.81.150\Vault Mounts: 2 DevInfo: 0x20020 Attributes: 0xc700ee
        PathComponentMax: 255 Status: 1 type: DISK Serial Number: 0xbc92c893
        Share Capabilities: None Aligned, Partition Aligned, SSD, TRIM-support, Share Flags: 0x800
        tid: 0x5        Optimal sector size: 0x1000     Maximal Access: 0x1f01ff


        Server interfaces: 4    Last updated: 286 seconds ago
        1)      Speed: 56Gbps
                Capabilities: rdma rss 
                IPv4: 169.254.81.150
                Weight (cur,total): (4,56)
                Allocated channels: 4
                [CONNECTED]

        2)      Speed: 40Gbps
                Capabilities: rdma rss 
                IPv4: 169.254.82.151
                Weight (cur,total): (0,40)
                Allocated channels: 0

        3)      Speed: 1Gbps
                Capabilities: rss 
                IPv4: 192.168.50.247
                Weight (cur,total): (0,1)
                Allocated channels: 0

        4)      Speed: 1Gbps
                Capabilities: rss 
                IPv6: fe80:0000:0000:0000:ad46:1233:b1f5:35fa
                Weight (cur,total): (0,1)
                Allocated channels: 0


        MIDs: 
        Server ConnectionId: 0x2
                State: 2 com: 8 pid: 11701 cbdata: 0000000027d79db5 mid 3035654
                  (this repeated a bunch)

        Server ConnectionId: 0x3
State: 2 com: 8 pid: 11701 cbdata: 0000000027d79db5 mid 3035654
                  (this repeated a bunch)
        Server ConnectionId: 0x4
State: 2 com: 8 pid: 11701 cbdata: 0000000027d79db5 mid 3035654
                  (this repeated a bunch)
        Server ConnectionId: 0x5
State: 2 com: 8 pid: 11701 cbdata: 0000000027d79db5 mid 3035654
                  (this repeated a bunch)
--

2) ConnectionId: 0x1 Hostname: 169.254.81.150 
ClientGUID: 76F9F5C3-69C5-2846-B19C-5C3A48053B33
Number of credits: 8190,1,1 Dialect 0x311
Server capabilities: 0x300067
TCP status: 1 Instance: 1
Local Users To Server: 2 SecMode: 0x1 Req On Wire: 0 Net namespace: 4026531833 
In Send: 0 In MaxReq Wait: 0
Compression: no built-in support
Encryption: Negotiated cipher (AES128-GCM)

        Sessions: 
        1) Address: 169.254.81.150 Uses: 1 Capability: 0x300067 Session Status: 1 
        Security type: RawNTLMSSP  SessionId: 0x168b43c000079
        User: 0 Cred User: 0

        Shares: 
        0) IPC: \\169.254.81.150\IPC$ Mounts: 1 DevInfo: 0x0 Attributes: 0x0
        PathComponentMax: 0 Status: 1 type: 0 Serial Number: 0x0
        Share Capabilities: None        Share Flags: 0x30
        tid: 0x1        Maximal Access: 0x11f01ff

        1) \\169.254.81.150\Vault Mounts: 1 DevInfo: 0x20020 Attributes: 0xc700ee
        PathComponentMax: 255 Status: 1 type: DISK Serial Number: 0xbc92c893
        Share Capabilities: None Aligned, Partition Aligned, SSD, TRIM-support, Share Flags: 0x800
        tid: 0x5        Optimal sector size: 0x1000     Maximal Access: 0x1f01ff


        Server interfaces: 4    Last updated: 1580 seconds ago
        1)      Speed: 56Gbps
                Capabilities: rdma rss 
                IPv4: 169.254.81.150
                Weight (cur,total): (1,56)
                Allocated channels: 1
                [CONNECTED]

        2)      Speed: 40Gbps
                Capabilities: rdma rss 
                IPv4: 169.254.82.151
                Weight (cur,total): (0,40)
                Allocated channels: 0

        3)      Speed: 1Gbps
                Capabilities: rss 
                IPv4: 192.168.50.247
                Weight (cur,total): (0,1)
                Allocated channels: 0

        4)      Speed: 1Gbps
                Capabilities: rss 
                IPv6: fe80:0000:0000:0000:ad46:1233:b1f5:35fa
                Weight (cur,total): (0,1)
                Allocated channels: 0


        MIDs: 
--

        2) Address: 169.254.81.150 Uses: 1 Capability: 0x300067 Session Status: 1 
        Security type: RawNTLMSSP  SessionId: 0x1687d54000061
        User: 0 Cred User: 0

        Shares: 
        0) IPC: \\169.254.81.150\IPC$ Mounts: 1 DevInfo: 0x0 Attributes: 0x0
        PathComponentMax: 0 Status: 1 type: 0 Serial Number: 0x0
        Share Capabilities: None        Share Flags: 0x30
        tid: 0x1        Maximal Access: 0x11f01ff

        1) \\169.254.81.150\Vault Mounts: 1 DevInfo: 0x20020 Attributes: 0xc700ee
        PathComponentMax: 255 Status: 1 type: DISK Serial Number: 0xbc92c893
        Share Capabilities: None Aligned, Partition Aligned, SSD, TRIM-support, Share Flags: 0x800
        tid: 0x5        Optimal sector size: 0x1000     Maximal Access: 0x1f01ff


        Server interfaces: 4    Last updated: 1580 seconds ago
        1)      Speed: 56Gbps
                Capabilities: rdma rss 
                IPv4: 169.254.81.150
                Weight (cur,total): (1,56)
                Allocated channels: 1
                [CONNECTED]

        2)      Speed: 40Gbps
                Capabilities: rdma rss 
                IPv4: 169.254.82.151
                Weight (cur,total): (0,40)
                Allocated channels: 0

        3)      Speed: 1Gbps
                Capabilities: rss 
                IPv4: 192.168.50.247
                Weight (cur,total): (0,1)
                Allocated channels: 0

        4)      Speed: 1Gbps
                Capabilities: rss 
                IPv6: fe80:0000:0000:0000:ad46:1233:b1f5:35fa
                Weight (cur,total): (0,1)
                Allocated channels: 0


        MIDs: 
--

Witness registrations:

and yeahh after I get everything working, I'll manually assign the IPs so they're not \\169.254.x ;)
 

Attachments

  • 1776019019432.png
    1776019019432.png
    1.2 KB · Views: 2
You must log in or register to reply here.
Top Bottom
Back