I did some tests and sometimes it works and sometimes (the most
times...) it gives the error...
The error usually appears when I give the command
nsh> ifconfig
or
nsh> renew eth0
but not all the times. I think that it can be a problem with memory
sizes; I'll try more investigations
BR
Roberto
NuttShell (NSH) NuttX-12.4.0-RC0
nsh> ping 192.168.1.155
PING 192.168.1.155 56 bytes of data
56 bytes from 192.168.1.155: icmp_seq=0 time=38.0 ms
56 bytes from 192.168.1.155: icmp_seq=1 time=62.0 ms
56 bytes from 192.168.1.155: icmp_seq=2 time=104.0 ms
56 bytes from 192.168.1.155: icmp_seq=3 time=124.0 ms
56 bytes from 192.168.1.155: icmp_seq=4 time=62.0 ms
56 bytes from 192.168.1.155: icmp_seq=5 time=84.0 ms
56 bytes from 192.168.1.155: icmp_seq=6 time=12.0 ms
56 bytes from 192.168.1.155: icmp_seq=7 time=46.0 ms
56 bytes from 192.168.1.155: icmp_seq=8 time=75.0 ms
56 bytes from 192.168.1.155: icmp_seq=9 time=106.0 ms
10 packets transmitted, 10 received, 0% packet loss, time 10010 ms
rtt min/avg/max/mdev = 12.000/71.300/124.000/32.655 ms
nsh> ifconfig
eth0 Link encap:Ethernet HWaddr 52:d3:8e:aa:5d:41 at UP mtu 1486
inet addr:192.168.1.251 DRaddr:192.168.1.1 Mask:255.255.255.0
lo Link encap:Local Loopback at RUNNING mtu 1518
inet addr:127.0.0.1 DRaddr:127.0.0.1 Mask:255.0.0.0
IPv4 TCP UDP ICMP
Received 000c 0000 0002 000a
Dropped 0000 0000 0000 0000
IPv4 VHL: 0000 Frg: 0000
Checksum 0000 0000 0000 ----
TCP ACK: 0000 SYN: 0000
RST: 0000 0000
Type 0000 ---- ---- 0000
Sent 000c 0000 0002 000a
Rexmit ---- 0000 ---- ----
On 2/6/24 16:55, Gregory Nutt wrote:
The network monitor is part of apps/netutils/netinit so it is not a
part of NSH. NSH can automatically perform the network initialization
if so configured and which, optionally, starts the network monitor
thread. But the logic is not architecturally a part of NSH nor does
it depend on N SH.
On 2/6/2024 9:32 AM, Nathan Hartman wrote:
On Tue, Feb 6, 2024 at 8:45 AM Sebastien Lorquet <sebast...@lorquet.fr>
wrote:
However, the default network configuration provided in NuttX
examples is
cumbersome and too much linked with NSH
It can work for simple tests and demos, but you will have to write a
proper network management daemon if you plan to use more than one
network app.
It would be a nice thing if the network management daemon could be
factored
out of NSH so that boards that don't run NSH could have the same network
management without implementing it again.
Cheers
Nathan
