Re: [Astlinux-devel] Remote access of devices behind Astlinux

Unless you need to update packages on an installed system, without
refreshing the whole image, then I think Buildroot would be a great place
to start.  I think (but could be wrong) buildroot does not have a package
manager to allow updates to existing systems.  Instead you select all the
packages you want during build time, and the install image is created...
just like Astlinux.

There is a lot of documentation at Buildroot including recommendations on
how to layout and add your own custom packages which would not be part of
Buildroot itself... for example, all Astlinux custom web interfaces could
be added as a custom package on your own fork of Buildroot.  If you follow
the design recommendations in the documentation then it should fit in
fairly easily to the build environment.

Of course I say this without having tried it myself.  If it was me, I would
start by trying to get a very simple Buildroot image to build, install and
boot.  Step two would then be to select all the packages I expect to
need... build, install and boot that.  Step three would be to add custom
packages like a user interface.

I'd love to have a go at this, but unfortunately I simply don't have the
time.

David

On Sun, Jul 13, 2025 at 7:46 PM Michael Knill <
mic...@ip...> wrote:

> Thanks Lonnie/Christopher
>
>
>
> Yes we are now at the stage where our company has no choice but to roll
> our own and we are actively seeking to develop (and/or buy) the skills
> required to do so.
>
> So Im certainly interested in recommendations for doing so.
>
>
>
> Regards
>
> Michael Knill
>
>
>
>
>
> *From: *Lonnie Abelbeck <li...@lo...>
> *Date: *Sunday, 13 July 2025 at 11:36 pm
> *To: *AstLinux Developers Mailing List <
> ast...@li...>
> *Subject: *Re: [Astlinux-devel] Remote access of devices behind Astlinux
>
> Hi Michael,
>
> Christopher (Cadillac Kid) has good info for you.
>
> If I were in your shoes Michael, rolling your own solution from either a
> Debian base or the latest Buildroot seems much better than trying to start
> with the very old Buildroot snapshot AstLinux is based on.  While we have
> maintained the old Buildroot by backporting from upstream over time, this
> is a lot to learn and understand if you are just getting started with
> building custom images.
>
> Lonnie
>
>
> > On Jul 12, 2025, at 7:06 AM, The Cadillac Kid via Astlinux-devel <
> ast...@li...> wrote:
> >
> > we use VPN access for many of our sites..  (granted we rolled our own
> starting about 15 years ago).. we run Mikrotik Hex lites (or other
> variants) in front of our asterisk servers and set up VPN access for
> RMATS..  sites which they wont give us a public IP, we hae a site-to-site
> connection where we can log in to our NOC and remotely access devices on
> the system..  we had issues using straight proxy as grandstream gateways
> werent happy with the oroxy, their web GUI does some wierd stuff.
> >
> > we had broken away from the "one box does it all" setup that astlinux
> provides as we started doing larger sites and asking our systems to do more
> and more.. thus why the MT out front. we have several 3000+ line systems
> out there.. which are also handling communications for hotel PMS, cost
> accounting, etc..
> >
> > On Friday, July 11, 2025 at 10:13:55 PM EDT, Michael Knill <
> mic...@ip...> wrote:
> >
> >
> > Hi All
> >
> > I currently connect to devices behind Astlinux (mainly IP Phones) using
> SSH Tunnelling. This works well but is clunky and not easily scalable (I am
> looking at SSH Certificate Authentication which will be an improvement).
> > I really only need to connect to a directly accessible IP Phone via
> Astlinux using HTTP/S via some proxy mechanism.
> > Does anyone have any ideas? Note that it does not necessarily need to be
> existing Astlinux functionality as we are experimenting with rolling our
> own.
> >
> > Thanks so much.
> >
> > Regards
> >
> > Michael Knill
> > Managing Director
> >
> > D: +61 2 6189 1360
> > P: +61 2 6140 4656
> > E: mic...@ip...
> > W: ipcsolutions.com.au
> >
> >  <image001.png>Smarter Business Communications
> >
> > _______________________________________________
> > Astlinux-devel mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-devel
> > <image001.png>_______________________________________________
> > Astlinux-devel mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>
>
>
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>