Using RPC in two different container
Hi, I just used hello-camkes-1 tutorial to send and receive a message between a client and an echo. My understanding is that both client and echo are in the same machine but different address. What changes do I need to make so that client and echo are in different machine? I have used docker for using seL4 environment. I was thinking about using container1 for client and container2 for echo and communicate between them. Is there any way I can do it by modifying the hello-camkes-1tutorial? If not, can anyone suggest a way to do it? Thanks! -- Regards' Shahnewaz Karim Sakib
"Shahnewaz" == Shahnewaz Sakib
writes:
Shahnewaz> I just used hello-camkes-1 tutorial to send and receive a Shahnewaz> message between a client and an echo. My understanding is Shahnewaz> that both client and echo are in the same machine but Shahnewaz> different address. This is correct. seL4 IPC and the CamKES connectors are for joining together components on a single host. The primary usecase for seL4 is securing systems on a single host. Shahnewaz> What changes do I need to make so that Shahnewaz> client and echo are in different machine? You'd need to set up a network stack, interface (e.g., ethernet) driver, and a communications protocol. Rumprun may be of some use here, as it has driver and network components. I heard someone was doing an MQTT implementation, but I can't remember who. Peter C -- Dr Peter Chubb Tel: +61 2 9490 5852 http://ts.data61.csiro.au/ Trustworthy Systems Group CSIRO's Data61
participants (2)
-
Chubb, Peter (Data61, Kensington NSW)
-
Shahnewaz Sakib