[nos-bbs] RIP Error (JNOS)
Chris Maness
christopher.maness at gmail.com
Mon Feb 6 15:54:40 EST 2023
Ok, it is working now. I think the problem with trying to port
forward the udp.520 directly to JNOS is the "destination unreachable"
bug that is the reason that I can't use his amprd on all but Slackware
and PiOS without installing a kernel module. I get the same error
with trying to do routing directly in JNOS. The AMPR-RIP is better
than the munge script, but I really liked the amprd as it routed only
to your neighbors instead of EVERY host on 44-net. Oh well. I guess
I can try the kernel module and see if that fixes it. Here is the
wireshark dump:
Type: 3 (Destination unreachable)
On Mon, Feb 6, 2023 at 11:05 AM <maiko at pcsinternet.ca> wrote:
>
>
> 1) You 'could' try and do the following ...
>
> Add this define to your config.h :
>
> #define IGNORE_RIP_TAG
>
> Then do a small recompile as follows :
>
> rm rip.o ; make
>
> 2) Here is the reasoning, Gus was probably using a similar setup :
>
> #ifndef IGNORE_RIP_TAG
> /*
> * 09Mar2010, Maiko, Only accept IPIP routes right now. Brian
> indicateddefault via 10.44.170.209 dev enp0s29u1u3 proto dhcp src 10.44.170.215 metric 1024
> * to me that there is at least one IPUDP route in the RIP
> updates, but
> * for this initial version, just ignore it, even though JNOS
> has the
> * code to handle it - just want to get this initial version
> working.
> *
> * 04Aug2013, Maiko, Seems that Gus is getting RIP routes for
> which the
> * tag field is NOT being set, which effectively makes JNOS
> ignore ALL the
> * RIP broadcasts. Add '#define IGNORE_RIP_TAG' to config.h to
> fix this.
> */
> if (ep->rip_tag != 4)
> {
> rip_trace (2, "Route %s/%u is not ipip - ignore type %d (for
> now)",
> inet_ntoa (target), bits, ep->rip_tag);
>
> return;
> }
> #endif
>
> Maiko / VE4KLM
>
>
> On 2023-02-06 12:39, Chris Maness wrote:
> > I am using YO2JOL (I think) C version of ampr-ripd, and it is working
> > fine. However, I would like to simplify my setup and just do RIP in
> > JNOS since I have figured out port forwarding to the tun0 device. It
> > looks like I am getting packets, but JNOS does not like them, any
> > suggestions?
> >
> > 6 10:36:17 2023 - Route 44.185.113.0/24 is not ipip - ignore type 44
> > (for now)
--
Thanks,
Chris Maness
More information about the nos-bbs
mailing list