What kind of obvious stuff have you tried?
I don't see a route in your script to specifically take your local
subnet and direct it to the other NIC that you mentioned
I run a similar setup, and here is my startup:
https://www.qsl.net/kb9mwr/wapr/tcpip/startampr
On Thu, Aug 29, 2019 at 7:37 PM Albert Lawson via 44Net
<44net(a)mailman.ampr.org> wrote:
Greatings...!!!
I'm setting up an AMPR Gateway on an Ubuntu 16.04 box. This box is behind a Ubiquiti
Unifi USG. I'm forwarding IP Protocol 4 to the internal IP of the box.
The layout of the box is two NIC cards...one that sits on my home network, the other card
will handle my 44 net allocations with connection to the rest of the AMPR Net via the AMPR
Net tunnel.
When I first bring the box up, and before I bring up the tunnel, I'm able to ping the
44 net hosts inside of my network. Using TCPDUMP I can follow the flow of packets pretty
easily. The problem starts when I bring up the tunnel. As soon the tunnel comes up, when
I try to ping one of my 44 hosts, I can see the packets are now going out on the tunnel
interface and not on the NIC card on my 44 network. I've gone through this line by
line on my scripts, and the problem starts when the actual default route to the AMPR
Gateway is added. From that point on, all the packets are sent thru the tunnel. I've
tried three different versions of scripts that I've found on the Internet and the
result is the same.
Here's one script that I got off the AMPR Wiki:
#!/bin/sh
###
## Create AMPRNet Tunnel and routing
##
## Configure Tunnel (put your ISP you received from your ISP Here).
ip tunnel add ampr0 mode ipip local 192.168.12.158 ttl 255
## Bring it up
ip link set dev ampr0 up
## Enable Multicast in order to receive routes
ifconfig ampr0 multicast
## Configure Policy Based routing
# Packets to 44/8 network use routing table 44
ip rule add to 44.0.0.0/8 table 44 priority 44
# Packets from our 44 subnet use table 44 (put your AMPRNet Subnet here)
ip rule add from 44.26.2.32/27 table 44 priority 45
## Configure static routes
# Default route for table 44 is to send traffic to amprnet gateway at UCSD
ip route add default dev ampr0 via 169.228.34.84 onlink table 44
# Route packets for our net to local interface (put your AMPRNet Subnet here)
ip route add 44.26.2.32/27 dev ens192 table 44
## Start ampr-ripd to learn rest of mesh routes
# Be sure to substitute the password you found earlier for <SecretPassword>
# Put your static IP you received from your ISP here.
ampr-ripd -s -i ampr0 -a 192.168.12.158 -t 44
I've tried the obvious stuff...removing the route, re-adding the route....but I
can't seem to figure this out. Any input, ideas, suggestions would be appreciated.
73's
Albert
WB7AWL
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net