Ok, so that's not 100% correct/complete, but it is not the cause of the observed behavior...
Since there are 2 parts to this network, the correct set should be:
ip route add default via 169.228.34.84 dev tunl0 onlink table 44 ip rule from 44.0.0.0/9 priority 1 table 44 ip rule from 44.128.0.0/10 priority 1 table 44
The last part has no effect (an IP other than 0.0.0.0 with netmask /0 makes no sense), but it is superseded by the default rule anyway. The correct form would be: ip rule to 44.0.0.0/9 priority 1 table 44 ip rule to 44.128.0.0/10 priority 1 table 44
At least this is not the reason why it happens...
On 21/01/2024 02:03, kc8qba--- via 44net wrote:
I've got: ip route add default via 169.228.34.84 dev tunl0 onlink table 44 ip rule from 44.0.0.0/9 priority 1 table 44 ip rule to 44.0.0.0/0 priority 1 table 44 also, rip44d is -i tunl0 -a my_public_gateway_ip -t 44 -p password _______________________________________________ 44net mailing list -- 44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org