During the night, amprgw fetched a copy of the encap file from the portal which was truncated (it had 259 entries instead of over 600) and one of the entries that was in the copy fetched had no gateway address. Viz:
route addprivate 44.131.168.128/29 encap
This caused the ipip daemon to segfault and so there was no routing between Internet and tunnel subnets for an hour. The rip sender was similarly affected.
Later fetches of the encap file obtained ones that appear to be intact and all routing is again operational.
I've modified the code in the daemons to be more robust in the face of a bad encap fetch, and taken steps to ensure that future fetches are checked better. - Brian
Thank U for Dedicated work for the AMPRNet Community for so long years
an hour of downtime is nothing for ham radio business ....
Regards
Ronen - 4Z4ZQ
Ronen Pinchooks (4Z4ZQ) WebSitehttp://www.ronen.org/ www.ronen.org ronen.org (Ronen Pinchooks (4Z4ZQ) WebSite) is hosted by domainavenue.com
________________________________
This caused the ipip daemon to segfault and so there was no routing between Internet and tunnel subnets for an hour. - Brian
_________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
On Fri, Apr 14, 2017 at 9:02 AM, Brian Kantor Brian@ucsd.edu wrote:
(Please trim inclusions from previous messages) _______________________________________________ During the night, amprgw fetched a copy of the encap file from the portal which was truncated (it had 259 entries instead of over 600) and one of the entries that was in the copy fetched had no gateway address. Viz:
route addprivate 44.131.168.128/29 encap
This caused the ipip daemon to segfault and so there was no routing between Internet and tunnel subnets for an hour. The rip sender was similarly affected.
Later fetches of the encap file obtained ones that appear to be intact and all routing is again operational.
I've modified the code in the daemons to be more robust in the face of a bad encap fetch, and taken steps to ensure that future fetches are checked better. - Brian
Have you considered open sourcing this infrastructure software so we can get more eyes looking for bugs like this?
Tom KD7LXL
On 4/14/17 2:00 PM, Tom Hayward wrote:
Have you considered open sourcing this infrastructure software so we can get more eyes looking for bugs like this?
+1
+1
Andrew
On Apr 14, 2017, at 12:07 PM, Bryan Fields Bryan@bryanfields.net wrote:
(Please trim inclusions from previous messages) _______________________________________________
On 4/14/17 2:00 PM, Tom Hayward wrote: Have you considered open sourcing this infrastructure software so we can get more eyes looking for bugs like this?
+1
-- Bryan Fields
727-409-1194 - Voice http://bryanfields.net _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
I have; the problem is that it's derived from several non-open-source programs that I don't own the copyright on. Getting permission to freely distribute it would be extremely difficult. It's also unclear whether the parts I wrote aren't owned by my employer. So no, I doubt it'll ever be open-source. - Brian
On Fri, Apr 14, 2017 at 11:00:20AM -0700, Tom Hayward wrote:
Have you considered open sourcing this infrastructure software so we can get more eyes looking for bugs like this?
Tom KD7LXL
Yeah if parts of the code are written on company time or with company resources (laptop and such) then the code is strictly owned by your employer. No doubt about it, it's in your contract (and mine and everyone else in IT) :/
On 14 Apr 2017, at 21:05, Brian Kantor Brian@UCSD.Edu wrote:
(Please trim inclusions from previous messages) _______________________________________________ I have; the problem is that it's derived from several non-open-source programs that I don't own the copyright on. Getting permission to freely distribute it would be extremely difficult. It's also unclear whether the parts I wrote aren't owned by my employer. So no, I doubt it'll ever be open-source.
- Brian
On Fri, Apr 14, 2017 at 11:00:20AM -0700, Tom Hayward wrote: Have you considered open sourcing this infrastructure software so we can get more eyes looking for bugs like this?
Tom KD7LXL
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Except that you work for a State University supported by tax payers. Thus Open Records laws apply to any and all code you develop while working for UCSD.
On Fri, Apr 14, 2017 at 5:39 PM, Ruben ON3RVH on3rvh@on3rvh.be wrote:
(Please trim inclusions from previous messages) _______________________________________________ Yeah if parts of the code are written on company time or with company resources (laptop and such) then the code is strictly owned by your employer. No doubt about it, it's in your contract (and mine and everyone else in IT) :/
On 14 Apr 2017, at 21:05, Brian Kantor Brian@UCSD.Edu wrote:
(Please trim inclusions from previous messages) _______________________________________________ I have; the problem is that it's derived from several non-open-source programs that I don't own the copyright on. Getting permission to freely distribute it would be extremely difficult. It's also unclear whether the parts I wrote aren't owned by my employer. So no, I doubt it'll ever be open-source.
- Brian
On Fri, Apr 14, 2017 at 11:00:20AM -0700, Tom Hayward wrote: Have you considered open sourcing this infrastructure software so we can get more eyes looking for bugs like this?
Tom KD7LXL
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
That's a rather simplistic view, and not quite true: UCSD isn't a State University. Open Records laws apparently do not apply to software developed by the University. It's complicated, but the copyright in the code clearly belongs to the Regents of the University of California, and while I can apply for permission from our Technology Transfer Office to freely distribute what I exclusively have written, the ownership of the code it was derived from probably makes that moot. And to answer the question before it is asked, no, it wasn't funded by a Federal grant either. - Brian
On Fri, Apr 14, 2017 at 05:48:29PM -0400, Lin Holcomb wrote:
Except that you work for a State University supported by tax payers. Thus Open Records laws apply to any and all code you develop while working for UCSD.
-
Andrew Ragone -
Bill Vodall -
Brian Kantor -
Bryan Fields -
Lin Holcomb -
R P -
Ruben ON3RVH -
Tom Hayward