3 Jun
2017
3 Jun
'17
1:47 a.m.
It was always suitable (my amprd system it is also on a dynamic IP). You
just can not place a hostname in the ignore list, that's all.
But this should not bother you. If you use the daemon as recommended (/8
netmask on its interface), all other routes, including your own you need
to ignore would be defined in your routing table, and would take
precedence over the 44/8 rule via the tunnel interface (you don't need
all individual routes for amprd). So there is nothing to block using it
on a dynamic interface. Your routing table should look something like this:
default via <def gw ip> dev <some interface> <--- the system's default
route
44.0.0.0/8 dev ampr0 <--- default 44 gateway
44.a.b.c/32 via <def gw ip> dev <some interface> <--- host routes for 44
IPIP endpoint
44.b.c.d/32 via <def gw ip> dev <some interface> <--- host routes for 44
IPIP endpoint
44.x.y.x dev <some other interface> <--- your network
44.x.y.z dev <some other interface> <--- your network
Marius, YO2LOJ
On 02.06.2017 18:09, Gustavo Ponza wrote:
- amprd (my favorite) will adapt automatically to
the gateway that is
broadcasted as the gateway for 44.0.0.1 (since the first release
actually).
Is it now suitable to run over dynamic IP system?
I was unable to run it... perhaps my fault.