Re: OSPF socket error on "bge0" invalid argument

31 Dec 2016

      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;
        area 0 {
           interface "bge0" {
                cost 5;
                hello 10; retransmit 2; wait 10; dead 40;
                type broadcast;
                };
           interface "*" {
                cost 1000;
                stub;
                };
        };
}

Router B
protocol ospf {
        router id 10.8.60.2;
        debug all;
        import filter ospf_in_routera;
        export filter ospf_in_routera;
        area 0 {
           interface "bge0" {
                cost 5;
                hello 10; retransmit 2; wait 10; dead 40;
                };
           interface "*" {
                cost 1000;
                stub;
                };
        };
}

2016-12-31 10:44:51 <TRACE> ospf1: HELLO packet sent via bge0
2016-12-31 10:44:51 <ERR> ospf1: Socket error on bge0: Invalid argument

How to debug this instance in a deep level?

Thank you

Best regards,
David S.
------------------------------------------------
e. david@zeromail.us
w. pnyet.web.id
p. 087881216110

On Sat, Dec 31, 2016 at 9:19 AM, Ondrej Zajicek <santiago@crfreenet.org>
wrote:
...
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.40.18/30
Hi
...
bird.conf in router-a
router id 10.5.16.1;
        debug all;
        import filter ospf_in_routerb;
        export filter ospf_out_routerb;
        tick 2;
Why tick 2?
...
area 0 {
           interface "bge0" {
                stub;
There should not be 'stub' if the interface is supposed to be active.
...
networks {
                103.22.40.16/30;
                };
'networks' is irrelevant unless you have multiple areas.
...
interface "*" {
                cost 1000;
                stub;
                };
        };
}
I found the following error message from bird.log:
2016-12-31 07:52:38 <ERR> ospf1: Socket error on bge0: Invalid argument
2016-12-31 07:52:43 <ERR> ospf1: Socket error on bge0: Invalid argument
2016-12-31 07:52:48 <ERR> ospf1: Socket error on bge0: Invalid argument
It is interesting what causes socket error if the interface is declared
to be stub.
--
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."