The quic simulation stops at 302s.

[lishuo3331]

I use the last version quic in ns-3.32, when i run the quic-tester, the simulation stoped at 302s. Some information about links: serverApps.Stop (Seconds (400.0)) clientApps.Stop (Seconds (500.0));
Log:

+294.871752002s 0 QuicL5Protocol:DisgregateRecv(): fragment size 0
+294.871752002s 0 QuicSocketRxBuffer:Size(0x55bc1779d8e0)
+294.871752002s 0 QuicL5Protocol:CreateStream(0x55bc17879d80, 3, 2)
+294.871752002s 0 QuicL5Protocol:DispatchRecv(): Receiving frame on stream 0 trigger socket
+302.028264004s 1  [node 1] QuicL4Protocol:SendPacket(0x55bc1778d170, 0x55bc1788ad40)
+302.028264004s 1  [node 1] QuicL4Protocol:SendPacket(): 0x55bc1778d170 sending seq 149 data size 41
+302.028264004s 1  [node 1] QuicL4Protocol:SendPacket(): Sending Packet Through UDP Socket
+302.028264004s 1  [node 1] QuicL4Protocol:UdpSend(0x55bc1778d170, 0x55bc1788c840)
+302.030393604s 0  [node 0] QuicL4Protocol:ForwardUp(0x55bc17776e60)
+302.030393604s 0  [node 0] QuicL4Protocol:ForwardUp(): Receiving packet on UDP socket
+302.030393604s 0  [node 0] QuicL4Protocol:ForwardUp(): 0
+302.030393604s 0  [node 0] QuicL4Protocol:ForwardUp(): 0x55bc17776e60 waking up handler of socket 0x55bc178894d0
+302.030393604s 0  [node 0] QuicL4Protocol:SendPacket(0x55bc17776e60, 0x55bc178894d0)
+302.030393604s 0  [node 0] QuicL4Protocol:SendPacket(): 0x55bc17776e60 sending seq 101 data size 36
+302.030393604s 0  [node 0] QuicL4Protocol:SendPacket(): Sending Packet Through UDP Socket
+302.030393604s 0  [node 0] QuicL4Protocol:UdpSend(0x55bc17776e60, 0x55bc17889b30)
+302.032515204s 1  [node 1] QuicL4Protocol:ForwardUp(0x55bc1778d170)
+302.032515204s 1  [node 1] QuicL4Protocol:ForwardUp(): Receiving packet on UDP socket
+302.032515204s 1  [node 1] QuicL4Protocol:ForwardUp(): 0
+302.032515204s 1  [node 1] QuicL4Protocol:ForwardUp(): 0x55bc1778d170 waking up handler of socket 0x55bc1788ad40
+302.071752002s 0 QuicSocketTxScheduler:GetNewSegment(0x55bc17784e70, 1460)
+302.071752002s 0 QuicSocketTxScheduler:GetNewSegment(): Update: remaining App Size 0, object size 0
+302.071752002s 0 QuicL5Protocol:GetMaxData(0x55bc17879d80)
+302.071752002s 0 QuicSocketTxScheduler:GetNewSegment(0x55bc17784e70, 1460)
+302.071752002s 0 QuicSocketTxScheduler:GetNewSegment(): Update: remaining App Size 0, object size 0
+302.071752002s 0 QuicL5Protocol:GetMaxData(0x55bc17879d80)
+392.028264004s 1  [node 1] QuicL4Protocol:RemoveSocket(0x55bc1778d170)
+392.028264004s 1 QuicL4Protocol:~QuicUdpBinding(0x55bc1788b160)
+400.000000000s 1 QuicEchoServerApplication:StopApplication(): ##########  QUIC Echo Server STOP at time 400 ##########
+400.000000000s 1 QuicEchoServerApplication:StopApplication(0x55bc17805f80)
+400.000000000s 1  [node 1] QuicL4Protocol:RemoveSocket(0x55bc1778d170)
+400.000000000s 1 QuicL4Protocol:~QuicUdpBinding(0x55bc177a99a0)
+400.000000000s 1  [node 1] QuicL4Protocol:RemoveSocket(): 0x55bc1778d170 Closing all the cloned sockets
+500.000000000s 0 QuicEchoClientApplication:StopApplication(): ##########  QUIC Echo Client STOP at time 500 ##########
+500.000000000s 0 QuicEchoClientApplication:StopApplication(0x55bc17826820)

[utkarsh912]

hi, can you share your email, i want to discuss about this project. it will help me to complete my major prjecct.
utakrsh Tamrakar
[email protected]
NFSU Gandhinagar