Quicr / old-quicrq

BSD 2-Clause "Simplified" License
4 stars 2 forks source link

Demo client usage #96

Closed clarkzjw closed 2 years ago

clarkzjw commented 2 years ago

I'm a little confused about how to use the demo program quicrq_app.

Following the README, I first run quicrq_app in server mode,

./quicrq_app -q qlog -c ./ca/ca-cert.pem -k ./ca/server-key.pem -p 4433 -w ./tests server

The tests folder contains video1_source.bin.

And run quicrq_app in client mode,

./quicrq_app client localhost d 4433 get:video1_source.bin:./tmp

and the client only shows

QUICRQ Version 0.22, Picoquic Version 1.04a
Waiting for packets.

In this case, I try to connect the client directly to the server and no relay node was set up. Is this the right syntax for scenarios? I'm confused by *{{'get'|'post'}':'<url>':'<path>[':'<log_path>]';'}.

Update: I also tried to add a relay like this:

./quicrq_app -c ./ca/ca-cert.pem -k ./ca/server-key.pem -p 4434 -w ./tests relay localhost s 4433

and let the client to connect to the relay:

./quicrq_app client localhost s 4434 get:video1_source.bin:./tmp
VidarHUN commented 1 year ago

Hi, I also have the same problem. I can run a server like this:

./quicrq_app -p 3000 -c certs/cert.pem -k certs/key.pem server
QUICRQ Version 0.30, Picoquic Version 1.1.8.1
Waiting for packets.

And the client:

./quicrq_app client 127.0.0.1 d 3000 get:tests/video1_source.bin:./tmp                         
QUICRQ Version 0.30, Picoquic Version 1.1.8.1
Waiting for packets.

What am I doing wrong?

clarkzjw commented 1 year ago

@VidarHUN You can check https://github.com/Quicr/quicrq/issues/104#issuecomment-1360082364

VidarHUN commented 1 year ago

Thanks for the quick response. I somehow missed that issue...