Re: OSPF ptmp

2017-03-05 Thread Ondrej Zajicek
On Sun, Mar 05, 2017 at 04:51:47AM +, Борис Коваленко wrote: > Hello, Ondrej! > > Ough. It was deep night when I returned to this problem. Of course you are > right. Here is info for ptmp. No packets from FreeBSD. Well, it is clear. Because PtMP mode in BIRD does not use multicast (as per RFC

Re: OSPF ptmp

2017-03-04 Thread Борис Коваленко
Hello, Ondrej! Ough. It was deep night when I returned to this problem. Of course you are right. Here is info for ptmp. No packets from FreeBSD. [root@ugw]~# tcpdump -n -i em0.102 -vvv proto ospf tcpdump: listening on em0.102, link-type EN10MB (Ethernet), capture size 262144 bytes 09:47:20.696959

Re: OSPF ptmp

2017-03-04 Thread Ondrej Zajicek
On Sat, Mar 04, 2017 at 06:19:54PM +, Борис Коваленко wrote: > Hello, Ondrej! > > Something strange. So, FreeBSD 11 with bird 1.6.3, and Mikrotik 6.38.3. As > said previous - no problems with broadcast mode. When PtP - no luck. OSPF > is running on em0.102 interface. FreeBSD IP is X.X.16.82, a

Re: OSPF ptmp

2017-03-04 Thread Борис Коваленко
Hello, Ondrej! Something strange. So, FreeBSD 11 with bird 1.6.3, and Mikrotik 6.38.3. As said previous - no problems with broadcast mode. When PtP - no luck. OSPF is running on em0.102 interface. FreeBSD IP is X.X.16.82, and lo1 is X.X.16.78 [root@ugw]~# tcpdump -n -i em0.102 -vvv proto ospf tcp

Re: OSPF ptmp

2017-02-27 Thread Ondrej Zajicek
On Sat, Feb 25, 2017 at 06:38:24AM +, Борис Коваленко wrote: > пн, 20 февр. 2017, 9:06 Борис Коваленко : > > 1) No, there are no incoming HELLOs in log Hi That looks strange. Could you send me output of tcpdump (with Hello packets from the other side), config file and output of 'show interf

Re: OSPF ptmp

2017-02-24 Thread Борис Коваленко
Hello! Any suggestions? Regards, Boris пн, 20 февр. 2017, 9:06 Борис Коваленко : 1) No, there are no incoming HELLOs in log 2) AFAIK Cisco (for example) in PTMP mode also send packet from IP to 224.0.0.5 (checked with debug ip ospf hello) 3) No neighbors 4) No, strict nbma is not set Regards,

Re: OSPF ptmp

2017-02-19 Thread Борис Коваленко
1) No, there are no incoming HELLOs in log 2) AFAIK Cisco (for example) in PTMP mode also send packet from IP to 224.0.0.5 (checked with debug ip ospf hello) 3) No neighbors 4) No, strict nbma is not set Regards, Boris пн, 20 февр. 2017 г. в 3:58, Ondrej Zajicek : > On Sun, Feb 19, 2017 at 05:47

Re: OSPF ptmp

2017-02-19 Thread Ondrej Zajicek
On Sun, Feb 19, 2017 at 05:47:16AM +, Борис Коваленко wrote: > Hello, Ondrej! Hello > There was something wrong with my previous test. So I did new one. > > Answering your questions: > > 1) Where interface is broadcast and mode is ptmp - bird does not send > any packet (checked with tcpdump

OSPF ptmp

2017-02-18 Thread Борис Коваленко
Hello, Ondrej! There was something wrong with my previous test. So I did new one. Answering your questions: 1) Where interface is broadcast and mode is ptmp - bird does not send any packet (checked with tcpdump) but with "debug all" there are messages " main_ospf: HELLO packet sent via em0" ever

Re: OSPF ptmp

2017-02-17 Thread Борис Коваленко
Hello! Sorry for a long answer. I think I saw hello from previous configuration. Now test it again and with mode = ptmp bird does not send hello until neighbors are configured. Unfortunatelly, I also does not lear neighbors from incoming hellos. Yes, I know about API change, but official FreeBSD b

Re: OSPF ptmp

2017-02-07 Thread Ondrej Zajicek
On Sun, Feb 05, 2017 at 09:38:20AM +, Борис Коваленко wrote: > Hello! > > Trying to run bird on ethernet interface with type = ptmp. Yes, I know that > ethernet is broadcast interface, but there is a good practice to use ptmp > on ethernet. I found a strange bug. When type = ptmp, bird sends o

OSPF ptmp

2017-02-05 Thread Борис Коваленко
Hello! Trying to run bird on ethernet interface with type = ptmp. Yes, I know that ethernet is broadcast interface, but there is a good practice to use ptmp on ethernet. I found a strange bug. When type = ptmp, bird sends only one Hello packet and then stops (and even receive?) next packets until