The portal has it at 3.15.163.76. I think fixing that may be enough to
get RIP broadcast but you will also need a DNS entry for 44.76.0.12 to
have traffic routed via gateway.
On Thu, Jan 23, 2020 at 3:40 PM Stephen Thomas via 44Net
<44net(a)mailman.ampr.org> wrote:
To learn the routing protocol, I created an Amazon EC2 instance of a Linux
Ubuntu router inside a virtual private cloud (VPC) where I have full
control over IP and can open 0.0.0.0/0 in both directions over all
protocols (EC2 without a VPC only permits TCP/UDP/ICMP access control).
When I run the daemon in verbose mode it is stuck calling home:
ubuntu@ip-192-168-44-12:~$ sudo ampr-ripd -d -v -L KZ0FOX@EM89mx
Using metric 0 for routes.
Using TCP window 840 for routes.
Using gateway 192.168.44.1 for direct 44net endpoints via interface eth0.
Calling home
Waiting for RIPv2 broadcasts...
Calling home
Calling home
Calling home
This system is online in the portal as 3.135.62.22 (
ec2-3-135-62-22.us-east-2.compute.amazonaws.com) and subnet 44.76.0.12/32.
Setting up a reference implementation like this one may be good for
learning the basic premise and ability to test out a configuration with
less variables than one may have at home with an ISP.
I welcome any constructive comments or suggestions.
Best regards,
Stephen Thomas
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net