carp and arp_rtrequest: bad gateway 1.1.1.5 (!AF_LINK)
I got 2 servers with CARP enabled. One is MASTER, second - BACKUP. CARP is for HA of running some service on that servers. All works fine, but today I've got interesting case: Service was not responding for 5 minutes. Can't tell more details because it was said by not IT guy. Okay, 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-backup kernel: arp_rtrequest: bad gateway 1.1.1.6 (!AF_LINK) Oct 20 12:15:00 carp-backup kernel: arp_rtrequest: bad gateway 1.1.1.9 (!AF_LINK) .. Oct 20 12:49:58 carp-backup kernel: arp_rtrequest: bad gateway 1.1.1.5 (!AF_LINK) Oct 20 12:49:58 carp-backup kernel: arp_rtrequest: bad gateway 1.1.1.6 (!AF_LINK) Oct 20 12:49:58 carp-backup kernel: arp_rtrequest: bad gateway 1.1.1.9 (!AF_LINK) Total about 300 records. Can anyone comment something about it? What was that? Backup server was loosing connectivity with Master server? In sysctl.conf I've got only net.inet.carp.preempt=1.Now I tuned log to net.inet.carp.log=2. This should log carp info messages. Am I right about loosing connectivity between master-backup servers or there can be another reason? ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: carp and arp_rtrequest: bad gateway 1.1.1.5 (!AF_LINK)
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_LINK) Oct 23 04:00:06 carp2 kernel: carp0: MASTER -> BACKUP (more frequent advertisement received) Oct 24 00:10:18 carp2 kernel: arp_rtrequest: bad gateway 1.1.1.5 (!AF_LINK) Oct 24 00:10:18 carp2 kernel: arp_rtrequest: bad gateway 1.1.1.6 (!AF_LINK) Oct 24 00:10:18 carp2 kernel: arp_rtrequest: bad gateway 1.1.1.9 (!AF_LINK) Oct 24 00:10:18 carp2 kernel: carp0: MASTER -> BACKUP (more frequent advertisement received) 2010/10/20 c0re : > I got 2 servers with CARP enabled. One is MASTER, second - BACKUP. > CARP is for HA of running some service on that servers. > > All works fine, but today I've got interesting case: > Service was not responding for 5 minutes. Can't tell more details > because it was said by not IT guy. > > Okay, 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-backup kernel: arp_rtrequest: bad gateway 1.1.1.6 > (!AF_LINK) > Oct 20 12:15:00 carp-backup kernel: arp_rtrequest: bad gateway 1.1.1.9 > (!AF_LINK) > .. > Oct 20 12:49:58 carp-backup kernel: arp_rtrequest: bad gateway 1.1.1.5 > (!AF_LINK) > Oct 20 12:49:58 carp-backup kernel: arp_rtrequest: bad gateway 1.1.1.6 > (!AF_LINK) > Oct 20 12:49:58 carp-backup kernel: arp_rtrequest: bad gateway 1.1.1.9 > (!AF_LINK) > > Total about 300 records. > > Can anyone comment something about it? What was that? Backup server > was loosing connectivity with Master server? > > In sysctl.conf I've got only net.inet.carp.preempt=1.Now I tuned log > to net.inet.carp.log=2. This should log carp info messages. > > Am I right about loosing connectivity between master-backup servers or > there can be another reason? > ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: carp and arp_rtrequest: bad gateway 1.1.1.5 (!AF_LINK)
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+Current&arch=i386&format=html ) I found that info: Taken together, the advbase and advskew indicate how frequently, in seconds, the host will advertise the fact that it considers itself master of the virtual host. The formula is advbase + (advskew / 256). If the master does not advertise within three times this interval, this host will begin advertising as master. Due to CARP be ported from openbsd I think it should be same for freebsd too. So 2nd server should take MASTER state after 3*(advbase+(advskew / 256)) = 3*(1+(100/256)) =~ 4 secs. But when I promote 1st servers CARP interface down, 2nd server became MASTER immediately, no 4 seconds holdtime/timeout occurs. Why is it so? Any tips? Want to understand why 2nd server takes master state too often while 1st server are still available in network. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Strange behavior of MTU on loopback interfaces.
Hello all! I'm testing setting lower MTU on loopback interfaces to avoid some MTU problems with IPSEC in a path of traffic. ifconfig lo1 create ifconfig lo1 mtu 1300 ifconfig lo1 5.5.5.5/32 # ifconfig lo1 lo1: flags=8049 metric 0 mtu 1300 inet 5.5.5.5 netmask 0x #ifconfig em0 em0: flags=8843 metric 0 mtu 1500 options=9b ether 12:ac:29:7c:fa:39 inet 10.0.0.1 netmask 0xff00 broadcast 10.0.0.255 media: Ethernet autoselect (1000baseTX ) status: active And I set only one "Listen 5.5.5.5:80" in http.conf in apache 2.2 # sockstat -4 | grep 80 www httpd 96843 3 tcp4 5.5.5.5:80*:* www httpd 96838 3 tcp4 5.5.5.5:80*:* www httpd 96837 3 tcp4 5.5.5.5:80*:* www httpd 96836 3 tcp4 5.5.5.5:80*:* www httpd 96835 3 tcp4 5.5.5.5:80*:* www httpd 96834 3 tcp4 5.5.5.5:80*:* root httpd 96833 3 tcp4 5.5.5.5:80*:* I run tcpdump -ni em0 port 80. And made telnet 5.5.5.5 80 from other host and saw something wrong. 10:26:01.640866 IP 10.0.0.2.57553 > 5.5.5.5.80: S 1049284626:1049284626(0) win 65535 10:26:01.640902 IP 5.5.5.5.80 > 10.0.0.2.57553: S 2144222949:2144222949(0) ack 1049284627 win 65535 10:26:01.642632 IP 10.0.0.2.57553 > 5.5.5.5.80: . ack 1 win 65535 5.5.5.5:80 said that it has got tcp mss 1460. Why? I was waiting for something like 1260. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: FreeBSD 7.3, reboot after panic: double fault
8 #46 0xc09bd5a8 in tcp_mtudisc (inp=0xc4c5d44c, errno=0) at tcp_offload.h:282 #47 0xc09bac9b in tcp_output (tp=0xc4c5f768) at /usr/src/sys/netinet/tcp_output.c:1248 #48 0xc09bd5a8 in tcp_mtudisc (inp=0xc4c5d44c, errno=0) at tcp_offload.h:282 #49 0xc09bac9b in tcp_output (tp=0xc4c5f768) at /usr/src/sys/netinet/tcp_output.c:1248 ---Type to continue, or q to quit--- #50 0xc09bd5a8 in tcp_mtudisc (inp=0xc4c5d44c, errno=0) at tcp_offload.h:282 #51 0xc09bac9b in tcp_output (tp=0xc4c5f768) at /usr/src/sys/netinet/tcp_output.c:1248 #52 0xc09bd5a8 in tcp_mtudisc (inp=0xc4c5d44c, errno=0) at tcp_offload.h:282 #53 0xc09bac9b in tcp_output (tp=0xc4c5f768) at /usr/src/sys/netinet/tcp_output.c:1248 #54 0xc09bd5a8 in tcp_mtudisc (inp=0xc4c5d44c, errno=0) at tcp_offload.h:282 #55 0xc09bac9b in tcp_output (tp=0xc4c5f768) at /usr/src/sys/netinet/tcp_output.c:1248 #56 0xc09b78e5 in tcp_do_segment (m=0xc4a83800, th=0xc4aa4024, so=0xc4a2480c, tp=0xc4c5f768, drop_hdrlen=52, tlen=0, iptos=0 '\0', ti_locked=3) at /usr/src/sys/netinet/tcp_input.c:2684 #57 0xc09b8b7d in tcp_input (m=0xc4a83800, off0=20) at /usr/src/sys/netinet/tcp_input.c:1020 #58 0xc09af671 in ip_input (m=0xc4a83800) at /usr/src/sys/netinet/ip_input.c:804 #59 0xc0946a09 in netisr_dispatch_src (proto=1, source=0, m=0xc4a83800) at /usr/src/sys/net/netisr.c:917 #60 0xc0946ca0 in netisr_dispatch (proto=1, m=0xc4a83800) at /usr/src/sys/net/netisr.c:1004 #61 0xc093d2aa in ether_demux (ifp=0xc42d7000, m=0xc4a83800) at /usr/src/sys/net/if_ethersubr.c:901 #62 0xc093d82f in ether_input (ifp=0xc42d7000, m=0xc4a83800) at /usr/src/sys/net/if_ethersubr.c:760 #63 0xc0623c4a in lem_handle_rxtx (context=0xc42ea000, pending=1) at /usr/src/sys/dev/e1000/if_lem.c:3616 #64 0xc08cb282 in taskqueue_run (queue=0xc42c9c80) at /usr/src/sys/kern/subr_taskqueue.c:239 #65 0xc08cb48d in taskqueue_thread_loop (arg=0xc42ee5a8) at /usr/src/sys/kern/subr_taskqueue.c:360 #66 0xc0868831 in fork_exit (callout=0xc08cb3d0 , arg=0xc42ee5a8, frame=0xe460dd38) at /usr/src/sys/kern/kern_fork.c:843 #67 0xc0b28c10 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:270 (kgdb) 2010/4/21 Bjoern A. Zeeb > On Tue, 20 Apr 2010, pluknet wrote: > > On 20 April 2010 15:48, John Baldwin wrote: >> >>> On Tuesday 20 April 2010 2:53:16 am c0re wrote: >>> >>>> Hello All! >>>> I've upgraded freebsd from 7.0 to 7.3 and all was good until I tryed to >>>> configure gre interface and use ipfw fwd. >>>> I'm actually does not know what was the point of failure in my >>>> configuration. >>>> >>>> [ some details snipped ] >>>> >>>> It worked about one week and then I made some configuration changes: >>>> added gre interface and 2 aliases: >>>> >>>> # cat /etc/rc.conf |grep >>>> ifconfig_xl0="inet 192.168.0.10 netmask 255.255.255.0" >>>> ifconfig_xl0_alias0="192.168.0.11 netmask 255.255.255.255" >>>> ifconfig_xl0_alias1="192.168.0.12 netmask 255.255.255.255" >>>> cloned_interfaces="gre0" >>>> ifconfig_gre0="inet 192.168.250.6 192.168.250.5 tunnel 192.168.0.12 >>>> 192.168.200.15 netmask 255.255.255.252 link1 up" >>>> >>>> and >>>> >>>> # cat /etc/rc.local >>>> #!/bin/sh >>>> ipfw add fwd 192.168.250.5 icmp from 192.168.0.11 to any out via xl0 >>>> ipfw add fwd 192.168.250.5 tcp from 192.168.0.11 443 to any out via xl0 >>>> ipfw add allow ip from any to any >>>> >>>> # ifconfig gre0 >>>> gre0: flags=b050 metric 0 mtu >>>> 1476 >>>> tunnel inet 192.168.0.12 --> 192.168.200.15 >>>> inet 192.168.250.6 --> 192.168.250.5 netmask 0xfffc >>>> >>>> I shutted down gre interface to prevent requests via gre to buggy IP. >>>> >>>> The main idea of such configurations was: fwd all connections to https >>>> to >>>> 192.168.0.1 via gre interface. >>>> And also I made apache configurations to make it listen on 192.168.0.11 >>>> too. >>>> >>>> And make some tests: ping 192.168.0.11 - was fine, goes via gre. Telnet >>>> to >>>> 192.168.0.11 443 was fine too. Then I tryed to make browser https >>>> connection to 192.168.0.11. Apache showed me certificate warning and I >>>> accepted, then in browser nothing happened, it was trying to open page. >>>> But >>>> server got kernel panic at that moment. >>>> >>>> At first time I thought that it was some power failure, I tryed 2 more >>>> times >>>> and
CARP as module
Hello freebsd-net! It was asked many times, but i'll bump it again. There was patch in 8.0 to allow CARP as module http://lists.freebsd.org/pipermail/freebsd-net/2009-April/021774.html But it was not committed... Any chances to see CARP as module in GENERIC? My interest is to use freebsd-update with CARP enabled systems. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
