~h-box/h-box/rewrite : changes

~h-box/h-box/rewrite » Changes from revision 38

From Revision 38 to 19

Rev	Summary	Authors	Date
38	Added a directory for thesis development Added a directory for thesis development	Vu Dung	12 years ago
37	updating the installation file updating the installation file	Amit Soni	12 years ago
36	final changes by amit soni final changes by amit soni	Amit Soni	12 years ago
35	adding m4 files adding m4 files	amit	13 years ago
34	if there is a failed action response then the user wasn't ab... if there is a failed action response then the user wasn't able to execute subsequent, this has been fixed in this comit	amit	13 years ago
33	README modified with the sample run README modified with the sample run	amit	13 years ago
32	removing unnecessary things from the INSTALL file. removing unnecessary things from the INSTALL file.	amit	13 years ago
31	Commit for #693033 automatize address rewriting process Commit for #693033 automatize address rewriting process	amit	13 years ago
30	Adding installation instructions Adding installation instructions	amit	13 years ago
29	Makefile and configure file committed. Makefile and configure file committed.	amit	13 years ago
28	Comments added. Dead code removed. Comments added. Dead code removed.	amit	13 years ago
27	Packet forwarding has been done at the application level. Ea... Packet forwarding has been done at the application level. Earlier discussions were going on to do packet forwarding at the socket(TCP) level but then iptables were becoming too complicated since HIP also uses iptables to farward packets by makin hole in the NAT router. Socket level forwarding is still on the table. Currently after this commit we would be able to communicate between two hboxes directly but only one of them can be behind NAT. Handling the situation where both the hboxes are behind NAT is the next thing to do. This comit also uses boost threads so the extra package (boost threads) is now required to run hbox.	amit	13 years ago
26	Synchroniztion of the ACTION_RESPONSE has been added. We are... Synchroniztion of the ACTION_RESPONSE has been added. We are now able to get the action response from the remote hbox instantaneously. HIP assosiation has also been done and LSI has also been recovered from the hipconf command. Result of which is to say that we are now able to ping the remote hbox using the LSI. This checkin assumes that only one hbox is behind the NAT, in other words, atleast one hbox is able to ping the other hbox using IPv4. If both the hboxes are inside the NAT then relay server is required.	amit	13 years ago
25	Almost everything is handled for the newly added device in t... Almost everything is handled for the newly added device in the remote network. It's just that due to some bug in the cybergarage library new device object can't load the description file.	amit	13 years ago
24	Case when two devices that share the same URLs in the servic... Case when two devices that share the same URLs in the services handled in this commit. Code for handling newly added devices is also added but currently it's not in the working state.	amit	13 years ago
23	Individual device removal in the remote hbox has now been ha... Individual device removal in the remote hbox has now been handled.	amit	13 years ago
22	Individual device removal in the remote hbox has now been ha... Individual device removal in the remote hbox has now been handled.	amit	13 years ago
21	Hbox we now be able to cleanly remove the remote hbox. Earli... Hbox we now be able to cleanly remove the remote hbox. Earlier it used to crash whenever a remtoe hbox was removed. Individual device removal in the remote hbox has not been handled yet.	amit	13 years ago
20	Adding comments regarding where to forward ports on rendrer ... Adding comments regarding where to forward ports on rendrer side hbox to the server side hbox and afterwards advertize it to the actual media rendrer device.	amit	13 years ago
19	Hbox at the media rendrer is now able to receive the forward... Hbox at the media rendrer is now able to receive the forwarded ports at the Media Server side. Now, task remaining is to forward ports at the rendrer side and setup the connection using the forwarded ports	amit	13 years ago

Older »