Return to Answer

So trying to tackle the several technical aspects of your question.

The biggest technical problem is having the same netblock in your two ethernet and your one wifi network interfaces. That will mess up your routing.

I also see you seem to be shifting too fast between MAC addresses in the wifi interface. That will interfere with your current connections (and shut down them).

As wifi is authenticated, once you spoof a new MAC address, you have to take down your interface (before spoofing), and put it up again (after spoofing), going again by all the authentication process with the new MAC address. Otherwise, the AP with stop dealing with you as it does not know your interface as being authenticated anymore.

Caveats: on some equipments/setup/brands it is necessary to wait a while or repeat the process a couple of times with the same new MAC, for the old MAC to be out of the picture (caches, others). In some more rarer wifi drivers, the driver might not like if you change the first three bytes of the MAC address that identify the brand of the wifi, so you are only able to spoof the lower three bytes.

Furthermore, your IPv6 addresses are bleeing to the outside your MAC addresses. As your provider is giving IPv6 and you are already assuming several IPv6 addresses, this will give you problems, as in Linux, IPv6 by default takes precedence over IPv4. Furthermore, such bleeding will quickly let any network administrator pick up you are up to no good. A possible work around is disabling IPv6 altogether while you are spooing MAC addresses.

Aditionally, the name of your interface denotes you are using a realtek based-chipset. While cheap, their quality is low, and they are know to give connection stability problems. Certain models of ralink or atheros are much better for this kind of activities. see related Wi-Fi problems using ASUS USB-N13 adapter (realtek)

PS. Obviously, there are no crystal balls. It is due to a set of clues put together that point out the kind of activities your system is up to. I advise trying to understand better what are the consequences of using less well behaved utilities for doing more obscure operations.

So trying to tackle the several technical aspects of your question.

The biggest technical problem is having the same netblock on your two ethernet and your one wifi network interfaces. That will mess up your routing.

I also see you seem to be shifting too fast between MAC addresses in the wifi interface. That will interfere with your current connections (and shut down them).

As wifi is authenticated, once you spoof a new MAC address, you have to take down your interface (before spoofing), and put it up again (after spoofing), going again by all the authentication process with the new MAC address. Otherwise, the AP with stop dealing with you as it does not know your interface as being authenticated.

Caveats: on some equipments/setup/brands it is necessary to wait a while or repeat the process a couple of times with the same new MAC, for the old MAC to be out of the picture (caches, others). In some more rarer wifi drivers, the driver might not like if you change the first three bytes of the MAC address that identify the brand of the wifi, so you are only able to spoof the lower three bytes.

Furthermore, your IPv6 addresses are bleeing to the outside your MAC addresses. As your provider is giving IPv6 and you are already assuming several IPv6 addresses, this will give you problems, as in Linux, IPv6 by default takes precedence over IPv4. Furthermore, such bleeding will quickly let any network administrator pick up you are up to no good. A possible work around is disabling IPv6 altogether while you are spooing MAC addresses.

Aditionally, the name of your interface denotes you are using a realtek based-chipset. While cheap, their quality is low, and they are know to give connection stability problems. Certain models of ralink or atheros are much better for this kind of activities. see related Wi-Fi problems using ASUS USB-N13 adapter (realtek)

PS. Obviously, there are no crystal balls. It is due to a set of clues put together that point out the kind of activities your system is up to. I advise trying to understand better what are the consequences of using less well behaved utilities for doing more obscure operations.

So trying to tackle the several technical aspects of your question.

The biggest technical problem is having the same netblock in your two ethernet and your one wifi network interfaces. That will mess up your routing.

I also see you seem to be shifting too fast between MAC addresses in the wifi interface. That will interfere with your current connections (and shut down them).

As wifi is authenticated, once you spoof a new MAC address, you have to take down your interface, and put it up again, going again by all the authentication process with the new MAC address. Otherwise, the AP with stop dealing with you as it does not know your interface as being authenticated anymore.

Caveats: on some equipments/setup/brands it is necessary to wait a while or repeat the process a couple of times with the same new MAC, for the old MAC to be out of the picture (caches, others). In some more rarer wifi drivers, the driver might not like if you change the first three bytes of the MAC address that identify the brand of the wifi, so you are only able to spoof the lower three bytes.

Furthermore, your IPv6 addresses are bleeing to the outside your MAC addresses. As your provider is giving IPv6 and you are already assuming several IPv6 addresses, this will give you problems, as in Linux, IPv6 by default takes precedence over IPv4. Furthermore, such bleeding will quickly let any network administrator pick up you are up to no good. A possible work around is disabling IPv6 altogether while you are spooing MAC addresses.

Aditionally, the name of your interface denotes you are using a realtek based-chipset. While cheap, their quality is low, and they are know to give connection stability problems. Certain models of ralink or atheros are much better for this kind of activities. see related Wi-Fi problems using ASUS USB-N13 adapter (realtek)

PS. Obviously, there are no crystal balls. It is due to a set of clues put together that point out the kind of activities your system is up to. I advise trying to understand better what are the consequences of using less well behaved utilities for doing more obscure operations.

