astlinux-users — AstLinux Users Mailing List

Re: [Astlinux-users] New Protectli hardware

[Michael K. <mic...@ip...>]

Thanks Lonnie

What about a script that does the check on startup in rc.elocal for instance and if the MAC’s are different it deletes the file and reboots itself?

Regards
Michael Knill


From: Lonnie Abelbeck <li...@lo...>
Date: Thursday, 8 May 2025 at 12:48 am
To: AstLinux Users Mailing List <ast...@li...>
Subject: Re: [Astlinux-users] New Protectli hardware
> You could build a few of them (USB) in advance and just plug them into whatever hardware you happen to use. Do you think I could write a script that checks the NIC MAC’s on bootup and automatically regenerates 70-persistent-net.rules if they are different?

Not on bootup, the 70-persistent-net.rules file is used early when udev is initiated and NIC modules loaded.

You could create a /mnt/kd/rc.local.stop shell script (make executable)
-- /mnt/kd/rc.local.stop --
#!/bin/sh

RULES_FILE="/mnt/asturw/etc/udev/rules.d/70-persistent-net.rules"

## Remove 70-persistent-net.rules on shutdown
if [ -f "$RULES_FILE" ]; then
  rm "$RULES_FILE"
fi
--

So, if the system was shutdown cleanly, this would work.

Lonnie



> On May 6, 2025, at 8:57 PM, Michael Knill <mic...@ip...> wrote:
>
> <!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} @font-face {font-family:Aptos; panose-1:2 11 6 4 2 2 2 2 2 4;} @font-face {font-family:"Times New Roman \(Body CS\)"; panose-1:2 11 6 4 2 2 2 2 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0cm; font-size:12.0pt; font-family:"Aptos",sans-serif;} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} span.EmailStyle19 {mso-style-type:personal-reply; font-family:"Calibri",sans-serif; color:windowtext;} .MsoChpDefault {mso-style-type:export-only; font-size:10.0pt; mso-ligatures:none;} @page WordSection1 {size:612.0pt 792.0pt; margin:72.0pt 72.0pt 72.0pt 72.0pt;} div.WordSection1 {page:WordSection1;} --> Thanks Lonnie. Yep was aware of removing the 70-persistent-net.rules when changing hardware (and VM’s too in some cases).
>  Yes I will likely use NVMe but the USB did seem attractive. You could build a few of them in advance and just plug them into whatever hardware you happen to use. Do you think I could write a script that checks the NIC MAC’s on bootup and automatically regenerates 70-persistent-net.rules if they are different?
>   Regards
> Michael Knill
>    From: Lonnie Abelbeck <li...@lo...>
> Date: Wednesday, 7 May 2025 at 6:03 am
> To: AstLinux Users Mailing List <ast...@li...>
> Subject: Re: [Astlinux-users] New Protectli hardware
> A reminder, whenever switching an AstLinux drive from box to box, be-it SATA, NVMe or USB, be sure to remove the file:
> --
> /mnt/asturw/etc/udev/rules.d/70-persistent-net.rules
> --
> before shutdown, then when paced into the new box it will be auto-generated from the new box NIC MACs.
>
> BTW, I tested an AstLinux box with only a "SAMSUNG FIT Plus 3.1 USB Flash Drive, 128GB" as storage.  It worked as expected, about as fast as a M.2 SATA drive.  While running, I removed the USB drive and re-inserted it, while a reboot was needed to recover, no data loss was detected.
>
> All in all, I would recommend an NVMe drive with the "V1210 – 2 Port Intel® N5105" over a USB drive. (AstLinux 1.5.10)
>
> Lonnie
>
>
> > On May 5, 2025, at 8:34 PM, Michael Knill <mic...@ip...> wrote:
> >
> > Thanks Lonnie for the info. Yes I was aware Netgate had some eMMC issues.
> >  Interesting concept using a USB Flash drive for storage. This could be quite handy for field hardware replacement e.g. just move across the drive to the new hardware.
> >  Regards
> > Michael Knill
> >   From: Lonnie Abelbeck <li...@lo...>
> > Date: Monday, 5 May 2025 at 12:46 pm
> > To: AstLinux Users Mailing List <ast...@li...>
> > Subject: Re: [Astlinux-users] New Protectli hardware
> > Hi Michael,
> >
> > In mid-2020 I purchased a "Protectli FW4B CPU J3160 NIC x4" with Coreboot, and it worked with AstLinux out of the box.
> >
> > The "V1210 – 2 Port Intel® N5105" should work (test to be sure) with the just released AstLinux 1.5.10 as it uses M.2 NVMe.
> >
> > AstLinux does not support eMMC storage (kernel CONFIG_MMC disabled).  Supporting eMMC has been discussed, but being non-removable, slowish and typically of poor quality, it was never a production solution in my mind. [1]
> >
> > I recently purchased a "Silicon Power 128GB NVMe M.2" for $19 USD, a far better choice than non-removable eMMC.
> >
> > Even quality (stubby) USB storage "SAMSUNG FIT Plus 3.1 USB Flash Drive, 128GB" is $15 USD would be better than eMMC ... this would work with pre-1.5.10 AstLinux.  With some caveats [2].
> >
> > Lonnie
> >
> > [1] I have read where some Netgate appliances stopped booting because after a couple years the eMMC failed.
> >
> > [2] https://doc.astlinux-project.org/userdoc:boot-usb-storage
> >
> >
> >
> > > On May 4, 2025, at 7:59 PM, Michael Knill <mic...@ip...> wrote:
> > >
> > > Hi All
> > >  There is new Protecli hardware (https://protectli.com/product/v1210/) which I was wondering if it was compatible with Astlinux? I would be wanting to use the onboard 32G eMMC.
> > >  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-users mailing list
> > > Ast...@li...
> > > https://lists.sourceforge.net/lists/listinfo/astlinux-users
> > >
> > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
> >
> >
> >
> >
> > _______________________________________________
> > Astlinux-users mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-users
> >
> > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
> > _______________________________________________
> > Astlinux-users mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-users
> >
> > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
>
>
>
>
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....




_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Re: [Astlinux-users] New Protectli hardware

[Lonnie A. <li...@lo...>]

> You could build a few of them (USB) in advance and just plug them into whatever hardware you happen to use. Do you think I could write a script that checks the NIC MAC’s on bootup and automatically regenerates 70-persistent-net.rules if they are different?

Not on bootup, the 70-persistent-net.rules file is used early when udev is initiated and NIC modules loaded.

You could create a /mnt/kd/rc.local.stop shell script (make executable)
-- /mnt/kd/rc.local.stop --
#!/bin/sh

RULES_FILE="/mnt/asturw/etc/udev/rules.d/70-persistent-net.rules"

## Remove 70-persistent-net.rules on shutdown
if [ -f "$RULES_FILE" ]; then
  rm "$RULES_FILE"
fi
--

So, if the system was shutdown cleanly, this would work.

Lonnie



> On May 6, 2025, at 8:57 PM, Michael Knill <mic...@ip...> wrote:
> 
> <!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} @font-face {font-family:Aptos; panose-1:2 11 6 4 2 2 2 2 2 4;} @font-face {font-family:"Times New Roman \(Body CS\)"; panose-1:2 11 6 4 2 2 2 2 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0cm; font-size:12.0pt; font-family:"Aptos",sans-serif;} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} span.EmailStyle19 {mso-style-type:personal-reply; font-family:"Calibri",sans-serif; color:windowtext;} .MsoChpDefault {mso-style-type:export-only; font-size:10.0pt; mso-ligatures:none;} @page WordSection1 {size:612.0pt 792.0pt; margin:72.0pt 72.0pt 72.0pt 72.0pt;} div.WordSection1 {page:WordSection1;} --> Thanks Lonnie. Yep was aware of removing the 70-persistent-net.rules when changing hardware (and VM’s too in some cases).
>  Yes I will likely use NVMe but the USB did seem attractive. You could build a few of them in advance and just plug them into whatever hardware you happen to use. Do you think I could write a script that checks the NIC MAC’s on bootup and automatically regenerates 70-persistent-net.rules if they are different?
>   Regards
> Michael Knill
>    From: Lonnie Abelbeck <li...@lo...>
> Date: Wednesday, 7 May 2025 at 6:03 am
> To: AstLinux Users Mailing List <ast...@li...>
> Subject: Re: [Astlinux-users] New Protectli hardware
> A reminder, whenever switching an AstLinux drive from box to box, be-it SATA, NVMe or USB, be sure to remove the file:
> --
> /mnt/asturw/etc/udev/rules.d/70-persistent-net.rules
> --
> before shutdown, then when paced into the new box it will be auto-generated from the new box NIC MACs.
> 
> BTW, I tested an AstLinux box with only a "SAMSUNG FIT Plus 3.1 USB Flash Drive, 128GB" as storage.  It worked as expected, about as fast as a M.2 SATA drive.  While running, I removed the USB drive and re-inserted it, while a reboot was needed to recover, no data loss was detected.
> 
> All in all, I would recommend an NVMe drive with the "V1210 – 2 Port Intel® N5105" over a USB drive. (AstLinux 1.5.10)
> 
> Lonnie
> 
> 
> > On May 5, 2025, at 8:34 PM, Michael Knill <mic...@ip...> wrote:
> > 
> > Thanks Lonnie for the info. Yes I was aware Netgate had some eMMC issues.
> >  Interesting concept using a USB Flash drive for storage. This could be quite handy for field hardware replacement e.g. just move across the drive to the new hardware.
> >  Regards
> > Michael Knill
> >   From: Lonnie Abelbeck <li...@lo...>
> > Date: Monday, 5 May 2025 at 12:46 pm
> > To: AstLinux Users Mailing List <ast...@li...>
> > Subject: Re: [Astlinux-users] New Protectli hardware
> > Hi Michael,
> > 
> > In mid-2020 I purchased a "Protectli FW4B CPU J3160 NIC x4" with Coreboot, and it worked with AstLinux out of the box.
> > 
> > The "V1210 – 2 Port Intel® N5105" should work (test to be sure) with the just released AstLinux 1.5.10 as it uses M.2 NVMe.
> > 
> > AstLinux does not support eMMC storage (kernel CONFIG_MMC disabled).  Supporting eMMC has been discussed, but being non-removable, slowish and typically of poor quality, it was never a production solution in my mind. [1]
> > 
> > I recently purchased a "Silicon Power 128GB NVMe M.2" for $19 USD, a far better choice than non-removable eMMC.
> > 
> > Even quality (stubby) USB storage "SAMSUNG FIT Plus 3.1 USB Flash Drive, 128GB" is $15 USD would be better than eMMC ... this would work with pre-1.5.10 AstLinux.  With some caveats [2].
> > 
> > Lonnie
> > 
> > [1] I have read where some Netgate appliances stopped booting because after a couple years the eMMC failed.
> > 
> > [2] https://doc.astlinux-project.org/userdoc:boot-usb-storage
> > 
> > 
> > 
> > > On May 4, 2025, at 7:59 PM, Michael Knill <mic...@ip...> wrote:
> > > 
> > > Hi All
> > >  There is new Protecli hardware (https://protectli.com/product/v1210/) which I was wondering if it was compatible with Astlinux? I would be wanting to use the onboard 32G eMMC.
> > >  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-users mailing list
> > > Ast...@li...
> > > https://lists.sourceforge.net/lists/listinfo/astlinux-users
> > > 
> > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
> > 
> > 
> > 
> > 
> > _______________________________________________
> > Astlinux-users mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-users
> > 
> > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
> > _______________________________________________
> > Astlinux-users mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-users
> > 
> > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
> 
> 
> 
> 
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Re: [Astlinux-users] New Protectli hardware

[Michael K. <mic...@ip...>]

Thanks Lonnie. Yep was aware of removing the 70-persistent-net.rules when changing hardware (and VM’s too in some cases).

Yes I will likely use NVMe but the USB did seem attractive. You could build a few of them in advance and just plug them into whatever hardware you happen to use. Do you think I could write a script that checks the NIC MAC’s on bootup and automatically regenerates 70-persistent-net.rules if they are different?

Regards
Michael Knill


From: Lonnie Abelbeck <li...@lo...>
Date: Wednesday, 7 May 2025 at 6:03 am
To: AstLinux Users Mailing List <ast...@li...>
Subject: Re: [Astlinux-users] New Protectli hardware
A reminder, whenever switching an AstLinux drive from box to box, be-it SATA, NVMe or USB, be sure to remove the file:
--
/mnt/asturw/etc/udev/rules.d/70-persistent-net.rules
--
before shutdown, then when paced into the new box it will be auto-generated from the new box NIC MACs.

BTW, I tested an AstLinux box with only a "SAMSUNG FIT Plus 3.1 USB Flash Drive, 128GB" as storage.  It worked as expected, about as fast as a M.2 SATA drive.  While running, I removed the USB drive and re-inserted it, while a reboot was needed to recover, no data loss was detected.

All in all, I would recommend an NVMe drive with the "V1210 – 2 Port Intel® N5105" over a USB drive. (AstLinux 1.5.10)

Lonnie


> On May 5, 2025, at 8:34 PM, Michael Knill <mic...@ip...> wrote:
>
> Thanks Lonnie for the info. Yes I was aware Netgate had some eMMC issues.
>  Interesting concept using a USB Flash drive for storage. This could be quite handy for field hardware replacement e.g. just move across the drive to the new hardware.
>  Regards
> Michael Knill
>   From: Lonnie Abelbeck <li...@lo...>
> Date: Monday, 5 May 2025 at 12:46 pm
> To: AstLinux Users Mailing List <ast...@li...>
> Subject: Re: [Astlinux-users] New Protectli hardware
> Hi Michael,
>
> In mid-2020 I purchased a "Protectli FW4B CPU J3160 NIC x4" with Coreboot, and it worked with AstLinux out of the box.
>
> The "V1210 – 2 Port Intel® N5105" should work (test to be sure) with the just released AstLinux 1.5.10 as it uses M.2 NVMe.
>
> AstLinux does not support eMMC storage (kernel CONFIG_MMC disabled).  Supporting eMMC has been discussed, but being non-removable, slowish and typically of poor quality, it was never a production solution in my mind. [1]
>
> I recently purchased a "Silicon Power 128GB NVMe M.2" for $19 USD, a far better choice than non-removable eMMC.
>
> Even quality (stubby) USB storage "SAMSUNG FIT Plus 3.1 USB Flash Drive, 128GB" is $15 USD would be better than eMMC ... this would work with pre-1.5.10 AstLinux.  With some caveats [2].
>
> Lonnie
>
> [1] I have read where some Netgate appliances stopped booting because after a couple years the eMMC failed.
>
> [2] https://doc.astlinux-project.org/userdoc:boot-usb-storage
>
>
>
> > On May 4, 2025, at 7:59 PM, Michael Knill <mic...@ip...> wrote:
> >
> > Hi All
> >  There is new Protecli hardware (https://protectli.com/product/v1210/) which I was wondering if it was compatible with Astlinux? I would be wanting to use the onboard 32G eMMC.
> >  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-users mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-users
> >
> > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
>
>
>
>
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....




_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Re: [Astlinux-users] New Protectli hardware

[Lonnie A. <li...@lo...>]

A reminder, whenever switching an AstLinux drive from box to box, be-it SATA, NVMe or USB, be sure to remove the file:
--
/mnt/asturw/etc/udev/rules.d/70-persistent-net.rules
--
before shutdown, then when paced into the new box it will be auto-generated from the new box NIC MACs.

BTW, I tested an AstLinux box with only a "SAMSUNG FIT Plus 3.1 USB Flash Drive, 128GB" as storage.  It worked as expected, about as fast as a M.2 SATA drive.  While running, I removed the USB drive and re-inserted it, while a reboot was needed to recover, no data loss was detected.

All in all, I would recommend an NVMe drive with the "V1210 – 2 Port Intel® N5105" over a USB drive. (AstLinux 1.5.10)

Lonnie


> On May 5, 2025, at 8:34 PM, Michael Knill <mic...@ip...> wrote:
> 
> Thanks Lonnie for the info. Yes I was aware Netgate had some eMMC issues.
>  Interesting concept using a USB Flash drive for storage. This could be quite handy for field hardware replacement e.g. just move across the drive to the new hardware.
>  Regards
> Michael Knill
>   From: Lonnie Abelbeck <li...@lo...>
> Date: Monday, 5 May 2025 at 12:46 pm
> To: AstLinux Users Mailing List <ast...@li...>
> Subject: Re: [Astlinux-users] New Protectli hardware
> Hi Michael,
> 
> In mid-2020 I purchased a "Protectli FW4B CPU J3160 NIC x4" with Coreboot, and it worked with AstLinux out of the box.
> 
> The "V1210 – 2 Port Intel® N5105" should work (test to be sure) with the just released AstLinux 1.5.10 as it uses M.2 NVMe.
> 
> AstLinux does not support eMMC storage (kernel CONFIG_MMC disabled).  Supporting eMMC has been discussed, but being non-removable, slowish and typically of poor quality, it was never a production solution in my mind. [1]
> 
> I recently purchased a "Silicon Power 128GB NVMe M.2" for $19 USD, a far better choice than non-removable eMMC.
> 
> Even quality (stubby) USB storage "SAMSUNG FIT Plus 3.1 USB Flash Drive, 128GB" is $15 USD would be better than eMMC ... this would work with pre-1.5.10 AstLinux.  With some caveats [2].
> 
> Lonnie
> 
> [1] I have read where some Netgate appliances stopped booting because after a couple years the eMMC failed.
> 
> [2] https://doc.astlinux-project.org/userdoc:boot-usb-storage
> 
> 
> 
> > On May 4, 2025, at 7:59 PM, Michael Knill <mic...@ip...> wrote:
> > 
> > Hi All
> >  There is new Protecli hardware (https://protectli.com/product/v1210/) which I was wondering if it was compatible with Astlinux? I would be wanting to use the onboard 32G eMMC.
> >  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-users mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-users
> > 
> > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
> 
> 
> 
> 
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Re: [Astlinux-users] New Protectli hardware

[Michael K. <mic...@ip...>]

Thanks Lonnie for the info. Yes I was aware Netgate had some eMMC issues.

Interesting concept using a USB Flash drive for storage. This could be quite handy for field hardware replacement e.g. just move across the drive to the new hardware.

Regards
Michael Knill


From: Lonnie Abelbeck <li...@lo...>
Date: Monday, 5 May 2025 at 12:46 pm
To: AstLinux Users Mailing List <ast...@li...>
Subject: Re: [Astlinux-users] New Protectli hardware
Hi Michael,

In mid-2020 I purchased a "Protectli FW4B CPU J3160 NIC x4" with Coreboot, and it worked with AstLinux out of the box.

The "V1210 – 2 Port Intel® N5105" should work (test to be sure) with the just released AstLinux 1.5.10 as it uses M.2 NVMe.

AstLinux does not support eMMC storage (kernel CONFIG_MMC disabled).  Supporting eMMC has been discussed, but being non-removable, slowish and typically of poor quality, it was never a production solution in my mind. [1]

I recently purchased a "Silicon Power 128GB NVMe M.2" for $19 USD, a far better choice than non-removable eMMC.

Even quality (stubby) USB storage "SAMSUNG FIT Plus 3.1 USB Flash Drive, 128GB" is $15 USD would be better than eMMC ... this would work with pre-1.5.10 AstLinux.  With some caveats [2].

Lonnie

[1] I have read where some Netgate appliances stopped booting because after a couple years the eMMC failed.

[2] https://doc.astlinux-project.org/userdoc:boot-usb-storage



> On May 4, 2025, at 7:59 PM, Michael Knill <mic...@ip...> wrote:
>
> Hi All
>  There is new Protecli hardware (https://protectli.com/product/v1210/) which I was wondering if it was compatible with Astlinux? I would be wanting to use the onboard 32G eMMC.
>  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-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....




_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Re: [Astlinux-users] New Protectli hardware

[Lonnie A. <li...@lo...>]

Hi Michael,

In mid-2020 I purchased a "Protectli FW4B CPU J3160 NIC x4" with Coreboot, and it worked with AstLinux out of the box.

The "V1210 – 2 Port Intel® N5105" should work (test to be sure) with the just released AstLinux 1.5.10 as it uses M.2 NVMe.

AstLinux does not support eMMC storage (kernel CONFIG_MMC disabled).  Supporting eMMC has been discussed, but being non-removable, slowish and typically of poor quality, it was never a production solution in my mind. [1]

I recently purchased a "Silicon Power 128GB NVMe M.2" for $19 USD, a far better choice than non-removable eMMC.

Even quality (stubby) USB storage "SAMSUNG FIT Plus 3.1 USB Flash Drive, 128GB" is $15 USD would be better than eMMC ... this would work with pre-1.5.10 AstLinux.  With some caveats [2].

Lonnie

[1] I have read where some Netgate appliances stopped booting because after a couple years the eMMC failed.

[2] https://doc.astlinux-project.org/userdoc:boot-usb-storage



> On May 4, 2025, at 7:59 PM, Michael Knill <mic...@ip...> wrote:
> 
> Hi All
>  There is new Protecli hardware (https://protectli.com/product/v1210/) which I was wondering if it was compatible with Astlinux? I would be wanting to use the onboard 32G eMMC.
>  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-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

[Astlinux-users] New Protectli hardware

[Michael K. <mic...@ip...>]

Hi All

There is new Protecli hardware (https://protectli.com/product/v1210/) which I was wondering if it was compatible with Astlinux? I would be wanting to use the onboard 32G eMMC.

Regards

Michael Knill
Managing Director

D: +61 2 6189 1360<tel:+61261891360>
P: +61 2 6140 4656<tel:+61261404656>
E: mic...@ip...<mailto:mic...@ip...>
W: ipcsolutions.com.au<https://ipcsolutions.com.au/>

 [Icon  Description automatically generated]
Smarter Business Communications

Re: [Astlinux-users] [Astlinux-devel] Announcing AstLinux Release: 1.5.10

[Michael K. <mic...@ip...>]

Thanks Lonnie for the info.

Regards
Michael Knill


From: Lonnie Abelbeck <li...@lo...>
Date: Thursday, 1 May 2025 at 12:00 pm
To: AstLinux Users Mailing List <ast...@li...>
Subject: Re: [Astlinux-users] [Astlinux-devel] Announcing AstLinux Release: 1.5.10
Hi Michael,

We have no plans on supporting ARM hardware.  There are single NIC x86_64 boxes [1] that cost about the same (or less) than Raspberry Pi systems (board, case, power, etc.).

As for the old Qotom J1900 box, while it works, there are a lot of newer N100 boxes about the same price.  Additionally with 1.5.10, NVMe is supported, so that opens up more bare metal box choices.

Lonnie

[1] https://doc.astlinux-project.org/userdoc:board_bmax_b1_plus



> On Apr 30, 2025, at 6:28 PM, Michael Knill <mic...@ip...> wrote:

> Thanks Lonnie

>  So could it be possible to support some ARM hardware in the future? This would be quite interesting e.g. Rasberry Pi?
>  Regards
> Michael Knill
>
>
> On Apr 30, 2025, at 5:23 PM, Michael Knill <mic...@ip...> wrote:

> Hi Lonnie
>  Some additional interesting hardware here.
> We are looking at putting Astlinux back on hardware again for our Telephony Gateway’s because its cost effective, we have already established the management infrastructure and its so darn reliable (so many issues with OpenWRT based systems).
>  We are looking at using the Qotom Q190S-S01 (https://www.qotom.net/product/33.html) which I assume will be fine as its very similar to the Q190G4N/U?
> I can get this box shipped and ready to go for around $140 USD which is pretty good. Still wish we could use an APU though as they were incredibly reliable ☹
>   Regards
> Michael Knill



_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Re: [Astlinux-users] [Astlinux-devel] Announcing AstLinux Release: 1.5.10

[Lonnie A. <li...@lo...>]

Hi Michael,

We have no plans on supporting ARM hardware.  There are single NIC x86_64 boxes [1] that cost about the same (or less) than Raspberry Pi systems (board, case, power, etc.).

As for the old Qotom J1900 box, while it works, there are a lot of newer N100 boxes about the same price.  Additionally with 1.5.10, NVMe is supported, so that opens up more bare metal box choices.

Lonnie

[1] https://doc.astlinux-project.org/userdoc:board_bmax_b1_plus



> On Apr 30, 2025, at 6:28 PM, Michael Knill <mic...@ip...> wrote:

> Thanks Lonnie

>  So could it be possible to support some ARM hardware in the future? This would be quite interesting e.g. Rasberry Pi?
>  Regards
> Michael Knill
>  
> 
> On Apr 30, 2025, at 5:23 PM, Michael Knill <mic...@ip...> wrote:

> Hi Lonnie
>  Some additional interesting hardware here.
> We are looking at putting Astlinux back on hardware again for our Telephony Gateway’s because its cost effective, we have already established the management infrastructure and its so darn reliable (so many issues with OpenWRT based systems).
>  We are looking at using the Qotom Q190S-S01 (https://www.qotom.net/product/33.html) which I assume will be fine as its very similar to the Q190G4N/U?
> I can get this box shipped and ready to go for around $140 USD which is pretty good. Still wish we could use an APU though as they were incredibly reliable ☹
>   Regards
> Michael Knill

Re: [Astlinux-users] [Astlinux-devel] Announcing AstLinux Release: 1.5.10

[Michael K. <mic...@ip...>]

Hi Lonnie

Some additional interesting hardware here.
We are looking at putting Astlinux back on hardware again for our Telephony Gateway’s because its cost effective, we have already established the management infrastructure and its so darn reliable (so many issues with OpenWRT based systems).

We are looking at using the Qotom Q190S-S01 (https://www.qotom.net/product/33.html) which I assume will be fine as its very similar to the Q190G4N/U?
I can get this box shipped and ready to go for around $140 USD which is pretty good. Still wish we could use an APU though as they were incredibly reliable ☹

Regards
Michael Knill


From: Lonnie Abelbeck <li...@lo...>
Date: Thursday, 1 May 2025 at 6:08 am
To: AstLinux Users Mailing List <ast...@li...>
Cc: AstLinux Developers Mailing List <ast...@li...>
Subject: [Astlinux-devel] Announcing AstLinux Release: 1.5.10
Announcing AstLinux Release: 1.5.10

More Info: AstLinux Project
https://www.astlinux-project.org/

New Documentation Topics:
Qotom Q10922H6 Intel N100 Fanless Appliance [1]
MeLE QuieterDL Intel N100 Fanless Mini PC [2]
UTM (macOS Apple Silicon) [3]

AstLinux 1.5.10 Highlights:
* Asterisk Versions: 16.30.0, 18.26.1, 20.13.0

* Linux Kernel 5.10.236-cip59, security and bug fixes (Switch to using the "Civil Infrastructure Platform" SLTS v5.10 kernel)
* RUNNIX, version bump to runnix-0.6.22
* r8125, version 9.015.00, Realtek RTL8125 2.5-Gigabit Ethernet Network Driver
* OpenSSH, version 8.4p1, security fix: CVE-2025-26465
* libcurl (curl) version bump to 8.13.0, security fix: CVE-2025-0167, CVE-2025-0665, CVE-2025-0725
* expat, version bump to 2.7.1, security fixes: CVE-2024-8176
* htop, version bump to 3.4.1
* keepalived, version bump to 2.3.3
* kmod, version bump to 34.2
* Monit, version bump to 5.35.1
* msmtp, version bump to 1.8.28
* sqlite, version bump to 3.49.1
* tarsnap, version bump to 1.0.41, "Trust No One" encrypted backups using the Tarsnap Backup service
* virtiofs, for genx86_64-vm builds, Proxmox 8.4 and later supports this feature via QEMU on the host
* vnStat, version bump to 2.13
* ca-certificates, update trusted root certificates 2025-02-25
* Time Zone Database update, tzdata2025b and php-timezonedb-2025.2
* Asterisk '16se' (stable edition) version 16.30.0 is the last Asterisk 16.x "Legacy" version, built --without-pjproject and --without-dahdi
* Package upgrades providing important security and bug fixes

Full ChangeLog:
https://raw.githubusercontent.com/astlinux-project/astlinux/1.5.10/docs/ChangeLog.txt

All users are encouraged to upgrade, read the ChangeLog for the details.

AstLinux Team

[1] https://doc.astlinux-project.org/userdoc:board_qotom_q10922h6
[2] https://doc.astlinux-project.org/userdoc:board_mele_quieterdl
[3] https://doc.astlinux-project.org/userdoc:guest_vm_utm

_______________________________________________
Astlinux-devel mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-devel

[Astlinux-users] Announcing AstLinux Release: 1.5.10

[Lonnie A. <li...@lo...>]

Announcing AstLinux Release: 1.5.10

More Info: AstLinux Project
https://www.astlinux-project.org/

New Documentation Topics:
Qotom Q10922H6 Intel N100 Fanless Appliance [1]
MeLE QuieterDL Intel N100 Fanless Mini PC [2]
UTM (macOS Apple Silicon) [3]

AstLinux 1.5.10 Highlights:
* Asterisk Versions: 16.30.0, 18.26.1, 20.13.0

* Linux Kernel 5.10.236-cip59, security and bug fixes (Switch to using the "Civil Infrastructure Platform" SLTS v5.10 kernel)
* RUNNIX, version bump to runnix-0.6.22
* r8125, version 9.015.00, Realtek RTL8125 2.5-Gigabit Ethernet Network Driver
* OpenSSH, version 8.4p1, security fix: CVE-2025-26465
* libcurl (curl) version bump to 8.13.0, security fix: CVE-2025-0167, CVE-2025-0665, CVE-2025-0725
* expat, version bump to 2.7.1, security fixes: CVE-2024-8176
* htop, version bump to 3.4.1
* keepalived, version bump to 2.3.3
* kmod, version bump to 34.2
* Monit, version bump to 5.35.1
* msmtp, version bump to 1.8.28
* sqlite, version bump to 3.49.1
* tarsnap, version bump to 1.0.41, "Trust No One" encrypted backups using the Tarsnap Backup service
* virtiofs, for genx86_64-vm builds, Proxmox 8.4 and later supports this feature via QEMU on the host
* vnStat, version bump to 2.13
* ca-certificates, update trusted root certificates 2025-02-25
* Time Zone Database update, tzdata2025b and php-timezonedb-2025.2
* Asterisk '16se' (stable edition) version 16.30.0 is the last Asterisk 16.x "Legacy" version, built --without-pjproject and --without-dahdi
* Package upgrades providing important security and bug fixes

Full ChangeLog:
https://raw.githubusercontent.com/astlinux-project/astlinux/1.5.10/docs/ChangeLog.txt

All users are encouraged to upgrade, read the ChangeLog for the details.

AstLinux Team

[1] https://doc.astlinux-project.org/userdoc:board_qotom_q10922h6
[2] https://doc.astlinux-project.org/userdoc:board_mele_quieterdl
[3] https://doc.astlinux-project.org/userdoc:guest_vm_utm

Re: [Astlinux-users] Astlinux with Asterisk 20

[Michael K. <mic...@ip...>]

Thanks Michael.

PS not sure if anyone has used the Asterisk Guru GPT for ChatGPT. Its excellent so I may end up moving to PJSIP anyway.

Regards
Michael Knill


From: Michael Keuter <li...@mk...>
Date: Saturday, 19 April 2025 at 5:24 pm
To: ast...@li... <ast...@li...>
Subject: Re: [Astlinux-users] Astlinux with Asterisk 20
Yes, chan_sip is still built in AstLinux for Asterisk 20.

Sent from a mobile device.

Michael Keuter


Am 19.04.2025 um 08:52 schrieb Michael Knill <mic...@ip...>:

Hi Group

I’m reading that chan_sip is no longer built by default in Asterisk 19. Has this been added to Asterisk 20 in Astlinux?
I know I need to go to pjsip but I’m hanging out as long as I can.

Regards
Michael Knill

_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Re: [Astlinux-users] Astlinux with Asterisk 20

[Michael K. <li...@mk...>]

Yes, chan_sip is still built in AstLinux for Asterisk 20.

Sent from a mobile device.

Michael Keuter

> Am 19.04.2025 um 08:52 schrieb Michael Knill <mic...@ip...>:
> 
> 
> Hi Group
>  
> I’m reading that chan_sip is no longer built by default in Asterisk 19. Has this been added to Asterisk 20 in Astlinux?
> I know I need to go to pjsip but I’m hanging out as long as I can.
>  
> Regards
> Michael Knill
>  
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

[Astlinux-users] Astlinux with Asterisk 20

[Michael K. <mic...@ip...>]

Hi Group

I’m reading that chan_sip is no longer built by default in Asterisk 19. Has this been added to Asterisk 20 in Astlinux?
I know I need to go to pjsip but I’m hanging out as long as I can.

Regards
Michael Knill

Re: [Astlinux-users] Zabbix Agent User Parameters

[Dan R. <da...@ry...>]

[Off list for noise mitigation.]

Thanks for the tip, Lonnie.  

I'm now in pretty good shape after a day of tinkering and testing. 
However,  I checked this and no zabbix files appear.   

Zabbix is a very useful tool!  

Best wishes,

Dan​  
​
On Wednesday, 26-03-2025 at 12:21 Lonnie Abelbeck wrote:



Hi Dan,

Just a tip, when things are not acting as expected while editing using
the CLI, issue the "show-union" command:

# show-union
-- example output --
/mnt/asturw/stat/var/www/admin/.htpasswd
/mnt/asturw/etc/passwd-
/mnt/asturw/etc/passwd
/mnt/asturw/etc/rc.modules
/mnt/asturw/etc/shadow
/mnt/asturw/etc/shadow-
/mnt/asturw/etc/udev/rules.d/70-persistent-net.rules
--

Your show-union files may differ, but if there are files with 'zabbix'
in them, that is a sign of overwritten init.d scripts, symlinks or
such.

Lonnie


> On Mar 26, 2025, at 9:58 AM, Dan Ryson  wrote:
> 
> Hi Lonnie and Team AstLinux,
> 
> After reviewing the zabbix init.d script, it's apparent that the
provided documentation and code is perfect.  Specifically,
"additional" parameters in /mnt/kd/zabbix_agentd.userparams.conf are
included.  
> 
> I've repeated my prior steps but can't repeat the problem that I
thought I observed.  Please file this one under USER ERROR.
> 
> Thank you for the guidance.  I also appreciate going the extra
mile to check the script.  Apologies for the confusion.
> 
> Dan​
> ​
> On Wednesday, 26-03-2025 at 8:41 Lonnie Abelbeck wrote:
> Hi Dan,
> 
> Reference here [1], zabbix init.d script.
> 
> If "/mnt/kd/zabbix_agentd.conf" exists, then the complete agent
config must be defined there.
> 
> If "/mnt/kd/zabbix_agentd.userparams.conf" is defined, and no
"/mnt/kd/zabbix_agentd.conf", then an autogenerated entry:
> --
> Include=/mnt/kd/zabbix_agentd.userparams.conf
> --
> will be included in the autogenerated config.
> 
> Lonnie
> 
> [1]
https://github.com/astlinux-project/astlinux/blob/1e27e446214c991eab6ce88f18549ce2c48b57c3/package/zabbix/zabbix.init#L116
> 
> 
> 
> > On Mar 26, 2025, at 7:04 AM, Dan Ryson  wrote:
> > 
> > Hi Michael,
> > 
> > Thanks for the prompt reply and your insight.  
> > 
> > I misunderstood that files added to /mnt/kd replace and do not add
to an autogenerated file.  Zabbix agent continues to work fine after
renaming zabbix_agentd.userparams.conf =>
zabbix_agentd.conf.  Apparently, either file name in /mnt/kd does
the same thing.  
> > 
> > Best wishes,
> > 
> > Dan​   
> > ​
> > On Tuesday, 25-03-2025 at 19:14 Michael Knill wrote:
> > Hi Dan
> >  
> > We use Zabbix extensively with Astlinux and it has become a
critical part of our infrastructure.
> >  
> > Just updating zabbix_agentd.userparams.conf should be all that you
need to edit. We use PSK so we have updated the init file to add this
but should not be necessary normally.
> > In Astlinux, normally autogenerated files added to /mnt/kd will
replace and not add to an autogenerated file as part of the init
process so yes this would be expected behaviour.
> >  
> > Regards
> > Michael Knill
> >  
> >  
> > From: Dan Ryson 
> > Date: Wednesday, 26 March 2025 at 3:02 am
> > To: AstLinux Users Mailing List 
> > Subject: [Astlinux-users] Zabbix Agent User Parameters
> > Team AstLinux,
> > 
> > I recently tried to enable Zabbix and a custom Zabbix Agent user
parameter to diagnose a fleeting, intermittent networking problem. 
> > 
> > The AstLinux documentation (here) was a great start.  However, I
ran into trouble while trying to "include" a custom user parameter
using added file /mnt/kd/zabbix_agentd.userparams.conf as suggested by
the instructions.  That file contained a single line starting with
"UserParameter=".
> > 
> > After some troubleshooting, I found a comment in
/usr/bin/zabbix_agentd.conf explaining to edit
/mnt/kd/zabbix_agentd.conf instead.  (Note the missing "userparams"
part.)  Much to my surprise, using that file name prevented the
zabbix_agent from starting.  It wasn't until I put the whole
configuration (including Server, ListenPort, etc.) into
/mnt/kd/zabbix_agentd.conf that the agent began working.  The custom
UserParameter, added as the last line, is also working. 
> > 
> > Is this the expected behavior?  Or is there something that I can
do to allow the auto-generated web parameters to be used by zabbix
agent - while adding the UserParameter via a separate file as
suggested by the documentation?
> > 
> > Thanks for any insight.
> > 
> > Dan​ _______________________________________________
> > Astlinux-users mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-users
> > 
> > Donations to support AstLinux are graciously accepted via PayPal
to pa...@kr....
> 
> 
> 
> 
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to
pa...@kr...._______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to
pa...@kr....




_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to
pa...@kr....

Re: [Astlinux-users] Zabbix Agent User Parameters

[Lonnie A. <li...@lo...>]

Hi Dan,

Just a tip, when things are not acting as expected while editing using the CLI, issue the "show-union" command:

# show-union
-- example output --
/mnt/asturw/stat/var/www/admin/.htpasswd
/mnt/asturw/etc/passwd-
/mnt/asturw/etc/passwd
/mnt/asturw/etc/rc.modules
/mnt/asturw/etc/shadow
/mnt/asturw/etc/shadow-
/mnt/asturw/etc/udev/rules.d/70-persistent-net.rules
--

Your show-union files may differ, but if there are files with 'zabbix' in them, that is a sign of overwritten init.d scripts, symlinks or such.

Lonnie


> On Mar 26, 2025, at 9:58 AM, Dan Ryson <da...@ry...> wrote:
> 
> Hi Lonnie and Team AstLinux,
> 
> After reviewing the zabbix init.d script, it's apparent that the provided documentation and code is perfect.  Specifically, "additional" parameters in /mnt/kd/zabbix_agentd.userparams.conf are included.  
> 
> I've repeated my prior steps but can't repeat the problem that I thought I observed.  Please file this one under USER ERROR.
> 
> Thank you for the guidance.  I also appreciate going the extra mile to check the script.  Apologies for the confusion.
> 
> Dan​
> ​
> On Wednesday, 26-03-2025 at 8:41 Lonnie Abelbeck wrote:
> Hi Dan,
> 
> Reference here [1], zabbix init.d script.
> 
> If "/mnt/kd/zabbix_agentd.conf" exists, then the complete agent config must be defined there.
> 
> If "/mnt/kd/zabbix_agentd.userparams.conf" is defined, and no "/mnt/kd/zabbix_agentd.conf", then an autogenerated entry:
> --
> Include=/mnt/kd/zabbix_agentd.userparams.conf
> --
> will be included in the autogenerated config.
> 
> Lonnie
> 
> [1] https://github.com/astlinux-project/astlinux/blob/1e27e446214c991eab6ce88f18549ce2c48b57c3/package/zabbix/zabbix.init#L116
> 
> 
> 
> > On Mar 26, 2025, at 7:04 AM, Dan Ryson <da...@ry...> wrote:
> > 
> > Hi Michael,
> > 
> > Thanks for the prompt reply and your insight.  
> > 
> > I misunderstood that files added to /mnt/kd replace and do not add to an autogenerated file.  Zabbix agent continues to work fine after renaming zabbix_agentd.userparams.conf => zabbix_agentd.conf.  Apparently, either file name in /mnt/kd does the same thing.  
> > 
> > Best wishes,
> > 
> > Dan​   
> > ​
> > On Tuesday, 25-03-2025 at 19:14 Michael Knill wrote:
> > Hi Dan
> >  
> > We use Zabbix extensively with Astlinux and it has become a critical part of our infrastructure.
> >  
> > Just updating zabbix_agentd.userparams.conf should be all that you need to edit. We use PSK so we have updated the init file to add this but should not be necessary normally.
> > In Astlinux, normally autogenerated files added to /mnt/kd will replace and not add to an autogenerated file as part of the init process so yes this would be expected behaviour.
> >  
> > Regards
> > Michael Knill
> >  
> >  
> > From: Dan Ryson <da...@ry...>
> > Date: Wednesday, 26 March 2025 at 3:02 am
> > To: AstLinux Users Mailing List <ast...@li...>
> > Subject: [Astlinux-users] Zabbix Agent User Parameters
> > Team AstLinux,
> > 
> > I recently tried to enable Zabbix and a custom Zabbix Agent user parameter to diagnose a fleeting, intermittent networking problem. 
> > 
> > The AstLinux documentation (here) was a great start.  However, I ran into trouble while trying to "include" a custom user parameter using added file /mnt/kd/zabbix_agentd.userparams.conf as suggested by the instructions.  That file contained a single line starting with "UserParameter=".
> > 
> > After some troubleshooting, I found a comment in /usr/bin/zabbix_agentd.conf explaining to edit /mnt/kd/zabbix_agentd.conf instead.  (Note the missing "userparams" part.)  Much to my surprise, using that file name prevented the zabbix_agent from starting.  It wasn't until I put the whole configuration (including Server, ListenPort, etc.) into /mnt/kd/zabbix_agentd.conf that the agent began working.  The custom UserParameter, added as the last line, is also working. 
> > 
> > Is this the expected behavior?  Or is there something that I can do to allow the auto-generated web parameters to be used by zabbix agent - while adding the UserParameter via a separate file as suggested by the documentation?
> > 
> > Thanks for any insight.
> > 
> > Dan​ _______________________________________________
> > Astlinux-users mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-users
> > 
> > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
> 
> 
> 
> 
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr...._______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Re: [Astlinux-users] Zabbix Agent User Parameters

[Dan R. <da...@ry...>]

Hi Lonnie and Team AstLinux,

After reviewing the zabbix init.d script, it's apparent that the
provided documentation and code is perfect.  Specifically,
"additional" parameters in /mnt/kd/zabbix_agentd.userparams.conf are
included.  

I've repeated my prior steps but can't repeat the problem that I
thought I observed.    Please file this one under USER ERROR.

Thank you for the guidance.  I also appreciate going the extra mile
to check the script.  Apologies for the confusion.

Dan​
​
On Wednesday, 26-03-2025 at 8:41 Lonnie Abelbeck wrote:



Hi Dan,

Reference here [1], zabbix init.d script.

If "/mnt/kd/zabbix_agentd.conf" exists, then the complete agent config
must be defined there.

If "/mnt/kd/zabbix_agentd.userparams.conf" is defined, and no
"/mnt/kd/zabbix_agentd.conf", then an autogenerated entry:
--
Include=/mnt/kd/zabbix_agentd.userparams.conf
--
will be included in the autogenerated config.

Lonnie

[1]
https://github.com/astlinux-project/astlinux/blob/1e27e446214c991eab6ce88f18549ce2c48b57c3/package/zabbix/zabbix.init#L116



> On Mar 26, 2025, at 7:04 AM, Dan Ryson  wrote:
> 
> Hi Michael,
> 
> Thanks for the prompt reply and your insight.  
> 
> I misunderstood that files added to /mnt/kd replace and do not add
to an autogenerated file.  Zabbix agent continues to work fine after
renaming zabbix_agentd.userparams.conf =>
zabbix_agentd.conf.  Apparently, either file name in /mnt/kd does
the same thing.  
> 
> Best wishes,
> 
> Dan​   
> ​
> On Tuesday, 25-03-2025 at 19:14 Michael Knill wrote:
> Hi Dan
>  
> We use Zabbix extensively with Astlinux and it has become a critical
part of our infrastructure.
>  
> Just updating zabbix_agentd.userparams.conf should be all that you
need to edit. We use PSK so we have updated the init file to add this
but should not be necessary normally.
> In Astlinux, normally autogenerated files added to /mnt/kd will
replace and not add to an autogenerated file as part of the init
process so yes this would be expected behaviour.
>  
> Regards
> Michael Knill
>  
>  
> From: Dan Ryson 
> Date: Wednesday, 26 March 2025 at 3:02 am
> To: AstLinux Users Mailing List 
> Subject: [Astlinux-users] Zabbix Agent User Parameters
> Team AstLinux,
> 
> I recently tried to enable Zabbix and a custom Zabbix Agent user
parameter to diagnose a fleeting, intermittent networking problem. 
> 
> The AstLinux documentation (here) was a great start.  However, I
ran into trouble while trying to "include" a custom user parameter
using added file /mnt/kd/zabbix_agentd.userparams.conf as suggested by
the instructions.  That file contained a single line starting with
"UserParameter=".
> 
> After some troubleshooting, I found a comment in
/usr/bin/zabbix_agentd.conf explaining to edit
/mnt/kd/zabbix_agentd.conf instead.  (Note the missing "userparams"
part.)  Much to my surprise, using that file name prevented the
zabbix_agent from starting.  It wasn't until I put the whole
configuration (including Server, ListenPort, etc.) into
/mnt/kd/zabbix_agentd.conf that the agent began working.  The custom
UserParameter, added as the last line, is also working. 
> 
> Is this the expected behavior?  Or is there something that I can
do to allow the auto-generated web parameters to be used by zabbix
agent - while adding the UserParameter via a separate file as
suggested by the documentation?
> 
> Thanks for any insight.
> 
> Dan​ _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to
pa...@kr....




_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to
pa...@kr....

Re: [Astlinux-users] Zabbix Agent User Parameters

[Lonnie A. <li...@lo...>]

Hi Dan,

Reference here [1], zabbix init.d script.

If "/mnt/kd/zabbix_agentd.conf" exists, then the complete agent config must be defined there.

If "/mnt/kd/zabbix_agentd.userparams.conf" is defined, and no "/mnt/kd/zabbix_agentd.conf", then an autogenerated entry:
--
Include=/mnt/kd/zabbix_agentd.userparams.conf
--
will be included in the autogenerated config.

Lonnie

[1] https://github.com/astlinux-project/astlinux/blob/1e27e446214c991eab6ce88f18549ce2c48b57c3/package/zabbix/zabbix.init#L116



> On Mar 26, 2025, at 7:04 AM, Dan Ryson <da...@ry...> wrote:
> 
> Hi Michael,
> 
> Thanks for the prompt reply and your insight.  
> 
> I misunderstood that files added to /mnt/kd replace and do not add to an autogenerated file.  Zabbix agent continues to work fine after renaming zabbix_agentd.userparams.conf => zabbix_agentd.conf.  Apparently, either file name in /mnt/kd does the same thing.  
> 
> Best wishes,
> 
> Dan​   
> ​
> On Tuesday, 25-03-2025 at 19:14 Michael Knill wrote:
> Hi Dan
>  
> We use Zabbix extensively with Astlinux and it has become a critical part of our infrastructure.
>  
> Just updating zabbix_agentd.userparams.conf should be all that you need to edit. We use PSK so we have updated the init file to add this but should not be necessary normally.
> In Astlinux, normally autogenerated files added to /mnt/kd will replace and not add to an autogenerated file as part of the init process so yes this would be expected behaviour.
>  
> Regards
> Michael Knill
>  
>  
> From: Dan Ryson <da...@ry...>
> Date: Wednesday, 26 March 2025 at 3:02 am
> To: AstLinux Users Mailing List <ast...@li...>
> Subject: [Astlinux-users] Zabbix Agent User Parameters
> Team AstLinux,
> 
> I recently tried to enable Zabbix and a custom Zabbix Agent user parameter to diagnose a fleeting, intermittent networking problem. 
> 
> The AstLinux documentation (here) was a great start.  However, I ran into trouble while trying to "include" a custom user parameter using added file /mnt/kd/zabbix_agentd.userparams.conf as suggested by the instructions.  That file contained a single line starting with "UserParameter=".
> 
> After some troubleshooting, I found a comment in /usr/bin/zabbix_agentd.conf explaining to edit /mnt/kd/zabbix_agentd.conf instead.  (Note the missing "userparams" part.)  Much to my surprise, using that file name prevented the zabbix_agent from starting.  It wasn't until I put the whole configuration (including Server, ListenPort, etc.) into /mnt/kd/zabbix_agentd.conf that the agent began working.  The custom UserParameter, added as the last line, is also working. 
> 
> Is this the expected behavior?  Or is there something that I can do to allow the auto-generated web parameters to be used by zabbix agent - while adding the UserParameter via a separate file as suggested by the documentation?
> 
> Thanks for any insight.
> 
> Dan​ _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Re: [Astlinux-users] Zabbix Agent User Parameters

[Dan R. <da...@ry...>]

Hi Michael,

Thanks for the prompt reply and your insight.  

I misunderstood that files added to /mnt/kd _replace_ and do not _add
to_ an autogenerated file.  Zabbix agent continues to work fine after
renaming zabbix_agentd.userparams.conf =>  zabbix_agentd.conf. 
Apparently, either file name in /mnt/kd does the same thing.  

Best wishes,

Dan​   
​
On Tuesday, 25-03-2025 at 19:14 Michael Knill wrote:






Hi Dan



 



We use Zabbix extensively with Astlinux and it has become a critical
part of our infrastructure.



 



Just updating zabbix_agentd.userparams.conf should be all that you
need to edit. We use PSK so we have updated the init file to add this
but should not be necessary normally.



In Astlinux, normally autogenerated files added to /mnt/kd will
replace and not add to an autogenerated file as part of the init
process so yes this would be expected behaviour.



 





Regards



Michael Knill

  

 



 







 From: Dan Ryson 
Date: Wednesday, 26 March 2025 at 3:02 am
To: AstLinux Users Mailing List 
Subject: [Astlinux-users] Zabbix Agent User Parameters

 

Team AstLinux,

I recently tried to enable Zabbix and a custom Zabbix Agent user
parameter to diagnose a fleeting, intermittent networking problem.  

The AstLinux documentation (here [1]) was a great start.  However, I
ran into trouble while trying to "include" a custom user parameter
using added file /mnt/kd/zabbix_agentd.userparams.conf as suggested by
the instructions.  That file contained a single line starting with
"UserParameter=". 

After some troubleshooting, I found a comment in
/usr/bin/zabbix_agentd.conf explaining to edit
/mnt/kd/zabbix_agentd.conf instead.  (Note the missing "userparams"
part.)  Much to my surprise, using that file name prevented the
zabbix_agent from starting.  It wasn't until I put the whole
configuration (including Server, ListenPort, etc.) into
/mnt/kd/zabbix_agentd.conf that the agent began working.  The custom
UserParameter, added as the last line, is also working.  

Is this the expected behavior?  Or is there something that I can do
to allow the auto-generated web parameters to be used by zabbix agent
- while adding the UserParameter via a separate file as suggested by
the documentation?

Thanks for any insight.

Dan​ 

    



Links:
------
[1] https://doc.astlinux-project.org/userdoc:tt_zabbix_monitoring

Re: [Astlinux-users] Zabbix Agent User Parameters

[Michael K. <mic...@ip...>]

Hi Dan

We use Zabbix extensively with Astlinux and it has become a critical part of our infrastructure.

Just updating zabbix_agentd.userparams.conf should be all that you need to edit. We use PSK so we have updated the init file to add this but should not be necessary normally.
In Astlinux, normally autogenerated files added to /mnt/kd will replace and not add to an autogenerated file as part of the init process so yes this would be expected behaviour.

Regards
Michael Knill


From: Dan Ryson <da...@ry...>
Date: Wednesday, 26 March 2025 at 3:02 am
To: AstLinux Users Mailing List <ast...@li...>
Subject: [Astlinux-users] Zabbix Agent User Parameters
Team AstLinux,

I recently tried to enable Zabbix and a custom Zabbix Agent user parameter to diagnose a fleeting, intermittent networking problem.

The AstLinux documentation (here<https://doc.astlinux-project.org/userdoc:tt_zabbix_monitoring>) was a great start.  However, I ran into trouble while trying to "include" a custom user parameter using added file /mnt/kd/zabbix_agentd.userparams.conf as suggested by the instructions.  That file contained a single line starting with "UserParameter=".

After some troubleshooting, I found a comment in /usr/bin/zabbix_agentd.conf explaining to edit /mnt/kd/zabbix_agentd.conf instead.  (Note the missing "userparams" part.)  Much to my surprise, using that file name prevented the zabbix_agent from starting.  It wasn't until I put the whole configuration (including Server, ListenPort, etc.) into /mnt/kd/zabbix_agentd.conf that the agent began working.  The custom UserParameter, added as the last line, is also working.

Is this the expected behavior?  Or is there something that I can do to allow the auto-generated web parameters to be used by zabbix agent - while adding the UserParameter via a separate file as suggested by the documentation?

Thanks for any insight.

Dan​

[Astlinux-users] Zabbix Agent User Parameters

[Dan R. <da...@ry...>]

Team AstLinux,

I recently tried to enable Zabbix and a custom Zabbix Agent user
parameter to diagnose a fleeting, intermittent networking problem.  

The AstLinux documentation (here [1]) was a great start.  However, I
ran into trouble while trying to "include" a custom user parameter
using added file /mnt/kd/zabbix_agentd.userparams.conf as suggested by
the instructions.  That file contained a single line starting with
"UserParameter=".  

After some troubleshooting, I found a comment in
/usr/bin/zabbix_agentd.conf explaining to edit
/mnt/kd/zabbix_agentd.conf instead.  (Note the missing "userparams"
part.)  Much to my surprise, using that file name prevented the
zabbix_agent from starting.  It wasn't until I put the whole
configuration (including Server, ListenPort, etc.) into
/mnt/kd/zabbix_agentd.conf that the agent began working.  The custom
UserParameter, added as the last line, is also working.  

Is this the expected behavior?  Or is there something that I can do
to allow the auto-generated web parameters to be used by zabbix agent
- while adding the UserParameter via a separate file as suggested by
the documentation?

Thanks for any insight.

Dan​

Links:
------
[1] https://doc.astlinux-project.org/userdoc:tt_zabbix_monitoring

Re: [Astlinux-users] Assistance Needed with Old ASTLinux PBX Setup

[Michael K. <mic...@ip...>]

Hi Nedi

More information would be required to assist with troubleshooting. Can you explain the current architecture a little better regarding network connectivity.

Regards
Michael Knill


From: Silver via Astlinux-users <ast...@li...>
Date: Friday, 31 January 2025 at 12:10 pm
To: Astlinux list <ast...@li...>
Cc: Silver <ne...@gm...>
Subject: [Astlinux-users] Assistance Needed with Old ASTLinux PBX Setup
Hello,
I am currently facing an issue with an older version of ASTLinux PBX that I’ve been using for several years. Recently, I moved the PBX to a new location and established a VPN connection, but since the relocation, the previously working clients no longer function correctly. They briefly register, then immediately unregister.
I do not have double NAT in place; I have a router directly in the DMZ that builds the VPN connection.
The phones are Snom and Gigaset models. Both are unable to maintain a stable connection.
However, when using the VPN from my MacBook with a phone app, the internal numbers stay registered permanently over the same OpenVPN connection.
At location 1, the phones have IP addresses like 192.168.1.10, 192.168.1.11, etc. When connected via VPN, they register with IP addresses like 192.168.20.xx, but with different ports.
At location 2, the IP addresses are 192.168.5.10, 192.168.5.11, and so on. Everything works fine at the new location, but only five phones are connected.
Here is the relevant part of my SIP configuration:
[general]
useragent=MYOLDPBX
port=5060
context = from-sip-external
alwaysauthreject=yes
deny=0.0.0.0/0.0.0.0
permit=192.168.1.0/255.255.255.0
permit=192.168.20.0/255.255.255.0
permit=192.168.5.0/255.255.255.0
localnet=192.168.20.0/24
localnet=192.168.5.0/24
localnet=192.168.1.0/24
allowguest=no
disallow=all
allow=alaw
allow=ulaw
language=de
registerattempts=3
registertimeout=20
register_retry_403=yes
maxexpiry=3600
defaultexpiry=200
qualify=1000
notifycid=yes
srvlookup=no
nat=yes
allowsubscribe=yes
subscribecontext=hints
trustrpid=yes
sendrpid=yes
faxdetect=yes



SIP Numbers Name/username Host Dyn Forcerport ACL Port Status
10/10 192.168.20.2 D N 36395 UNREACHABLE
11/11 192.168.20.2 D N 54644 UNREACHABLE
110/110 192.168.5.29 D N 5060 OK (8 ms)
111/111 192.168.5.59 D N 5060 OK (10 ms)
113/113 192.168.5.129 D N 5060 OK (9 ms)
114/114 192.168.5.228 D N 5060 OK (9 ms)
12/12 192.168.20.2 D N 41784 UNREACHABLE
13/13 192.168.20.2 D N 54146 OK (12 ms)
14/14 192.168.20.2 D N 54627 UNREACHABLE

As you can see, some devices are marked as unreachable despite using the correct IP addresses.
Could you please help me troubleshoot this issue? I would appreciate any guidance on resolving the connectivity problem, particularly with regards to the VPN setup and SIP registration.
Best regards,
nedi

[Astlinux-users] Assistance Needed with Old ASTLinux PBX Setup

[Silver <ne...@gm...>]

Hello, 
I am currently facing an issue with an older version of ASTLinux PBX that I’ve been using for several years. Recently, I moved the PBX to a new location and established a VPN connection, but since the relocation, the previously working clients no longer function correctly. They briefly register, then immediately unregister.
I do not have double NAT in place; I have a router directly in the DMZ that builds the VPN connection.

The phones are Snom and Gigaset models. Both are unable to maintain a stable connection.

However, when using the VPN from my MacBook with a phone app, the internal numbers stay registered permanently over the same OpenVPN connection.

At location 1, the phones have IP addresses like 192.168.1.10, 192.168.1.11, etc. When connected via VPN, they register with IP addresses like 192.168.20.xx, but with different ports.

At location 2, the IP addresses are 192.168.5.10, 192.168.5.11, and so on. Everything works fine at the new location, but only five phones are connected.

Here is the relevant part of my SIP configuration:

[general]
useragent=MYOLDPBX
port=5060
context = from-sip-external
alwaysauthreject=yes
deny=0.0.0.0/0.0.0.0
permit=192.168.1.0/255.255.255.0
permit=192.168.20.0/255.255.255.0
permit=192.168.5.0/255.255.255.0
localnet=192.168.20.0/24
localnet=192.168.5.0/24
localnet=192.168.1.0/24
allowguest=no
disallow=all
allow=alaw
allow=ulaw
language=de
registerattempts=3
registertimeout=20
register_retry_403=yes
maxexpiry=3600
defaultexpiry=200
qualify=1000
notifycid=yes
srvlookup=no
nat=yes
allowsubscribe=yes
subscribecontext=hints
trustrpid=yes
sendrpid=yes
faxdetect=yes



SIP Numbers Name/username Host Dyn Forcerport ACL Port Status 
10/10 192.168.20.2 D N 36395 UNREACHABLE 
11/11 192.168.20.2 D N 54644 UNREACHABLE 
110/110 192.168.5.29 D N 5060 OK (8 ms) 
111/111 192.168.5.59 D N 5060 OK (10 ms) 
113/113 192.168.5.129 D N 5060 OK (9 ms) 
114/114 192.168.5.228 D N 5060 OK (9 ms) 
12/12 192.168.20.2 D N 41784 UNREACHABLE 
13/13 192.168.20.2 D N 54146 OK (12 ms) 
14/14 192.168.20.2 D N 54627 UNREACHABLE 

As you can see, some devices are marked as unreachable despite using the correct IP addresses.

Could you please help me troubleshoot this issue? I would appreciate any guidance on resolving the connectivity problem, particularly with regards to the VPN setup and SIP registration.

Best regards,

nedi

[Astlinux-users] Announcing AstLinux Release: 1.5.6

[Lonnie A. <li...@lo...>]

Announcing AstLinux Release: 1.5.6

More Info: AstLinux Project
https://www.astlinux-project.org/

AstLinux 1.5.6 Highlights:
* Asterisk Versions: 16.30.0, 18.26.1, 20.11.1

* Linux Kernel 5.10.233, security and bug fixes
* RUNNIX, version bump to runnix-0.6.20
* r8125, version 9.014.01, Realtek RTL8125 2.5-Gigabit Ethernet Network Driver
* OpenSSL, version 1.1.1w, security fixes: CVE-2023-5678, CVE-2024-0727, CVE-2024-2511, CVE-2024-4741, CVE-2024-5535, CVE-2024-9143
* libcurl (curl) version bump to 8.11.1, security fix: CVE-2024-9681, CVE-2024-11053
* expat, version bump to 2.6.4, security fixes: CVE-2024-45490, CVE-2024-45491, CVE-2024-45492, CVE-2024-50602
* iperf3, version bump to 3.18, security fix: CVE-2024-53580
* php, version 7.2.34, add security fixes: CVE-2024-8925, CVE-2024-8927, CVE-2024-8932, CVE-2024-11234, CVE-2024-11236
* unbound, version bump to 1.22.0, security fix: CVE-2024-8508
* chrony, version bump to 4.6.1
* kexec, version bump to 2.0.30
* Monit, version bump to 5.34.4
* s3fs, version bump to 1.95
* screen, version bump to 5.0.0
* sqlite, version bump to 3.47.2
* unionfs (fuse), version bump to 3.6
* ca-certificates, update trusted root certificates 2024-12-31
* mac2vendor, oui.txt database snapshot 2025-01-10
* Time Zone Database update, tzdata2025a and php-timezonedb-2025.1
* Asterisk '16se' (stable edition) version 16.30.0 is the last Asterisk 16.x "Legacy" version, built --without-pjproject and --without-dahdi
* Package upgrades providing important security and bug fixes

Full ChangeLog:
https://raw.githubusercontent.com/astlinux-project/astlinux/1.5.6/docs/ChangeLog.txt

All users are encouraged to upgrade, read the ChangeLog for the details.

AstLinux Team



_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

[Astlinux-users] dhcp-range in dnsmasq.static

[Michael K. <mic...@ip...>]

Hi Group

Well after all these years I realised that I was not configuring dnsmasq DHCP ranges correctly ☹

I was adding the following in dnsmasq.static:
dhcp-range=lan,172.16.16.21,172.16.16.21,24h

I assumed that it overwrote the autogenerated rc.conf range but it appears to append this range as well per what the logs are showing me:
Jan 28 13:49:37 39990-IPCBuild-CM1 daemon.info dnsmasq-dhcp[3027]: DHCP, IP range 172.16.16.50 -- 172.16.16.150, lease time 1d
Jan 28 13:49:37 39990-IPCBuild-CM1 daemon.info dnsmasq-dhcp[3027]: DHCP, IP range 172.16.16.100 -- 172.16.16.220, lease time 1d

I know that I can change the range in user.conf but this changes the DHCP range for ALL LAN interfaces which I do not want. Is there any way to change this?

Regards

Michael Knill
Managing Director

D: +61 2 6189 1360<tel:+61261891360>
P: +61 2 6140 4656<tel:+61261404656>
E: mic...@ip...<mailto:mic...@ip...>
W: ipcsolutions.com.au<https://ipcsolutions.com.au/>

 [Icon  Description automatically generated]
Smarter Business Communications