[BlueField] Unable to set TCP MD5SIG option on socket
Bug #1956238 reported by
Vladimir Sokolovsky
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-bluefield (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
$ grep TCP_MD5SIG /boot/config-
# CONFIG_TCP_MD5SIG is not set
Expected:
CONFIG_TCP_MD5SIG=y
tags: | added: patch |
Changed in linux-bluefield (Ubuntu Focal): | |
status: | New → Fix Committed |
Changed in linux-bluefield (Ubuntu): | |
status: | New → Invalid |
To post a comment you must log in.
This bug is awaiting verification that the linux-bluefield /5.4.0- 1026.29 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification- needed- focal' to 'verification- done-focal' . If the problem still exists, change the tag 'verification- needed- focal' to 'verification- failed- focal'.
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation how to enable and use -proposed. Thank you!