How to move to a different NIC or network config

ts678 · September 22, 2024, 7:29pm

This seems like it would result in a more solid failure to communicate, yet your backup is

which is after (generally) a list at start of backup, and a bunch of put (upload) operations.
This is why I’m asking you to test those. The performance test is to see if perhaps the new networking is losing performance due to some packet damage such as delay, loss, or swap.

The NIC generally just transports packets and has nothing to do with routing, firewalling, etc.
Another way to test packet transport (somewhat) is with ping (but probably not excessively):

C:\>ping api.backblazeb2.com

Pinging api.backblazeb2.com [104.153.233.180] with 32 bytes of data:
Reply from 104.153.233.180: bytes=32 time=76ms TTL=52
Reply from 104.153.233.180: bytes=32 time=77ms TTL=52
Reply from 104.153.233.180: bytes=32 time=79ms TTL=52
Reply from 104.153.233.180: bytes=32 time=79ms TTL=52

Ping statistics for 104.153.233.180:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 76ms, Maximum = 79ms, Average = 77ms

C:\>

Call the Native API is the citation for that host. B2 starts there, then other hosts are used later.

github.com

duplicati/duplicati/blob/5ee6ca17ba2361d8496c5af38df6263ea9d24ec6/Duplicati/Library/Backend/Backblaze/B2AuthHelper.cs#L94-L99


      
          var req = base.CreateRequest(AUTH_URL);

          req.Headers.Add("Authorization", string.Format("Basic {0}", m_credentials));

          req.ContentType = "application/json; charset=utf-8";

          

          using(var resp = (HttpWebResponse)new AsyncHttpRequest(req).GetResponse())

              m_config = ReadJSONResponse<AuthResponse>(resp);

is Duplicati’s B2 authorization. It’s doing high level HTTP requests. All of the details are below.

Network interface controller describes how some NICs have support for higher levels like TCP. Generally I think the NIC leaves TCP to the OS. Your use has virtualization added to the stack. Possibly you can also try reconfiguring that with new NIC. Default setup looks to me to be NAT.