litespeedtech / litespeedtech/lsquic

echo_client doesn't receives path challenge frames

Open
#357 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

question
Dominant language
C
Stars
1.9k
Forks
397
Avg merge
2d 22h
Merged PRs (30d)
8

Description

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](https://user-images.githubusercontent.com/8955753/152778247-628876e3-135c-4cd0-bfcf-de0196cc6e40.png)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the reported connection-migration scenario with echo_client and echo_server, using the stated address change and Wireshark capture. Inspect whether path challenge frames are generated or received and compare the packets labeled "Unknown QUIC connection"; done means identifying the cause or documenting a confirmed implementation defect.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.