Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

iperf3 test cause "panic: message too long" #13

Open
sbilly opened this issue Mar 29, 2019 · 1 comment
Open

iperf3 test cause "panic: message too long" #13

sbilly opened this issue Mar 29, 2019 · 1 comment

Comments

@sbilly
Copy link

sbilly commented Mar 29, 2019

I'v connected to veth NICs by using 'https://github.com/newtools/zsocket/blob/master/examples/2simplebridge.go'

And iperf3 test cause "panic: message too long".

66 66
67 67
66 66
70 70
66 66
123 123
66 66
67 67
74 74
74 74
66 66
103 103
66 66
66 66
68 68
66 66
7306 7306
panic: message too long

goroutine 19 [running]:
main.main.func1(0xc00009e740, 0xc01c8a1c8a)
        /root/tmp/xxx/main.go:28 +0x1dd
github.com/newtools/zsocket.(*ZSocket).Listen(0xc0000c6000, 0xc000082480, 0xc000070300, 0xc0000c6070)
        /root/.go/src/github.com/newtools/zsocket/zsocket.go:307 +0x1d3
created by main.main
        /root/tmp/xxx/main.go:18 +0x129
@sbilly
Copy link
Author

sbilly commented Mar 31, 2019

It occurs when zsocket send or recived a packet bigger than MTU.

https://en.wikipedia.org/wiki/TCP_segmentation_offloading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant