Bug 1105189
| Summary: | HTTP request generated by gPXE has wrong TCP flag (SYN & PSH) in first packet in session | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Przemyslaw Sztoch <psztoch> |
| Component: | gpxe | Assignee: | Alex Williamson <alex.williamson> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.5 | CC: | chayang, juzhang, michen, psztoch, qiguo, qzhang, virt-maint, xigao |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | gpxe-0.9.7-6.11.el6 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-10-14 08:06:32 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Przemyslaw Sztoch
2014-06-05 14:31:10 UTC
Przemyslaw, thank you for taking the time to enter a bug report with us. We appreciate the feedback and look to use reports such as this to guide our efforts at improving our products. That being said, we're not able to guarantee the timeliness or suitability of a resolution for issues entered here because this is not a mechanism for requesting support. If this issue is critical or in any way time sensitive, please raise a ticket through your regular Red Hat support channels to make certain it receives the proper attention and prioritization to assure a timely resolution. For information on how to contact the Red Hat production support team, please visit: https://www.redhat.com/support/process/production/#howto Przemyslaw, Can you please test whether the following package resolves this issue? http://people.redhat.com/~alwillia/bz1105189/gpxe-roms-qemu-0.9.7-6.10.aw1.el6.noarch.rpm This package is for testing purposes only. Alex, It is the fastest bug fix in my RHEL history ;-) HTTP works perfectly. Thanks a lot. Issue is resolved. (In reply to Przemyslaw Sztoch from comment #4) > Alex, > > It is the fastest bug fix in my RHEL history ;-) > > HTTP works perfectly. > > Thanks a lot. Issue is resolved. Thanks for testing! Fix included in gpxe-0.9.7-6.11.el6 Reproduce this bug with gpxe-roms-qemu-0.9.7-6.10.el6.noarch Steps as comment 6 Cli: # /usr/libexec/qemu-kvm -cpu host -rtc base=localtime,clock=host,driftfix=slew -M pc -nodefaults -nodefconfig -enable-kvm -name rhel6-64 -smp 4,cores=4,threads=1,sockets=1 -m 4G -boot menu=on -netdev tap,id=hostnet0,script=/etc/qemu-ifup -device e1000,netdev=hostnet0,id=net0,mac=52:54:00:01:1a:10 -vnc :10 -vga std -monitor stdio -S -device sga -serial stdio From the tcpdump reslult, capture the 1st package ... 01:07:06.562908 IP (tos 0x0, ttl 64, id 7, offset 0, flags [none], proto TCP (6), length 56) 10.66.10.247.1024 > 72.52.4.91.http: Flags [SP], cksum 0xf06d (correct), seq 784182161, win 4096, options [nop,nop,TS val 73266 ecr 0,mss 1460], length 0 ... Result: The first package shows it is set with SYN and PSH, so this bug is reproduced. Verify this bug with gpxe-roms-qemu-0.9.7-6.11.el6.noarch cli: # /usr/libexec/qemu-kvm -cpu host -rtc base=localtime,clock=host,driftfix=slew -M pc -nodefaults -nodefconfig -enable-kvm -name rhel6-64 -smp 4,cores=4,threads=1,sockets=1 -m 4G -boot menu=on -netdev tap,id=hostnet0,script=/etc/qemu-ifup -device e1000,netdev=hostnet0,id=net0,mac=52:54:00:01:1a:10 -vnc :10 -vga std -monitor stdio -S -device sga -serial stdio From the tcpdump reslult, capture the 1st package ... 01:24:24.664232 IP (tos 0x0, ttl 64, id 7, offset 0, flags [none], proto TCP (6), length 56) 10.66.10.247.1024 > 10.66.78.204.http: Flags [S], cksum 0x070b (correct), seq 1540886915, win 4096, options [nop,nop,TS val 92177 ecr 0,mss 1460], length 0 .... Result: The first package shows it is set with SYN only, so this bug is verified. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1574.html |