Oops, I spoke too soon. I did get an output line after a bunch of minutes: Received 50 buffers: 66.8 Kb (avg 1.3 Kb) in 101.00 Sec ( 0.6 > Kb/Sec) >
So maybe it's going very very slowly? -adam On Mon, Feb 10, 2020 at 12:19 PM Adam Feuer <a...@starcat.io> wrote: > Greg, > > I tried the IPv6 version you sent... It starts, but there's no further > output: > >> >> nsh> tcpclient >> Binding to IPv6 Address: 0000:0000:0000:0000:0000:0000:0000:0000 >> server: Accepting connections on port 5471 >> Connecting to IPv6 Address: 0000:0000:0000:0000:0000:0000:0000:0100 >> client: Connected >> server: Connection accepted -- receiving >> > > I'll try to get it working on IPv4. How do I turn on debug output? > > -adam > > > > On Mon, Feb 10, 2020 at 12:13 PM Gregory Nutt <spudan...@gmail.com> wrote: > >> >> > nsh> tcpclient >> > Binding to IPv6 Address: 0000:0000:0000:0000:0000:0000:0000:0000 >> > server: Accepting connections on port 5471 >> > Connecting to IPv6 Address: 0000:0000:0000:0000:0000:0000:0000:0100 >> > client: Connected >> > server: Connection accepted -- receiving >> > >> > Then nothing more. >> > >> > In this configuration, the server runs as a daemon on the same >> > platform. It is started by the client. But after that, they should >> > behave the same. >> > >> > NOTE that I have it set up to use IPv6 with the IPv6 loopback >> > address. IPv4 would probably be simpler to debug. >> > >> Well, it does look like it is sending TCP packets. I switched to IPv4 >> and enabled debug output. In the debug output I can see that it is >> sending and receiving TCP packets and that the TCP packets are being >> ACKed. But, for some reason, there is no printf output. I think TCP is >> working in this new configuration, but needs better debug output >> instrumentation. Although it seem to be working, there is nothing >> visible on the console. >> >> Can you take a look and see if you learn anything? >> >> >> > > -- > Adam Feuer <a...@starcat.io> > -- Adam Feuer <a...@starcat.io>
