Further workaround:
1st server has advbase 1 and advskew 0
2nd server has advbase 1 and advskew 100
So 2nd server should failover after what period of time when 1st server fails?
In openbsd man 8 ifconfig (
http://www.openbsd.org/cgi-bin/man.cgi?query=ifconfig&apropos=0&sektion=8&manpath=OpenBSD
It's strange... No log messages about moving from BACKUP to MASTER.
Oct 23 04:00:05 carp2 kernel: arp_rtrequest: bad gateway 1.1.1.5 (!AF_LINK)
Oct 23 04:00:05 carp2 kernel: arp_rtrequest: bad gateway 1.1.1.6 (!AF_LINK)
Oct 23 04:00:05 carp2 kernel: arp_rtrequest: bad gateway 1.1.1.9 (!AF
I went to check logs on master and backup servers. All was fine
except dmesg and messages:
Master server has no recored in messages for about 1 hour.
But on slave server I saw that:
Oct 20 12:15:00 carp-backup kernel: arp_rtrequest: bad gateway 1.1.1.5
(!AF_LINK)
Oct 20 12:15:00 carp-bac
On 3/14/06, MoonblueZ <[EMAIL PROTECTED]> wrote:
>
> i have some log in /var/log/message right this :
>
> Mar 14 10:44:27 cidomo kernel: arp_rtrequest: bad gateway
> 202.161.14.115(!AF_LINK)
> Mar 14 10:45:23 cidomo squid[431]: parseHttpRequest: PF open failed: (13)
> P
i have some log in /var/log/message right this :
Mar 14 10:44:27 cidomo kernel: arp_rtrequest: bad gateway
202.161.14.115(!AF_LINK)
Mar 14 10:45:23 cidomo squid[431]: parseHttpRequest: PF open failed: (13)
Permission denied
i dont know what is mean, anyone can help me?
--
No Rulez No Filterz
SIN(rt_mask(rt))->sin_addr.s_addr != 0x)
>rt->rt_flags |= RTF_CLONING;
Good catch. This can and should be committed; it's a common sense null
pointer check.
> arp_rtrequest: bad gateway 192.168.100.0 (!AF_LINK)
> 192.168.100
Pawel Malachowski wrote:
On Mon, Oct 25, 2004 at 07:12:18PM +0300, Iasen Kostov wrote:
This is the segment of code:
if ((rt->rt_flags & RTF_HOST) == 0 &&
SIN(rt_mask(rt))->sin_addr.s_addr != 0x)
rt->rt_flags |= RTF_CLONING;
BTW,
zebra tries to add this
route which until this moment is inactive. And then *POOF* kernel
panic in arp_rtrequest() at 180.
This is the segment of code:
if ((rt->rt_flags & RTF_HOST) == 0 &&
SIN(rt_mask(rt))->sin_addr.s_addr != 0x)
On Mon, Oct 25, 2004 at 07:12:18PM +0300, Iasen Kostov wrote:
> This is the segment of code:
>
>if ((rt->rt_flags & RTF_HOST) == 0 &&
>SIN(rt_mask(rt))->sin_addr.s_addr != 0x)
>rt->rt_flags |= RTF_CLONING;
BTW, http://www.freebs
is
route which until this moment is inactive. And then *POOF* kernel
panic in arp_rtrequest() at 180.
This is the segment of code:
if ((rt->rt_flags & RTF_HOST) == 0 &&
SIN(rt_mask(rt))->sin_addr.s_addr != 0x)
r
il
this moment is inactive. And then *POOF* kernel panic in arp_rtrequest()
at 180.
This is the segment of code:
if ((rt->rt_flags & RTF_HOST) == 0 &&
SIN(rt_mask(rt))->sin_addr.s_addr != 0x)
rt->rt_flags |= RTF_C
On Wed, Jan 21, 2004 at 10:51:18AM +0300, Vasenin Alexander aka BlackSir wrote:
> Those messages sometimes appears in log. Maybe someone know where to find
> what it actually mean?
>
> Jan 21 02:58:54 inet /kernel: arp_rtrequest: bad gateway value
> Jan 21 03:03:54 inet /kernel
Those messages sometimes appears in log. Maybe someone know where to find
what it actually mean?
Jan 21 02:58:54 inet /kernel: arp_rtrequest: bad gateway value
Jan 21 03:03:54 inet /kernel: arp_rtrequest: bad gateway value
Jan 21 03:08:53 inet /kernel: arp_rtrequest: bad gateway value
Jan 21 03
Hi,
since a few days, I get the following message, any idea ?
Jun 28 07:00:01 gits /kernel: arp_rtrequest: bad gateway value
# uname -a
FreeBSD gits 4.6-STABLE FreeBSD 4.6-STABLE #15: Sun Jun 23 06:31:23 CEST 2002
root@gits:/disk2/freebsd/src/sys/compile/CUSTOM i386
# ifconfig -a
On Fri, 23 Nov 2001, Paul Herman wrote:
> On Thu, 22 Nov 2001, Ruslan Ermilov wrote:
>
> > On Wed, Nov 21, 2001 at 05:32:27PM -0800, Paul Herman wrote:
> > > Hi,
> > >
> > > I'd like to pick some brains before I file a PR.
> > >
> > There's already a PR open on this, kern/29170.
> >
> > [...]
> >
interface. I decided to try out routed, and
> started noticing gobs and gobs of messages:
>
> Nov 15 11:38:10 tick /kernel: arp_rtrequest: bad gateway value
> Nov 15 11:43:10 tick /kernel: arp_rtrequest: bad gateway value
> Nov 15 11:47:59 tick /kernel: arp_rtrequest: bad gat
Hi,
I'd like to pick some brains before I file a PR.
I've got 4.4-RELEASE running on FreeBSD-alpha with more than one
alias on my network interface. I decided to try out routed, and
started noticing gobs and gobs of messages:
Nov 15 11:38:10 tick /kernel: arp_rtrequest: bad gat
s different. This results in a
changed route with AF_INET gateway, but route's IFA still points to
Ethernet device and rt_ifa->ifa_rtrequest == arp_rtrequest. This
results in this message as AF_INET != AF_LINK. The message is
harmless. This is also reproduceable on a 4.1-RELEASE machi
18 matches
Mail list logo
