芋圆源钰
芋圆源钰
This guy hasn't written anything yet

注册于 1 year ago

回答
1
文章
0
关注者
1

哪位兄弟了解到官网 iperf测试UDP TX测试的-b带宽参数是否已经支持了呢?

查了一周,还是老老实实跟代码发先就是一个宏的问题.

+++ b/source/ekernel/subsys/net/rt-thread/net_tools/netutils-master/libcurl2rtt-latest/curl/curl_config.h
@@ -30,7 +30,7 @@
 #define   HAVE_FCNTL_O_NONBLOCK  1
 
 /* Define to 1 if you have the gethostbyname_r function. */
-#define   HAVE_GETHOSTBYNAME_R  1
+//#define   HAVE_GETHOSTBYNAME_R  1

注释后测试已正常:

msh />curl --verbose -k --capath ./ [url=https://www.rt-thread.com/service/rt-thread.txt]https://www.rt-thread.com/service/rt-thread.txt[/url]  
* timeout on name lookup is not supported
*   Trying 118.31.15.152:443...
* TCP_NODELAY set
* Connected to [url=http://www.rt-thread.com]www.rt-thread.com[/url] () port 443 (#0)
* mbedTLS: Connecting to [url=http://www.rt-thread.com:443]www.rt-thread.com:443[/url]
* mbedTLS: Set min SSL version to TLS 1.0
* mbedTLS: Handshake complete, cipher is TLS-ECDHE-RSA-WITH-AES-128-GCM-SHA256
* Dumping cert info:
* cert. version     : 3
* serial number     : 06:43:FD:59:D0:4D:C8:94:2F:54:BA:AF:82:55:72:0E
* issuer name       : C=US, O=DigiCert Inc, OU=www.digicert.com, CN=Encryption Everywhere DV TLS CA - G1
* subject name      : CN=www.rt-thread.com
* issued  on        : 2020-06-21 00:00:00
* expires on        : 2021-06-22 12:00:00
* signed using      : RSA with SHA-256
* RSA key size      : 2048 bits
* basic constraints : CA=false
* subject alt name  : [url=http://www.rt-thread.com]www.rt-thread.com[/url], rt-thread.com
* key usage         : Digital Signature, Key Encipherment
* ext key usage     : TLS Web Server Authentication, TLS Web Client Authentication

* SSL connected
> GET /service/rt-thread.txt HTTP/1.1
> Host: [url=http://www.rt-thread.com]www.rt-thread.com[/url]
> User-Agent: curl/7.67.0-DEV
> Accept: */*
> 
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Server: nginx/1.10.3 (Ubuntu)
< Date: Wed, 01 Jul 2020 07:50:41 GMT
< Content-Type: text/plain
< Content-Length: 267
< Connection: keep-alive
< Last-Modified: Tue, 18 Sep 2018 03:55:48 GMT
< ETag: "10b-5761d43d95900"
< Accept-Ranges: bytes
< Vary: Accept-Encoding
< 
RT-Thread is an open source IoT operating system from China, which has strong scalability: from a tiny kernel running on a tiny core, for example ARM Cortex-M0, or Cortex-M3/4/7, to a rich feature system running on MIPS32, ARM Cortex-A8, ARM Cortex-A9 DualCore etc.

发现一个新问题:
直接用ip地址代替rt-thread.com出现301返回码?

msh />curl --verbose -k --capath ./ [url=https://118.31.15.152/service/rt-thread.txt]https://118.31.15.152/service/rt-thread.txt[/url]  
* timeout on name lookup is not supported
*   Trying 118.31.15.152:443...
* TCP_NODELAY set
* Connected to 118.31.15.152 () port 443 (#0)
* mbedTLS: Connecting to 118.31.15.152:443
* mbedTLS: Set min SSL version to TLS 1.0
* mbedTLS: Handshake complete, cipher is TLS-ECDHE-RSA-WITH-AES-256-GCM-SHA384
* Dumping cert info:
* cert. version     : 3
* serial number     : 09:2F:6D:AE:96:EC:D7:D0:24:55:D2:F5:64:20:50:23
* issuer name       : C=US, O=DigiCert Inc, OU=www.digicert.com, CN=RapidSSL RSA CA 2018
* subject name      : CN=*.rt-thread.org
* issued  on        : 2020-06-05 00:00:00
* expires on        : 2021-06-05 12:00:00
* signed using      : RSA with SHA-256
* RSA key size      : 2048 bits
* basic constraints : CA=false
* subject alt name  : *.rt-thread.org, rt-thread.org
* key usage         : Digital Signature, Key Encipherment
* ext key usage     : TLS Web Server Authentication, TLS Web Client Authentication

* SSL connected
> GET /service/rt-thread.txt HTTP/1.1
> Host: 118.31.15.152
> User-Agent: curl/7.67.0-DEV
> Accept: */*
> 
* Mark bundle as not supporting multiuse
< HTTP/1.1 301 Moved Permanently
< Server: nginx/1.10.3 (Ubuntu)
< Date: Wed, 01 Jul 2020 07:43:17 GMT
< Content-Type: text/html
< Content-Length: 194
< Connection: keep-alive
< Location: [url=https://www.rt-thread.org/service/rt-thread.txt]https://www.rt-thread.org/service/rt-thread.txt[/url]
< Strict-Transport-Security: max-age=1800; includeSubdomains; preload
< 

301 Moved Permanently

301 Moved Permanently
nginx/1.10.3 (Ubuntu)


* Connection #0 to host 118.31.15.152 left intact

aozima 发表于 2020-6-18 15:15
楼主这里好像是dns解析不出来,还没到证书那阶段。


是的呢,直接ping www.rt-thread.com都能正常解析.
不清楚是否这个包的那个配置有问题.还请指教.

在qemu中测试,证书DIGICERT_ROOT_CA.cer放到 ./ 目录下调用 curl --verbose -k --capath ./ https://www.r ...

谢谢你的回复,
1.我这里是DNS解析不了.
2.你图里面执行时加了-k参数是跳过证书了额.

aozima 发表于 2020-6-18 09:24
当https的server有多个域名的时候,需要SNI传输域名才行,所以你直接用IP访问,他就不知道你需要访问哪个域 ...


谢谢!
看来还是逃不过哦,我得先把DNS服务调通.
大神知道下面这个是什么情况吗?
移植的libcurl2rtt包,dns服务总是过不了,直接ping www.rt-thread.com都能通.
msh />curl --verbose -k --capath ./ https://www.rt-thread.com/service/rt-thread.txt
* timeout on name lookup is not supported
* Curl_ipv4_resolve_r failed for www.rt-thread.com
* Couldn't resolve host 'www.rt-thread.com'
* Closing connection 0
curl: (6) Couldn't resolve host 'www.rt-thread.com'

msh />ping www.rt-thread.com
60 bytes from 118.31.15.152 icmp_seq=0 ttl=49 time=60 ms
60 bytes from 118.31.15.152 icmp_seq=1 ttl=49 time=30 ms
60 bytes from 118.31.15.152 icmp_seq=2 ttl=49 time=30 ms
60 bytes from 118.31.15.152 icmp_seq=3 ttl=49 time=30 ms

Cheney_Chen 发表于 2018-10-27 12:21
[md]楼主你好,首先感谢你对 webclient 软件包的使用和支持,可以看到楼主花了很长时间和精力在软件包问题 ...


你好,我现在使用webclient时也遇到两个问题,还烦请赐教.
1.根据软件包中的文档介绍使用wget时,明明链接是http的.为什么还是会走https的流程.
msh />wget http://www.rt-thread.com /service/rt-thread.txt
[E/web] not support https connect, please enable webclient https configure!
[E/web.file] get file failed, wrong response: -1 (-0xFFFFFFFF).
msh />
2.配置了mebdtls作为加密方式,又出现如下问题.
[E/mbedtls.clnt] verify peer certificate fail....
[E/mbedtls.clnt] verification info: ! The certificate is not correctly signed by the trusted CA
! The certificate validity starts in the future
好像是证书不对?

还烦请赐教一下.谢谢.

你好,我在使用webclient自带的wget时遇到如下两个问题,麻烦帮忙看看.感激.
1.链接明明是http怎么提示需要enable https configure.
msh />wget /service/rt-thread.txt
[E/web] not support https connect, please enable webclient https configure!
[E/web.file] get file failed, wrong response: -1 (-0xFFFFFFFF).
msh />
2.配置了mebdtls作为加密方式,又出现如下问题.
[E/mbedtls.clnt] verify peer certificate fail....
[E/mbedtls.clnt] verification info: ! The certificate is not correctly signed by the trusted CA
! The certificate validity starts in the future
好像是证书不对?

楼主使用webclient时,https怎么测试的啊,
我尝试打开WEBCLIENT_USING_MBED_TLS宏后,
找不到文件
里面有些自定义的接口
mbedtls_client_init
mbedtls_client_read
mbedtls_client_write
mbedtls_client_context
mbedtls_client_connect
mbedtls_client_close
这些接口在也不是原生的mbedtls中的.

所以我现在一直编译不过.:'(
指导一下.谢谢

aozima 发表于 2020-5-21 18:15
依赖 mbedtls 包


是的呢,但是mbedtls包是没有这些接口的,应该是在tls_client.h中
不过没有找到这个文件.

你好,请问你的rtsp协议是适配rtthread的吗?我在最新的rtthread默认sdk中没有找到这个应用.
方便给一下吗?最近想学习一下.
谢谢!

你好,请问,你的rtsp协议源码从哪里来的啊.默认rtthread中没有,最近刚刚好想学习一下.
谢谢.

发布
问题