4 Jun
2017
4 Jun
'17
9:11 a.m.
Wouldn't it be much easier to add some simple stuff to your system:
I understand you use table 44, local ip is 44.60.44.1 on tunl0, and
br-amprlan is your local 44net bridge.
So you probably have already a default route via 169.228.34.84 in that
table, and a lot of routes created by ampr-ripd.
And you have some policy routing in place, like:
ip rule add from 44.60.44.1 table 44
Now if you add:
ip rule add from 44.60.44.1 to 44.60.44.0/24 table main
ip rule add from 44.60.44.1 to 44.0.0.0/8 table 44
This should make your system use table 44 for outgoing 44net traffic,
including the interface address 44.60.44.1
This will not affect your outward forwarded traffic which will never
have source address 44.60.44.1, and your incoming 44net traffic will be
routed by the table main, which should hold your local routes.
Marius, YO2LOJ
On 04.06.2017 04:16, lleachii--- via 44Net wrote:
SNAT is possible, and my machines are already on a
VLAN, but no
"dual-connectivity" (I discovered another anomaly in the Linux Kernel
that makes ping-44.php fail). DHCP is not used on my 44LAN, but I
could implement it.
...but, this doesn't solve anything as you described, though, since
(as I noted) this only occurs because this is my REAL router. The only
thing I can do is make routes, mangles and policies specific to
44.60.44.1...or simply code an argument for SRC IP in ampr-ripd.
- Lynwood