On 7/22/05, alan walters <[EMAIL PROTECTED]> wrote: > > > > > Jul 22 09:51:11 > > kernel: arp_rtrequest: bad gateway 10.250.3.1 (!AF_LINK) > > Jul 22 09:51:11 > > kernel: arp_rtrequest: bad gateway 192.168.168.10 (!AF_LINK) > > Jul 22 09:51:11 > > kernel: arp_rtrequest: bad gateway 192.168.168.8 (!AF_LINK) > > > Jul 22 09:51:11 > > kernel: arp_rtrequest: bad gateway 10.250.3.1 (!AF_LINK) > > Jul 22 09:51:11 > > kernel: arp_rtrequest: bad gateway 192.168.168.10 (!AF_LINK) > > Jul 22 09:51:11 > > kernel: arp_rtrequest: bad gateway 192.168.168.8 (!AF_LINK) > >
Scott will have to answer this one definitively, but here's some background info. Everything I've seen says this is caused by "a screwed routing table". Also seems to be a known CARP issue. http://groups-beta.google.com/group/lucky.freebsd.pf/browse_thread/thread/8f861c8f6036a1d3/230215e48dca5411?q=%22arp_rtrequest:+bad+gateway+%22&rnum=3&hl=en#230215e48dca5411 hell it even seems to happen on OpenBSD http://groups-beta.google.com/groups?q=%22arp_rtrequest:+bad+gateway+%22&start=0&scoring=d&hl=en&lr=&; and from the FreeBSD archives: -- The ARP entries are stored in the routing table. A valid ARP entry has a link-type gateway address. If your routing table is misconfigured, it's possible that gateway will be something else -- then the kernel whines. -- http://groups-beta.google.com/group/mailing.freebsd.net/browse_thread/thread/1f2dc2ca79375e85/45ab37b002b8dda7?q=%22arp_rtrequest:+bad+gateway+%22&rnum=1&hl=en#45ab37b002b8dda7 -cmb --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
