I have followed Marius' instructions and have my EdgeRouter X working and passing traffic via 44net. Thank you, Marius!
My issue is this: I am using 44.2.10.1 for the tunnel, 44.2.10.2 for the computer (a Raspberry Pi 3), and 44.2.10.3 for JNOS using a point to point tunnel. I have the following routing in the EdgeRouter:
w6ray@edgerouter:~$ sudo route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 104.49.12.134 0.0.0.0 UG 0 0 0 eth1 44.2.10.0 0.0.0.0 255.255.255.248 U 0 0 0 eth2 44.2.10.1 0.0.0.0 255.255.255.255 UH 0 0 0 tun44 44.2.10.8 44.2.10.9 255.255.255.248 UG 0 0 0 eth3 104.49.12.128 0.0.0.0 255.255.255.248 U 0 0 0 eth1 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
44.2.10.0/29 eth2 is for the local 44net.
I use the 44.2.10.8/29 on eth3 for the Ubiquity microwave link to the repeater site where the TNC's and radios are, among other things (DSTAR, DMR, etc.) I can use the link's LAN 172.16.0.0/16 instead of the 44.2.10.8/29, I just need to figure out how to route traffic. (The link radios have IP aliases in the 44.2.10.8/29) I do not wish these to be accessible outside my network.
The 104.49.12.128/29 on eth0 is my public network address.
192.168.1.0/24 on eth0 is so I can access the Edgerouter from the local LAN.
While I would like for JNOS to be accessible outside 44net, it is not required. I would like to allow our local hams who do not have a TNC access. I would, however, like to be able to access the Internet from the Pi (44.2.10.2) so I can use my browser to do searches, and update the OS via apt.
My question is "How do I accomplish this? Do I have the EdgeRouter X set up correctly with the proper address(es)?
SJVBBS w6ray.ampr.org
Nice that you have got it working.
About the subnets:
Set up your local networking as you like, using the router's standard interfaces. As long as you suppress the routes for your subnets in the ampr script (the -a options, e.g. adding your gateway's public IP address), those routes should work.
The idea is that the router evaluates the ampr routes in the 44 table. Since there is no default route in that table, it will jump to the main table afterwards, and evaluate the routes set in the GUI/CLI.
The only time you need to interact with the tun44 interface is at firewall level, where you can use it to apply rules to all 44net traffic other than your local one.
Marius, YO2LOJ
May 8, 2019 7:01 AM, "Ray Quinn" w6ray@sbcglobal.net wrote:
I have followed Marius' instructions and have my EdgeRouter X working and passing traffic via 44net. Thank you, Marius!
My issue is this: I am using 44.2.10.1 for the tunnel, 44.2.10.2 for the computer (a Raspberry Pi 3), and 44.2.10.3 for JNOS using a point to point tunnel. I have the following routing in the EdgeRouter:
w6ray@edgerouter:~$ sudo route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 104.49.12.134 0.0.0.0 UG 0 0 0 eth1 44.2.10.0 0.0.0.0 255.255.255.248 U 0 0 0 eth2 44.2.10.1 0.0.0.0 255.255.255.255 UH 0 0 0 tun44 44.2.10.8 44.2.10.9 255.255.255.248 UG 0 0 0 eth3 104.49.12.128 0.0.0.0 255.255.255.248 U 0 0 0 eth1 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
44.2.10.0/29 eth2 is for the local 44net.
-
marius＠yo2loj.ro -
Ray Quinn