Avi Kivity wrote:
>
> Can you tcpdump on bond0, br0, vnet0, and the guest's interface to see
> where the packet is lost?
>
Sure. Using the tcpdump command line:
tcpdump -i br0 -w /var/tmp/tcpdump.br0 ether host 00:16:36:2f:f1:d2
(similar for other interfaces) I can see the DHCPOFFER coming
from my dhcp server on bond0:
11:00:08.237350 00:15:17:91:3f:59 > 00:16:36:2f:f1:d2, ethertype IPv4 (0x0800),
length 364: (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17),
length 350)
172.19.96.124.67 > 172.19.97.250.68: BOOTP/DHCP, Reply, length 322, xid
0x78fb274e, secs 3, Flags [none]
Your-IP 172.19.97.250
Client-Ethernet-Address 00:16:36:2f:f1:d2 [|bootp]
It is also visible on br0:
11:00:08.237350 00:15:17:91:3f:59 > 00:16:36:2f:f1:d2, ethertype IPv4 (0x0800),
length 364: (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17),
length 350)
172.19.96.124.67 > 172.19.97.250.68: BOOTP/DHCP, Reply, length 322, xid
0x78fb274e, secs 3, Flags [none]
Your-IP 172.19.97.250
Client-Ethernet-Address 00:16:36:2f:f1:d2 [|bootp]
But it is not visible on vnet0, and of course not on the
guest. All I see there are the DHCPDISCOVER calls sent by
the guest, and some IPv6 traffic:
:
11:00:05.245090 00:16:36:2f:f1:d2 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800),
length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:16:36:2f:f1:d2, length 300
11:00:05.245247 00:16:36:2f:f1:d2 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800),
length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:16:36:2f:f1:d2, length 300
11:00:08.237025 00:16:36:2f:f1:d2 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800),
length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:16:36:2f:f1:d2, length 300
11:00:08.237135 00:16:36:2f:f1:d2 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800),
length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:16:36:2f:f1:d2, length 300
11:00:08.237147 00:16:36:2f:f1:d2 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800),
length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:16:36:2f:f1:d2, length 300
11:00:08.237196 00:16:36:2f:f1:d2 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800),
length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:16:36:2f:f1:d2, length 300
11:00:08.883308 00:16:36:2f:f1:d2 > 33:33:00:00:00:16, ethertype IPv6 (0x86dd),
length 90: :: > ff02::16: HBH ICMP6, multicast listener report v2, 1 group
record(s), length 28
11:00:08.883381 00:16:36:2f:f1:d2 > 33:33:00:00:00:16, ethertype IPv6 (0x86dd),
length 90: :: > ff02::16: HBH ICMP6, multicast listener report v2, 1 group
record(s), length 28
11:00:08.883411 00:16:36:2f:f1:d2 > 33:33:00:00:00:16, ethertype IPv6 (0x86dd),
length 90: :: > ff02::16: HBH ICMP6, multicast listener report v2, 1 group
record(s), length 28
11:00:08.883419 00:16:36:2f:f1:d2 > 33:33:00:00:00:16, ethertype IPv6 (0x86dd),
length 90: :: > ff02::16: HBH ICMP6, multicast listener report v2, 1 group
record(s), length 28
11:00:14.238455 00:16:36:2f:f1:d2 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800),
length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:16:36:2f:f1:d2, length 300
11:00:14.238523 00:16:36:2f:f1:d2 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800),
length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:16:36:2f:f1:d2, length 300
11:00:14.238544 00:16:36:2f:f1:d2 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800),
length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:16:36:2f:f1:d2, length 300
:
I can send you the complete tcpdumps, if you are interested?
Regards
Harri
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
