Date: Sun, 9 Dec 2001 23:45:38 +1100 (EST) From: Rowan Crowe <rowan@sensation.net.au> To: freebsd-isp@freebsd.org Subject: Re: arplookup Message-ID: <Pine.BSF.4.21.0112092341210.45148-100000@velvet.sensation.net.au> In-Reply-To: <Pine.BSF.4.21.0112090702040.7267-100000@veager.jwweeks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 9 Dec 2001, Jim Weeks wrote: > Right now it is set to 255.255.255.0. I will try changing it as soon as > someone is physically in the NOC. I suggested doing this, but the admin > at the ISP insisted 255.255.255.0 was necessary. I guess I should have > tried it any way. Just a warning that this will break connectivity to IPs in that block of 65535 IPs that are *not* on that LAN. For example, if your IP is 1.1.100.3 and your netmask is 255.255.255.0, your LAN has 255 local hosts, and everything else is routed via the gateway. If you change it to 255.255.0.0, then your LAN has 65535 local hosts, and everything else is routed via the gateway. This means that if you try to communicate with (say) 1.1.200.1, it will fail, because your machine assumes it's on the LAN, when it's *really* outside of that network, and can only be reached via the gateway. Coming full circle, setting that hostmask may actually cause similar or identical ARP errors on other machines, because there will be ARP requests coming from your machine for IPs that *are not* on the LAN (but your machine thinks they are) Cheers. -- Rowan Crowe - Melbourne, Australia www.camrecord.com | www.camdiscover.com | www.sensationbot.com 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.0112092341210.45148-100000>