Warning: Cannot modify header information - headers already sent by (output started at /home/content/41/9406341/html/release14_org/wp-includes/class-wp.php:1) in /home/content/41/9406341/html/release14_org/wp-includes/feed-rss2.php on line 8
RELEASE14 http://www.release14.org Release 14 ORG Tue, 03 Jan 2017 19:09:12 +0000 en-US hourly 1 https://wordpress.org/?v=4.7.3 121307428 pMINK finally on GitHub http://www.release14.org/blog/pmink-finally-on-github/ http://www.release14.org/blog/pmink-finally-on-github/#respond Tue, 03 Jan 2017 08:41:34 +0000 http://www.release14.org/?p=882 Continue Reading]]>

Happy new year !!!

It’s been a while since I wrote something on this blog, and I hope that this prolonged absence will be forgiven by the time you’ve read this article.

When we first started this project (website, company, etc.) almost 5 years ago, our plans and priorities were still in the making and we had to make slight adjustments on every
step of the way. Most of you will probably criticize us for not keeping our word and releasing the code to Open Source years ago, but keeping both the project and the company
alive is a task not short of problems and obstacles. The biggest issue we had from the very beginning was the lack of testing environment; unlike most open source projects which
can be cloned and tested by virtually anyone, pMINK MNO requires access to a core network of mobile operator in order for all the test cases to be properly executed. Needless to
say, that sort of access is not easily obtainable and requires effort from both sides. I am happy to inform you that for the better part of last year, pMINK MNO has been properly
tested and benchmarked in production environment and most of critical bugs were fixed to give way to system stability.

Another major obstacle and an ever lasting problem is system documentation. For the moment, there is a general overview of all major components comprising the pMINK MNO, and a more  detailed documentation for FGN (openSMSF). The plan for this year is to release separate manuals for both Signal Transfer Point (STP) and Signalling Gateway Node (SGN).

After this short summary of our past activities and plans for the future, here comes the most important piece of news: pMINK MNO source code  is now available on GitHub.

Lawful Interception (openLI) components will be released as soon as I’m finished with the Makefiles and some other adjustments; pMINK GitHub repository will then be updated with openLI source code. Regarding documentation, we have also prepared a user’s manual (usable but not completely finished) for openLI which will be made available along with the source code.

]]>
http://www.release14.org/blog/pmink-finally-on-github/feed/ 0 882
New team member http://www.release14.org/blog/new-team-member/ Mon, 08 Oct 2012 10:05:44 +0000 http://www.release14.org/?p=739 Hi Everyone,

Release14 Team just got bigger. We have been looking for a way to incorporate Danijel to our core team for some time now. We are certain his expertise in Encryption, SS7 and IP networking will come in very handy.

Stay tuned,
Josip & R14

]]>
739
openLI might change the game a bit… http://www.release14.org/blog/openli-australia-game-change/ Wed, 19 Sep 2012 10:21:24 +0000 http://www.release14.org/?p=713 Continue Reading]]> Hi Everyone,

we just read an interesting article on ZDNet about Lawful Interception in Australia (first part is about Huawei), but here comes the interesting part:

“The Australian Mobile Telecommunications Association and the Communications Alliance said in a joint submission that any costs associated with the implementation of data retention, and other proposals that impact on telecommunications providers, should be minimised to avoid that cost being passed onto consumers. The groups estimate that the cost of data retention could be in the range of “tens to hundreds of millions of dollars”.

“If source and destination IP addresses were required to be included, setting up technology to capture this information would cost between AU$500 million and AU$700 million, the groups estimated, and the addition of a single data element could increase this figure by tens of millions of dollars.””

It looks like interesting times are upon us and hopefully there is a chance to change the monopoly game a bit.

Stay tuned,

Josip & R14

Whole article can be found here.

]]>
713
Release14 in Web-u.ME http://www.release14.org/blog/release14-in-web-u-me/ Mon, 17 Sep 2012 21:35:49 +0000 http://www.release14.org/?p=704 Hello everybody!

We have been chosen to attend a conference in Montenegro where we will present R14 to the public and potentially win a sponsored entry to TechCrunch Disrupt in May, 2013.

You can see more info HERE!

Damir & R14

]]>
704
Wireshark plugin for R14P http://www.release14.org/blog/wireshark-plugin-for-r14p/ Tue, 14 Aug 2012 13:30:57 +0000 http://www.release14.org/?p=637

Hello again!

We have finished our first alpha release of R14P plugin for Wireshark! Since R14P has been registered with IANA, we will do our best to have it included in the next official version of Wireshark.

