Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add information about running WiFi and Ethernet together #80

Open
edpgcooper opened this issue Jun 2, 2021 · 5 comments
Open

Add information about running WiFi and Ethernet together #80

edpgcooper opened this issue Jun 2, 2021 · 5 comments
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@edpgcooper
Copy link

I have both interfaces connected (my device has two IP addresses), is it smart enough to prioritise Ethernet for Helium traffic when it's available? If not how do I stop it using WiFi without a total reset?

@vpetersson
Copy link

Interesting question. The network is managed by Network Manager behind the scenes. It is certainly possible to run both WiFi and Ethernet simultaneously, but I'm not sure if Network Manager is intelligent enough to prioritize properly. I know that macOS will automatically route traffic over Ethernet if both Ethernet and WiFi is present.

This would be relatively easy to test, but I cannot personally allocate the bandwidth for it at the moment.

@salmanfarisvp salmanfarisvp added enhancement New feature or request documentation Improvements or additions to documentation labels Jun 5, 2021
@shawaj
Copy link
Member

shawaj commented Jun 5, 2021

One thing I also wondered, is whether having both simultaneously connected can cause any issues with libp2p successfully communicating with peers...?

@edpgcooper
Copy link
Author

I've actually tried many times to clear the WiFi credentials from the device with zero luck - perhaps some clarification is needed as to how you can remove the WiFi credentials when you just want to use Ethernet

@ghost
Copy link

ghost commented Aug 6, 2021

I set up separate policies on my Fortigate firewall for traffic on 44158. One coming from Wi-Fi, the other coming from wired Ethernet. Placed them before all other rules so the counters would reflect traffic. Tested with a Nebra hotspot. I plugged it in, cleared all logs, and plugged the Ethernet cable in shortly after. Pay attention to "Bytes" at the very end of the image.

image

Couple minutes later:

image

From a different view. Wifi Hotspot Traffic should appear.

image

Now I will unplug the Ethernet cable.

image

image

Back to wired.

image

I was not seeing traffic from the wired and had no ethernet lights, so I rebooted.

image

Suspect it was a switch security setting that caused the port not to light up, so trying again. Switching back to wireless in the next picture.

image

Wired comes back, and the sessions have dropped from Wifi.

image

Port stayed online this time. As seen above, I wasn't seeing much traffic on Wired. I reset the ipv4 policy counters:

image

image

Works as expected, from this point of view.

Edit: I switched my PC's port with the hotspot, and the same port went offline for no reason. The switch was the reason it didn't work correctly the first time, it seems.

@DGMurdockIII
Copy link

I would love easy way to remove the wifi from being listed in my router

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants