[prev in list] [next in list] [prev in thread] [next in thread] 

List:       bird-users
Subject:    Re: Testing release
From:       Gustavo Ponza <g.ponza () tin ! it>
Date:       2014-11-08 10:56:13
Message-ID: 1415444173.2309.49.camel () ubuntu
[Download RAW message or body]

Hi Ondrej,

a first question: I don't know if is possible to inject
through the 'ppp' interface (linux -> Mikrotik)
the following routes/prefixes, since they remain sit on the
linux kernel, and not propagated, although are recognized
by the BIRD as follows:

root@ir0rm-7:/home/i0ojj# birdc
BIRD 1.5.0pre ready.
bird> sh route
0.0.0.0/0          via 192.168.1.1 on eth0 [kernel1 23:38:02] * (10)
44.135.48.0/24     via 173.179.100.113 on tunl0 [kernel1 10:05:11] *
(10)
44.135.49.0/27     via 76.28.121.159 on tunl0 [kernel1 10:05:11] * (10)
44.4.50.3/32       via 38.99.34.76 on tunl0 [kernel1 10:05:11] * (10)
44.135.50.0/26     via 206.80.251.222 on tunl0 [kernel1 10:05:11] * (10)
10.26.241.100/30   via 10.58.2.3 on ppp0 [ospf1 23:38:17] * I (150/30)
[8.13.154.136]
44.135.83.24/32    via 24.55.196.48 on tunl0 [kernel1 10:05:11] * (10)
44.42.128.0/24     via 65.7.249.190 on tunl0 [kernel1 10:05:11] * (10)
44.134.48.0/24     via 95.228.227.225 on tunl0 [kernel1 10:05:11] * (10)
44.135.52.0/24     via 132.213.22.244 on tunl0 [kernel1 10:05:11] * (10)
44.133.8.13/32     via 80.37.63.33 on tunl0 [kernel1 10:05:11] * (10)
44.137.24.5/32     via 89.18.172.156 on tunl0 [kernel1 10:05:11] * (10)
44.154.64.0/24     via 37.6.202.94 on tunl0 [kernel1 10:05:11] * (10)
44.178.224.0/24    via 188.93.56.29 on tunl0 [kernel1 10:05:11] * (10)
44.74.0.128/28     via 98.24.18.197 on tunl0 [kernel1 10:05:11] * (10)
44.136.9.0/24      via 110.175.8.109 on tunl0 [kernel1 10:05:11] * (10)
44.4.50.2/32       via 199.103.53.117 on tunl0 [kernel1 10:05:11] * (10)

<snip>

and so displayed in linux machine by the 'route' command:

root@ir0rm-7:/home/i0ojj# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
44.46.0.11      199.187.163.73  255.255.255.255 UGH   0      0        0
tunl0
44.153.54.20    190.1.38.237    255.255.255.255 UGH   0      0        0
tunl0
44.46.0.12      207.119.186.111 255.255.255.255 UGH   0      0        0
tunl0
44.153.54.21    190.97.49.15    255.255.255.255 UGH   0      0        0
tunl0
44.153.54.22    190.97.49.15    255.255.255.255 UGH   0      0        0
tunl0
44.153.54.23    190.97.49.15    255.255.255.255 UGH   0      0        0
tunl0
44.151.6.9      87.106.152.158  255.255.255.255 UGH   0      0        0
tunl0
44.38.64.1      74.183.193.166  255.255.255.255 UGH   0      0        0
tunl0

<snip>

That routes are collected by a non-standard RIPv2 client, via the
'tunl0' interface, from a remote RIPv2 server, with the RIP protocol
modified and so *not* compatible with the standard RIPv2.

The second question is: having an 'openvpn' tunnel and so a 'tap0'
interface if I want stop the OSPF (namely, don't receive and don't
transit anything) is the following the right setup?

                interface "tap0" {
                        stub;
                };

Very thanks!

gus


[prev in list] [next in list] [prev in thread] [next in thread]