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

ad-hoc mode issues #4

Open
botik32 opened this Issue Aug 30, 2013 · 28 comments

Comments

Projects
None yet
4 participants
@botik32

botik32 commented Aug 30, 2013

There seem to be issues with ad-hoc mode (short version: it did not work on my gentoo machine). is ad-hoc mode supported by this driver?

long version:

after iwconfig wlan0 essid daihinia mode ad-hoc on two machines with tl-wn723n I get this:

machine 1:

Mode:Ad-Hoc Frequency:2.412 Ghz Cell: 02:11:87:C6:B2:FE
Link Quality:0 Signal level:0 Noise level:0

machine 2:

Mode:Ad-Hoc Frequency:2.412 Ghz Cell: 02:11:87:6A:20:FF
Link Quality:0 Signal level:0 Noise level:0

Then there is no way I can get them to be in the same cell, and ping does not work between them (after setting them to the same network with ifconfig)

possibly related, I get this in the log:

[45541.999446] Chip Version Info: CHIP_8188E_Normal_Chip_TSMC_A_CUT_1T1R_RomVer(0)
[45542.032799] usbcore: registered new interface driver rtl8188eu
[45542.540705] MAC Address = f8:1a:67:26:34:0e
[45542.557066] RTL8188: ERROR indicate disassoc

I can provide more details if needed.
Thanks.
Alex.

@botik32

This comment has been minimized.

botik32 commented Aug 30, 2013

See latest 3 posts in the thread below, someone else seems to be experiencing the same issues. They said they got other cards that use 8192cu working properly:

http://www.raspberrypi.org/phpBB3/viewtopic.php?t=49870&p=387391

@sergforce

This comment has been minimized.

sergforce commented Oct 1, 2013

I can confirm that 2 rtl8188eu devices doesn't work in ad-hoc mode with each other. I used TP-LINK 723N and DLink DWA-125 Rev D1. But if I use a rtl8188eu device in ad-hoc mode on one side and BCM4321 (PCIe card) on the other it works, but rtl8188eu should be configured last. If rtl8188eu is configured first and then BCM4321 is configured in ad-hoc latter they doesn't see each other.

More interesting I set 3 machines in ad-hoc mode (in the same network):
A: BCM4321 (10.0.0.1)
B: TP-LINK 723N (10.0.0.2)
C: DLink DWA-125 Rev D1 (10.0.0.3)

in 3 machines configuration on (B) and (C) I get ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready (it never become ready on 2 machines rtl8188eu to rtl8188eu ad-hoc link)

(A) can see both (B) and (C)
(B) sees only (A) if I start pinging (C) it never replies
(C) sees only (A) if I start pinging (B) it never replies

Do you have any idea of what it could be? I can do more testing if you tell me what to test

@botik32

This comment has been minimized.

botik32 commented Oct 1, 2013

Yeah, same here, got it connecting to an existing ad-hoc network (used broadcom too). But if there is no ad-hoc network to connect to, then it is impossible to initiate the ad-hoc network from a rtl8188eu.

@botik32

This comment has been minimized.

botik32 commented Oct 1, 2013

To confirm, the same behaviour of both rtl cards seeing the third one, not each other, and the other one sees both.

@lwfinger

This comment has been minimized.

Owner

lwfinger commented Oct 1, 2013

I seldom use ad-hoc mode, and it will be some time before I would be able to work on this problem.

It would be helpful if you set up wireshark on a third computer to capture the over-the-air traffic. You need to capture the working case when the non-8188eu device is started first, and the non-working case when the 8188eu unit is started before the BCM4321.

Which driver are you using on the 4321?

@botik32

This comment has been minimized.

botik32 commented Oct 1, 2013

I also tried intel centrino on my laptop, same story with ad-hoc and cards not seeing each other but seeing the centrino one. Driver is iwlwifi.

@botik32

This comment has been minimized.

botik32 commented Oct 1, 2013

The broadcom was on ARM (driver is bcm40181)

@botik32

This comment has been minimized.

botik32 commented Oct 1, 2013

I believe I could get you the tcpdump for both cases. Please stay tuned.
Thanks,
Alex.

@lwfinger

This comment has been minimized.

Owner

lwfinger commented Oct 1, 2013

The tcpdump output will likely not be sufficient. It only sees what makes it through the driver. Any discarded packets are not seen, but will be present in the over-the-air info.

@sergforce

This comment has been minimized.

sergforce commented Oct 1, 2013

For 4321 I used wl and tried b43 to get captures on air but without a luck
so far.

@botik32

This comment has been minimized.

botik32 commented Oct 1, 2013

no worries, got a wireshark capture for successful join, and getting the
bad case capture in 10 minutes

On Tue, Oct 1, 2013 at 10:33 PM, sergforce notifications@github.com wrote:

For 4321 I used wl and tried b43 to get captures on air but without a luck
so far.

On Tue, Oct 1, 2013 at 4:04 PM, lwfinger notifications@github.com
wrote:

I seldom use ad-hoc mode, and it will be some time before I would be
able
to work on this problem.

It would be helpful if you set up wireshark on a third computer to
capture
the over-the-air traffic. You need to capture the working case when the
non-8188eu device is started first, and the non-working case when the
8188eu unit is started before the BCM4321.

Which driver are you using on the 4321?


Reply to this email directly or view it on GitHub<
https://github.com/lwfinger/rtl8188eu/issues/4#issuecomment-25443412>
.


Reply to this email directly or view it on GitHubhttps://github.com//issues/4#issuecomment-25444942
.

@botik32

This comment has been minimized.

botik32 commented Oct 1, 2013

I wish I could attach a file here. Otherwise I'll just send them by e-mail

@botik32

This comment has been minimized.

botik32 commented Oct 1, 2013

https://docs.google.com/file/d/0B5QI4DmQSXpxaU5LLXNaekRtOFE/edit?usp=drive_web
https://docs.google.com/file/d/0B5QI4DmQSXpxU2xkTWM1VnhUWFk/edit?usp=drive_web

The bad case tried connecting to essid "daihinia2", since it appears some of my neighbours latched onto "daihinia".
The good case connected to essid "daihinia" which someone was part of.
Also note that 2 identical rtl8188eu devices were connecting from the same machine.
Please let me know if this is ok.

@sergforce

This comment has been minimized.

sergforce commented Oct 1, 2013

Hi Alex,

Is it capture with 802.11 ? I tried to open it in Wireshark and it says
it's Ethernet with 0x886c packet type. And it doesn't know 0x886c. Which
dissector are you using?

Air capture isn't working on BCM4321 :( Trying to get one which supports.

On Tue, Oct 1, 2013 at 5:25 PM, botik32 notifications@github.com wrote:

https://docs.google.com/file/d/0B5QI4DmQSXpxaU5LLXNaekRtOFE/edit?usp=drive_web

https://docs.google.com/file/d/0B5QI4DmQSXpxU2xkTWM1VnhUWFk/edit?usp=drive_web


Reply to this email directly or view it on GitHubhttps://github.com//issues/4#issuecomment-25448119
.

@botik32

This comment has been minimized.

botik32 commented Oct 1, 2013

same here, wireshark did not know how to decode it...

On Tue, Oct 1, 2013 at 11:58 PM, sergforce notifications@github.com wrote:

Hi Alex,

Is it capture with 802.11 ? I tried to open it in Wireshark and it says
it's Ethernet with 0x886c packet type. And it doesn't know 0x886c. Which
dissector are you using?

Air capture isn't working on BCM4321 :( Trying to get one which supports.

On Tue, Oct 1, 2013 at 5:25 PM, botik32 notifications@github.com wrote:

https://docs.google.com/file/d/0B5QI4DmQSXpxaU5LLXNaekRtOFE/edit?usp=drive_web

https://docs.google.com/file/d/0B5QI4DmQSXpxU2xkTWM1VnhUWFk/edit?usp=drive_web


Reply to this email directly or view it on GitHub<
https://github.com/lwfinger/rtl8188eu/issues/4#issuecomment-25448119>
.


Reply to this email directly or view it on GitHubhttps://github.com//issues/4#issuecomment-25451434
.

@botik32

This comment has been minimized.

botik32 commented Oct 1, 2013

I could re-capture in 802.11 mode, reading on it right now.

On Wed, Oct 2, 2013 at 12:14 AM, Alexandru Botezatu abotezatu@gmail.comwrote:

same here, wireshark did not know how to decode it...

On Tue, Oct 1, 2013 at 11:58 PM, sergforce notifications@github.comwrote:

Hi Alex,

Is it capture with 802.11 ? I tried to open it in Wireshark and it says
it's Ethernet with 0x886c packet type. And it doesn't know 0x886c. Which
dissector are you using?

Air capture isn't working on BCM4321 :( Trying to get one which supports.

On Tue, Oct 1, 2013 at 5:25 PM, botik32 notifications@github.com
wrote:

https://docs.google.com/file/d/0B5QI4DmQSXpxaU5LLXNaekRtOFE/edit?usp=drive_web

https://docs.google.com/file/d/0B5QI4DmQSXpxU2xkTWM1VnhUWFk/edit?usp=drive_web


Reply to this email directly or view it on GitHub<
https://github.com/lwfinger/rtl8188eu/issues/4#issuecomment-25448119>
.


Reply to this email directly or view it on GitHubhttps://github.com//issues/4#issuecomment-25451434
.

@botik32

This comment has been minimized.

botik32 commented Oct 1, 2013

OK I got a 802.11 capture, but I had to do it from the same machine with
the 8188eu card, could not get it done from the ARM one.

The MAC of the 8188eu card is f8:1a:67:0c:02:72
The MAC of the active ad-hoc card for the good capture is 00:22:f4:66:79:8a
(the ARM machine with the broadcom adapter)

https://docs.google.com/file/d/0B5QI4DmQSXpxbHkyZWxYZ1h6ZDA/edit?usp=drive_web
https://docs.google.com/file/d/0B5QI4DmQSXpxQTFuenRjMW45RVk/edit?usp=drive_web

I cannot make any sense of this, except that maybe the channel is different so it is not recorded by wireshark. Any comments appreciated.

On Wed, Oct 2, 2013 at 12:16 AM, Alexandru Botezatu abotezatu@gmail.comwrote:

I could re-capture in 802.11 mode, reading on it right now.

On Wed, Oct 2, 2013 at 12:14 AM, Alexandru Botezatu abotezatu@gmail.comwrote:

same here, wireshark did not know how to decode it...

On Tue, Oct 1, 2013 at 11:58 PM, sergforce notifications@github.comwrote:

Hi Alex,

Is it capture with 802.11 ? I tried to open it in Wireshark and it says
it's Ethernet with 0x886c packet type. And it doesn't know 0x886c. Which
dissector are you using?

Air capture isn't working on BCM4321 :( Trying to get one which
supports.

On Tue, Oct 1, 2013 at 5:25 PM, botik32 notifications@github.com
wrote:

https://docs.google.com/file/d/0B5QI4DmQSXpxaU5LLXNaekRtOFE/edit?usp=drive_web

https://docs.google.com/file/d/0B5QI4DmQSXpxU2xkTWM1VnhUWFk/edit?usp=drive_web


