I prefer to keep them separate, this should be one tool which is part of a chain of tools. One can using iptables or other firewall tools to manage outside of routing table updates.
For example, one might setup a website on the 44.x.x.x net that should be accessible from any Internet address, but you might want to only allow 44.x.x.x sourced traffic on a radio port. Or if we start moving things like D-STAR / Winlink gateways onto 44.x.x.x addresses there will be some that operate on public Internet addresses for updates and interconnection, though traffic such as D-STAR DD (ethernet over D-STAR) might send 44.x.x.x traffic only through designated paths.
------------------------------ John D. Hays K7VE PO Box 1223, Edmonds, WA 98020-1223 http://k7ve.org/blog http://twitter.com/#!/john_hays http://www.facebook.com/john.d.hays
On Tue, Aug 6, 2013 at 1:55 PM, Demetre SV1UY demetre.sv1uy@gmail.comwrote:
(Please trim inclusions from previous messages)
Any chance the program setting up a firewall too, in order to allow only AMPRnet connections?
-- 73 de SV1UY Demetre Ch. Valaris IP Coordinator for AMPRnet in Greece e-mail: demetre.sv1uy@gmail.com Radio e-mail: sv1uy@winlink.org (to use my radio e-mail put //WL2K in the beginning of the subject line) http://www.qsl.net/sv1uy _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html