'No such device, repeatedly showing in error log

Support / Troubleshooting
1

When I examine my twingate log I see numerous lines like this :

Aug 24 11:15:54 x1 twingated[34292]: [2023-08-24T11:15:54.381504+0100] [ERROR] [client][34292] is_wifi: No such device: ioctl(SIOCGIWNAME) for ‘veth23b9dca’ interface
Aug 24 13:11:15 x1 twingated[34292]: [2023-08-24T13:11:15.161590+0100] [ERROR] [client][34292] is_wifi: No such device: ioctl(SIOCGIWNAME) for ‘veth9e73e49’ interface
Aug 24 13:11:15 x1 twingated[34292]: [2023-08-24T13:11:15.534008+0100] [ERROR] [client][34292] is_wifi: No such device: ioctl(SIOCGIWNAME) for ‘veth9b544a4’ interface
Aug 24 13:11:15 x1 twingated[34292]: [2023-08-24T13:11:15.539114+0100] [ERROR] [client][34292] is_wifi: No such device: ioctl(SIOCGIWNAME) for ‘veth9b544a4’ interface
Aug 24 13:11:15 x1 twingated[34292]: [2023-08-24T13:11:15.543251+0100] [ERROR] [client][34292] is_wifi: No such device: ioctl(SIOCGIWNAME) for ‘veth9e73e49’ interface
Aug 24 13:11:15 x1 twingated[34292]: [2023-08-24T13:11:15.545888+0100] [ERROR] [client][34292] is_wifi: No such device: ioctl(SIOCGIWNAME) for ‘veth9b544a4’ interface
Aug 24 13:11:15 x1 twingated[34292]: [2023-08-24T13:11:15.548714+0100] [ERROR] [client][34292] is_wifi: No such device: ioctl(SIOCGIWNAME) for ‘veth9b544a4’ interface
Aug 24 13:11:15 x1 twingated[34292]: [2023-08-24T13:11:15.551320+0100] [ERROR] [client][34292] is_wifi: No such device: ioctl(SIOCGIWNAME) for ‘veth9b544a4’ interface

The interface name seems to change all the time, so that over the last 6 hours there are over 2000 different interface names.

I am running on linux (ubuntu)

Linux x1 6.2.0-26-generic #26~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Jul 13 16:27:29 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
Twingate 2023.208.90980 | 0.146.0

Any idea what is happening here?

Thanks

Andy

2

Hi WJ,

This is very odd, especially the 2k interfaces.
If you restart the machine, do the interfaces persist, or do things go back to “normal” (and start climbing again).

Have you tried removing the client and reinstalling? (I know I know, the worst computer related advice ever)

-arthur

3

Hey all :wave:

Just following up on this thread, since we worked on this internally via a support ticket.

The cause of the increased interface counts was due to containers being spun up in the background via Docker Swarm. Shutting down the docker daemon resolved the logging, where the Client was attempting to identify functional network paths, deleting connections with invalid interfaces.