I'm using bird 1.0.4 on an Intel Linux box (homemade distro). I've configured bird to do RIP broadcast. I then plugged the system into my local network and into a separate network and did the same with my desktop system. I configured bird to dump lots of debug info to the syslog, and I see it say that it broadcasts its routing table to both eth0 and eth1, but watching either network shows me absolutely no traffic from either interface. I pinged back and forth to be sure, and I can see the pings and the associated ARP traffic quite clearly, but no RIP broadcasts at all. The configuration is as simple as possible. From what I can tell from the manual I've got everything necessary to make RIP run, but it doesn't want to share its routes with anyone. Any ideas about what might be malfunctioning? Below is the configuration file I'm using. ---8<--- cut here ---8<--- log syslog all; debug protocols all; protocol direct { interface "*"; } protocol kernel { learn yes; persist no; scan time 20; import all; export all; } protocol device { scan time 10; } protocol static { debug all; } protocol rip { debug all; honor always; authentication none; interface "*" { mode broadcast; }; } -- James A. Crippen <james@unlambda.com> ,-./-. Lambda Unlimited Anchorage, Alaska | |/ | 61.2069 N Y=\f.(\x.f(xx))(\x.f(xx)) | |\ | 149.766 W YF=F(YF) \_,-_/
Date: Thu, 28 Dec 2000 11:53:29 -0900 (AKST) From: "James A. Crippen" <james@UnLambda.COM> I'm using bird 1.0.4 on an Intel Linux box (homemade distro). I've configured bird to do RIP broadcast. I then plugged the system into my local network and into a separate network and did the same with my desktop system. I configured bird to dump lots of debug info to the syslog, and I see it say that it broadcasts its routing table to both eth0 and eth1, but watching either network shows me absolutely no traffic from either interface. I pinged back and forth to be sure, and I can see the pings and the associated ARP traffic quite clearly, but no RIP broadcasts at all. How are you watching?? Can you see UDP traffic? If not, use Ethereal.
On Thu, 28 Dec 2000, Network Administration wrote:
Date: Thu, 28 Dec 2000 11:53:29 -0900 (AKST) From: "James A. Crippen" <james@UnLambda.COM>
I'm using bird 1.0.4 on an Intel Linux box (homemade distro). I've configured bird to do RIP broadcast. I then plugged the system into my local network and into a separate network and did the same with my desktop system. I configured bird to dump lots of debug info to the syslog, and I see it say that it broadcasts its routing table to both eth0 and eth1, but watching either network shows me absolutely no traffic from either interface. I pinged back and forth to be sure, and I can see the pings and the associated ARP traffic quite clearly, but no RIP broadcasts at all.
How are you watching?? Can you see UDP traffic? If not, use Ethereal.
I am using tethereal, the command line version of the same. It can see UDP, pretty sure. -- James A. Crippen <james@unlambda.com> ,-./-. Lambda Unlimited Anchorage, Alaska | |/ | 61.2069 N Y=\f.(\x.f(xx))(\x.f(xx)) | |\ | 149.766 W YF=F(YF) \_,-_/
On Thu, 28 Dec 2000, James A. Crippen wrote: I didn't get any conclusive replies to this problem which is still plaguing me so I'm reposting it. I'd also like to note the messages from my syslog below this included message.
I'm using bird 1.0.4 on an Intel Linux box (homemade distro). I've configured bird to do RIP broadcast. I then plugged the system into my local network and into a separate network and did the same with my desktop system. I configured bird to dump lots of debug info to the syslog, and I see it say that it broadcasts its routing table to both eth0 and eth1, but watching either network shows me absolutely no traffic from either interface. I pinged back and forth to be sure, and I can see the pings and the associated ARP traffic quite clearly, but no RIP broadcasts at all.
The configuration is as simple as possible. From what I can tell from the manual I've got everything necessary to make RIP run, but it doesn't want to share its routes with anyone.
Any ideas about what might be malfunctioning?
Below is the configuration file I'm using.
---8<--- cut here ---8<---
log syslog all;
debug protocols all;
protocol direct { interface "*"; }
protocol kernel { learn yes; persist no; scan time 20; import all; export all; }
protocol device { scan time 10; }
protocol static { debug all; }
protocol rip { debug all; honor always; authentication none; interface "*" { mode broadcast; }; }
Here's the messages from my syslog, starting from BIRD's startup. Dec 29 11:46:45 utilitia bird: direct1: Initializing Dec 29 11:46:45 utilitia bird: kernel1: Initializing Dec 29 11:46:45 utilitia bird: device1: Initializing Dec 29 11:46:45 utilitia bird: static1: Initializing Dec 29 11:46:45 utilitia bird: rip1: Initializing Dec 29 11:46:45 utilitia bird: direct1: Starting Dec 29 11:46:45 utilitia bird: direct1: State changed to feed Dec 29 11:46:45 utilitia bird: kernel1: Starting Dec 29 11:46:45 utilitia bird: kernel1: State changed to feed Dec 29 11:46:45 utilitia bird: device1: Starting Dec 29 11:46:45 utilitia bird: device1: Scanning interfaces Dec 29 11:46:45 utilitia bird: Guessed router ID 10.1.1.1 according to interface eth1 Dec 29 11:46:45 utilitia bird: device1: State changed to feed Dec 29 11:46:45 utilitia bird: static1: Starting Dec 29 11:46:45 utilitia bird: static1: State changed to feed Dec 29 11:46:45 utilitia bird: rip1: Starting Dec 29 11:46:45 utilitia bird: rip1: Listening on (dummy), port 520, mode broadcast (0.0.0.0) Dec 29 11:46:45 utilitia bird: rip1: State changed to feed Dec 29 11:46:45 utilitia bird: direct1 < primary address 127.0.0.0/8 on interface lo added Dec 29 11:46:45 utilitia bird: direct1 > added [best] 127.0.0.0/8 dev lo Dec 29 11:46:45 utilitia bird: direct1 < primary address 12.17.190.208/28 on interface eth0 added Dec 29 11:46:45 utilitia bird: direct1 > added [best] 12.17.190.208/28 dev eth0 Dec 29 11:46:45 utilitia bird: direct1 < primary address 10.1.1.0/24 on interface eth1 added Dec 29 11:46:45 utilitia bird: direct1 > added [best] 10.1.1.0/24 dev eth1 Dec 29 11:46:45 utilitia bird: direct1: State changed to up Dec 29 11:46:45 utilitia bird: kernel1: Connected to table master Dec 29 11:46:45 utilitia bird: kernel1 < added 10.1.1.0/24 dev eth1 Dec 29 11:46:45 utilitia bird: kernel1 < added 127.0.0.0/8 dev lo Dec 29 11:46:45 utilitia bird: kernel1 < added 12.17.190.208/28 dev eth0 Dec 29 11:46:45 utilitia bird: kernel1: State changed to up Dec 29 11:46:45 utilitia bird: device1: State changed to up Dec 29 11:46:45 utilitia bird: static1 < interface lo goes up Dec 29 11:46:45 utilitia bird: static1 < interface eth0 goes up Dec 29 11:46:45 utilitia bird: static1 < interface eth1 goes up Dec 29 11:46:45 utilitia bird: static1 < interface tunl0 created Dec 29 11:46:45 utilitia bird: static1 < interface gre0 created Dec 29 11:46:45 utilitia bird: static1 < interface teql0 created Dec 29 11:46:45 utilitia bird: static1 < interface brg0 created Dec 29 11:46:45 utilitia bird: static1 < interface eth2 created Dec 29 11:46:45 utilitia bird: static1: State changed to up Dec 29 11:46:45 utilitia bird: rip1: Connected to table master Dec 29 11:46:45 utilitia bird: rip1 < interface lo goes up Dec 29 11:46:45 utilitia bird: rip1 < interface eth0 goes up Dec 29 11:46:45 utilitia bird: rip1 < interface eth1 goes up Dec 29 11:46:45 utilitia bird: rip1 < interface tunl0 created Dec 29 11:46:45 utilitia bird: rip1 < interface gre0 created Dec 29 11:46:45 utilitia bird: rip1 < interface teql0 created Dec 29 11:46:45 utilitia bird: rip1 < interface brg0 created Dec 29 11:46:45 utilitia bird: rip1 < interface eth2 created Dec 29 11:46:45 utilitia bird: rip1 < filtered out 10.1.1.0/24 dev eth1 Dec 29 11:46:45 utilitia bird: rip1 < out of scope 127.0.0.0/8 dev lo Dec 29 11:46:45 utilitia bird: rip1 < filtered out 12.17.190.208/28 dev eth0 Dec 29 11:46:45 utilitia bird: rip1: State changed to up Dec 29 11:46:45 utilitia bird: kernel1: Scanning routing table Dec 29 11:46:45 utilitia bird: kernel1: 0.0.0.0/0: [alien] created Dec 29 11:46:45 utilitia bird: kernel1: Pruning table master Dec 29 11:46:45 utilitia bird: kernel1: Pruning inherited routes Dec 29 11:46:45 utilitia bird: kernel1 > added [best] 0.0.0.0/0 via 12.17.190.209 on eth0 Dec 29 11:46:45 utilitia bird: kernel1 < added 0.0.0.0/0 via 12.17.190.209 on eth0 Dec 29 11:46:45 utilitia bird: rip1 < filtered out 0.0.0.0/0 via 12.17.190.209 on eth0 Dec 29 11:46:45 utilitia bird: rip1: Listening on eth1, port 520, mode broadcast (10.1.1.255) Dec 29 11:46:45 utilitia bird: rip1: Listening on eth0, port 520, mode broadcast (12.17.190.223) Dec 29 11:46:51 utilitia bird: rip1: Broadcasting routing table to eth0 Dec 29 11:46:51 utilitia bird: rip1: Broadcasting routing table to eth1 Dec 29 11:46:55 utilitia bird: device1: Scanning interfaces Dec 29 11:47:02 utilitia bird: rip1: Broadcasting routing table to eth0 Dec 29 11:47:02 utilitia bird: rip1: Broadcasting routing table to eth1 Dec 29 11:47:05 utilitia bird: device1: Scanning interfaces Dec 29 11:47:05 utilitia bird: kernel1: Scanning routing table Dec 29 11:47:05 utilitia bird: kernel1: 0.0.0.0/0: [alien] seen Dec 29 11:47:05 utilitia bird: kernel1: Pruning table master Dec 29 11:47:05 utilitia bird: kernel1: Pruning inherited routes Dec 29 11:47:08 utilitia bird: rip1: Broadcasting routing table to eth0 Dec 29 11:47:08 utilitia bird: rip1: Broadcasting routing table to eth1 Dec 29 11:47:15 utilitia bird: rip1: Broadcasting routing table to eth0 Dec 29 11:47:15 utilitia bird: rip1: Broadcasting routing table to eth1 Dec 29 11:47:15 utilitia bird: device1: Scanning interfaces Dec 29 11:47:25 utilitia bird: device1: Scanning interfaces Dec 29 11:47:25 utilitia bird: rip1: Broadcasting routing table to eth0 Dec 29 11:47:25 utilitia bird: rip1: Broadcasting routing table to eth1 Dec 29 11:47:25 utilitia bird: kernel1: Scanning routing table Dec 29 11:47:25 utilitia bird: kernel1: 0.0.0.0/0: [alien] seen Dec 29 11:47:25 utilitia bird: kernel1: Pruning table master Dec 29 11:47:25 utilitia bird: kernel1: Pruning inherited routes Dec 29 11:47:33 utilitia bird: rip1: Broadcasting routing table to eth0 Dec 29 11:47:33 utilitia bird: rip1: Broadcasting routing table to eth1 Dec 29 11:47:35 utilitia bird: device1: Scanning interfaces And this continues ad nauseam... It seems to be saying that it's actually broadcasting RIP out of the eth0 and eth1 interfaces. I watch both interfaces from my desktop machine (which is directly connected to both networks that these interfaces are on, and has an appropriate IP address for each network) and I see absolutely no RIP traffic whatsoever. I can see other traffic from this machine (NTP for instance, and UDP traceroutes) just fine. I've used both tethereal and tcpdump to watch the traffic on both network interfaces, and the results are the same. Any ideas on why these broadcasts aren't actually happening? Where in the source should I look for clues? advTHANKSance 'james -- James A. Crippen <james@unlambda.com> ,-./-. Lambda Unlimited Anchorage, Alaska | |/ | 61.2069 N Y=\f.(\x.f(xx))(\x.f(xx)) | |\ | 149.766 W YF=F(YF) \_,-_/
I realized why RIP wasn't broadcasting routes. In the below configuration section: protocol rip { debug all; honor always; authentication none; interface "*" { mode broadcast; }; } I also needed to specify importing and exporting routes. Thus protocol rip { #... import all; export all; } Now it works happily. This wasn't terribly clear in the manual, but I eventually figured it out. So I eat humble pie. 'james -- James A. Crippen <james@unlambda.com> ,-./-. Anchorage, Alaska, Lambda Unlimited: Recursion 'R' Us | |/ | USA, 61.2069 N, 149.766 W, Y = \f.(\x.f(xx)) (\x.f(xx)) | |\ | Earth, Sol System, Y(F) = F(Y(F)) \_,-_/ Milky Way.
participants (2)
-
James A. Crippen -
Network Administration