I don’t use exactly ifconfig, I use the Node.js core module os:
I do:
const interfaces = os.networkInterfaces()
Which returns something like this:
{
lo: [
{
address: '127.0.0.1',
netmask: '255.0.0.0',
family: 'IPv4',
mac: '00:00:00:00:00:00',
internal: true,
cidr: '127.0.0.1/8'
},
{
address: '::1',
netmask: 'ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff',
family: 'IPv6',
mac: '00:00:00:00:00:00',
scopeid: 0,
internal: true,
cidr: '::1/128'
}
],
eth0: [
{
address: '192.168.1.108',
netmask: '255.255.255.0',
family: 'IPv4',
mac: '01:02:03:0a:0b:0c',
internal: false,
cidr: '192.168.1.108/24'
},
{
address: 'fe80::a00:27ff:fe4e:66a1',
netmask: 'ffff:ffff:ffff:ffff::',
family: 'IPv6',
mac: '01:02:03:0a:0b:0c',
scopeid: 1,
internal: false,
cidr: 'fe80::a00:27ff:fe4e:66a1/64'
}
]
}
Then I check if any « IPv6 » addresses are available ![]()
Normally, if you no longer have any IPv6 interfaces, it should also disappear on the Gladys side.
If you want to see the result of the request on your side, you can open your browser inspector and select this request:
Not sure I understand the question? I develop on a Mac and my Gladys runs on a Beelink mini S12 Pro ![]()
Thanks for testing! ![]()
Okay, I expected that — iOS doesn’t keep any record of devices, and therefore doesn’t do any old ↔ new matching, it just deletes everything. That’s brutal I think
Also, for now on these platforms there is no history (no graphical view), so they don’t care much about legacy, which is not our case.
For info, I hadn’t pushed my improvements from this morning yet, so you tested the Saturday night version ![]()
I just pushed a new Docker build with automatic matching based on the « UNIQUE_ID + position » pair (imperfect solution I remind you, but « good enough »)
Even so, you should still see it in the list under « settings », right? The decommissioning must not have worked.
