ok.. I guess the only reason I thought any more about it is because I get errors like the following in my system log from time to time:
Aug 24 12:30:58 kernel: arp_rtrequest: bad gateway 192.168.2.1 (! AF_LINK) Aug 24 12:30:58 kernel: arp_rtrequest: bad gateway 192.168.3.1 (! AF_LINK) Aug 24 12:30:58 kernel: arp_rtrequest: bad gateway 192.168.4.1 (! AF_LINK) Aug 24 12:30:58 kernel: arp_rtrequest: bad gateway 192.168.5.1 (! AF_LINK) Aug 24 12:30:58 kernel: arp_rtrequest: bad gateway 12.34.56.78 (! AF_LINK) (i changed the public ip to 12.34.56.78 for posting) I thought maybe it had something to do with the netmask not being entirely accurate. On Thu, 2005-08-25 at 11:20 -0400, Scott Ullrich wrote: > On FreeBSD /32 works just fine for aliases. > > Scott > > > On 8/25/05, Matthew Lenz <[EMAIL PROTECTED]> wrote: > > Is this always supposed to be a /32? I'm using /32 on all of them right > > now and it works but it still seems to me that since its asking for the > > netmask of that ip that I should be using /24 (192.168.1.0 network) for > > the private gw vips and /27 (which is what my public ip range is) for > > the public vips. Back when I first added the interfaces several > > revisions ago things just wouldn't work unless I used a /32 .. which is > > the single ip correct? > > > > i know enough about networking to be dangerous :) > > > >
