[prev in list] [next in list] [prev in thread] [next in thread]
List: quagga-users
Subject: [quagga-users 11844] How to verify ripd.conf / RIPd announcing
From: Timo Schoeler <timo.schoeler () riscworks ! net>
Date: 2010-09-28 9:15:46
Message-ID: 4CA1B242.3060207 () riscworks ! net
[Download RAW message or body]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi list,
I'm still struggling with RIPd announcing routes I'm not happy with.
However, if I run vtysh and issue 'sh ru', I don't see what I told RIPd
in its config file (e.g., I don't see the 'no default-information
originate' I did configure).
When trying to start RIPd with a *knowingly* invalid config (e.g., I add
a typo to test it), it barks and does not start. It starts with the
config attached without complaining, but vtysh does not show e.g. that I
enabled set 'no default-information originate'.
Is there a way I can verify RIPd's config?
I already tried to configure RIPd from scratch using vtysh, and writing
it to a file (resulting in Quagga.conf), hoping it would create a sane
config. It won't.
I tested this running CentOS' original quagga-0.98.6-5.el5_5.1.x86_64
(which is very very old) as well as my own, self built
quagga-0.99.17-0.el5, which can be fetched here:
http://riscworks.net/CentOS/quagga/
- ---
(For a more detailed description of my setup I'd like to quote myself:
http://lists.quagga.net/pipermail/quagga-users/2010-September/011822.html)
Setup is a bunch of CentOS 5.5 machines that run the quagga suite (from
the repo, that is quagga-0.98.6-5.el5_5.1. The machines have two NICs,
both of them hold some VLANs.
On the second NIC there's five VLANs that carry 10.0.0.0/16 networks on
which I would like to use RIPd. There's already (non-quagga) routers
running in this setup.
Those 10.0.0.0/16 networks should be isolated, no traffic to any other
network, just amongst each other.
As soon as I fire up RIPd it announces the box' default gw (which is an
official, registrated IPv4 IP, which is also used for management of the
box, such as SNMP, etc.) and the traffic of the 10.0.0.0/16 networks
collapses because it 'ends here'. This is the case even with 'no
redistribute kernel' set in the config. I want to use 'redistribute
connected' some day, as the box should also be able to act as a dial in
machine.
IP forwarding is enabled.
When starting RIPd with eth0.xxx interfaces in passive mode, everything
is okay.
Thanks,
Timo
- ----8<----8<----8<----
ripd.conf:
hostname laelles.riscworks.net
password bla
enable password blabla
!
router rip
version 2
redistribute connected
no redistribute bgp
no redistribute static
no redistribute kernel
network eth0.xxx
network eth0.xxx
network eth0.xxx
network eth0.xxx
network eth0.xxx
passive-interface default
!no passive-interface eth0.xxx
!no passive-interface eth0.xxx
!no passive-interface eth0.xxx
!no passive-interface eth0.xxx
!no passive-interface eth0.xxx
!
no default-information originate
!
interface eth0.xxx
no ip rip authentication mode md5
!
interface eth0.xxx
no ip rip authentication mode md5
!
interface eth0.xxx
no ip rip authentication mode md5
!
interface eth0.xxx
no ip rip authentication mode md5
!
interface eth0.xxx
no ip rip authentication mode md5
!
debug rip packet
debug rip events
debug rip packet recv
debug rip packet send
!
line vty
!
log file /var/log/quagga/ripd.log
!
I see RIPd announcing packets like this:
No. Time Source Destination
Protocol Info
205 2010-09-24 17:05:49.675216 10.8.4.28 224.0.0.9
RIPv2 Response
Frame 205 (548 bytes on wire, 548 bytes captured)
Arrival Time: Sep 24, 2010 17:05:49.675216000
[Time delta from previous captured frame: 0.000131000 seconds]
[Time delta from previous displayed frame: 0.000131000 seconds]
[Time since reference or first frame: 5.382758000 seconds]
Frame Number: 205
Frame Length: 548 bytes
Capture Length: 548 bytes
[Frame is marked: False]
[Protocols in frame: sll:ip:udp:rip]
[Coloring Rule Name: UDP]
[Coloring Rule String: udp]
Linux cooked capture
Packet type: Sent by us (4)
Link-layer address type: 1
Link-layer address length: 6
Source: Supermic_ba:d6:f8 (00:30:48:ba:d6:f8)
Protocol: IP (0x0800)
Internet Protocol, Src: 10.8.4.28 (10.8.4.28), Dst: 224.0.0.9 (224.0.0.9)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
0000 00.. = Differentiated Services Codepoint: Default (0x00)
.... ..0. = ECN-Capable Transport (ECT): 0
.... ...0 = ECN-CE: 0
Total Length: 532
Identification: 0x0000 (0)
Flags: 0x04 (Don't Fragment)
0... = Reserved bit: Not set
.1.. = Don't fragment: Set
..0. = More fragments: Not set
Fragment offset: 0
Time to live: 1
Protocol: UDP (0x11)
Header checksum: 0x89ac [correct]
[Good: True]
[Bad : False]
Source: 10.8.4.28 (10.8.4.28)
Destination: 224.0.0.9 (224.0.0.9)
User Datagram Protocol, Src Port: router (520), Dst Port: router (520)
Source port: router (520)
Destination port: router (520)
Length: 512
Checksum: 0x242b [correct]
[Good Checksum: True]
[Bad Checksum: False]
Routing Information Protocol
Command: Response (2)
Version: RIPv2 (2)
Routing Domain: 0
IP Address: 10.10.39.106, Metric: 2
Address Family: IP (2)
Route Tag: 0
IP Address: 10.10.39.106 (10.10.39.106)
Netmask: 255.255.255.255 (255.255.255.255)
Next Hop: 0.0.0.0 (0.0.0.0)
Metric: 2
IP Address: 10.10.39.110, Metric: 2
Address Family: IP (2)
Route Tag: 0
IP Address: 10.10.39.110 (10.10.39.110)
Netmask: 255.255.255.255 (255.255.255.255)
Next Hop: 0.0.0.0 (0.0.0.0)
Metric: 2
(...)
So, it announces itself as the router (Next Hop) *altough* the devices
for which the routes are established are located on one of the Ciscos,
not this machine.
Furthermore, it seems to ignore most of the settings I set in ripd.conf,
nevertheless it starts up and operates.
Help is very much appreciated.
Best,
Timo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFMobJCfg746kcGBOwRAlBwAJ47XlBLIAWoA7N7DplHKuzSY0JcNwCdGJq0
6Jg4fDHLARc7jAscwZ/39hY=
=i/MD
-----END PGP SIGNATURE-----
_______________________________________________
Quagga-users mailing list
Quagga-users@lists.quagga.net
http://lists.quagga.net/mailman/listinfo/quagga-users
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic