Date: Sat, 20 Oct 2001 22:57:12 -0400 (EDT) From: Jim Weeks <jim@siteplus.net> To: Rowan Crowe <rowan@sensation.net.au> Cc: freebsd-isp@FreeBSD.ORG Subject: Re: arplookup failed: Message-ID: <Pine.BSF.4.21.0110202255160.961-100000@veager.jwweeks.com> In-Reply-To: <Pine.BSF.4.21.0110211248480.36258-100000@velvet.sensation.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Ok, thats what I thought you meant. No, I can login to the offending machine to do the trace, I'll try your idea. Thanks, -- Jim Weeks On Sun, 21 Oct 2001, Rowan Crowe wrote: > On Sat, 20 Oct 2001, Jim Weeks wrote: > > > A traceroute from my server back to the offending machine travels through > > my default gateway, which is how it should be, I think. Or shouldn't the > > trace also show the gateway for the offending machine? > > Hello Jim, > > Are you able to trace back from the other end? That's what I was getting > at. > > If you can't, then use tcpdump -e to compare ethernet addresses; see if > the packets FROM the other server have the source ethernet address of your > gateway. If not, then something is funny (like the host sending > directly...) > > Cheers. > > > -- > Rowan Crowe > camrecord.com / camdiscover.com / Sensation Internet Services > Melbourne, Australia > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0110202255160.961-100000>