Hi Christian, thank you for suggestions!
Here, the tcp_terminal is nagging about a missing policy configuration for a client session request labeled 'vfs -> '. Thus, it may be good to provide one in the <config> of tcp_terminal. Let's look into tcp_terminal.run.
...
The configuration defines a policy for test-terminal_echo that can easily be changed to the demands of your scenario.
<policy label_prefix="vfs" port="<desired port>"/>
or even
<policy label="vfs -> " port="<desired port>»/>
it helps to get rid of message, but does not help to solve the problem of attachment of bash to tcp_terminal (failed to create <terminal> VFS node below) I want something like nic(tcp with port 8888) -> tcp_terminal -> bash
If I follow your suggestion then it seems that I mentioned 2 separate port: <policy label_prefix="vfs" port=«8888»/> <policy label_prefix=«/bin/bash" port="8888"/> while in my idea I probably need only one, not clear the meaning of second mention of port...
result log is: [init] child "timer" announces service "Timer" [init] child "rtc_drv" announces service "Rtc" [init] child "nic_router" announces service "Nic" [init] child "nic_router" announces service "Uplink" Warning: invalid signal-context capability [init -> terminal] lwIP Nic interface down [init -> terminal] --- TCP terminal started --- [init] child "terminal" announces service "Terminal" [init -> vfs] Error: Terminal-session creation failed (ram_quota=10240, cap_quota=3, label="") [init -> vfs] Error: failed to create <terminal> VFS node [init] child "vfs" announces service "File_system" [init] child "vfs_rom" announces service "ROM" [init -> /bin/bash] 0x1000000 .. 0x10ffffff: linker area [init -> /bin/bash] 0x40000000 .. 0x4fffffff: stack area [init -> /bin/bash] 0x50000000 .. 0x601b1fff: ld.lib.so [init -> /bin/bash] 0x10e2c000 .. 0x10ffffff: libc.lib.so [init -> /bin/bash] 0x10d87000 .. 0x10e2bfff: vfs.lib.so [init -> /bin/bash] 0x10d45000 .. 0x10d86fff: libm.lib.so [init -> /bin/bash] 0x10d3d000 .. 0x10d44fff: posix.lib.so [init -> terminal] Warning: read blocked until lwIP interface is ready [init -> terminal] lwIP Nic interface up address=10.0.3.2 netmask=255.255.255.0 gateway=10.0.3.1 [init -> terminal] listening on port 8888... [init -> terminal] connection established
I am able to connect telnet localhost 5555 -but no command can be executed and log say that bind to port 8888 failed right after telnet. [init -> terminal] listening on port 8888... [init -> terminal] connection established [init -> /bin/bash] Error: no plugin found for fcntl(3) [init -> /bin/bash] Error: no plugin found for fcntl(4) [init -> /bin/bash] Error: no plugin found for fcntl(5) [init -> /bin/bash] Error: no plugin found for fcntl(6) [init -> /bin/bash] Error: no plugin found for fcntl(7) [init -> /bin/bash] Error: no plugin found for fcntl(8) [init -> /bin/bash] Error: no plugin found for fcntl(9) [init -> /bin/bash] Error: no plugin found for fcntl(10) [init -> /bin/bash] Error: no plugin found for fcntl(11) [init -> /bin/bash] Error: no plugin found for fcntl(12) [init -> /bin/bash] Error: no plugin found for fcntl(13) [init -> /bin/bash] Error: no plugin found for fcntl(14) [init -> /bin/bash] Error: no plugin found for fcntl(15) [init -> /bin/bash] Error: no plugin found for fcntl(16) [init -> /bin/bash] Error: no plugin found for fcntl(17) [init -> /bin/bash] Error: no plugin found for fcntl(18) [init -> /bin/bash] Error: no plugin found for fcntl(19) [init -> terminal] Error: bind to port 8888 failed Kernel: Bad memory access (signum=7), see Linux kernel log for details
I am stuck a bit and move to ssh.run example, integrating it with toolchain test. here I have to setup ssh_server and use ssh client from outside instead of telnet.
In this moment it works somehow and I am trying to force toolchain to work inside genode.
Sincerely, Alexander