Date: Tue, 2 Aug 2016 16:52:10 -0700 From: Kevin Oberman <rkoberman@gmail.com> To: Julian Elischer <julian@freebsd.org> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: Xen networking problems in -current with xn driver? Message-ID: <CAN6yY1u2tLeF89uGLiakuQCW2PCesvM=wAM5385DBZF9c9-Z9A@mail.gmail.com> In-Reply-To: <0b90d4f0-fc02-7a07-6ce1-135a61cbc352@freebsd.org> References: <0b90d4f0-fc02-7a07-6ce1-135a61cbc352@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Aug 2, 2016 at 11:12 AM, Julian Elischer <julian@freebsd.org> wrote: > I upgraded my VPS machine to today's current, and on reboot I couldn't get > into it by network. > > A quick switch to the VNC console showed that it was up but that it > couldn't get out. > > > The xn interfaces said they were UP but attempts to get out were met with > "network is down". > > if I did 'tcpdump -n -i xn0' (and xn1) hten all was fine again. > > tcpdump saw packets, and in fact ipfw saw some packets coming in even > before that but it was not possible to send. > > > Has anyone seen similar? > > some relevant parts of the dmesg output.: > > [...] A bit of a guess, but the obvious thing that I see is that when you start tcpdump you are placing the interface in promiscuous mode. Looks like the "device" fails to properly see packet addressed to it. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1u2tLeF89uGLiakuQCW2PCesvM=wAM5385DBZF9c9-Z9A>