Reply to this email directly or view it on GitHub<
https://github.com/lwfinger/rtl8188eu/issues/4#issuecomment-25448119>
.


Reply to this email directly or view it on GitHubhttps://github.com//issues/4#issuecomment-25451434
.

@lwfinger

This comment has been minimized.

Owner

lwfinger commented Oct 1, 2013

Those look more promising. One other piece of info would be useful: In each case, what are the last two digits of the MAC address of the two interfaces?

@botik32

This comment has been minimized.

botik32 commented Oct 1, 2013

This time I used only one 8188eu card, the MAC is f8:1a:67:0c:02:72.
For the bad case, I did not record bringing the broadcom nic to ad-hoc. Let me repeat the bad case to subsequently set ad-hoc on the broadcom.

@botik32

This comment has been minimized.

botik32 commented Oct 1, 2013

OK, this time I first tried connecting to ad-hoc with the 8188eu NIC, then at around 200 seconds I switched the broadcom NIC to ad-hoc. At around 240 seconds I connected 8188eu to ad-hoc again, with success.

The MAC of the 8188eu card is f8:1a:67:0c:02:72
The MAC of the broadcom nic is 00:22:f4:66:79:8a

https://docs.google.com/file/d/0B5QI4DmQSXpxclg4VXh2YUJrR2M/edit?usp=drive_web

@botik32

This comment has been minimized.

botik32 commented Oct 1, 2013

This one is 8188eu connecting to the laptop intel NIC, intel NIC already in ad-hoc mode.
The intel MAC is 00:27:10:6a:6e:3c
The MAC of the 8188eu card is f8:1a:67:0c:02:72

https://docs.google.com/file/d/0B5QI4DmQSXpxMENjZWNoRncxTUU/edit?usp=drive_web

@botik32

This comment has been minimized.

botik32 commented Oct 2, 2013

And below is a capture of ad-hoc for an Atheros chipset driven by ath9k_htc. Note that this is the case where it is the first node in the ad-hoc network, the case where 8188eu fails. This nic succeeds with ad-hoc though.
its MAC is f8:d1:11:1b:ff:d9.

https://docs.google.com/file/d/0B5QI4DmQSXpxbzFnWDVfZVY4dFE/edit?usp=drive_web

@botik32

This comment has been minimized.

botik32 commented Oct 2, 2013

I am confused as to why some captures do not have anything from the 8188eu nic, and some other do have probe requests.

One thing I noticed about atheros' probe request (probably un-related) is that the request includes the active channel parameter:
Tag: DS Parameter set : Current Channel: 1

Anyway, please let me know if there is anything else I can do to help.
Alex.

@sergforce

This comment has been minimized.

sergforce commented Oct 3, 2013

Hi,

I've done more experiments. Since I don't have reliable air scanner I added
more logging in driver. I added

addr1 = GetAddr1Ptr(ptr);
addr2 = GetAddr2Ptr(ptr);
addr3 = GetAddr3Ptr(ptr);

printk(KERN_WARNING "RECV [TYPE=%x:%x DS=%d MF=%d R=%d P=%d MD=%d W=%d

O=%d] ID=%d addr1=%x:%x:%x:%x:%x:%x addr2=%x:%x:%x:%x:%x:%x
addr3=%x:%x:%x:%x:%x:%x seq=%d:%d ",
type, subtype, pattrib->to_fr_ds, pattrib->mfrag, GetRetry(ptr),
pattrib->pw_save, pattrib->mdata, pattrib->privacy, pattrib->order,
*(__le16 *)((size_t)(ptr) + 2),
addr1[0], addr1[1], addr1[2], addr1[3], addr1[4], addr1[5],
addr2[0], addr2[1], addr2[2], addr2[3], addr2[4], addr2[5],
addr3[0], addr3[1], addr3[2], addr3[3], addr3[4], addr3[5],
pattrib->seq_num, pattrib->frag_num);

if (type == 0) {
    u8* ssidptr = NULL;
    switch (subtype) {
    case 0x50: /* Probe response */
    case 0x80: /* Beacon */
        printk(" TS=%llx BI=%d CAP=%x", (long unsigned

long)((u64)(ptr+24)), (u16)(ptr+24+8), (u16)(ptr+24+8+2));
ssidptr = ptr + 24 + 12;
break;
case 0x40: /* Probe reuest */
ssidptr = ptr + 24;
break;
}
if (ssidptr) {
u8 len = ssidptr[1];
u8 i;

        printk(" TAG=%d len=%d SSID=", ssidptr[0], len);
        for (i = 0; i < len; i++)
            printk("%c", ssidptr[2+i]);
    }
}
printk("\n");

into validate_recv_frame in rtw_recv.c which seems to me the place must be
called for every packet relevant packet. I analyse only control packets.

During iwlist wlan0 scan I can see beacons and probe responses from other
networks. And it seems in survey mode rtl8188eu accepts only 0x50 & 0x80
subtype packets. Are others filtered out by firmware/hardware?

