From owner-freebsd-isp Sat Jan 19 12: 9:11 2002 Delivered-To: freebsd-isp@freebsd.org Received: from misery.sdf.com (misery.sdf.com [207.200.153.226]) by hub.freebsd.org (Postfix) with ESMTP id DF45737B400 for ; Sat, 19 Jan 2002 12:09:05 -0800 (PST) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 16S1Bg-000281-00; Sat, 19 Jan 2002 11:30:00 -0800 Date: Sat, 19 Jan 2002 11:29:59 -0800 (PST) From: Tom Samplonius To: John Brooks Cc: freebsd-isp@FreeBSD.ORG Subject: Re: OT Gateway IP is Broadcast IP In-Reply-To: <000b01c1a11f$defc0140$1505010a@daylight.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sat, 19 Jan 2002, John Brooks wrote: > The other day I came across a Win2k network that has assigned their gateway > IP to their broadcast IP. Seemed strange to me. Is this normal in a windows > environment? > > network: x.x.x.96/29 > gateway: x.x.x.103 > broadcast: x.x.x.103 Usually Windows systems with messed up gateways default to using proxy arp. For instance many sites deliberately set the hosts own IP and the gateway IP to be the same. This means they send ARP requests for every non local IP. Hopefully, the border router is set to handle proxy arp. Proxy arp generates a lot of broadcast traffic. On a DSL network, broadcasts may be flooded to lots of other areas, so you don't necessarily know which router is responding. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message