10000 WiFi tethering only some clients can connect · Issue #673 · osmc/osmc · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

WiFi tethering only some clients can connect #673

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.

Sign up for GitHub

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

Jump to bottom
Open
dekart811 opened this issue Dec 31, 2021 · 7 comments
Open

WiFi tethering only some clients can connect #673

dekart811 opened this issue Dec 31, 2021 · 7 comments

Comments

@dekart811
Copy link

I'm having a strange issue regarding the WiFi tethering feature.

I'm running the latest stable version of OSMC on an Raspberry Pi 3B+ and it's connected to the network via cable and it gets it's IP address via DHCP.
I've configured WiFi tethering via the GUI, but I didn't get an IP address assigned when I tried connecting to the WiFi hotspot.
That was easily fixed by setting dnsproxy=yes inside of /etc/connman.pers, but then I've noticed that some devices are able to connect to the WiFi perfectly fine and some can't connect at all.

I tired my and my mother's phone, which are both OnePlus devices running LineageOS and they connect just fine to the WiFi.
But the Samsung phones of my sister and her boyfriend (both the same model running the Samsung stock ROM) wouldn't connect no matter what you would try.

Then I tried connecting my mother's laptop which is running Ubuntu and it connects perfectly fine.
After that I tried my Macbook Pro from 2014 which is running macOS Catalina and Windows 10, when I'm on macOS the WiFi connection works, but as soon as I switch to Windows 10 it wont connect anymore.

All devices that refuse to connect are just telling that they could not connect to the WiFi and nothing else, but if I try to connect those devices to any other WiFi e.g. a regular router, they work as intended.

I haven't found anything on the internet that would be helpful for this really strange problem so that's why I'm opening up this issue.
@samnazarko
Copy link
Contributor

I'm not sure and don't have a phone to test with, but perhaps the Samsung tests for external connectivity and drops the connection if there is no WAN connectivity.

@dekart811
Copy link
Author
dekart811 commented Jan 8, 2022 •
edited
Loading

But then Windows 10 would actually do the same, because like I already mentioned. When I boot up Windows 10 on my Macbook it behaves exactly the same way, it won't connect. If I boot macOS on that machine instead the connection works fine.

Before I switched to OSMC I was using libreELEC on that Pi and there the WiFi tethering was working perfectly fine.

@tomdoyle87
Copy link
Contributor
tomdoyle87 commented Jan 8, 2022 •
edited
Loading

Hi,

Could you please provide the output of:

systemctl status connman -l

journalctl | grep connman

Will give us more info.

when a device fails to connect.

Thanks Tom.

@dekart811
Copy link
Author

I tried that with my Macbook Pro, I don't have access to the other affected devices at the moment.

This is the output that I got when I successfully connected while I was running macOS:

root@golf:~# journalctl -f --unit=connman
-- Logs begin at Thu 2019-02-14 11:11:58 CET. --
Jan 18 13:58:21 golf connmand[261]: DHCP server: Received REQUEST NIP -1062731770
Jan 18 13:58:21 golf connmand[261]: DHCP server: Sending ACK
Jan 18 13:58:21 golf connmand[261]: DHCP server: Sending ACK to 192.168.0.6
Jan 18 13:58:21 golf connmand[261]: DHCP server: Broadcasting packet to client
Jan 18 13:58:22 golf connmand[261]: DHCP server: lease_mac 0x1c605e0 lease_nip 0x1c605e0
Jan 18 13:58:22 golf connmand[261]: DHCP server: Received REQUEST NIP -1062731770
Jan 18 13:58:22 golf connmand[261]: DHCP server: Sending ACK
Jan 18 13:58:22 golf connmand[261]: DHCP server: Sending ACK to 192.168.0.6
Jan 18 13:58:22 golf connmand[261]: DHCP server: Broadcasting packet to client
Jan 18 13:58:22 golf connmand[261]: DHCP server: lease_mac 0x1c605e0 lease_nip 0x1c605e0

I then switched to Windows 10 and tired to connect but I didn't get any new output this is what Windows 10 told me:
photo_2022-01-18_14-09-23
At this point I'm thinking that the WiFi client implementation of the affected devices is simply, for some unknown reason, refusing to connect to the network.

@tomdoyle87
Copy link
Contributor

Hi,

You'll probably need to established a wired connection to the vero, so you can see the logs when the tethered connections fail.

Do any of the devices (failed or otherwise) have private/random mac address enabled?

Thanks Tom.

@dekart811
Copy link
Author

MAC address randomization isn't enabled on any client I use.

@tomdoyle87
Copy link
Contributor

ok just thought.

anyway hard to diagnose further, without logs showing a failed connection from journalctl

Regrds Tom.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@samnazarko @dekart811 @tomdoyle87
0