Stay tuned,
Damir & R14

]]>
637
Support Release14 http://www.release14.org/blog/support-release14/ Sat, 11 Aug 2012 20:22:04 +0000 http://www.release14.org/?p=629 Hi everybody!

We have just added a donation button on our website. Support Release14 and our projects by making a donation.

Sincerely Yours,
Release14 Team

]]>
629
R14P Implementation http://www.release14.org/blog/r14p-implementation/ Sun, 05 Aug 2012 17:01:00 +0000 http://www.release14.org/?p=609 Continue Reading]]> Hi everybody

Here’s a little update on the latest developments. At the moment, we are working on R14P part of Project MINK, starting from connection management and low level stuff. Most of the actual code is contained in R14PSession class, which should be the main starting point for potential contributors and/or plugin developers. All SCTP and R14P logic and thread handling will be completely transparent and event driven. Here is a simple example of basic R14P session initialization and NEW_CLIENT callback event notification.

Cheers,
Damir and R14

#include <iostream>
#include <sctp.h>
#include <r14p.h>


class TestCallback : public r14p::R14PCallbackMethod {
public:
	void run(r14p::R14PCallbackArgs* args) {
		if(args != NULL){
			r14p::R14PClient* client = (r14p::R14PClient*)args->args;
			std::cout	<< "new_client_callback: "
						<< client->get_end_point_address()
						<< ":"
						<< client->get_end_point_port()
						<< std::endl;

		}

	}
};


int main(){
	// start R14P session
	r14p::R14PSession* r14ps = r14p::init_session();
	TestCallback tcb;
	// set callback for NEW_CLIENT event
	r14ps->set_callback(r14p::R14P_CB_NEW_CLIENT, &tcb);
	// accept connections (server mode)
	r14ps->start_server(NULL, 10000);
	// connect to end point
	r14p::R14PClient* r14p_client = r14ps->connect("127.0.0.1", 10000, 16, NULL, 0);
	// disconnect client
	r14p_client->disconnect();
	// remove client, free memory
	r14ps->remove_client(r14p_client);
	// stop server
	r14ps->stop_server();
	// destroy session, free memory
	r14p::destroy_session(r14ps);


	return 1;

}
]]>
609
R14P preview http://www.release14.org/blog/r14p-preview/ Wed, 18 Jul 2012 13:01:05 +0000 http://www.release14.org/?p=601 Continue Reading]]> Greeting earthlings!

Among other things we are currently working on, R14P is one of the most important components of pMINK platform. It is widely used as a main communication channel between various pMINK daemons and external plugins. The protocol itself is defined using ASN.1 syntax notation and transmitted in BER encoding. We are also preparing to release a Wireshark dissector plugin for R14P in near future.

R14P draft

Cheers,
R14 Team

]]>
601
pMINK CLI http://www.release14.org/blog/pmink-cli/ Wed, 27 Jun 2012 20:00:35 +0000 http://www.release14.org/?p=575 Continue Reading]]> Project MINK gets a brand new Command Line Interface (CLI)

Hi everybody!

After some careful consideration and extensive thinking, we have decided not to use any third party CLI libraries or tools for mink’s command line interface. Our brand new CLI offers an extremely flexible and intuitive approach for system wide configuration and administration. It is highly structured and relies heavily on its TAB activated auto-complete feature. Our inspiration for this particular part of project MINK comes from both Vyatta and Cisco command line interfaces. Having had the opportunity to work with the mentioned systems, we tried to combine the best of both worlds to achieve a highly natural and efficient user interface.

P.S.
This sreenshot does not include any actual commands.

]]>
575
Partnership with NTOP.org http://www.release14.org/blog/partnership-with-ntop-org/ Tue, 12 Jun 2012 12:18:47 +0000 http://www.release14.org/?p=565 Continue Reading]]> Release14 team is proud to announce our first partnership with NTOP.org

Ntop is a developer of open-source traffic monitoring solutions running on commodity hardware. Its portfolio includes Linux packet capture acceleration including virtual machine support as well as  packet-to-disk and packet-to-NetFlow probes. Ntop also provides solutions for 10 Gbit wire rate RX/TX, IDS/IPS packet capture/transmission accelerators, and web-based packet and flows collectors.

Ntop started as an open source project in 1998 whose goal was to create a simple yet effective web-based traffic monitoring platform. Many things have changed since then, including the nature of the traffic being analyzed, operating systems running on PCs, and the type of users. Ntop has changed as well, and from a single-project centric effort, have evolved into a full fledged research company whose goal is still the original one. Namely innovate in network monitoring using commodity hardware and open-source operating systems.

]]>
565