You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 20, 2020. It is now read-only.
Hi,
Whenever I send (ipv6) packets of size > 56Bytes (well within tunnel MTU of 1500 Bytes) to tun_echo example, I receive the contents echo'ed back in 2 or more packets. ep.Read() returns data of size not more than 56Bytes per call.
Any settings/configuration on endpoint that can give me the entire TCP payload in a single call to Read() ?
running it on Ubuntu 16.04
thanks,
The text was updated successfully, but these errors were encountered:
Can you include a packet trace? When you say send packets, I assume you mean you're using ep.Write? (I'm just wondering if maybe there's a new connection and you're looking at the end of the handshake?)
the payload of length 506 (packet #4) that is sent from 192.168.11.1 -> 192.168.11.11 is being echo'ed back in three different packets of sizes 76 (packet #6), 256 (packet #8), 174 (packet #10).
I use netcat to send messages to the echo example in netstack.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
Whenever I send (ipv6) packets of size > 56Bytes (well within tunnel MTU of 1500 Bytes) to tun_echo example, I receive the contents echo'ed back in 2 or more packets.
ep.Read()
returns data of size not more than 56Bytes per call.Any settings/configuration on endpoint that can give me the entire TCP payload in a single call to Read() ?
running it on Ubuntu 16.04
thanks,
The text was updated successfully, but these errors were encountered: