I thought the whole point of RIP was that it is a *DYNAMIC* routing
protocol.
Eric
AF6EP
On Fri, Mar 28, 2014 at 3:34 PM, G1FEF <chris(a)g1fef.co.uk> wrote:
> The RIP announcements are just broadcast from the authoritative source,
> which is the portal data, as provided by each and every gateway operator.
>
> Sent from my iPhone
>
> > On 28 Mar 2014, at 22:26, Eric Fort <eric.fort(a)gmail.com> wrote:
> >
> > (Please trim inclusions from previous messages)
> > _______________________________________________
> > Not intending to hyjack the thread here.... but isn't this backwards?
> > shouldn't the encap be built from the rip announcements rather than the
> > reverse? I.E. rip being the current reality vs the encap being more of a
> > statement of network architecture.
> >
> > Eric
> > AF6EP
> >
> >
> >> On Fri, Mar 28, 2014 at 3:10 PM, Chris <chris(a)g1fef.co.uk> wrote:
> >>
> >> (Please trim inclusions from previous messages)
> >> _______________________________________________
> >> Brian replicates the portal database in realtime local to where his RIP
> >> server is and uses the live database to populate the routing
> announcements.
> >> I'm not sure how often the RIP software polls the database, but I'm
sure
> >> Brian can enlighten us...
> >>
> >> I'm in the process of adding the portal code to a subversion repository
> >> and once that has been completed I will probably open source it. In the
> >> meantime if anyone wants to assist with developing the portal code or
> with
> >> translations into other languages, please get in touch.
> >>
> >> Thanks,
> >> Chris
> >>
> >>
> >>> On 28 Mar 2014, at 21:59, Bart Kus <me(a)bartk.us> wrote:
> >>>
> >>> (Please trim inclusions from previous messages)
> >>> _______________________________________________
> >>> Hey Chris,
> >>>
> >>> Do you know how timely the multicast RIP announcements are? Are they
> >> sent out every time someone re-configures a gateway on the portal? Is
> >> there some scheduled re-broadcast of all routes?
> >>>
> >>> Also, where is the source code for all this?
> >>>
> >>> Thanks for any details,
> >>>
> >>> --Bart
> >>>
> >>>
> >>>> On 03/28/2014 02:55 PM, Chris wrote:
> >>>> (Please trim inclusions from previous messages)
> >>>> _______________________________________________
> >>>> Hi Tom,
> >>>>
> >>>>> Second issue:
> >>>> This is not a bug, this is intentional. I have been re-writing
> sections
> >> of the portal to enhance security following several hacking attempts.
> One
> >> insecure script I found when I audited the system was the getdata.php
> >> script. It has been re-written to be secure, You should not have been
> able
> >> to access the encap file directly from it in the first place, that kind
> of
> >> access was never documented, nor was it ever intended to be used like
> that.
> >>>>
> >>>> The correct way to access the encap file remotely by script, is via
> >> FTP. I have had a couple of people asking about an API which I may
> >> introduce at a later stage, but for now you should access the encap file
> >> via FTP.
> >>>>
> >>>> Regards,
> >>>> Chris
> >>>>
> >>>>> Something changed with the encap file download process. The
script
> >>>>> that builds our IPIP tunnels uses "curl
> >>>>>
https://portal.ampr.org/getdata.php" to download the encap
data. A
> few
> >>>>> days ago this was working just fine. Now the returned file is
empty.
> >>>>>
> >>>>> Loading that url with a web browser also returns an empty page.
> >>>>> However, if I click the "download encap" link at
> >>>>>
https://portal.ampr.org/gateways_list.php, it works fine. Some
funky
> >>>>> session bug, I assume.
> >>>>>
> >>>>> Please fix this issue, or point me towards the documentation
that
> >>>>> explains a better way to get the encap data.
> >>>> _________________________________________
> >>>> 44Net mailing list
> >>>> 44Net(a)hamradio.ucsd.edu
> >>>>
http://hamradio.ucsd.edu/mailman/listinfo/44net
> >>>
> >>> _________________________________________
> >>> 44Net mailing list
> >>> 44Net(a)hamradio.ucsd.edu
> >>>
http://hamradio.ucsd.edu/mailman/listinfo/44net
> >>
> >> _________________________________________
> >> 44Net mailing list
> >> 44Net(a)hamradio.ucsd.edu
> >>
http://hamradio.ucsd.edu/mailman/listinfo/44net
> >