DGX Spark gains a new ipv6 address every time Sync connects?

Accelerated Computing DGX Spark / GB10 User Forum DGX Spark / GB10
1

Has anyone else noticed this? I am not sure if it’s concerning, but it’s a little untidy, at least…?

$ ssh 192.168.0.240
Welcome to NVIDIA DGX Spark Version 7.2.3 (GNU/Linux 6.11.0-1016-nvidia aarch64)

System information as of Tue Nov 4 07:43:55 PM EST 2025

System load: 0.9
Usage of /: 8.2% of 3.67TB
Memory usage: 3%
Swap usage: 0%
Temperature: 44.0 C
Processes: 518
Users logged in: 1
IPv4 address for enP7s7: 192.168.0.240
IPv6 address for enP7s7: 2600:4041:5c45:8e00:9c7c:123c:edf1:3e41
IPv6 address for enP7s7: 2600:4041:5c45:8e00:bc1b:3818:660f:1e7a
IPv6 address for enP7s7: 2600:4041:5c49:9400:b4fa:a7d5:473b:b468
IPv6 address for enP7s7: 2600:4041:5c49:9400:ec7:c3d9:bccf:3f94
IPv6 address for enP7s7: 2600:4041:5c07:4200:2d6e:f1e1:6db6:7bdd
IPv6 address for enP7s7: 2600:4041:5c07:4200:f423:7d9:132b:ad33
Last login: Tue Nov 4 19:43:55 2025 from 192.168.0.176

2

I’m a bit concerned about what’s running in the background.

I only had Mozilla, AI Workbench Open, VS Coder just installed and it’s been at 70 to 75GB RAM consumption doing nothing, which to me, is concerning.

image
image583×557 37.9 KB

3

Hi simon.thornington
If you run ip -f inet6 a do you see all of those addresses on enP7s7?

4

Yes they are there. I had to reboot the spark to change power strips so a lot of them are gone now, but this is what I have:

image
image711×434 8.31 KB

5

Sync doing clean reconnects doesn’t seem to trigger it, it might be when the laptop is taken to work and back and the Sync toolbar thing has the big red Disconnected box, aka an unclean exit or something?

6

I’ll look into this. Could you send an nvidia-bug-report by following these directions?

7

nvidia-bug-report.log.gz (560.1 KB)

uploaded!

there are a few more now:

Welcome to NVIDIA DGX Spark Version 7.2.3 (GNU/Linux 6.11.0-1016-nvidia aarch64)

System information as of Wed Nov 5 09:25:30 PM EST 2025

System load: 0.11
Usage of /: 8.5% of 3.67TB
Memory usage: 7%
Swap usage: 0%
Temperature: 45.0 C
Processes: 518
Users logged in: 1
IPv4 address for enP7s7: 192.168.0.240
IPv6 address for enP7s7: 2600:4041:5bee:1500:c222:a48b:670a:8d26
IPv6 address for enP7s7: 2600:4041:5bee:1500:1916:231b:37f3:70b8
IPv6 address for enP7s7: 2600:4041:5c27:c000:f2ee:5747:d60a:32be
IPv6 address for enP7s7: 2600:4041:5c27:c000:d9c7:fe5:4b46:3aeb
IPv6 address for enP7s7: 2600:4041:5c00:7800:776c:4fe2:887b:a561
IPv6 address for enP7s7: 2600:4041:5c00:7800:2a33:2ff3:d3bb:b4a5
Last login: Wed Nov 5 21:23:49 2025 from 192.168.0.176

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 state UNKNOWN qlen 1000
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: enP7s7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000
inet6 2600:4041:5bee:1500:c222:a48b:670a:8d26/64 scope global temporary dynamic
valid_lft 65222sec preferred_lft 65222sec
inet6 2600:4041:5bee:1500:1916:231b:37f3:70b8/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 65222sec preferred_lft 65222sec
inet6 2600:4041:5c27:c000:f2ee:5747:d60a:32be/64 scope global temporary dynamic
valid_lft 68863sec preferred_lft 68863sec
inet6 2600:4041:5c27:c000:d9c7:fe5:4b46:3aeb/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 68863sec preferred_lft 68863sec
inet6 2600:4041:5c00:7800:776c:4fe2:887b:a561/64 scope global temporary dynamic
valid_lft 86352sec preferred_lft 75542sec
inet6 2600:4041:5c00:7800:2a33:2ff3:d3bb:b4a5/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 86352sec preferred_lft 86352sec
inet6 fe80::7f49:36e4:43cd:861d/64 scope link noprefixroute
valid_lft forever preferred_lft forever
7: wlP9s9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000
inet6 2600:4041:5bee:1500:b409:d6bf:756c:2cb2/64 scope global temporary dynamic
valid_lft 65166sec preferred_lft 65166sec
inet6 2600:4041:5bee:1500:b3db:dee1:ea90:2098/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 65166sec preferred_lft 65166sec
inet6 2600:4041:5c27:c000:c00c:7d7a:22e1:8c88/64 scope global temporary dynamic
valid_lft 68863sec preferred_lft 68863sec
inet6 2600:4041:5c27:c000:6c45:9228:416a:12e8/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 68863sec preferred_lft 68863sec
inet6 2600:4041:5c00:7800:a2ed:3baa:30ed:67cc/64 scope global temporary dynamic
valid_lft 86352sec preferred_lft 75967sec
inet6 2600:4041:5c00:7800:3e39:6dd7:cb:7725/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 86352sec preferred_lft 86352sec
inet6 fe80::7a26:4eb2:2446:10e4/64 scope link noprefixroute
valid_lft forever preferred_lft forever
9: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 state DOWN
inet6 fe80::24d9:2ff:fe31:fceb/64 scope link
valid_lft forever preferred_lft forever
10: br-44a2196a9f0c: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP
inet6 fe80::1c12:2ff:fe85:8c18/64 scope link
valid_lft forever preferred_lft forever
11: vethd2dfc58@enP7s7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP
inet6 fe80::9417:76ff:fe77:7ec0/64 scope link
valid_lft forever preferred_lft forever
46: vethd4803d3@enP7s7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP
inet6 fe80::543b:3cff:fe1d:44e8/64 scope link
valid_lft forever preferred_lft forever

8

The interface has multiple IPv6 addresses likely because your LAN advertises three /64 prefixes. For each prefix, the OS creates a stable address and a temporary privacy address (used for outbound connections and rotated over time). This results in two global addresses per prefix. This is normal IPv6 behavior and not a misconfiguration on the host or Sync

9

Is it normal that it grows over time? I’ve seen it have 20+ ipv6 addresses if I’ve been been working on the thing for a while.

10

@simon.thornington how many IPv6 networks are you connecting to? Also, your interface has long address lease times, i.e:

inet6 2600:4041:5c00:7800:2a33:2ff3:d3bb:b4a5/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 86352sec preferred_lft 86352sec

86352sec that’s close to 24 hours!

11

There is only one network that I am aware of, this is at my home network. My other devices on the same network do not exhibit this, e.g. my MacBook.

12

You have the 10G interface up, enP7s7 , and two virtual interfaces vethd2dfc58@enP7s7 & vethd4803d3@enP7s7

That gives you six global IPv6 addresses for the 3 prefixes, as @aniculescu mentioned. What are the veth used for? Containers?

13

I don’t know, is that something that AI Workbench does?