Hello Alexander,
please find my remarks inline below.
On Mon, Jan 10, 2022 at 15:45:43 CET, Alexander Tormasov via users wrote:
I think that I can adopt scenario of GUI based terminal implementation (taken from bash.run) by replacement of terminal -> tcp_terminal, and then it does not work. main problem is here [init -> tcp_terminal] lwIP Nic interface down [init -> tcp_terminal] --- TCP terminal started --- [init] child "tcp_terminal" announces service "Terminal" … [init -> nic_drv] MAC address 52:54:00:12:34:56 [init -> tcp_terminal] Warning: no policy defined for label 'vfs -> '
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.
<start name="tcp_terminal" caps="200"> <resource name="RAM" quantum="8M"/> <provides> <service name="Terminal"/> </provides> <config> <policy label_prefix="test-terminal_echo" port="8888"/> <vfs> <dir name="dev"> <log/> </dir> <dir name="socket"> <lwip dhcp="yes"/> </dir> <dir name="pipe"> <pipe/> </dir> </vfs> <libc stdout="/dev/log" socket="/socket" pipe="/pipe"/> </config> <route> <service name="Nic"> <child name="nic_router"/> </service> <any-service> <parent/> <any-child/> </any-service> </route> </start>
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>"/>
I hope this helps.
Regards