bird does not speak OSPF on a GRE tunnel interface
Hello, Could you please help with an OSPF configuration. I have configured a GRE tunnel between two peers - '172.16.0.9' and '172.16.0.4'. I configured then a local address on the newly created tunnel interface '172.16.1.1'. I would like to configure bird to speak on the GRE interface. I tried with the following configuration but I cannot see that bird is announcing anything: *# ifconfig* eth0 Link encap:Ethernet HWaddr 00:D0:12:05:C6:D6 inet addr:172.16.0.4 Bcast:172.16.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:12613 errors:0 dropped:1 overruns:0 frame:0 TX packets:9503 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:1237627 (1.1 MiB) TX bytes:2152677 (2.0 MiB) eth1 Link encap:Ethernet HWaddr 00:D0:12:06:C7:D7 inet addr:10.0.4.1 Bcast:10.0.4.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:294 errors:0 dropped:1 overruns:0 frame:0 TX packets:421 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:53820 (52.5 KiB) TX bytes:97344 (95.0 KiB) *gretesttunnel* Link encap:UNSPEC HWaddr AC-10-00-04-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:172.16.1.2 P-t-P:172.16.1.1 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:320 (320.0 B) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 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 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) *bird config:* protocol kernel { # persist; # Don't remove routes on BIRD shutdown scan time 20; # Scan kernel routing table every 20 seconds export all; # Default is export none learn; device routes; } protocol device { scan time 10; # Scan interfaces every 10 seconds } #protocol direct { # interface "*"; # export all; #} protocol ospf OSPF { rfc1583compat; export all; import all; area 172.16.0.0 { networks { *172.16.1.0/24 <http://172.16.1.0/24>;* }; } Thanks in advance! Alexander Velkov
On Mon, Jun 27, 2016 at 02:40:24PM +0200, Alexander Velkov wrote:
Hello,
Could you please help with an OSPF configuration.
I have configured a GRE tunnel between two peers - '172.16.0.9' and '172.16.0.4'. I configured then a local address on the newly created tunnel interface '172.16.1.1'. I would like to configure bird to speak on the GRE interface.
You have to specify interfaces on which OSPF should run. 'networks' statement does not do that (it is just for area-boundary routers). -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
Hi Ondrej, Thanks for you answer! I did exactly this and bird finally became more 'chatty' :). This is very nice, although I expected that bird is "sensing" the state of the interfaces (e.g. through the device/direct protocols). What is "scanned" actually by the 'device' protocol ? Thanks, Alex On Mon, Jun 27, 2016 at 3:13 PM, Ondrej Zajicek <santiago@crfreenet.org> wrote:
On Mon, Jun 27, 2016 at 02:40:24PM +0200, Alexander Velkov wrote:
Hello,
Could you please help with an OSPF configuration.
I have configured a GRE tunnel between two peers - '172.16.0.9' and '172.16.0.4'. I configured then a local address on the newly created tunnel interface '172.16.1.1'. I would like to configure bird to speak on the GRE interface.
You have to specify interfaces on which OSPF should run. 'networks' statement does not do that (it is just for area-boundary routers).
-- Elen sila lumenn' omentielvo
Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
On Mon, Jun 27, 2016 at 03:26:41PM +0200, Alexander Velkov wrote:
Hi Ondrej,
Thanks for you answer! I did exactly this and bird finally became more 'chatty' :). This is very nice, although I expected that bird is "sensing" the state of the interfaces (e.g. through the device/direct protocols).
Yes, it does that. But you still have to specify which interfaces it is allowed to use for specific protocols. You can use wildcards (e.g. "eth*") instead of specific interfaces.
What is "scanned" actually by the 'device' protocol ?
List of interfaces and its addresses/prefixes. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
Hi Ondrej,
Yes, it does that. But you still have to specify which interfaces it is allowed to use for specific protocols. You can use wildcards (e.g. "eth*") instead of specific interfaces.
In quagga it is OK to specify a network only, quagga automatically detects when the interfaces' IP address is in the configured range. This is quite handy when having dynamic interface configurations, because you don't need to alter the quagga config or care how the interface is called.
List of interfaces and its addresses/prefixes.
OK. Thanks, Alex On Tue, Jun 28, 2016 at 12:19 PM, Ondrej Zajicek <santiago@crfreenet.org> wrote:
On Mon, Jun 27, 2016 at 03:26:41PM +0200, Alexander Velkov wrote:
Hi Ondrej,
Thanks for you answer! I did exactly this and bird finally became more 'chatty' :). This is very nice, although I expected that bird is "sensing" the state of the interfaces (e.g. through the device/direct protocols).
Yes, it does that. But you still have to specify which interfaces it is allowed to use for specific protocols. You can use wildcards (e.g. "eth*") instead of specific interfaces.
What is "scanned" actually by the 'device' protocol ?
List of interfaces and its addresses/prefixes.
-- Elen sila lumenn' omentielvo
Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
participants (2)
-
Alexander Velkov -
Ondrej Zajicek