| Summary: | peth0: received packet with own address as source address | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Qixiang Wan <qwan> | ||||
| Component: | xen | Assignee: | Michal Novotny <minovotn> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 5.7 | CC: | areis, jentrena, jzheng, mrezanin, mshao, pbonzini, xen-maint | ||||
| Target Milestone: | rc | Keywords: | Regression | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | xen-3.0.3-126.el5 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-07-21 09:15:34 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Qixiang Wan
2011-03-14 09:34:12 UTC
We can use printf "fe:%02x:%02x:%02x:%02x:%02x" \ $(($RANDOM % 256)) $(($RANDOM % 256)) $(($RANDOM % 256)) \ $(($RANDOM % 256)) $(($RANDOM % 256)) to create a random MAC address instead. Created attachment 484180 [details]
Generate random MAC
Well, after discussing this with Paolo I used his code to generate the random MAC address and implemented this into tools/ioemu/target-i386-dm/qemu-ifup script to generate the MAC address randomly for any network interface of HVM guest and here's the example output in dom0:
# ifconfig | grep tap
tap0 Link encap:Ethernet HWaddr FE:7A:71:A2:29:0D
tap1 Link encap:Ethernet HWaddr FE:4F:FE:4D:6E:D5
So the MAC addresses are generated randomly. I'm putting the patch here for testing but according to my testing I can see no messages as mentioned in description.
Michal
Fix built into xen-3.0.3-126.el5 VERIFIED with xen-3.0.3-126.el5. The message of 'peth0: received packet with own address as source address' isn't present in dmesg after the fix applied. (Use 'network-bridge-mac' as the network-script in xend-config.sxp before test this.)
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
When an HVM guest was started with at least one virtual interface attached to it and with the network-script option set to "network-bridge-mac", a lot of "peth0: received packet with own address as source address" error messages appeared in the dmesg command output. With this update, a random MAC address is generated for TAP devices, and this bug no longer occurs.
I removed the technical notes, because the bug was introduced in the development of RHEL5.7 and was never in a released version. Deleted Technical Notes Contents. Old Contents: When an HVM guest was started with at least one virtual interface attached to it and with the network-script option set to "network-bridge-mac", a lot of "peth0: received packet with own address as source address" error messages appeared in the dmesg command output. With this update, a random MAC address is generated for TAP devices, and this bug no longer occurs. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-1070.html An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-1070.html |