<div dir="ltr"><span style="font-family:arial,sans-serif;font-size:14px">Hi Jouni,</span><br><div><span style="font-family:arial,sans-serif;font-size:14px"><br></span></div><div style><span style="font-family:arial,sans-serif;font-size:14px">I think Google, Boardcom and Intel use this solution for the </span><font face="arial, sans-serif"><span style="font-size:14px">Wi-Fi P2P cross connection</span></font><span style="font-family:arial,sans-serif;font-size:14px">, but it can not run fine in Android 4.2.2 yet. </span><span style="font-family:arial,sans-serif;font-size:14px">Please refer to the following information of android </span><span style="font-family:arial,sans-serif;font-size:14px">P2P</span><span style="font-family:arial,sans-serif;font-size:14px">, it is a </span><span style="font-family:arial,sans-serif;font-size:14px">P2P</span><span style="font-family:arial,sans-serif;font-size:14px">-GO role in mobile,</span></div>
<div style><span style="font-family:arial,sans-serif;font-size:14px">if wlan0 connect the internet, and system uses iptable(maybe more another techonology) to create a special relation between </span><span style="font-family:arial,sans-serif;font-size:14px">p2p0 </span><span style="font-family:arial,sans-serif;font-size:14px"> and </span><span style="font-family:arial,sans-serif;font-size:14px">wlan0</span><span style="font-family:arial,sans-serif;font-size:14px">, </span><span style="font-family:arial,sans-serif;font-size:14px">P2P</span><span style="font-family:arial,sans-serif;font-size:14px">-Client will very </span><span style="font-family:arial,sans-serif;font-size:14px">conveniently </span><font face="arial, sans-serif"><span style="font-size:14px">surf internet via </span></font><span style="font-family:arial,sans-serif;font-size:14px"> the </span><font face="arial, sans-serif"><span style="font-size:14px">Wi-Fi P2P cross connection</span></font><font face="arial, sans-serif"><span style="font-size:14px">. In fact this </span></font><span style="font-family:arial,sans-serif;font-size:14px">functionality is simalerly tetheing </span></div>
<div style><font face="arial, sans-serif"><span style="font-size:14px"><br></span></font></div><div style>May be described as:<br></div><div style><div><font face="arial, sans-serif"><span style="font-size:14px">Cross Connection is the optional capability of a P2P Group Owner to provide</span></font></div>
<div><font face="arial, sans-serif"><span style="font-size:14px">WLAN access to P2P Clients within its P2P Group.</span></font></div><div><font face="arial, sans-serif"><span style="font-size:14px"><br></span></font></div>
<div><font face="arial, sans-serif"><span style="font-size:14px">In fact, this is an integrated technology, concurrently enable Wi-Fi tethering and P2P.</span><br></font></div></div><div style><font face="arial, sans-serif"><span style="font-size:14px"><br>
</span></font></div><div style><font face="arial, sans-serif"><span style="font-size:14px"><br></span></font></div><div style><font face="arial, sans-serif"><span style="font-size:14px">Hi Arend,</span></font></div><div style>
<br></div><div style><font face="arial, sans-serif"><span style="font-size:14px">Could you please consult with the firmware or Android network system </span></font><span style="font-family:arial,sans-serif;font-size:14px">engineer</span><span style="font-family:arial,sans-serif;font-size:14px"> in </span><span style="font-family:arial,sans-serif;font-size:14px">Boardcom,</span><font face="arial, sans-serif"><span style="font-size:14px"><br>
</span></font></div><div style><span style="font-family:arial,sans-serif;font-size:14px">and please clarify the thinking behind this one? </span><span style="font-family:arial,sans-serif;font-size:14px"><br></span></div><div style>
<span style="font-family:arial,sans-serif;font-size:14px"><br></span></div><div style><span style="font-family:arial,sans-serif;font-size:14px">Thanks.</span></div><div style><br></div><div style>---------------------------------------------------------------------------------------------------------</div>
<div style><font face="arial, sans-serif"><span style="font-size:14px">Reference information:</span></font></div><div style><div><font face="arial, sans-serif"><span style="font-size:14px">root@android:/ # ifconfig </span></font></div>
<div><font face="arial, sans-serif"><span style="font-size:14px">lo Link encap:Local Loopback </span></font></div><div><font face="arial, sans-serif"><span style="font-size:14px"> inet addr:127.0.0.1 Mask:255.0.0.0</span></font></div>
<div><font face="arial, sans-serif"><span style="font-size:14px"> inet6 addr: ::1/128 Scope:Host</span></font></div><div><font face="arial, sans-serif"><span style="font-size:14px"> UP LOOPBACK RUNNING MTU:16436 Metric:1</span></font></div>
<div><font face="arial, sans-serif"><span style="font-size:14px"> RX packets:18401 errors:0 dropped:0 overruns:0 frame:0</span></font></div><div><font face="arial, sans-serif"><span style="font-size:14px"> TX packets:18401 errors:0 dropped:0 overruns:0 carrier:0</span></font></div>
<div><font face="arial, sans-serif"><span style="font-size:14px"> collisions:0 txqueuelen:0 </span></font></div><div><font face="arial, sans-serif"><span style="font-size:14px"> RX bytes:149934880 (142.9 MiB) TX bytes:149934880 (142.9 MiB)</span></font></div>
<div><font face="arial, sans-serif"><span style="font-size:14px"><br></span></font></div><div><font face="arial, sans-serif"><span style="font-size:14px">p2p0 Link encap:Ethernet HWaddr 12:68:3F:38:6E:2C </span></font></div>
<div><font face="arial, sans-serif"><span style="font-size:14px"> inet addr:192.168.49.1 Bcast:192.168.49.255 Mask:255.255.255.0</span></font></div><div><font face="arial, sans-serif"><span style="font-size:14px"> inet6 addr: fe80::1068:3fff:fe38:6e2c/64 Scope:Link</span></font></div>
<div><font face="arial, sans-serif"><span style="font-size:14px"> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1</span></font></div><div><font face="arial, sans-serif"><span style="font-size:14px"> RX packets:9 errors:0 dropped:0 overruns:0 frame:0</span></font></div>
<div><font face="arial, sans-serif"><span style="font-size:14px"> TX packets:21 errors:0 dropped:0 overruns:0 carrier:0</span></font></div><div><font face="arial, sans-serif"><span style="font-size:14px"> collisions:0 txqueuelen:100 </span></font></div>
<div><font face="arial, sans-serif"><span style="font-size:14px"> RX bytes:1285 (1.2 KiB) TX bytes:2677 (2.6 KiB)</span></font></div><div><font face="arial, sans-serif"><span style="font-size:14px"><br></span></font></div>
<div><font face="arial, sans-serif"><span style="font-size:14px">wlan0 Link encap:Ethernet HWaddr 10:68:3F:38:6E:2C </span></font></div><div><font face="arial, sans-serif"><span style="font-size:14px"> inet addr:192.168.1.100 Bcast:255.255.255.255 Mask:255.255.255.0</span></font></div>
<div><font face="arial, sans-serif"><span style="font-size:14px"> inet6 addr: fe80::1268:3fff:fe38:6e2c/64 Scope:Link</span></font></div><div><font face="arial, sans-serif"><span style="font-size:14px"> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1</span></font></div>
<div><font face="arial, sans-serif"><span style="font-size:14px"> RX packets:11553 errors:0 dropped:0 overruns:0 frame:0</span></font></div><div><font face="arial, sans-serif"><span style="font-size:14px"> TX packets:8693 errors:0 dropped:0 overruns:0 carrier:0</span></font></div>
<div><font face="arial, sans-serif"><span style="font-size:14px"> collisions:0 txqueuelen:100 </span></font></div><div><font face="arial, sans-serif"><span style="font-size:14px"> RX bytes:8538960 (8.1 MiB) TX bytes:1071653 (1.0 MiB)</span></font></div>
<div><font face="arial, sans-serif"><span style="font-size:14px"><br></span></font></div><div style><font face="arial, sans-serif"><span style="font-size:14px">Cheers,</span></font></div><div style><font face="arial, sans-serif"><span style="font-size:14px"><br>
</span></font></div><div style><font face="arial, sans-serif"><span style="font-size:14px">Chengyi</span></font></div><div style="font-family:arial,sans-serif;font-size:14px"><br></div></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">2013/7/1 Jouni Malinen <span dir="ltr"><<a href="mailto:j@w1.fi" target="_blank">j@w1.fi</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Sun, Jun 30, 2013 at 10:43:46PM +0200, Arend van Spriel wrote:<br>
> Good point. The P2P interface address and P2P device address only<br>
> need to be different if one would want to do P2P management and have<br>
> a group connection concurrently (correct me if I am wrong here,<br>
> maybe it is a restriction for brcm firmware only) so the check seems<br>
> a bit too restrictive.<br>
<br>
</div>There is no such restriction in the P2P protocol specification. I've<br>
been trying to figure out why Broadcom went with such design, but<br>
anyway, if that is indeed a restriction in the firmware, it could be<br>
useful to provide a driver capability flag to allow wpa_supplicant to<br>
determine which rule to use.. I would use either the non-P2P station<br>
interface MAC address or alternatively, the first P2P Interface Address<br>
(which should be that non-P2P station interface MAC address with the<br>
locally administered bit set to 1 or another globally unique MAC<br>
address) as the P2P Device Address.<br>
<br>
I would really like to avoid confusion and unjustifiable requests in<br>
this area where that existing design could be used to claim that other<br>
drivers need to behave similarly when there is no real technical reason<br>
for doing that. In other words, drivers should be able to select<br>
whichever P2P spec compliant mechanism they need. wpa_supplicant should<br>
hide these internal details from anything above it (and that can now<br>
finally be the case with the global control interface for P2P<br>
operations).<br>
<br>
An earlier thread seemed to already imply that some people may believe<br>
that this new dedicated P2P_DEVICE is needed for some concurrent P2P<br>
operations which is simply not the case; it just adds another option for<br>
internal driver/firmware/hardware design which should not add or remove<br>
any functionality and the only externally observable difference should<br>
be in MAC addresses potentially being different (but even those could be<br>
assigned using the same style between P2P_DEVICE and p2p-mgmt-netdev).<br>
<div class="im HOEnZb"><br>
--<br>
Jouni Malinen PGP id EFC895FA<br>
</div><div class="HOEnZb"><div class="h5">_______________________________________________<br>
HostAP mailing list<br>
<a href="mailto:HostAP@lists.shmoo.com">HostAP@lists.shmoo.com</a><br>
<a href="http://lists.shmoo.com/mailman/listinfo/hostap" target="_blank">http://lists.shmoo.com/mailman/listinfo/hostap</a><br>
</div></div></blockquote></div><br></div>