Hi all. I've some questions regarding the configuration of bird. 1. I have a box with lots of (virtual) network interfaces. All those interfaces use the eth-namespace (and I can not change this unfortunately). I want bird to use eth0 with RIP in broadcast mode and to exclude every other interface which name matches "eth*". Would this following be right for that purpose? protocol rip { [...] interface "eth0" { mode broadcast; }; interface "eth*" { quiet; }; [...] } 2. How do I tell bird not to accept and not to send any RIP requests/updates from/to given interfaces? If I understood the documentation correctly, "quiet" tells not to send anything (but to receive) and "nolisten" tells not to listen (but to send) to an interface. Is there a mode that permits both? 3. I'm using some vtun connection between hosts in the local network. Vtun is a package that sets up virtual ip tunnels between two hosts and is able to shape traffic and to encrypt the tunnel data for each connection seperatly (for more information: vtun.sourceforge.net). I use the tun-devices for the connections between the hosts, which is part of the vtun package. When I try to tell bird to broadcast RIP packages using one of the tun devices in a system, it tells the following: Apr 16 19:38:38 (none) daemon.err bird: rip1: rip is not defined over unnumbered links Apr 16 19:38:38 (none) daemon.warn bird: sk_open: bind: Cannot assign requested address Apr 16 19:38:38 (none) daemon.warn bird: rip1: could not listen on tun1 birdctl's "show interfaces" command shows the following data: bird> show interfaces lo up (index=1) MultiAccess AdminUp LinkUp Loopback Ignored MTU=3924 127.0.0.1/8 (Primary, broadcast 127.255.255.255, scope host) eth0 up (index=2) MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500 192.168.2.102/24 (Primary, broadcast 192.168.2.255, scope site) eth1 up (index=3) MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500 10.0.0.102/24 (Primary, broadcast 10.0.0.255, scope site) tun1 up (index=4) PtP Multicast AdminUp LinkUp MTU=1500 10.255.255.251/32 (Primary, broadcast 10.255.255.252, opposite 10.255.255.252, scope site, unnumbered) In addition, this is what ifconfig says: # ifconfig eth0 Link encap:Ethernet HWaddr 00:E0:4C:88:00:12 inet addr:192.168.2.102 Bcast:192.168.2.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:48 errors:0 dropped:0 overruns:0 frame:0 TX packets:63 errors:0 dropped:0 overruns:2 carrier:0 collisions:0 txqueuelen:100 Interrupt:11 Base address:0xe000 eth1 Link encap:Ethernet HWaddr 00:02:2D:00:D5:E3 inet addr:10.0.0.102 Bcast:10.0.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:46 errors:0 dropped:0 overruns:0 frame:0 TX packets:49 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:5 Base address:0x100 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:3924 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 tun1 Link encap:Point-to-Point Protocol inet addr:10.255.255.251 P-t-P:10.255.255.252 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:2 errors:0 dropped:0 overruns:0 frame:0 TX packets:2 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:10 What is meant by "unnumbered" (as told by bird itself and birdctl)? What can be done to set tun1 to "numbered" or to force bird to use the tun-devices for sharing routes with the other hosts? Bye, Mike -- ------------------------------------ CompuLAN Europe GmbH Development - Wireless Solutions ------------------------------------
Hi!
I've some questions regarding the configuration of bird.
2. How do I tell bird not to accept and not to send any RIP requests/updates from/to given interfaces? If I understood the documentation correctly, "quiet" tells not to send anything (but to receive) and "nolisten" tells not to listen (but to send) to an interface. Is there a mode that permits both?
If you do not want it to listen and do not want it to send, why are you configuring it on that interface? Pavel -- I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care." Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org
On Mon, 12 Feb 2001, Pavel Machek wrote:
Hi!
I've some questions regarding the configuration of bird. > > 2. How do I tell bird not to accept and not to send any RIP requests/updates from/to given interfaces? If I understood the documentation correctly, "quiet" > tells not to send anything (but to receive) and "nolisten" tells not to listen > (but to send) to an interface. Is there a mode that permits both?
If you do not want it to listen and do not want it to send, why are you configuring it on that interface?
If you don't want it to listen and don't want it to send then you just don't list it. List each eth* interface individually. Don't list the ones you don't want live. If it's a pain to write all those config lines then write a script that generates them. Works for me... '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.
Hi James. On Mon, 12 Feb 2001 11:16:29 -0900 (AKST) "James A. Crippen" <james@UnLambda.COM> wrote:
If you do not want it to listen and do not want it to send, why are you configuring it on that interface? If you don't want it to listen and don't want it to send then you just don't list it. List each eth* interface individually. Don't list the ones you don't want live.
Ok, so this answers my question to Pavel, I think :)
If it's a pain to write all those config lines then write a script that generates them. Works for me...
Already done :) Thanks for the quick answers to you both (Pavel and you). Bye, Mike -- ------------------------------------ CompuLAN Europe GmbH Development - Wireless Solutions ------------------------------------
Hi Pavel. On Mon, 12 Feb 2001 21:07:15 +0100 Pavel Machek <pavel@suse.cz> wrote:
If you do not want it to listen and do not want it to send, why are you configuring it on that interface?
Hmm... good point. But the documentation gives an example configuration which does not contain a single "interface" line for rip. The text for it explains that this configuration works with all interfaces of the system. Maybe thats why I thought bird would work with every interface by default and must be told to ignore some of them if desired. So, if there are interface lines, bird works only with the mentioned interfaces and ignores non-mentioned ones?
Pavel
Bye, Mike -- ------------------------------------ CompuLAN Europe GmbH Development - Wireless Solutions ------------------------------------
participants (3)
-
James A. Crippen -
Michael Renzmann -
Pavel Machek