So trying to tackle the several technical aspects of your question.

The biggest technical problem is having the same netblock in your two ethernet and your one wifi network interfaces. That will mess up your routing.

I also see you seem to be shifting too fast between MAC addresses in the wifi interface. That will interfere with your current connections (and shut down them).

As wifi is authenticated, once you spoof a new MAC address, you have to take down your interface (before spoofing), and put it up again (after spoofing), going again by all the authentication process with the new MAC address. Otherwise, the AP with stop dealing with you as it does not know your interface as being authenticated anymore.

Caveats: on some equipments/setup/brands it is necessary to wait a while or repeat the process a couple of times with the same new MAC, for the old MAC to be out of the picture (caches, others). In some more rarer wifi drivers, the driver might not like if you change the first three bytes of the MAC address that identify the brand of the wifi, so you are only able to spoof the lower three bytes.

Furthermore, your IPv6 addresses are bleeing to the outside your MAC addresses. As your provider is giving IPv6 and you are already assuming several IPv6 addresses, this will give you problems, as in Linux, IPv6 by default takes precedence over IPv4. Furthermore, such bleeding will quickly let any network administrator pick up you are up to no good. A possible work around is disabling IPv6 altogether while you are spooing MAC addresses.

Aditionally, the name of your interface denotes you are using a realtek based-chipset. While cheap, their quality is low, and they are know to give connection stability problems. Certain models of ralink or atheros are much better for this kind of activities. see related Wi-Fi problems using ASUS USB-N13 adapter (realtek)

PS. Obviously, there are no crystal balls. It is due to a set of clues put together that point out the kind of activities your system is up to. I advise trying to understand better what are the consequences of using less well behaved utilities for doing more obscure operations.

So trying to tackle the several technical aspects of your question.

The biggest technical problem is having the same netblock in your two ethernet and your one wifi network interfaces. That will mess up your routing.

I also see you seem to be shifting too fast between MAC addresses in the wifi interface. That will interfere with your current connections (or shut down them).

Furthermore, as wifi is authenticated, once you spoof a new MAC address, you have to take down your interface, and put it up again, going again by all the authentication process with the new MAC address. Otherwise, the AP with stop dealing with you as it does not know your interface as being authenticated anymore.

Caveats: on some equipments/setup/brands it is necessary to wait a while or repeat the process a couple of times with the same new MAC, for the old MAC to be out of the picture (caches, others). In some more rarer wifi drivers, the driver might not like if you change the first three bytes of the MAC address that identify the brand of the wifi, so you are only able to spoof the lower three bytes.

Furthermore, your IPv6 addresses are bleeing to the outside your MAC addresses. As your provider is giving IPv6 and you are already assuming several IPv6 addresses, this will give you problems, as in Linux, IPv6 by default takes precedence over IPv4. Furthermore, such bleeding will quickly let any network administrator pick up you are up to no good. A possible work around is disabling IPv6 altogether while you are spooing MAC addresses.

Aditionally, the name of your interface denotes you are using a realtek based-chipset. While cheap, their quality is low, and they are know to give connection stability problems. Certain models of ralink or atheros are much better for this kind of activities. see related Wi-Fi problems using ASUS USB-N13 adapter (realtek)

PS. Obviously, there are no crystal balls. It is due to a set of clues put together that point out the kind of activities your system is up to. I advise trying to understand better what are the consequences of using less well behaved utilities for doing more obscure operations.

So trying to tackle the several technical aspects of your question.

The biggest technical problem is having the same netblock in your two ethernet and your one wifi network interfaces. That will mess up your routing.

I also see you seem to be shifting too fast between MAC addresses in the wifi interface. That will interfere with your current connections (and shut down them).

As wifi is authenticated, once you spoof a new MAC address, you have to take down your interface, and put it up again, going again by all the authentication process with the new MAC address. Otherwise, the AP with stop dealing with you as it does not know your interface as being authenticated anymore.

Caveats: on some equipments/setup/brands it is necessary to wait a while or repeat the process a couple of times with the same new MAC, for the old MAC to be out of the picture (caches, others). In some more rarer wifi drivers, the driver might not like if you change the first three bytes of the MAC address that identify the brand of the wifi, so you are only able to spoof the lower three bytes.

Furthermore, your IPv6 addresses are bleeing to the outside your MAC addresses. As your provider is giving IPv6 and you are already assuming several IPv6 addresses, this will give you problems, as in Linux, IPv6 by default takes precedence over IPv4. Furthermore, such bleeding will quickly let any network administrator pick up you are up to no good. A possible work around is disabling IPv6 altogether while you are spooing MAC addresses.

Aditionally, the name of your interface denotes you are using a realtek based-chipset. While cheap, their quality is low, and they are know to give connection stability problems. Certain models of ralink or atheros are much better for this kind of activities. see related Wi-Fi problems using ASUS USB-N13 adapter (realtek)

PS. Obviously, there are no crystal balls. It is due to a set of clues put together that point out the kind of activities your system is up to. I advise trying to understand better what are the consequences of using less well behaved utilities for doing more obscure operations.