WiFi-Direct / Hotspot #23
Comments
|
When two people connect to the same Hotspot, then it should work. Maybe the Hotspot does not allow IPv6 traffic or isolate the different clients? |
|
Thanks for answering. And.... concerning the WiFi Direct. Any idea on how it could work? |
|
I haven't tested WiFi Direct yet. I could imagine that your phone is missing IPv6 support (starting with Android 6.0). Can you see the IP addresses of you phones wifi interface when connected to some hotspot? |
|
WiFi Direct: I'll check with hotpot too. |
|
Is it really ge80::..? Not fe80? |
|
you are right. both start with fe80. it was a typo. |
|
With hotspot > it connects both but the sound doesn't flow. |
|
The log would be useful. Maybe it is enough to understand the problem. |
|
ok.I'll try to make a log this weekend. Should I post it here? Or send it to you? |
|
Post it here. Maybe other people will find it helpful. |
|
ok. here we go. th scenario doesn't even involve WFiDirect.Both devices are connected to same wifi router. Device 1 sees device 2 (green ball) but device 2 doesn't see device 1 (red ball). |
|
another situation (same scenario: Both devices are connected to same wifi router. Device 1 sees device 2 (green ball) but device 2 doesn't see device 1 (red ball). |
|
I see |
|
Hi. |
|
I was helping a bit at most. |
|
I understand that meshenger uses webRTC. |
|
Maybe the audio device was not properly closed before or is used by other programs. Hard to tell. |
|
I guess the issue is within meshenger itself. |
|
It does not happen for my phones (both Lineage OS, Android 7.1.2). But when it works the first time, then it is likely to be a bug in the App. |
|
I have had the same problem, before the scanning issue that I have just reported. Using android 8.0.0 on one phone and 5.1.1 on the other. |
You had that problem and solved or is it still a problem? |
|
It would be good to know where the problem lies. There is a new version in progress as part of this years GSoC and maybe it can get fixed. Maybe you can check the following:
|
|
Hi. on device A, on meshenger screen I find the device B,
when I ping device B from device A: Other times the device that shows in the meshenger caller list is the fe80::e299:71ff:feaf:9e3 but the ping has the same effect. I can also test the other way around (device B reaches device A but doesn't gt the sound and after a few calls no device receives any sound) but maybe you prefer to get step by step info? |
|
@labregowski Does |
|
Or you need to use |
|
Hi. Not getting that ipv6 on ip a anymore. I realised that my test scenario must be using wifi direct and using a wifi was messing up. So, disconnected one of the devices from wlan, connected them through WifiDirect but without any other WiFi network. 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default I tried to |
|
"unknown host" might mean to ping interprets the address as a hostname and does not recognize/support ipv6 addresses. Is the ping6 command available? |
|
Is wlan0 the wifi-direct interface? Meshenger is hard coded to use wlan0 for everything. This can be extended of course. But needs some coding to do. Edit: I cannot test this myself, as my phone does not have working wifi-direct. |
|
OK, now my phones are scanning properly, I can contribute again. Phone B: Samsung A3. Android 8.0.0 QR codes copy. Both phones are connected to my wifi router. Like labregowski I would love this to work with hotspot enabled on one phone, but that fails totally. |
|
Thanks you for your input. From the MAC address, the first address that is generated from that is the IPV6 link local address (fe80:...). It would be interesting what fe80 address Phone A has on its wlan0 interface. I have release version 2.1.0, which would allow you to view all addresses available on your system. |
|
Take your time. I would like to see this working as well. |
Still need me to test this ? |
|
Would an advanced user option to manually selected preferred network interface help? Or allow user to change priorities of network interfaces? |
|
@labregowski I am still working on more important issues. I might ping you out of the blue when I continue investigating WiFi direct again. @ToEatFreshBabies no idea yet. |
Doesn't work with WiFi Direct nor Hotspot provided by one of the mobiles.
Is this something one could expect to be solved soon?
Best
The text was updated successfully, but these errors were encountered: