Rare project developers

[Gabriel Tetzner <gabrieltetznermenegueti16@gmail.com>]

Hi,

Thanks for responding,

I seem to have solved the problem with the command:
router ospf4 1 passive

I think I understood the issue, thank you very much again....

Em ter., 28 de jun. de 2022 às 14:38, mc36 <cs@mp.ls> escreveu:

hi,
normally not... (except if you forgot to passive a peering and got hacked by the peer:))
so in freerouter, we got the following severity levels of messages:
debug, info, warning, error, traceback, exception... most messages that worth logging
got the info severity, the neighbor up usually became warning, and neighbor down got
the error... normally, the same logic is followed in all the other routing protocols...
br,
cs


mc36@noti:~$ cat /nfs/own/web/src/src/net/freertr/rtr/rtrOspf* | grep logger.info
             logger.info("got from out of subnet peer " + pck.IPsrc);
             logger.info("got invalid area from " + pck.IPsrc);
             logger.info("got too small from " + peer);
             logger.info("got bad version from " + peer);
             logger.info("got truncated from " + peer);
             logger.info("got too small from " + peer);
             logger.info("got invalid area from " + peer);
             logger.info("got bad authentication from " + peer);
             logger.info("got bad authentication from " + peer);
             logger.info("got bad checksum from " + peer);
                 logger.info("got invalid packet from " + peer);
                 logger.info("got bad lsa from " + peer);
                 logger.info("got bad lsa from " + peer);
                 logger.info("got bad lsa from " + peer);
             logger.info("got from out of subnet peer " + pck.IPsrc);
             logger.info("got invalid area from " + pck.IPsrc);
             logger.info("got too small from " + peer);
             logger.info("got bad version from " + peer);
             logger.info("got truncated from " + peer);
             logger.info("got too small from " + peer);
             logger.info("got invalid area from " + peer);
             logger.info("got bad checksum from " + peer);
             logger.info("got invalid instance from " + peer);
                 logger.info("got invalid packet from " + peer);
                 logger.info("got bad lsa from " + peer);
                 logger.info("got bad lsa from " + peer);
                 logger.info("got bad lsa from " + peer);
mc36@noti:~$ cat /nfs/own/web/src/src/net/freertr/rtr/rtrOspf* | grep logger.warn
             logger.warn("neighbor area" + area.area + " " + peer + " up");
             logger.warn("neighbor area" + area.area + " " + peer + " up");
mc36@noti:~$ cat /nfs/own/web/src/src/net/freertr/rtr/rtrOspf* | grep logger.err
             logger.error("neighbor area" + area.area + " " + peer + " forgot us");
         logger.error("neighbor area" + area.area + " " + peer + " down");
             logger.error("neighbor area" + area.area + " " + peer + " forgot us");
         logger.error("neighbor area" + area.area + " " + peer + " down");
mc36@noti:~$


On 6/28/22 18:06, Gabriel Tetzner wrote:
> Hi all,
> testing the intra-domain routing experiment with OSPF:
> http://docs.freertr.org/guides/getting-started/004-igp/ <http://docs.freertr.org/guides/getting-started/004-igp/>
>
> image.png
> image.png
>
> These messages appear on all 4 routers in the experiment, the routing is working, for example it is pinging from r1 to r4.
>
> According to the messages is this something I should be concerned about?