Re: [Xen-devel] xen-netback notify DomU to send ARP.

[jianhai luan <jianhai.luan@xxxxxxxxxx>]

Sorry,
  My attachment is wrong, please check the patch.

On 2013-1-9 0:00, Ian Campbell wrote:
> On Tue, 2013-01-08 at 15:40 +0000, jianhai luan wrote:
> > On 2013-1-8 21:42, Ian Campbell wrote:
> > > On Tue, 2013-01-08 at 13:13 +0000, Jan Beulich wrote:
> > > > > > > On 08.01.13 at 12:57, jianhai luan <jianhai.luan@xxxxxxxxxx>
> > > > > > > wrote:
> > > > >      When Xen Dom0's network circumstance changed, DomU
> > > > > should be notified in some special condition. For
> > > > > example the below circumstance:
> > > > >      ping from Guest A to DomU:
> > > > >      Guest A --> eth0 - bond0 - xenbr0 --VIF(DOMU)
> > > > >                  eth1 /
> > > > >      when eth0 inactive, and eth1 active.
> > > How is eth0 failing? Are you unplugging it, un-enslaving it or
> > > taking
> > > some other sort of administrative action?
> > In my emulation environment, i unplug it or ifdown the interface,
> I expect these would behave rather different, since the affect of ifdown
> looks rather different to an unplug from the PoV of the switch.
>
> Is the ifdown case something which you are trying to solve or just what
> appeared to be a convenient test case? I'd be less inclined to worry
> about explict admin actions such as that.
>
> Unplugging the cable should cause:
>
> > > Doesn't this state change cause the switch to which eth0 and eth1
> > > are
> > > attached to forget the MAC tables associated with the eth0 port,
> > > meaning
> > > that subsequent traffic will be flooded until it learns that eth1 is
> > > the
> > > new port?
> Ian

Attachment: 0001-xen-netback-notify-DomU-to-send-ARP.patch
Description: Text document

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel