The program runs fine and gets me my hardware address. I'll post it sometime sorry, it's on another Linux machine, and I have to clean some commented out code, like 5 lines first.
But here's my question: I have to supply the & family and I had wanted "eth0" but I now realize that not all of my Linux machines store the address for "eth0" in a family with that name. It always starts with an e, but has a different set of characters after that. Could be that way for wlan too not sure. So using the ioctl system calls (wrappers over kernel) seems to be kind of superfluous. I seem to be doing most of the work because I first have to go out and get the weirder names of the address family I'm looking for. So should I just go back to a file fopen approach or does my approach have some advantages? I don't really care which method I use. Any opinions appreciated, thank you.
But here's my question: I have to supply the & family and I had wanted "eth0" but I now realize that not all of my Linux machines store the address for "eth0" in a family with that name. It always starts with an e, but has a different set of characters after that. Could be that way for wlan too not sure. So using the ioctl system calls (wrappers over kernel) seems to be kind of superfluous. I seem to be doing most of the work because I first have to go out and get the weirder names of the address family I'm looking for. So should I just go back to a file fopen approach or does my approach have some advantages? I don't really care which method I use. Any opinions appreciated, thank you.