Hi Keenan and Ondrej,
I already update the configuration as your advice but the still couldn't be
established, here is the new configuration:
Router A
protocol ospf {
router id 10.8.60.1;
debug all;
import filter ospf_in_routerb;
export filter ospf_out_routerb;
On Sat, Dec 31, 2016 at 08:00:58AM +0700, David S. wrote:
> Dear All,
>
> I have trouble to establish ospf on BIRD 1.6.3 using FreeBSD 11 amd64, here
> is my topology and BIRD configuration:
>
> router-a -- router-b (directly connected use cat6)
>
> router-a: 10.22.40.17/30
> router-b: 10.22
Not sure what the behaviour is if you set stub and PTP, but I assume you are
getting stub behaviour here. Remove stub, should work.
Keenan
On Dec 30, 2016, 5:11 PM, at 5:11 PM, "David S." wrote:
>Hi Dave,
>
>No, the correct value is pointopoint or ptp, I have tried type ptp and
>broadcast but
Hi Dave,
No, the correct value is pointopoint or ptp, I have tried type ptp and
broadcast but still same.
The neighbor won't up.
I don't know if it's a bug or not but I have tried very basic configuration
from wiki page and still same.
Thank you
Best regards,
David S.
-
Just a guess "pointopoint" -> "pointtopoint"
On Dec 30, 2016 5:04 PM, "David S." wrote:
> Dear All,
>
> I have trouble to establish ospf on BIRD 1.6.3 using FreeBSD 11 amd64,
> here is my topology and BIRD configuration:
>
> router-a -- router-b (directly connected use cat6)
>
> router-a: 10
Dear All,
I have trouble to establish ospf on BIRD 1.6.3 using FreeBSD 11 amd64, here
is my topology and BIRD configuration:
router-a -- router-b (directly connected use cat6)
router-a: 10.22.40.17/30
router-b: 10.22.40.18/30
bird.conf in router-a
router id 10.5.16.1;
debug
Ondrej,
Thank you so much for the fast response. That fixed all of it. Sorry for
the noob mistake.
jerry
On 12/30/16 3:47 PM, Ondrej Zajicek wrote:
On Fri, Dec 30, 2016 at 12:27:13PM -0800, Jerry Scharf wrote:
Hi,
I did a quick look at the archives and didn't see exactly what I was
trying d
On Fri, Dec 30, 2016 at 12:27:13PM -0800, Jerry Scharf wrote:
> Hi,
>
> I did a quick look at the archives and didn't see exactly what I was
> trying discussed.
>
> filter load_default {
> if net = [0.0.0.0/0] then accept;
Hi
Here is the mistake - you have to use either 'net = 0.0.0.0/0' or
Hi,
I did a quick look at the archives and didn't see exactly what I was
trying discussed.
I have some border machines running bird connected to junpiers that are
bgp peering with our ISPS. I have the junipers set up such that they
generate a default route and send it to the border machines. I wa
On 2016-12-30 13:30, Michal wrote:
On 2016-12-30 13:26, Ondrej Zajicek wrote:
On Fri, Dec 30, 2016 at 01:13:59PM +0100, Michal wrote:
Stupid... increasing read buffer helped of course
sysctl -w net.core.rmem_default=1064960
I see, the bird is not increasing the read buffer on it's netlink
so
Hi!
> 2016-12-30 12:02:43 Kernel dropped some netlink messages, will
> resync on next scan.
> 2016-12-30 12:02:43 Kernel dropped some netlink messages, will
> resync on next scan.
> 2016-12-30 12:02:52 Kernel dropped some netlink messages, will
> resync on next scan.
> 2016-12-30 12:03:03 Kern
On 2016-12-30 13:26, Ondrej Zajicek wrote:
On Fri, Dec 30, 2016 at 01:13:59PM +0100, Michal wrote:
Stupid... increasing read buffer helped of course
sysctl -w net.core.rmem_default=1064960
I see, the bird is not increasing the read buffer on it's netlink
socket.
Would it be bad idea to creat
On Fri, Dec 30, 2016 at 01:13:59PM +0100, Michal wrote:
> Stupid... increasing read buffer helped of course
>
> sysctl -w net.core.rmem_default=1064960
>
> I see, the bird is not increasing the read buffer on it's netlink socket.
> Would it be bad idea to create an configuration option for that?
I'm using collectd netlink plugin to monitor traffic on those
interfaces. I would expect it generates some netlink traffic, but not
that big.
On 2016-12-30 13:15, Ondrej Zajicek wrote:
On Fri, Dec 30, 2016 at 12:27:13PM +0100, Michal wrote:
Hi,
I was trying to upgrade my bird instance from v
On Fri, Dec 30, 2016 at 12:27:13PM +0100, Michal wrote:
> Hi,
>
> I was trying to upgrade my bird instance from v1.6.0 to v1.6.3 today.
> Unfortunately immediately after start the bird started generating these
> messages
> ..
> I can see the warning log line was added at Dec 20 2016, which ended u
Stupid... increasing read buffer helped of course
sysctl -w net.core.rmem_default=1064960
I see, the bird is not increasing the read buffer on it's netlink
socket. Would it be bad idea to create an configuration option for that?
On 2016-12-30 12:27, Michal wrote:
Hi,
I was trying to upgrade
Hi,
I was trying to upgrade my bird instance from v1.6.0 to v1.6.3 today.
Unfortunately immediately after start the bird started generating these
messages
2016-12-30 12:02:35 Started
2016-12-30 12:02:43 I/O loop cycle took 8679 ms for 8 events
2016-12-30 12:02:43 Kernel dropped some netlin
17 matches
Mail list logo
