From owner-freebsd-net@FreeBSD.ORG Thu Oct 13 08:54:52 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 26A8416A41F for ; Thu, 13 Oct 2005 08:54:52 +0000 (GMT) (envelope-from discussion-lists@linnet.org) Received: from thorn.pobox.com (thorn.pobox.com [208.210.124.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id C9ABD43D48 for ; Thu, 13 Oct 2005 08:54:51 +0000 (GMT) (envelope-from discussion-lists@linnet.org) Received: from thorn (localhost [127.0.0.1]) by thorn.pobox.com (Postfix) with ESMTP id D21B1CE for ; Thu, 13 Oct 2005 04:32:45 -0400 (EDT) Received: from mappit.local.linnet.org (212-74-113-67.static.dsl.as9105.com [212.74.113.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by thorn.sasl.smtp.pobox.com (Postfix) with ESMTP id AE77D55F1 for ; Thu, 13 Oct 2005 04:32:45 -0400 (EDT) Received: from lists by mappit.local.linnet.org with local (Exim 4.54 (FreeBSD)) id 1EPyrN-0002pZ-AB for freebsd-net@freebsd.org; Thu, 13 Oct 2005 09:54:45 +0100 Date: Thu, 13 Oct 2005 09:54:45 +0100 From: Brian Candler To: freebsd-net@freebsd.org Message-ID: <20051013085445.GA10797@uk.tiscali.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: 255.255.255.255 broadcast changed from 4.x to 5.x X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Oct 2005 08:54:52 -0000 I've noticed a change in behaviour between FreeBSD 4.9 and FreeBSD 5.4 When sending an undirected broadcast to 255.255.255.255, FreeBSD 4.9 encapsulates this with the broadcast MAC address (ff:ff:ff:ff:ff:ff) as the destination. However, FreeBSD 5.4 encapsulates the packet using the MAC address of the default router, and therefore nobody else on the network sees it. Where this broke me was using wakeonlan. This utility sends a magic packet to 255.255.255.255 by default, and worked under FreeBSD 4.9 but not 5.4. After debugging with tcpdump -e, I found the issue with the MAC address. Configuring the program to send to the network's broadcast address instead of 255.255.255.255 fixed the problem; the packet was addressed to ff:ff:ff:ff:ff:ff, and the other computer woke up. Now I know about this, I can demonstrate it using 'ping 255.255.255.255' just as easily. My question is: is this an intentional change? Is it documented? # egrep -i '(broadcast|255)' /usr/src/UPDATING # Thanks, Brian.