8 May
2017
8 May
'17
8:55 p.m.
Yeah, that is exactly what I discovered earlier this afternoon and why your ipip route
didn't leave my gateway and went to /dev/null
I use the latest ampr-ripd as I believe and that hack is not in it.
Bob VE3TOK
On 2017-05-08 01:40 PM, M6XCV (Mike) wrote:
(Please trim inclusions from previous messages)
_______________________________________________
If you are not using ampr-ripd or rip44d then this could be the issue.
What route is used for traffic from the gateway IP to 44.131.14.253?
Is this also trying to follow the /31 over the tunnel interface?
The recent update added a "hack" to the RIP daemons so that when
adding 44.131.14.252/31 it would also add a route for 44.131.14.253/32
via your normal internet path. If you are not using source-based
routing then you probably need something like this to reach me
properly.
Thanks,
Mike, M6XCV
On 8 May 2017 at 15:55, Leon Zetekoff <wa4zlw(a)backwoodswireless.net> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
hi brian....beats me...I'll have to check with marius since I'm using his
script. I can get to other sites
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net