Your message dated Tue, 30 May 2006 23:24:53 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#367600: further information, workaround, and maybe ok to
close
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: quagga
Version: 0.99.4-2
Severity: normal
I have quagga installed (I tried both the sarge and unstable versions, 0.98
and 0.99) as just a RIP client. When it starts up, it joins the RIP multicast
group, and gets correct initial routes via RIP from the two firewalls. However,
it does not report ever seeing any future RIP broadcasts, so 180 seconds later,
it decides the routes are stale and removes them.
netstat -g shows membership in the multicast group:
eth0 1 RIP2-ROUTERS.MCAST.NET
lsof -i shows that ripd appears to be listening for packets:
ripd 17540 quagga 5u IPv4 56156 UDP *:route
I found references on the web to a change in authentication behavior
about the same time a route injection vulnerability was patched, but
they seem to say that the log file would show the packet being heard
but rejected for bad auth, so I don't think that's the problem. I
tried this in case I'm wrong on that, but it didn't help:
>> ripd# configure terminal
>> ripd(config)# interface eth0
>> ripd(config-if)# no ip rip authentication mode
The same setup is working find on some fedora core 3 machines on the
same network using quagga/ripd 0.97.3 with the same ripd.conf
(although the below ripd.conf has been modified for more logging and
making the interface passive)
ripd.conf:
! -*- rip -*-
!
! RIPd configuration file
!
hostname ripd
password zebra
!
debug rip events
debug rip packet
debug rip packet recv detail
debug rip zebra
!
interface eth0
!
router rip
network 192.168.0.0/24
network eth0
!ip rip receive version 1 2
no redistribute kernel
no redistribute static
no redistribute connected
no redistribute ospf
no redistribute bgp
passive-interface default
!neighbor 192.168.0.1
!neighbor 192.168.0.2
! route 10.0.0.0/8
! distribute-list private-only in eth0
!
!access-list private-only permit 10.0.0.0/8
!access-list private-only deny any
!
log file /var/log/quagga/ripd.log
!
!log stdout
Some log output ("triggered update!" is where the routes are removed):
2006/05/16 16:26:11 RIP: RIPd 0.99.4 starting: [EMAIL PROTECTED]
2006/05/16 16:26:11 RIP: interface add eth0 index 2 flags 4163 metric
0 mtu 1
2006/05/16 16:26:11 RIP: interface eth0: passive = 1
2006/05/16 16:26:11 RIP: connected address 192.168.0.200/24 is added
2006/05/16 16:26:11 RIP: turn on eth0
2006/05/16 16:26:11 RIP: Redistribute new prefix 192.168.0.0/24 on the
interface
eth0
2006/05/16 16:26:11 RIP: triggered update!
2006/05/16 16:26:11 RIP: interface add lo index 1 flags 73 metric 0
mtu 1
2006/05/16 16:26:11 RIP: interface lo: passive = 1
2006/05/16 16:26:11 RIP: connected address 127.0.0.1/8 is added
2006/05/16 16:26:11 RIP: interface add sit0 index 3 flags 128 metric 0
mtu 1
2006/05/16 16:26:11 RIP: interface sit0: passive = 1
2006/05/16 16:26:12 RIP: multicast join at eth0
2006/05/16 16:26:12 RIP: multicast request on eth0
2006/05/16 16:26:12 RIP: rip_send_packet 192.168.0.200 > 224.0.0.9
(eth0)
2006/05/16 16:26:12 RIP: SEND to 224.0.0.9.520
2006/05/16 16:26:12 RIP: ignore packet comes from myself
2006/05/16 16:26:12 RIP: RECV packet from 192.168.0.1 port 520 on eth0
2006/05/16 16:26:12 RIP: RECV RESPONSE version 2 packet size 84
2006/05/16 16:26:12 RIP: 0.0.0.0/0 -> 0.0.0.0 family 2 tag 0 metric
1
2006/05/16 16:26:12 RIP: 63.0.0.0/8 -> 0.0.0.0 family 2 tag 0 metric
1
2006/05/16 16:26:12 RIP: 63.236.12.160/28 -> 0.0.0.0 family 2 tag 0
metric 1
2006/05/16 16:26:12 RIP: 169.254.0.0/16 -> 0.0.0.0 family 2 tag 0
metric 1
2006/05/16 16:26:12 RIP: RECV packet from 192.168.0.2 port 520 on eth0
2006/05/16 16:26:12 RIP: RECV RESPONSE version 2 packet size 64
2006/05/16 16:26:12 RIP: 0.0.0.0/0 -> 0.0.0.0 family 2 tag 0 metric
6
2006/05/16 16:26:12 RIP: 63.236.12.160/28 -> 0.0.0.0 family 2 tag 0
metric 6
2006/05/16 16:26:12 RIP: 169.254.0.0/16 -> 0.0.0.0 family 2 tag 0
metric 6
2006/05/16 16:26:13 RIP: update timer fire!
2006/05/16 16:26:47 RIP: update timer fire!
2006/05/16 16:27:22 RIP: update timer fire!
2006/05/16 16:27:53 RIP: update timer fire!
2006/05/16 16:28:30 RIP: update timer fire!
2006/05/16 16:28:57 RIP: update timer fire!
2006/05/16 16:29:12 RIP: triggered update!
2006/05/16 16:29:15 RIP: triggered update!
2006/05/16 16:29:34 RIP: update timer fire!
thanks
- M
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (800, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages quagga depends on:
ii adduser 3.63 Add and remove users and groups
ii debconf [debconf-2.0] 1.4.30.13 Debian configuration management sy
ii iproute 20041019-3 Professional tools to control the
ii libc6 2.3.6-7 GNU C Library: Shared libraries
ii libcap1 1:1.10-14 support for getting/setting POSIX.
ii libncurses5 5.5-2 Shared libraries for terminal hand
ii libpam0g 0.76-22 Pluggable Authentication Modules l
ii libreadline5 5.1-7 GNU readline and history libraries
ii logrotate 3.7-5 Log rotation utility
-- debconf information:
quagga/really_stop: false
--- End Message ---
--- Begin Message ---
Hello Mark
On 2006-05-18 Mark Montague wrote:
> On further investigation, it appears this problem has something to do
> If I'm the only one seeing this ripd behavior, it's probably OK to
> close the bug and leave this info for anyone with similar problems
> looking into a similar problem.
Ok, bug report gets closed now.
bye,
-christian-
--- End Message ---
