Marius at al,
I'm wondering if anyone has tried the new feature that sends RIP44. If so I have a question. If you use the -a, does it remove those routes?
I need to account for this in a script I'm writing depending on if the downstream device is on a WAN or if they have a private route/connection between themselves. Since I use policy-based routing, I can keep the false record for my own subnet on table 44 and encap file; but for others (and other projects for AMPRNet), I can see this used to be placed on a second device to provide a real-time looking-glass tool, etc.
- Lynwood KB3VWG
I'm wondering if anyone has tried the new feature that sends RIP44. If so I have a question. If you use the -a, does it remove those routes?
The -a option only affects regular routes and -e/-f re-broadcasting. The RIP44 sending is just a simple copy of incoming RIPv2 packets to the specified interface using an optional specified destination address (default is 224.0.0.9 multicast). No alteration is done to the content. The target needs to handle filtering.
-
lleachii＠aol.com -
marius＠yo2loj.ro