Version 17 (modified by 13 years ago) ( diff ) | ,
---|
[Jun 7th] Attend the MF weekly meeting and get myself familiar with the people and environment here; talked with Kiran about the project.
[Jun 8th] Get rooted Sprint Evo phone from Ivan and start to play with it.
[Jun 9th] Tested a sample android NDK example to call C socket API (socket(AF_INET, SOCK_STREAM, IPPROTO_TCP) succeed!); tried socket(AF_PACKET, SOCK_RAW, 0) and return errno 1 which means no root permission, so we need a way to run the app with root.
[Jun 14th] Two options for client MF stack implementation: 1) raw socket(??) 2) android libpcap. Click(use libpcap) is maybe a option if we could port it to android.
[Jun 15th] use both 'netcfg' and 'ifconfig' to check the interfaces in android.
[Jun 16th] ALL of the outdoor node have Intel Wimax card
Use following commands to load wifi driver after ubuntu.ndz was loaded
modprobe ath5k // for 5xxx card modprobe ath9k // for 9xxx card
Use following commands to load wimax driver after ubuntu.ndz was loaded
modprobe i2400m-usb // this will in turn load module 'wimax' and 'i2400m'
Now,
root@node1-5:/usr# ifconfig wmx0 wmx0 Link encap:Ethernet HWaddr 00:1d:e1:37:10:c1 NOARP MTU:1400 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:20 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Then, let's connect the Wimax client to Wimax BS
wimaxd -i wmx0 -b wimaxcu ron wimaxcu scan wimaxcu connect network 51
But failed to connect as of today.
[Jun 20th] Connection succeed with node1-6
root@node1-6:~# wimaxcu connect network 51 Current Preferred Profile is: ID : 51 Name: GENI 4G Connecting to GENI 4G Network... Connection successful
Command used to check the connection status
root@node1-6:~# wimaxcu status Connected.
Get IP.
root@node1-6:~# dhclient wmx0 root@node1-6:~# ifconfig wmx0 wmx0 Link encap:Ethernet HWaddr 00:1d:e1:36:ff:4f inet addr:10.41.1.6 Mask:255.255.0.0 inet6 addr: fe80::21d:e1ff:fe36:ff4f/64 Scope:Link UP RUNNING NOARP MTU:1400 Metric:1 RX packets:161 errors:0 dropped:0 overruns:0 frame:0 TX packets:214 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:20 RX bytes:21872 (21.8 KB) TX bytes:18836 (18.8 KB)
Sprint Evo 4G is connected.
# netcfg lo UP 127.0.0.1 255.0.0.0 0x00000049 dummy0 DOWN 0.0.0.0 0.0.0.0 0x00000082 rmnet0 DOWN 0.0.0.0 0.0.0.0 0x00001002 rmnet1 DOWN 0.0.0.0 0.0.0.0 0x00001002 rmnet2 DOWN 0.0.0.0 0.0.0.0 0x00001002 usb0 DOWN 0.0.0.0 0.0.0.0 0x00001002 sit0 DOWN 0.0.0.0 0.0.0.0 0x00000080 ip6tnl0 DOWN 0.0.0.0 0.0.0.0 0x00000080 wimax0 UP 10.41.4.1 255.255.0.0 0x00000043
After Ivan add the Evo IP:10.41.4.1 to the Wimax BS config file, ping went through between Evo and ourdoor node [1,6]
[Jun 21th] NetAPI:
http://www.eecs.berkeley.edu/Pubs/TechRpts/2009/EECS-2009-141.html. http://www.icsi.berkeley.edu/~barath/papers/fii-ccr11.pdf
NetAPI use 'schemes' to encapsulate specific classes of communication --------->??? similar to 'services' in MobilityFirst
NetAPI Connection: scheme://resource (web://, video://, voice:// etc.)
NetAPI: Application responsibilities: 1) breaking content into messages 2) specifying destination names (?? ) 3) specifying a high-level security policy
disconnection tolerance;multi-interface; best performance and best battery life policy
NetAPI provides five basic high-level operations:
open(scheme://resource, options) ⇒ handle put(handle, message, options) ⇒ result get(handle, options) ⇒ message control(handle, options) ⇒ result -----------> which MF GUID to use could be specified here close(handle, options) ⇒ result
Responsibilities of scheme
resolving names binding to address selecting transport protocols encoding messages ensuring communication security
[Jun 24th] MF Client System with emphasis on DTN style routing
Attachments (2)
- MFClientImplementation.png (148.8 KB ) - added by 13 years ago.
- MFClientImplementation2.png (184.8 KB ) - added by 13 years ago.
Download all attachments as: .zip