25 Mar
2022
25 Mar
'22
2:14 a.m.
Hi,
Let me follow up on this open topic.
44.0.0.1 is not reachable via tunnel, so it should be dropped in the
command line to use the default gateway instead. Because the RIPv2 data
publishes the 44.0.0.1 endpoint as a /8 subnet, the subnet must be
specified a 44.0.0.1/8 in the -a command option for it to be actually
rejected (if not rejected, it will be added by ampr-ripd as a /32 route
due to special handling of this subnet)
ampr-ripd -s -t 44 -i tun44 -m 90-g pppoe0
-a44.0.0.1/8,44.128.1.0/24,44.128.2.0/24,your.gw.com/(adapt this list to your needs -
commna separated, no spaces)/
I also updated the wiki with the corrected info.
73,
Marius, YO2LOJ
On 16/03/2022 05:55, C B via 44Net wrote:
Hi
please excuse my typo
To make 44.0.0.1 work from 10.0.4.xxx a static route was added 44.0.0.1/32 10
108.xxx.xxx.xxx
Chris
n6lxx
On Tuesday, March 15, 2022, 08:53:38 PM PDT, C B via
44Net<44net(a)mailman.ampr.org> wrote:
Hi
To make 4.0.0.1 work from 10.0.4.xxx a static route was added 4.0.0.1/32 10
108.xxx.xxx.xxx
Chris
n6lxx
On Tuesday, March 15, 2022, 08:36:29 PM PDT, Marius Petrescu via
44Net<44net(a)mailman.ampr.org> wrote:
Ok, it seems I had a local setup problem, 44.0.0.1 access should be fine.
To test your setup, you can access the CLI via the button on the top
right of the router's web page.
There you can use ping and traceroute to test.
You could try my VPS host at 44.182.21.1
The described setup was meant to be used only from computers in your LAN
using 44 addresses. For the 44net to be accessible from other LAN
computers, you need to setup a masquerade rule in Firewall/NAT so that
your local addresses are translated to the GW's IP (which is not
necessary the best idea). The proper solution is to assign your subnet
to an ethernet interface and use 44net addresses for your machines...
This is the reason your ampr.org access is not working, since it now
goes through the gateway tunnel which expects 44net addresses for the
hosts behind it.
Marius, YO2LOJ