Must run the script multiple times to get connected

[noahBax]

I am running the wifi-to-eth on a RPi 4. Just in case it could be causing issues, I am not using dnsmasq because I only have my PC connected and its ip is static, but this behavior happens regardless.

I can't tell if this is an issue where I must run the script multiple times, whether it's an amount of time I have to wait, or whether it's something Linux is doing. When I run the script after boot (I make sure to run it once connected) it does work as expected. My PC at the other end does connect to the internet, but gets disconnected after a short time. I can re-run the script again if I want to, but the same thing happens. After some time has passed (4 minutes when I last timed it) I can run the script and my device properly connects.

Some things I notice that might be pertinent: When I run the route command AFTER I run the wifi-to-eth script I do see an additional entry, but this disappears after the device loses connection. It stays after the device is properly connected.

When I run nmcli before the 'proper connection' I get

eth0: connecting (getting IP configuration) to Wired connection 1

After the proper connection when running wifi-to-eth I get

eth0: connected (externally) to eth0

And if I don't run wifi-to-eth, eth0 just says disconnected.

[arpitjindal97]

I do not have RPi right now. Can anyone from the community take a look into it?