Open Network Opimization Platform

Well I finally moved the code to GitHub. Mostly because it allows other users to contribute to the project easier and also because of its more advanced integrations for automated build services. I did have to re-write the commit's from the old ... [More] SourceForge usernames to standard email addresses so all previous commits are linked to the same user on GitHub. You can find the new code repository here: https://github.com/OpenNOP/opennop [Less]

Well I finally moved the code to GitHub. Mostly because it allows other users to contribute to the project easier and also because of its more advanced integrations for automated build services. I did have to re-write the commit's from the old ... [More] SourceForge usernames to standard email addresses so all previous commits are linked to the same user on GitHub. You can find the new code repository here: https://github.com/OpenNOP/opennop [Less]

I did some maintenance on the devel branch to remove invalid commit authors. I noticed a few commit's had localhost instead of a valid sf.net user email. This was confirmed by running this command. git log | grep "^Author: " | sort | uniq -c I ... [More] then replaced those "invalid" commits with a valid one. git filter-branch --commit-filter ' if [ "$GIT_AUTHOR_NAME" = "Sharwan Joram" ]; then GIT_AUTHOR_NAME="Sharwan Joram"; GIT_AUTHOR_EMAIL="[email protected]"; git commit-tree "$@"; else git commit-tree "$@"; fi' HEAD Unfortunatly I had to delete the entire devel branch on sf.net and repush from my local copy. git push origin :devel git push origin [Less]

I did some maintenance on the devel branch to remove invalid commit authors. I noticed a few commit's had localhost instead of a valid sf.net user email. This was confirmed by running this command. git log | grep "^Author: " | sort | uniq -c I ... [More] then replaced those "invalid" commits with a valid one. git filter-branch --commit-filter ' if [ "$GIT_AUTHOR_NAME" = "Sharwan Joram" ]; then GIT_AUTHOR_NAME="Sharwan Joram"; GIT_AUTHOR_EMAIL="[email protected]"; git commit-tree "$@"; else git commit-tree "$@"; fi' HEAD Unfortunatly I had to delete the entire devel branch on sf.net and repush from my local copy. git push origin :devel git push origin [Less]

Its been a long time but there are finally some new features and enhancements coming to OpenNOP. They are currently working but in a pretty rough state. There are lots of debug messages that need to be removed and some general code cleanup but here ... [More] is what you will see soon. IPC channel between OpenNOP neighbors. IPC has crude support for HMAC authentication and AES encryption. OpenNOP neighbors in a group is called a "Domain". OpenNOP Auto-Detection now uses a process I call NOD (Network Optimizer Detection). There is an RFC draft I am working on in the code now. OpenNOP Auto-Detection no longer injects IP address of OpenNOP appliance into TCP segments. This could be viewed as a data leak and so it now uses a sudo-random 32-bit ID. This ID is automatically negotiated between OpenNOP neighbors in the IPC negotiation. OpenNOP Auto-Detection requires that the source and destination OpenNOP appliances be inside the same Domain and are able to communicate with the IPC. There are some minor enhancements that got mixed in with all this too. There are some minor enhancements to the logging system that allow logging to be turn on/off in runtime. Some could find there way into this update. [Less]

Its been a long time but there are finally some new features and enhancements coming to OpenNOP. They are currently working but in a pretty rough state. There are lots of debug messages that need to be removed and some general code cleanup but ... [More] here is what you will see soon. IPC channel between OpenNOP neighbors. IPC has crude support for HMAC authentication and AES encryption. OpenNOP neighbors in a group is called a "Domain". OpenNOP Auto-Detection now uses a process I call NOD (Network Optimizer Detection). There is an RFC draft I am working on in the code now. OpenNOP Auto-Detection no longer injects IP address of OpenNOP appliance into TCP segments. This could be viewed as a data leak and so it now uses a sudo-random 32-bit ID. This ID is automatically negotiated between OpenNOP neighbors in the IPC negotiation. OpenNOP Auto-Detection requires that the source and destination OpenNOP appliances be inside the same Domain and are able to communicate with the IPC. There are some minor enhancements that got mixed in with all this too. There are some minor enhancements to the logging system that allow logging to be turn on/off in runtime. Some could find there way into this update. [Less]

The folks from Center for Open Middleware (COM) of Universidad Politecnica de Madrid in SPAIN have created a modified version of OpenNOP that includes a dictionary based compression algorithm for deduplication. https://github.com/centeropenmiddleware/solowan

The folks from Center for Open Middleware (COM) of Universidad Politecnica de Madrid in SPAIN have created a modified version of OpenNOP that includes a dictionary based compression algorithm for deduplication. https://github.com/centeropenmiddleware/solowan

Hi Justin, This sounds great a tool. Can we publish a weekly report of the results somewhere in this forum and we can target those in our milestones too.

Hi Justin, This sounds great a tool. Can we publish a weekly report of the results somewhere in this forum and we can target those in our milestones too.