search

litespeedtech / lsquic

LiteSpeed QUIC and HTTP/3 Library
MIT License
1.54k stars 334 forks source link

echo_client doesn't receives path challenge frames #357

Open wenlongkang opened 2 years ago

wenlongkang commented 2 years ago

Dear author First of all thank you for your contribution to the open source. I'm going through this project to learn about quic's connection migration, but I'm having some issues.It seems that no connection migration is taking place between the two endpoints. I use the latest master version lsquic,and wireshark version is 3.4.8 (v3.4.8-0-g3e1ffae201b8). I runs a echo_client on my MacOS which ip address is 10.222.101.223,and a echo_server on a public server which ip address is 154.85.48.113, both programs run uninterrupted,and quic packets can be captured through wireshark which run on my MacOS. then I modify the ip address of MacOS by setting a static ip 10.222.101.225, however,wireshark didn't capture path challenge frames,some packets are captured but showing "Unknown QUIC connection. Missing Initial Packet or migrated connection?". my question is why the client not receives path challenge frames? Thanks very much.

Best regards！

image

wenlongkang commented 2 years ago

I found the reason, I need to add the tls log to wireshark to see the PATH_CHALLENGE frame after decryption.please close this issues. image

wxie7 commented 2 years ago

I found the reason, I need to add the tls log to wireshark to see the PATH_CHALLENGE frame after decryption.please close this issues. image

Hello, when did you change the IP address of the client? between two carriage returns? Can I change the address inside the code, such as changing a port for the client?