[254961.596500] RECV [TYPE=0:50 DS=0 MF=0 R=1 P=0 MD=0 W=0 O=0] ID=314
addr1=20:2:af:2d:65:3a addr2=0🅱️85:84:2e:a9 addr3=0🅱️85:84:2e:a9
seq=1909:0 TS=4c11e2717 BI=100 CAP=421 TAG=0 len=7 SSID=myguest
addr2=0🅱️85:84:2e:a9 addr3=0🅱️85:84:2e:a9 seq=1910:0 TS=4c11ed181
BI=100 CAP=421 TAG=0 len=7 SSID=myguest
[254961.742644] RECV [TYPE=0:80 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=0🅱️85:84:2e:a9 addr3=0🅱️85:84:2e:a9
seq=1911:0 TS=4c1206181 BI=100 CAP=421 TAG=0 len=7 SSID=myguest
[254961.762750] RECV [TYPE=0:50 DS=0 MF=0 R=1 P=0 MD=0 W=0 O=0] ID=314
addr1=20:2:af:2d:65:3a addr2=0🅱️85:84:4c:c9 addr3=0🅱️85:84:4c:c9
seq=2079:0 TS=4c116b854 BI=100 CAP=421 TAG=0 len=7 SSID=myguest
[254961.781997] RECV [TYPE=0:80 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=0🅱️85:84:4c:c9 addr3=0🅱️85:84:4c:c9
seq=2080:0 TS=4c117033e BI=100 CAP=421 TAG=0 len=7 SSID=myguest

When rtl8188eu device isn't in survey mode I can see everything else
except 0x50 & 0x80 subtype packets. As I understand 802.11 beacon control
packets must be sending all the time. So it's defensively filtered out on
hw/fw.

[254385.688246] RECV [TYPE=0:40 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=10:bf:48:d0:37:ef addr3=ff:ff:ff:ff:ff:ff
seq=979:0 TAG=0 len=7 SSID=myguest
[254385.708618] RECV [TYPE=0:40 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=10:bf:48:d0:37:ef addr3=ff:ff:ff:ff:ff:ff
seq=980:0 TAG=0 len=7 SSID=myguest
[254385.790140] RECV [TYPE=0:40 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=10:bf:48:d0:37:ef addr3=ff:ff:ff:ff:ff:ff
seq=983:0 TAG=0 len=7 SSID=myguest
[254385.810645] RECV [TYPE=0:40 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=10:bf:48:d0:37:ef addr3=ff:ff:ff:ff:ff:ff
seq=984:0 TAG=0 len=7 SSID=myguest
[254387.755553] RECV [TYPE=0:c0 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=314
addr1=7c:61:93:84:55:66 addr2=0🅱️85:84:bc:19 addr3=0🅱️85:84:bc:19
seq=2928:0
[254390.085914] RECV [TYPE=0:b0 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=314
addr1=7c:61:93:84:55:66 addr2=0🅱️85:84:bc:19 addr3=0🅱️85:84:bc:19
seq=2965:0
[254390.097915] RECV [TYPE=0:10 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=314
addr1=7c:61:93:84:55:66 addr2=0🅱️85:84:bc:19 addr3=0🅱️85:84:bc:19
seq=2966:0
[254390.876988] RECV [TYPE=0:d0 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=304
addr1=c0:63:94:19:ae:9c addr2=b0:b2:dc:f9:24:68 addr3=b0:b2:dc:f9:24:68
seq=1845:0
[254395.930965] RECV [TYPE=0:40 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=10:bf:48:d0:37:ef addr3=ff:ff:ff:ff:ff:ff
seq=998:0 TAG=0 len=7 SSID=myguest

I have 3 hosts:
A: Broarcom HW:0:1d:4f:fc:9f:a5
B: TPLink HW:f8:1a:67:27:d0:a4 (rtl8188eu) (original driver)
C: DLINK HW:78:54:2e:21:06:61 (rtl8188eu) <-- On this host I take
logs with modified driver

experiment 1)
I setup IBSS on (A) SSID xxx and turn scanning (iwlist wlan0 scan) on (C),
I got:

[257484.227005] RECV [TYPE=0:40 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=18:af:61:50:d1:ca addr3=ff:ff:ff:ff:ff:ff
seq=52:0 TAG=0 len=7 SSID=myguest
[257484.909040] RECV [TYPE=0:80 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=0🅱️85:84:bc:19 addr3=0🅱️85:84:bc:19
seq=275:0 TS=1e5e51181 BI=100 CAP=21 TAG=0 len=7 SSID=myguest
[257484.911618] RECV [TYPE=0:50 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=314
addr1=78:54:2e:21:6:61 addr2=0🅱️85:84:2e:a9 addr3=0🅱️85:84:2e:a9
seq=1747:0 TS=5577aba3f BI=100 CAP=421 TAG=0 len=7 SSID=myguest
[257484.913150] RECV [TYPE=0:50 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=314
addr1=78:54:2e:21:6:61 addr2=0🅱️85:84:2e:a9 addr3=0🅱️85:84:2e:a9
seq=1748:0 TS=5577abff5 BI=100 CAP=421 TAG=0 len=7 SSID=myguest
[257484.914952] RECV [TYPE=0:50 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=314
addr1=78:54:2e:21:6:61 addr2=0🅱️85:84:bc:19 addr3=0🅱️85:84:bc:19
seq=276:0 TS=1e5e528e9 BI=100 CAP=421 TAG=0 len=7 SSID=myguest
[257484.916758] RECV [TYPE=0:80 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=0:1d:4f:fc:9f:a5 addr3=a2:10:af:d:dd:34
seq=692:0 TS=283d445 BI=100 CAP=2 TAG=0 len=3 SSID=xxx
[257484.918432] RECV [TYPE=0:50 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=314
addr1=78:54:2e:21:6:61 addr2=0:1d:4f:fc:9f:a5 addr3=a2:10:af:d:dd:34
seq=693:0 TS=283daca BI=100 CAP=2 TAG=0 len=3 SSID=xxx
[257484.929935] RECV [TYPE=0:80 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=0🅱️85:84:2e:a9 addr3=0🅱️85:84:2e:a9
seq=1749:0 TS=5577b0181 BI=100 CAP=421 TAG=0 len=7 SSID=myguest
[257485.014295] RECV [TYPE=0:80 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=0:1d:4f:fc:9f:a5 addr3=a2:10:af:d:dd:34
seq=694:0 TS=2855192 BI=100 CAP=2 TAG=0 len=3 SSID=xxx
[257485.016920] RECV [TYPE=0:50 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=314
addr1=78:54:2e:21:6:61 addr2=0:1d:4f:fc:9f:a5 addr3=a2:10:af:d:dd:34
seq=695:0 TS=2855bdb BI=100 CAP=2 TAG=0 len=3 SSID=xxx
[257485.112591] RECV [TYPE=0:50 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=314
addr1=78:54:2e:21:6:61 addr2=0:1d:4f:fc:9f:a5 addr3=a2:10:af:d:dd:34
seq=696:0 TS=286d11f BI=100 CAP=2 TAG=0 len=3 SSID=xxx
[257485.117448] RECV [TYPE=0:80 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=0:1d:4f:fc:9f:a5 addr3=a2:10:af:d:dd:34
seq=697:0 TS=286e427 BI=100 CAP=2 TAG=0 len=3 SSID=xxx
[257485.134857] RECV [TYPE=0:80 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=0🅱️85:84:2e:a9 addr3=0🅱️85:84:2e:a9
seq=1751:0 TS=5577e2181 BI=100 CAP=421 TAG=0 len=7 SSID=myguest
[257485.261982] RECV [TYPE=0:80 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=0🅱️85:84:4c:c9 addr3=0🅱️85:84:4c:c9
seq=1656:0 TS=557765181 BI=100 CAP=421 TAG=0 len=7 SSID=myguest
[257485.309205] RECV [TYPE=0:50 DS=0 MF=0 R=1 P=0 MD=0 W=0 O=0] ID=314
addr1=78:54:2e:21:6:61 addr2=0🅱️85:84:4c:c9 addr3=0🅱️85:84:4c:c9
seq=1657:0 TS=5577709f4 BI=100 CAP=421 TAG=0 len=7 SSID=myguest
[257485.350168] RECV [TYPE=0:50 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=314
addr1=78:54:2e:21:6:61 addr2=0🅱️85:84:4c:c9 addr3=0🅱️85:84:4c:c9
seq=1658:0 TS=55777a9ef BI=100 CAP=421 TAG=0 len=7 SSID=myguest
[257485.436993] RECV [TYPE=0:50 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=314
addr1=78:54:2e:21:6:61 addr2=0🅱️85:84:4c:c9 addr3=0🅱️85:84:4c:c9
seq=1660:0 TS=55778fcb7 BI=100 CAP=421 TAG=0 len=7 SSID=myguest
[257485.441681] RECV [TYPE=0:50 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=314
addr1=78:54:2e:21:6:61 addr2=0🅱️85:84:4c:c9 addr3=0🅱️85:84:4c:c9
seq=1661:0 TS=557790f44 BI=100 CAP=421 TAG=0 len=7 SSID=myguest
[257485.466875] RECV [TYPE=0:80 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=0🅱️85:84:4c:c9 addr3=0🅱️85:84:4c:c9
seq=1662:0 TS=557797181 BI=100 CAP=421 TAG=0 len=7 SSID=myguest
[257485.569313] RECV [TYPE=0:80 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=0🅱️85:84:4c:c9 addr3=0🅱️85:84:4c:c9
seq=1663:0 TS=5577b0181 BI=100 CAP=421 TAG=0 len=7 SSID=myguest
[257485.915606] RECV [TYPE=0:50 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=314
addr1=78:54:2e:21:6:61 addr2=0🅱️85:84:33:89 addr3=0🅱️85:84:33:89
seq=3330:0 TS=557162f90 BI=100 CAP=421 TAG=0 len=7 SSID=myguest
[257485.924284] RECV [TYPE=0:80 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=a0:f3:c1:7c:4:ea addr3=a0:f3:c1:7c:4:ea
seq=3875:0 TS=8e049f55a5 BI=100 CAP=431 TAG=0 len=3 SSID=sec
[257486.071794] RECV [TYPE=0:80 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=0🅱️85:84:33:89 addr3=0🅱️85:84:33:89
seq=3332:0 TS=557189181 BI=100 CAP=421 TAG=0 len=7 SSID=myguest

so we can see announcement of xxx network (beacon and probe response)

I setup IBSS on (B) SSID yyy and turn scanning (iwlist wlan0 scan) on (C),
I got:
[260485.836706] RECV [TYPE=0:80 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=0🅱️85:84:2e:a9 addr3=0🅱️85:84:2e:a9
seq=2842:0 TS=60a4d2181 BI=100 CAP=421 TAG=0 len=7 SSID=myguest
[260485.904100] RECV [TYPE=0:80 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=0:1d:4f:fc:9f:a5 addr3=a2:10:af:d:dd:34
seq=1556:0 TS=b55774dc BI=100 CAP=2 TAG=0 len=3 SSID=xxx
[260485.921194] RECV [TYPE=0:50 DS=0 MF=0 R=1 P=0 MD=0 W=0 O=0] ID=314
addr1=78:54:2e:21:6:61 addr2=0🅱️85:84:2e:a9 addr3=0🅱️85:84:2e:a9
seq=2843:0 TS=60a4e6bd9 BI=100 CAP=421 TAG=0 len=7 SSID=myguest
[260485.924753] RECV [TYPE=0:50 DS=0 MF=0 R=1 P=0 MD=0 W=0 O=0] ID=314
addr1=78:54:2e:21:6:61 addr2=0🅱️85:84:2e:a9 addr3=0🅱️85:84:2e:a9
seq=2843:0 TS=60a4e79a1 BI=100 CAP=421 TAG=0 len=7 SSID=myguest
[260485.927335] RECV [TYPE=0:50 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=314
addr1=78:54:2e:21:6:61 addr2=0:1d:4f:fc:9f:a5 addr3=a2:10:af:d:dd:34
seq=1557:0 TS=b557cf66 BI=100 CAP=2 TAG=0 len=3 SSID=xxx
[260486.005852] RECV [TYPE=0:80 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=0:1d:4f:fc:9f:a5 addr3=a2:10:af:d:dd:34
seq=1558:0 TS=b5590230 BI=100 CAP=2 TAG=0 len=3 SSID=xxx

there were no announcement of yyy network, I checked scan many times and
also check on host (A). It's definitely a problem.

experiment 2)
I have IBSS xxx tuned on (A) and I add host (B) to the same network.

[260990.091607] RECV [TYPE=0:50 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=314
addr1=78:54:2e:21:6:61 addr2=f8:1a:67:27:d0:a4 addr3=a2:10:af:d:dd:34
seq=77:0 TS=d362c6b6 BI=100 CAP=2 TAG=0 len=3 SSID=xxx
[260990.096972] RECV [TYPE=0:50 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=314
addr1=78:54:2e:21:6:61 addr2=f8:1a:67:27:d0:a4 addr3=a2:10:af:d:dd:34
seq=78:0 TS=d362dbaa BI=100 CAP=2 TAG=0 len=3 SSID=xxx
[260990.098839] RECV [TYPE=0:50 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=314
addr1=78:54:2e:21:6:61 addr2=0:1d:4f:fc:9f:a5 addr3=a2:10:af:d:dd:34
seq=2443:0 TS=d362e074 BI=100 CAP=2 TAG=0 len=3 SSID=xxx
[260990.148834] RECV [TYPE=0:80 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=0:1d:4f:fc:9f:a5 addr3=a2:10:af:d:dd:34
seq=2444:0 TS=d363a384 BI=100 CAP=2 TAG=0 len=3 SSID=xxx
[260990.195612] RECV [TYPE=0:50 DS=0 MF=0 R=1 P=0 MD=0 W=0 O=0] ID=314
addr1=78:54:2e:21:6:61 addr2=f8:1a:67:27:d0:a4 addr3=a2:10:af:d:dd:34
seq=79:0 TS=d3645cb1 BI=100 CAP=2 TAG=0 len=3 SSID=xxx
[260990.201248] RECV [TYPE=0:50 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=314
addr1=78:54:2e:21:6:61 addr2=0:1d:4f:fc:9f:a5 addr3=a2:10:af:d:dd:34
seq=2445:0 TS=d3647055 BI=100 CAP=2 TAG=0 len=3 SSID=xxx
[260990.202503] RECV [TYPE=0:50 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=314
addr1=78:54:2e:21:6:61 addr2=f8:1a:67:27:d0:a4 addr3=a2:10:af:d:dd:34
seq=80:0 TS=d3647792 BI=100 CAP=2 TAG=0 len=3 SSID=xxx
[260990.254024] RECV [TYPE=0:80 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=0:1d:4f:fc:9f:a5 addr3=a2:10:af:d:dd:34
seq=2446:0 TS=d3653e7a BI=100 CAP=2 TAG=0 len=3 SSID=xxx
[260990.289011] RECV [TYPE=0:50 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=314
addr1=78:54:2e:21:6:61 addr2=0:1d:4f:fc:9f:a5 addr3=a2:10:af:d:dd:34
seq=2447:0 TS=d365c6ba BI=100 CAP=2 TAG=0 len=3 SSID=xxx
[260990.292784] RECV [TYPE=0:50 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=314
addr1=78:54:2e:21:6:61 addr2=f8:1a:67:27:d0:a4 addr3=a2:10:af:d:dd:34
seq=81:0 TS=d365d838 BI=100 CAP=2 TAG=0 len=3 SSID=xxx

I can see prove response from both host, but beacon only from (A). I tried
it many times but haven't seen beacon from (B), but according to standard
each host must send beacon in specified interval if other hosts haven't.

experiment 3)

I have IBSS xxx tuned on (A), (B) and I add host (C) to the same network.

[261561.661568] RECV [TYPE=0:40 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=84:7a:88:14:2f:8e addr3=ff:ff:ff:ff:ff:ff
seq=1256:0 TAG=0 len=0 SSID=
[261561.683346] RECV [TYPE=0:40 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=84:7a:88:14:2f:8e addr3=ff:ff:ff:ff:ff:ff
seq=1257:0 TAG=0 len=0 SSID=
[261562.514163] rtw_select_and_join_from_scanned_queue: candidate:
xxx(a2:10:af:0d:dd:34 ch:1)
[261562.610064] RECV [TYPE=0:80 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=0:1d:4f:fc:9f:a5 addr3=a2:10:af:d:dd:34
seq=8:0 TS=f58073c4 BI=100 CAP=2 TAG=0 len=3 SSID=xxx
[261562.610917] RTL8188: ERROR assoc success
[261562.610955] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[261562.614147] RECV [TYPE=8:48 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=60
addr1=78:54:2e:21:6:61 addr2=0:1d:4f:fc:9f:a5 addr3=a2:10:af:d:dd:34
seq=9:0
[261562.712332] RECV [TYPE=0:80 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=0:1d:4f:fc:9f:a5 addr3=a2:10:af:d:dd:34
seq=10:0 TS=f582038b BI=100 CAP=2 TAG=0 len=3 SSID=xxx
[261562.814435] RECV [TYPE=0:80 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=0:1d:4f:fc:9f:a5 addr3=a2:10:af:d:dd:34
seq=12:0 TS=f583925a BI=100 CAP=2 TAG=0 len=3 SSID=xxx
[261562.916792] RECV [TYPE=0:80 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=0:1d:4f:fc:9f:a5 addr3=a2:10:af:d:dd:34
seq=13:0 TS=f58521ba BI=100 CAP=2 TAG=0 len=3 SSID=xxx
[262364.669107] RECV [TYPE=0:50 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=314
addr1=0:22:43:1b:7:67 addr2=f8:1a:67:27:d0:a4 addr3=a2:10:af:d:dd:34
seq=640:0 TS=1254c0e16 BI=100 CAP=2 TAG=0 len=3 SSID=xxx
[262364.669985] RECV [TYPE=0:50 DS=0 MF=0 R=1 P=0 MD=0 W=0 O=0] ID=314
addr1=0:22:43:1b:7:67 addr2=f8:1a:67:27:d0:a4 addr3=a2:10:af:d:dd:34
seq=640:0 TS=1254c11a0 BI=100 CAP=2 TAG=0 len=3 SSID=xxx
[262364.670857] RECV [TYPE=0:50 DS=0 MF=0 R=1 P=0 MD=0 W=0 O=0] ID=314
addr1=0:22:43:1b:7:67 addr2=f8:1a:67:27:d0:a4 addr3=a2:10:af:d:dd:34
seq=640:0 TS=1254c153e BI=100 CAP=2 TAG=0 len=3 SSID=xxx
[262364.671734] RECV [TYPE=0:50 DS=0 MF=0 R=1 P=0 MD=0 W=0 O=0] ID=314
addr1=0:22:43:1b:7:67 addr2=f8:1a:67:27:d0:a4 addr3=a2:10:af:d:dd:34
seq=640:0 TS=1254c18b4 BI=100 CAP=2 TAG=0 len=3 SSID=xxx
[262364.672737] RECV [TYPE=0:50 DS=0 MF=0 R=1 P=0 MD=0 W=0 O=0] ID=314
addr1=0:22:43:1b:7:67 addr2=f8:1a:67:27:d0:a4 addr3=a2:10:af:d:dd:34
seq=640:0 TS=1254c1c52 BI=100 CAP=2 TAG=0 len=3 SSID=xxx

well, not so much interesting here

experiment 4)
I configured IPs
A: Broarcom
HW:0:1d:4f:fc:9f:a5
10.0.0.1
B: TPLink HW:f8:1a:67:27:d0:a4 (rtl8188eu) (original
driver) 10.0.0.4
C: DLINK HW:78:54:2e:21:06:61 (rtl8188eu) <-- On this host I take
logs with modified driver 10.0.0.5

and run on (A) ping 10.0.0.5 and on (B) ping 10.0.0.5

[262891.343199] RECV [TYPE=8:8 DS=0 MF=0 R=1 P=0 MD=0 W=0 O=0] ID=44
addr1=f8:1a:67:27:d0:a4 addr2=0:1d:4f:fc:9f:a5 addr3=a2:10:af:d:dd:34
seq=859:0
[262891.346096] RECV [TYPE=8:88 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=293
addr1=0:1d:4f:fc:9f:a5 addr2=f8:1a:67:27:d0:a4 addr3=a2:10:af:d:dd:34
seq=152:0
[262892.032181] RECV [TYPE=8:8 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=f8:1a:67:27:d0:a4 addr3=a2:10:af:d:dd:34
seq=1055:0
[262892.344989] RECV [TYPE=8:88 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=293
addr1=0:1d:4f:fc:9f:a5 addr2=f8:1a:67:27:d0:a4 addr3=a2:10:af:d:dd:34
seq=153:0
[262893.031502] RECV [TYPE=8:8 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=f8:1a:67:27:d0:a4 addr3=a2:10:af:d:dd:34
seq=1056:0
[262893.344505] RECV [TYPE=8:8 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=44
addr1=f8:1a:67:27:d0:a4 addr2=0:1d:4f:fc:9f:a5 addr3=a2:10:af:d:dd:34
seq=882:0
[262893.344877] RECV [TYPE=8:8 DS=0 MF=0 R=1 P=0 MD=0 W=0 O=0] ID=44
addr1=f8:1a:67:27:d0:a4 addr2=0:1d:4f:fc:9f:a5 addr3=a2:10:af:d:dd:34
seq=882:0
[262893.347257] RECV [TYPE=8:88 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=293
addr1=0:1d:4f:fc:9f:a5 addr2=f8:1a:67:27:d0:a4 addr3=a2:10:af:d:dd:34
seq=154:0
[262894.060777] RECV [TYPE=8:8 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=f8:1a:67:27:d0:a4 addr3=a2:10:af:d:dd:34
seq=1057:0
[262894.345723] RECV [TYPE=8:8 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=44
addr1=f8:1a:67:27:d0:a4 addr2=0:1d:4f:fc:9f:a5 addr3=a2:10:af:d:dd:34
seq=892:0
[262895.060568] RECV [TYPE=8:8 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=f8:1a:67:27:d0:a4 addr3=a2:10:af:d:dd:34
seq=1058:0
[262895.347397] RECV [TYPE=8:8 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=44
addr1=f8:1a:67:27:d0:a4 addr2=0:1d:4f:fc:9f:a5 addr3=a2:10:af:d:dd:34
seq=903:0
[262895.366777] RECV [TYPE=8:88 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=293
addr1=0:1d:4f:fc:9f:a5 addr2=f8:1a:67:27:d0:a4 addr3=a2:10:af:d:dd:34
seq=156:0
[262895.367397] RECV [TYPE=8:88 DS=0 MF=0 R=1 P=0 MD=0 W=0 O=0] ID=293
addr1=0:1d:4f:fc:9f:a5 addr2=f8:1a:67:27:d0:a4 addr3=a2:10:af:d:dd:34
seq=156:0
[262895.368650] RECV [TYPE=8:88 DS=0 MF=0 R=1 P=0 MD=0 W=0 O=0] ID=293
addr1=0:1d:4f:fc:9f:a5 addr2=f8:1a:67:27:d0:a4 addr3=a2:10:af:d:dd:34
seq=156:0
[262895.371776] RECV [TYPE=8:88 DS=0 MF=0 R=1 P=0 MD=0 W=0 O=0] ID=293
addr1=0:1d:4f:fc:9f:a5 addr2=f8:1a:67:27:d0:a4 addr3=a2:10:af:d:dd:34
seq=156:0
[262896.065839] RECV [TYPE=8:8 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=f8:1a:67:27:d0:a4 addr3=a2:10:af:d:dd:34
seq=1059:0
[262897.108729] RECV [TYPE=8:8 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=f8:1a:67:27:d0:a4 addr3=a2:10:af:d:dd:34
seq=1060:0
[262897.683504] RECV [TYPE=0:50 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=314
addr1=8c:70:5a:ae:db:d4 addr2=f8:1a:67:27:d0:a4 addr3=a2:10:af:d:dd:34
seq=1061:0 TS=1450f4bed BI=100 CAP=2 TAG=0 len=3 SSID=xxx
[262897.691878] RECV [TYPE=0:50 DS=0 MF=0 R=1 P=0 MD=0 W=0 O=0] ID=314
addr1=8c:70:5a:ae:db:d4 addr2=f8:1a:67:27:d0:a4 addr3=a2:10:af:d:dd:34
seq=1061:0 TS=1450f6d08 BI=100 CAP=2 TAG=0 len=3 SSID=xxx
[262897.692756] RECV [TYPE=0:50 DS=0 MF=0 R=1 P=0 MD=0 W=0 O=0] ID=314
addr1=8c:70:5a:ae:db:d4 addr2=f8:1a:67:27:d0:a4 addr3=a2:10:af:d:dd:34
seq=1061:0 TS=1450f70a6 BI=100 CAP=2 TAG=0 len=3 SSID=xxx
[262897.694016] RECV [TYPE=0:50 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=314
addr1=8c:70:5a:ae:db:d4 addr2=f8:1a:67:27:d0:a4 addr3=a2:10:af:d:dd:34
seq=1062:0 TS=1450f759f BI=100 CAP=2 TAG=0 len=3 SSID=xxx
[262897.696131] RECV [TYPE=0:50 DS=0 MF=0 R=1 P=0 MD=0 W=0 O=0] ID=314
addr1=8c:70:5a:ae:db:d4 addr2=f8:1a:67:27:d0:a4 addr3=a2:10:af:d:dd:34
seq=1062:0 TS=1450f7db9 BI=100 CAP=2 TAG=0 len=3 SSID=xxx

then I close ping on (A) and see only

[262898.092611] RECV [TYPE=8:8 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=f8:1a:67:27:d0:a4 addr3=a2:10:af:d:dd:34
seq=1063:0
[262899.091244] RECV [TYPE=8:8 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=f8:1a:67:27:d0:a4 addr3=a2:10:af:d:dd:34
seq=1064:0
[262900.121771] RECV [TYPE=8:8 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=f8:1a:67:27:d0:a4 addr3=a2:10:af:d:dd:34
seq=1065:0
[262901.121528] RECV [TYPE=8:8 DS=0 MF=0 R=0 P=0 MD=0 W=0 O=0] ID=0
addr1=ff:ff:ff:ff:ff:ff addr2=f8:1a:67:27:d0:a4 addr3=a2:10:af:d:dd:34
seq=1066:0

well I can see broadcast messages from (B) on (C), probably ARP. So either
this device (C) do not reply or it replies but it get filtered on (B)

Conclusions

It's really hard to impossible to understand the causation of the problems
without knowing what's done in hardware and in firmware.

Is there mode to tun off hardware filtration on rtl8188eu? Without it and
knowing what's going on in hardware/wirmware I can't do any futher
investigation.

Best Regards,
Sergey

@lwfinger

This comment has been minimized.

Owner

lwfinger commented Oct 3, 2013

Welcome to my world. I have no knowledge of the internal workings of the chip other than what I can infer from the code, and you see that as well.

@sergforce

This comment has been minimized.

sergforce commented Oct 3, 2013

I thought you're in touch with realtek engineers and you can ask questions
to them. So without their help it's nearly impossible to debug :( Do you
have contacts with them? May be you can post error to them?

On Thu, Oct 3, 2013 at 6:56 PM, lwfinger notifications@github.com wrote:

Welcome to my world. I have no knowledge of the internal workings of the
chip other than what I can infer from the code, and you see that as well.


Reply to this email directly or view it on GitHubhttps://github.com//issues/4#issuecomment-25627431
.

@lwfinger

This comment has been minimized.

Owner

lwfinger commented Oct 3, 2013

Yes, I can contact them and ask questions, but I need to have the proper over-the-air captures. Until I get such data to send them, I choose not to bother them. So far, I have not had time to make such captures.

@Sultan91

This comment has been minimized.

Sultan91 commented Jul 5, 2017

I guess the problem is still persists.
Currently experiencing tha same issue with TL-WN722N wifi adapters. They don't ping each other till some other wifi adapter is present (for instance RPI3 intergrated WIFI).
Can someone reccomend 100% reliable wifi chipset or adapter model for ad-hoc modes?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment