Date: Sun, 24 Mar 2002 09:29:35 -0500 From: Brian Dean <bsd@bsdhome.com> To: freebsd-hackers@freebsd.org Subject: odd ethernet frame Message-ID: <20020324092935.A464@neutrino.bsdhome.com>
next in thread | raw e-mail | index | archive | help
This is probably not the best place to ask this, but I'm stumped. I've been seeing this ethernet frame via tcpdump: 04:11:13.433484 0:0:1:1:e3:69 45:0:0:24:15:c5 c0a8 36: 0x0000 2001 e000 0001 0900 8e4a 0102 0708 c0a8 .........J...... 0x0010 2001 8000 0001 ...... 04:18:50.926606 0:0:1:1:e2:f5 45:0:0:24:16:39 c0a8 36: 0x0000 2001 e000 0001 0900 8e4a 0102 0708 c0a8 .........J...... 0x0010 2001 8000 0001 ...... 04:27:33.502214 0:0:1:1:e2:23 45:0:0:24:17:b c0a8 36: 0x0000 2001 e000 0001 0900 8e4a 0102 0708 c0a8 .........J...... 0x0010 2001 8000 0001 ...... I can't find any reference to the frame type (c0a8), the link level addresses seem bogus and change with every occurance (both the source and the destination), and the packet arrives about every 9 minutes or so. This is on an interface (fxp1) that has a wireless access point attached, though I unplugged the access point and it the packet still shows up under tcpdump (even when the interface show "no carrier"!), so its not that. The system has another interface (fxp0) that connects it to the rest of my LAN and is set to forward between the interfaces. However, if I run a tcpdump on that interface, the mysterious packet never shows up there. I'm at a loss to find an explanation. Any ideas? Thanks, -Brian -- Brian Dean bsd@FreeBSD.org bsd@bsdhome.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020324092935.A464>