23 May
2017
23 May
'17
5:40 a.m.
Ronen,
I'm not sure the concerns about multicast, and I'm not sure about
"direct transfer". That description sound like FTP of Encap. If you are
in the Portal, the machine receives and processes the exact same
packets. The issue for me is HOW the Kernel processes the packets (and
others).
In your case, it seems you can't receive the RIP44 packets if the
interface isn't on the same subnet. That seems like a setting limitation
of the Router OS. On my machine, assigning a 44/8 to an interface on my
device is invalid for proper operation of my subnet. I didn't have your
exact issue.
On my device the following happened:
- In multicast mode, ampr-ripd and/or rip44d listen on udp/520 like a
normal server, the packets must come through tunl0 first
- In raw mode, ampr-ripd listens on IPENCAP (IP Protocol No. 4) and
'inspects' packets, seeking ones from 44.0.0.1 520/udp to 224.0.0.9 520/udp
I would assume using -r argument would turn on this mode, and
"multicast" in the way you describe MIGHT be disabled. This is not a
concern for me, in both modes, the route is made. I have various issues
in raw mode, and simply prefer to have my device listen on the LAN side
of my tunnel. Multicast mode solves all my issues experienced in raw mode.
73,
- Lynwood
KB3VWG