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
I'm on a Windows 10 machine that does not have an IPv6 internet connection. The host I'm trying to connect to advertises both A and AAAA records. It seems Vegeta is picking IPv6 network address much of the time, which results in errors.
I also downgraded to v12.11.0 and the above problem went away. Though, I now get a crash 50% of the time, which looks exactly like #649. 6fbe391 seems to have fixed the crashing if the order of IP addresses come in different orders, but it seems Vegeta will cache only the IPv6 address in some cases, which causes near 100% error rate.
The text was updated successfully, but these errors were encountered:
Version and Runtime
Version: v12.11.1
Commit: 6fbe391
Runtime: go1.20.8 windows/amd64
Date: 2023-10-02T09:05:14Z+0000
Expected Behaviour
attack to work
Actual Behaviour
Errors related to IPv6.
Steps to Reproduce
host.txt:
cat host.txt | vegeta attack -workers 1000 -rate 0 -max-workers 6000 -http2=false -keepalive=false -duration=30s
Additional Context
I'm on a Windows 10 machine that does not have an IPv6 internet connection. The host I'm trying to connect to advertises both A and AAAA records. It seems Vegeta is picking IPv6 network address much of the time, which results in errors.
I also downgraded to
v12.11.0
and the above problem went away. Though, I now get a crash 50% of the time, which looks exactly like #649. 6fbe391 seems to have fixed the crashing if the order of IP addresses come in different orders, but it seems Vegeta will cache only the IPv6 address in some cases, which causes near 100% error rate.The text was updated successfully, but these errors were encountered: