Is there a workaround to this, that would allow a remote site to access net44 directly via it's Internet connection, but fall back on a Microwave link if its Internet failed?
The only solution that I've been able to think of that would work in a timely manner is using an OpenVPN server to handle all my net44 routing. This allows me to use OpenVPN's routing mechanisms to create more advanced networks, but requires a colo machine with costs me about $15 a month.
So far I've been able to get net44 routed into my colo machine (44.4.36.1) and connect up my iPhone and MacBook Pro to that subnet as VPN clients. Routing between those three machines and out to the rest of net44 seems to be working (mostly). I'm a bit stalled out right now until I get my microwave gear in the mail.
Any cheaper solutions out there??
Blaine
Sent from my iPhone
On Aug 15, 2013, at 9:02 AM, Brian Kantor Brian@ucsd.edu wrote:
(Please trim inclusions from previous messages) _______________________________________________ On Thu, Aug 15, 2013 at 10:59:55AM -0400, Charles Hargrove wrote:
No least cost path routing for IP like MX records?
No, because of a fundamental difference. The SMTP protocol is a higher-level one which uses TCP connections which of course have a status of succeeded or not, so if a connection specified by an MX record does not succeed (is refused, etc) the mailer can try an alternate.
IP is much lower level and has no such status: packets are not acknowledged at the IP level so there may be no notification that a packet has not reached its destination. There is no way at the IP level to tell that a particular route isn't working and to therefore try another.
There are proposed mechanisms to allow a choice of routes (RSPF, OSPF, etc), but none of them have been implemented on AMPRNet and the existing encap scheme doesn't allow for them (yet).
- Brian
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html