30 Jan
2021
30 Jan
'21
8:56 p.m.
On Sat, Jan 30, 2021 at 1:05 PM Andrew Pepper via 44Net <
44net(a)mailman.ampr.org> wrote:
I'm having a similar issue as Lee.
I'm wondering if all the steps are in the two wiki articles?
I've tried both using a single erX( with a public IP on WAN) and hanging
a 2nd erX off one of my NAT erX and I get the same issue.
When I do a traceroute I'm going through UCSD, my IP shows as my 44
subnet (using IPchicken etc), I can ping but the RIP routes do not seem
to populate the tables.
Either I'm misreading the instructions (which is probably and highly
possible) or I'm missing something.
I did notice in
<https://wiki.ampr.org/wiki/Setting_up_a_gateway_on_Ubiquiti_EdgeRouter>
that the WAN_IN & WAN_LOCAL rulesets seem off.
I skipped the instructions available via that link - only applied the
instructions at this one:
https://wiki.ampr.org/wiki/Installing_ampr-ripd_on_a_Ubiquiti_EdgeRouter_or…
I thought about doing both, but I wasn't sure if two tunnel interfaces were
really needed. Perhaps the first one is just for sending default traffic
to UCSD that is not covered by the tunnel routes?
I'm not sure if it was needed, but in addition to adding a rule to allow
UDP 520 to the TUNNEL_LOCAL ruleset I added an equivalent rule to the
WAN_LOCAL ruleset. Doing a packet capture I could see the RIP packets
coming in on the WAN port (eth0), so I thought perhaps they needed to be
sent locally from there for the ampr-ripd instance to receive them.
-----<snip>----
73,
Lee K5DAT