23 Nov
2014
23 Nov
'14
5:58 a.m.
On 22 Nov 2014, at 23:29, Antonio Querubin
<tony(a)lavanauts.org> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
On Wed, 19 Nov 2014, Chris wrote:
Fair point, it is a CIDR prefix length really, not a netmask.
I will add another field “maskLength” then remove the “netmask” after a few days to allow
any scripts already written to adjust.
Chris
I have implemented an API for accessing the
Portal data programatically, if you login and select “API” from the menu there is some
info there about it.
So far I have only implemented one function: the ability to retrieve the encap routes.
I would appreciated comments / feedback / suggestions as well as any bug reports.
This is good stuff. One suggestion is to rename netmask to either masklen or prefixlen.
I've modified encapconvertnew.pl script to use the
API and renamed it to amprroutes.pl (encapconvertnew.pl is still available). I've
also added VyOS (Vyatta) as another possible router config.
http://ah6bw.ampr.org/amprroutes.pl
YMMV. BTW, if anybody knows how to apply policy routing to interface addresses in VyOS
I'd like to hear from you. As always feedback/comments welcome. Enjoy.
Antonio Querubin
e-mail: tony(a)lavanauts.org
xmpp: antonioquerubin(a)gmail.com
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net