astlinux-users — AstLinux Users Mailing List

Re: [Astlinux-users] PJSIP migration

[The C. K. <eld...@ya...>]

 PJSIP is confusing at first but after a short time its flow is pretty easy... the part i miss most about CHAN_SIP is the 'sip show peers' in a nice compact easy to read format.. pjsip show endpoints is not so easy..  several lines per station / trunk.. 
you can use the wizard format to have all of your PJSIP parameters in one entry vs multiple objects per peer / trunk. im not sure if astlinux has the wizrd co,piled in or not (ive been using regular asterisk for quite some time..  
    On Sunday, June 22, 2025 at 02:03:12 PM EDT, David Kerr <da...@ke...> wrote:  
 
 I migrated from SIP to PJSIP several months ago.  In general it went okay, but I ran into a problem with one DID provider... outbound would work fine, inbound calls just never arrived and nothing would show up in the asterisk debug messages.  I had to tcpdump the SIP packets to figure out what was going on.
The problem was authentication on the inbound SIP requests... PJSIP/asterisk was sending back an authentication challenge on the inbound calls.  This is typical for outbound, but not inbound and the DID provider could not handle. I commented out the "auth = did_provider" statement and that got it working on inbound calls.
David


On Sun, Jun 22, 2025 at 1:25 PM Dr. Peter Voigt <pv...@uo...> wrote:

Hi Lonie,

thanks for your quick reply. Nice to hear that chan_sip support will be
continued with version 20.x giving me at least some more time for this complex
migration. I've configured Asterisk numerous yours ago and almost left it
untoched as it is simply working. Therefore I am not an Asterisk expert at all
and I am having only little incentive to migrate to res_pjsip with lots of time
needed just to have things working as they to for years.

If you ever stumble over any of these migration scripts, please let me know to
let me give them a try.

Regards,
Peter


On Sat, 2025-06-21 at 17:38 -0500, Lonnie Abelbeck wrote:
> Hi Peter,
> 
> The AstLinux, Asterisk version 20.x [1] still contains chan_sip.  That will be
> the last of chan_sip support.
> 
> Personally I still use chan_sip, so I have no experience migrating to
> chan_pjsip.
> 
> It is my understanding there are scripts to roughly perform the migration for
> you.
> 
> Lonnie
> 
> [1] https://doc.astlinux-project.org/userdoc:tt_asterisk_upgrade_version
> 
> 
> 
> > On Jun 21, 2025, at 11:52 AM, Dr. Peter Voigt <pv...@uo...> wrote:
> > 
> > I am currently running astlinux-1.5.10 x86_64 - Asterisk 18.26.1 using
> > chan_sip.
> > 
> > If reading all information correctly, Asterisk 18 will be the last
> > Asterisk supporting chan_sip.
> > 
> > So I think it is time to start migrating to res_pjsip.so. My current 
> > chan_sip.so configuration is quite simple, just containing two trunk
> > definitions connecting to two different providers and two extensions
> > according
> > to my to phones.
> > 
> > I have checked already that module pjsip is loaded (res_pjsip.so and various
> > modules starting with res_pjsip).
> > 
> > To get a rough understanding of the whole migration process: Will it be
> > enough
> > to migrate configuration file sip.conf to pjsip.conf and subsequently delete
> > sip.conf. Furthermore, is it sufficient to replace any occurance of "SIP" in
> > extensions.conf with "PJSIP"?
> > 
> > I appreciate any feedback including helpful links for further reading
> > possibly
> > showing running pjsip.conf examples.
> > 
> > Regards,
> > Peter
> > 
> > 
> > 
> > _______________________________________________
> > 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] PJSIP migration

[David K. <da...@ke...>]

I migrated from SIP to PJSIP several months ago.  In general it went okay,
but I ran into a problem with one DID provider... outbound would work fine,
inbound calls just never arrived and nothing would show up in the asterisk
debug messages.  I had to tcpdump the SIP packets to figure out what was
going on.

The problem was authentication on the inbound SIP requests...
PJSIP/asterisk was sending back an authentication challenge on the inbound
calls.  This is typical for outbound, but not inbound and the DID provider
could not handle. I commented out the "auth = did_provider" statement and
that got it working on inbound calls.

David



On Sun, Jun 22, 2025 at 1:25 PM Dr. Peter Voigt <pv...@uo...> wrote:

> Hi Lonie,
>
> thanks for your quick reply. Nice to hear that chan_sip support will be
> continued with version 20.x giving me at least some more time for this
> complex
> migration. I've configured Asterisk numerous yours ago and almost left it
> untoched as it is simply working. Therefore I am not an Asterisk expert at
> all
> and I am having only little incentive to migrate to res_pjsip with lots of
> time
> needed just to have things working as they to for years.
>
> If you ever stumble over any of these migration scripts, please let me
> know to
> let me give them a try.
>
> Regards,
> Peter
>
>
> On Sat, 2025-06-21 at 17:38 -0500, Lonnie Abelbeck wrote:
> > Hi Peter,
> >
> > The AstLinux, Asterisk version 20.x [1] still contains chan_sip.  That
> will be
> > the last of chan_sip support.
> >
> > Personally I still use chan_sip, so I have no experience migrating to
> > chan_pjsip.
> >
> > It is my understanding there are scripts to roughly perform the
> migration for
> > you.
> >
> > Lonnie
> >
> > [1] https://doc.astlinux-project.org/userdoc:tt_asterisk_upgrade_version
> >
> >
> >
> > > On Jun 21, 2025, at 11:52 AM, Dr. Peter Voigt <pv...@uo...> wrote:
> > >
> > > I am currently running astlinux-1.5.10 x86_64 - Asterisk 18.26.1 using
> > > chan_sip.
> > >
> > > If reading all information correctly, Asterisk 18 will be the last
> > > Asterisk supporting chan_sip.
> > >
> > > So I think it is time to start migrating to res_pjsip.so. My current
> > > chan_sip.so configuration is quite simple, just containing two trunk
> > > definitions connecting to two different providers and two extensions
> > > according
> > > to my to phones.
> > >
> > > I have checked already that module pjsip is loaded (res_pjsip.so and
> various
> > > modules starting with res_pjsip).
> > >
> > > To get a rough understanding of the whole migration process: Will it be
> > > enough
> > > to migrate configuration file sip.conf to pjsip.conf and subsequently
> delete
> > > sip.conf. Furthermore, is it sufficient to replace any occurance of
> "SIP" in
> > > extensions.conf with "PJSIP"?
> > >
> > > I appreciate any feedback including helpful links for further reading
> > > possibly
> > > showing running pjsip.conf examples.
> > >
> > > Regards,
> > > Peter
> > >
> > >
> > >
> > > _______________________________________________
> > > 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] PJSIP migration

[Dr. P. V. <pv...@uo...>]

Hi Michael,

I did not yet know that there is a special section of ChatGPT dealing with
Asterisk configuration - thanks.

However, my experience with ChatGPT are very mixed especially with detailed
questions on complex topics which tend to be wrong in the first place. And even
if you more or less know that the answer is wrong or at least incomplete and
repeat the questions with more details giving, ChatGPT just agrees with you
about the previous wrong answer but does not give much more valuable information
for me to learn.

Therefore I will probably continue searching for documents and example
cocnfigurations that might be as base for my own configuration.

Last but not least you have to fully understand your final configuration
especially with regard to security.

Regards,
Peter


On Sat, 2025-06-21 at 22:34 +0000, Michael Knill wrote:
> Hi Peter
>  
> I need to do the same thing at some stage.
> I have seen migration articles online for this but I will be using ChatGPT
> with the Asterisk Ace GPT😊
>  
> Regards
> Michael Knill
>  
>  
> From:Dr. Peter Voigt <pv...@uo...>
> Date: Sunday, 22 June 2025 at 3:10 am
> To: AstLinux List <ast...@li...>
> Subject: [Astlinux-users] PJSIP migration
> I am currently running astlinux-1.5.10 x86_64 - Asterisk 18.26.1 using
> chan_sip.
> 
> If reading all information correctly, Asterisk 18 will be the last
> Asterisk supporting chan_sip.
> 
> So I think it is time to start migrating to res_pjsip.so. My current 
> chan_sip.so configuration is quite simple, just containing two trunk
> definitions connecting to two different providers and two extensions according
> to my to phones.
> 
> I have checked already that module pjsip is loaded (res_pjsip.so and various
> modules starting with res_pjsip).
> 
> To get a rough understanding of the whole migration process: Will it be enough
> to migrate configuration file sip.conf to pjsip.conf and subsequently delete
> sip.conf. Furthermore, is it sufficient to replace any occurance of "SIP" in 
> extensions.conf with "PJSIP"?
> 
> I appreciate any feedback including helpful links for further reading possibly
> showing running pjsip.conf examples.
> 
> Regards,
> Peter
> 
> 
> 
> _______________________________________________
> 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] PJSIP migration

[Dr. P. V. <pv...@uo...>]

Hi Lonie,

thanks for your quick reply. Nice to hear that chan_sip support will be
continued with version 20.x giving me at least some more time for this complex
migration. I've configured Asterisk numerous yours ago and almost left it
untoched as it is simply working. Therefore I am not an Asterisk expert at all
and I am having only little incentive to migrate to res_pjsip with lots of time
needed just to have things working as they to for years.

If you ever stumble over any of these migration scripts, please let me know to
let me give them a try.

Regards,
Peter


On Sat, 2025-06-21 at 17:38 -0500, Lonnie Abelbeck wrote:
> Hi Peter,
> 
> The AstLinux, Asterisk version 20.x [1] still contains chan_sip.  That will be
> the last of chan_sip support.
> 
> Personally I still use chan_sip, so I have no experience migrating to
> chan_pjsip.
> 
> It is my understanding there are scripts to roughly perform the migration for
> you.
> 
> Lonnie
> 
> [1] https://doc.astlinux-project.org/userdoc:tt_asterisk_upgrade_version
> 
> 
> 
> > On Jun 21, 2025, at 11:52 AM, Dr. Peter Voigt <pv...@uo...> wrote:
> > 
> > I am currently running astlinux-1.5.10 x86_64 - Asterisk 18.26.1 using
> > chan_sip.
> > 
> > If reading all information correctly, Asterisk 18 will be the last
> > Asterisk supporting chan_sip.
> > 
> > So I think it is time to start migrating to res_pjsip.so. My current 
> > chan_sip.so configuration is quite simple, just containing two trunk
> > definitions connecting to two different providers and two extensions
> > according
> > to my to phones.
> > 
> > I have checked already that module pjsip is loaded (res_pjsip.so and various
> > modules starting with res_pjsip).
> > 
> > To get a rough understanding of the whole migration process: Will it be
> > enough
> > to migrate configuration file sip.conf to pjsip.conf and subsequently delete
> > sip.conf. Furthermore, is it sufficient to replace any occurance of "SIP" in
> > extensions.conf with "PJSIP"?
> > 
> > I appreciate any feedback including helpful links for further reading
> > possibly
> > showing running pjsip.conf examples.
> > 
> > Regards,
> > Peter
> > 
> > 
> > 
> > _______________________________________________
> > 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] PJSIP migration

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

Hi Peter

I need to do the same thing at some stage.
I have seen migration articles online for this but I will be using ChatGPT with the Asterisk Ace GPT 😊

Regards
Michael Knill


From: Dr. Peter Voigt <pv...@uo...>
Date: Sunday, 22 June 2025 at 3:10 am
To: AstLinux List <ast...@li...>
Subject: [Astlinux-users] PJSIP migration
I am currently running astlinux-1.5.10 x86_64 - Asterisk 18.26.1 using
chan_sip.

If reading all information correctly, Asterisk 18 will be the last
Asterisk supporting chan_sip.

So I think it is time to start migrating to res_pjsip.so. My current
chan_sip.so configuration is quite simple, just containing two trunk
definitions connecting to two different providers and two extensions according
to my to phones.

I have checked already that module pjsip is loaded (res_pjsip.so and various
modules starting with res_pjsip).

To get a rough understanding of the whole migration process: Will it be enough
to migrate configuration file sip.conf to pjsip.conf and subsequently delete
sip.conf. Furthermore, is it sufficient to replace any occurance of "SIP" in
extensions.conf with "PJSIP"?

I appreciate any feedback including helpful links for further reading possibly
showing running pjsip.conf examples.

Regards,
Peter



_______________________________________________
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] PJSIP migration

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

Hi Peter,

The AstLinux, Asterisk version 20.x [1] still contains chan_sip.  That will be the last of chan_sip support.

Personally I still use chan_sip, so I have no experience migrating to chan_pjsip.

It is my understanding there are scripts to roughly perform the migration for you.

Lonnie

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



> On Jun 21, 2025, at 11:52 AM, Dr. Peter Voigt <pv...@uo...> wrote:
> 
> I am currently running astlinux-1.5.10 x86_64 - Asterisk 18.26.1 using
> chan_sip.
> 
> If reading all information correctly, Asterisk 18 will be the last
> Asterisk supporting chan_sip.
> 
> So I think it is time to start migrating to res_pjsip.so. My current 
> chan_sip.so configuration is quite simple, just containing two trunk
> definitions connecting to two different providers and two extensions according
> to my to phones.
> 
> I have checked already that module pjsip is loaded (res_pjsip.so and various
> modules starting with res_pjsip).
> 
> To get a rough understanding of the whole migration process: Will it be enough
> to migrate configuration file sip.conf to pjsip.conf and subsequently delete
> sip.conf. Furthermore, is it sufficient to replace any occurance of "SIP" in 
> extensions.conf with "PJSIP"?
> 
> I appreciate any feedback including helpful links for further reading possibly
> showing running pjsip.conf examples.
> 
> Regards,
> Peter
> 
> 
> 
> _______________________________________________
> 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] PJSIP migration

[Dr. P. V. <pv...@uo...>]

I am currently running astlinux-1.5.10 x86_64 - Asterisk 18.26.1 using
chan_sip.

If reading all information correctly, Asterisk 18 will be the last
Asterisk supporting chan_sip.

So I think it is time to start migrating to res_pjsip.so. My current 
chan_sip.so configuration is quite simple, just containing two trunk
definitions connecting to two different providers and two extensions according
to my to phones.

I have checked already that module pjsip is loaded (res_pjsip.so and various
modules starting with res_pjsip).

To get a rough understanding of the whole migration process: Will it be enough
to migrate configuration file sip.conf to pjsip.conf and subsequently delete
sip.conf. Furthermore, is it sufficient to replace any occurance of "SIP" in 
extensions.conf with "PJSIP"?

I appreciate any feedback including helpful links for further reading possibly
showing running pjsip.conf examples.

Regards,
Peter

Re: [Astlinux-users] Use of HD codecs for the Asterisk Record application

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

Yes I believe you would be far better recording in wav/alaw/ulaw e.g. @8K natively and if you could be bothered, use Asterisk ‘file convert’ to g722 if you don’t want to transcode when listening to the announcement internally. I use Set(__SIP_CODEC=alaw) to force this in the dialplan.

If you want HD announcements e.g. if building Public Address applications which sound rubbish at 8K, then you basically need to create an audio file separately and use sox to convert to wav16 and then ‘file convert’ if you want any other formats.

This has been an interesting learning experience for me.

Regards
Michael Knill


From: Lonnie Abelbeck <li...@lo...>
Date: Tuesday, 17 June 2025 at 12:20 am
To: AstLinux Users Mailing List <ast...@li...>
Subject: Re: [Astlinux-users] Use of HD codecs for the Asterisk Record application
Hi Michael,

Per this example [1] it seems "Record(en/custom-menu.g722)" would record what you want, but "slin" format might be more efficient transcoding to other formats.

Lonnie

[1] https://docs.asterisk.org/Deployment/Basic-PBX-Functionality/Auto-attendant-and-IVR-Menus/Record-Application/



> On Jun 15, 2025, at 7:11 PM, Michael Knill <mic...@ip...> wrote:
>
> PS just thought I would reply to this post.
>  It appears that the Asterisk Record application does not natively record at G.722 (see below):
>  CLI> core show channel SIP/1410-0000029b
> -- General --
>            Name: SIP/1410-0000029b
>            Type: SIP
>        UniqueID: 39990-IPCBuild-CM1-1749719640.3701
>        LinkedID: 39990-IPCBuild-CM1-1749719640.3701
>       Caller ID: 1410
> Caller ID Name: (N/A)
> Connected Line ID: *480
> Connected Line ID Name: AH Announcement
> Eff. Connected Line ID: *480
> Eff. Connected Line ID Name: AH Announcement
>     DNID Digits: *7480
>        Language: en_AI
>           State: Up (6)
>   NativeFormats: (g722)
>     WriteFormat: slin
>      ReadFormat: slin
> WriteTranscode: Yes (slin@8000)->(g722@16000)
>   ReadTranscode: Yes (g722@16000)->(slin@8000)
> Time to Hangup: 0
>    Elapsed Time: 0h0m8s
>       Bridge ID: (Not bridged)
> --   PBX   --
>         Context: subFeature-Recordannounce
>       Extension: start
>        Priority: 3
>      Call Group: 0
>    Pickup Group: 0
>     Application: Record
>            Data: /mnt/kd/monitor/announce*480:g722,30,120,k
> Call Identifer: [C-000002b2]
>       Variables:
> RECORDED_FILE=/mnt/kd/monitor/announce*480
> GOSUB_RETVAL=
> conname_dblookup=AH Announcement
> DB_RESULT=AH Announcement
> name_dblookup=
> ARGC=1
> ARG1=*480
> SIPCALLID=0_3708201006@172.30.253.14
> SIPDOMAIN=172.30.253.1
> SIPURI=sip:1410@172.30.253.14:5060
> -- Streams --
> Name: audio-0
>     Type: audio
>     State: sendrecv
>     Group: -1
>     Formats: (g722)
>     Metadata:
>  Rather annoying that I need to record everything in slin!
>  Regards
> Michael Knill
>   From: Michael Knill <mic...@ip...>
> Date: Sunday, 8 June 2025 at 10:14 am
> To: AstLinux Users Mailing List <ast...@li...>
> Subject: Re: [Astlinux-users] Use of HD codecs for the Asterisk Record application
> Hi All
>  Thanks for the reply. No problems with DTMF and current Asterisk sounds. They are all working fine. PS I am setting SIP_CODEC=alaw when dialling externally so there is no transcoding
>  The problem is when I am recording messages for announcements etc. They are written as {filename}.g722 and can be listened to fine as G.722 but just don’t sound as good as I would have expected for a G.722 recording.
> After doing further tests however, it does actually sound better than when recording in wav format but just not as good as the inbuilt prompts in G.722 format.
>  A bit of background for this, our next release will include integration into Azure’s Speech API which is pretty fantastic now. Im going to create my custom messages all now with TTS and I will likely rerecord all the inbuilt prompts as well. Incredible flexibility. Will also be doing voicemail transcription which is working great.
>  Im extremely thankful for the amazing toolbox we have.
>  Regards
> Michael Knill
>   From: Lonnie Abelbeck <li...@lo...>
> Date: Sunday, 8 June 2025 at 12:36 am
> To: AstLinux Users Mailing List <ast...@li...>
> Subject: Re: [Astlinux-users] Use of HD codecs for the Asterisk Record application
> For my internal phones, for many years...
> --
> dtmfmode=rfc2833
> disallow=all
> allow=g722
> allow=ulaw
> --
>
> $ upgrade-asterisk-sounds show
> Installed: asterisk-moh-opsound-g722-2.03, asterisk-moh-opsound-ulaw-2.03, asterisk-core-sounds-en-g722-1.6.1, asterisk-core-sounds-en-ulaw-1.6.1, asterisk-extra-sounds-en-g722-1.5.2, asterisk-extra-sounds-en-ulaw-1.5.2
>
>
> Lonnie
>
>
> > On Jun 7, 2025, at 8:55 AM, Michael Keuter <li...@mk...> wrote:
> >
> > Just a short info:
> > I had sometimes problems with DTMF tones when using G.722. You might need to tweak the DTMF type.
> >
> >> Am 07.06.2025 um 08:52 schrieb Michael Knill <mic...@ip...>:
> >>
> >> Hi Group
> >> Not sure if someone has come across this before. I have decided to use G.722 for internal calls and alaw for external calls and all seems fine so far. All the internal sounds are clear and crisp at G.722
> >> The issue that I have come across is using the Record application which I want to record native G.722. It appears to be working fine e.g. it stores the file as {filename}.g722 and it plays fine however it certainly does not sound like a G.722 recorded call.
> >> Could this be because there is no format_g722.so included?
> >> Do I have any other options?
> >> Im getting to the stage where I don’t really care!
> >> 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
> >
> >
> > Michael
> >
> > https://mksolutions.info
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > 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] Use of HD codecs for the Asterisk Record application

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

Hi Michael,

Per this example [1] it seems "Record(en/custom-menu.g722)" would record what you want, but "slin" format might be more efficient transcoding to other formats.

Lonnie

[1] https://docs.asterisk.org/Deployment/Basic-PBX-Functionality/Auto-attendant-and-IVR-Menus/Record-Application/



> On Jun 15, 2025, at 7:11 PM, Michael Knill <mic...@ip...> wrote:
> 
> PS just thought I would reply to this post.
>  It appears that the Asterisk Record application does not natively record at G.722 (see below):
>  CLI> core show channel SIP/1410-0000029b
> -- General --
>            Name: SIP/1410-0000029b
>            Type: SIP
>        UniqueID: 39990-IPCBuild-CM1-1749719640.3701
>        LinkedID: 39990-IPCBuild-CM1-1749719640.3701
>       Caller ID: 1410
> Caller ID Name: (N/A)
> Connected Line ID: *480
> Connected Line ID Name: AH Announcement
> Eff. Connected Line ID: *480
> Eff. Connected Line ID Name: AH Announcement
>     DNID Digits: *7480
>        Language: en_AI
>           State: Up (6)
>   NativeFormats: (g722)
>     WriteFormat: slin
>      ReadFormat: slin
> WriteTranscode: Yes (slin@8000)->(g722@16000)
>   ReadTranscode: Yes (g722@16000)->(slin@8000)
> Time to Hangup: 0
>    Elapsed Time: 0h0m8s
>       Bridge ID: (Not bridged)
> --   PBX   --
>         Context: subFeature-Recordannounce
>       Extension: start
>        Priority: 3
>      Call Group: 0
>    Pickup Group: 0
>     Application: Record
>            Data: /mnt/kd/monitor/announce*480:g722,30,120,k
> Call Identifer: [C-000002b2]
>       Variables:
> RECORDED_FILE=/mnt/kd/monitor/announce*480
> GOSUB_RETVAL=
> conname_dblookup=AH Announcement
> DB_RESULT=AH Announcement
> name_dblookup=
> ARGC=1
> ARG1=*480
> SIPCALLID=0_3708201006@172.30.253.14
> SIPDOMAIN=172.30.253.1
> SIPURI=sip:1410@172.30.253.14:5060
> -- Streams --
> Name: audio-0
>     Type: audio
>     State: sendrecv
>     Group: -1
>     Formats: (g722)
>     Metadata:
>  Rather annoying that I need to record everything in slin!
>  Regards
> Michael Knill
>   From: Michael Knill <mic...@ip...>
> Date: Sunday, 8 June 2025 at 10:14 am
> To: AstLinux Users Mailing List <ast...@li...>
> Subject: Re: [Astlinux-users] Use of HD codecs for the Asterisk Record application
> Hi All
>  Thanks for the reply. No problems with DTMF and current Asterisk sounds. They are all working fine. PS I am setting SIP_CODEC=alaw when dialling externally so there is no transcoding
>  The problem is when I am recording messages for announcements etc. They are written as {filename}.g722 and can be listened to fine as G.722 but just don’t sound as good as I would have expected for a G.722 recording.
> After doing further tests however, it does actually sound better than when recording in wav format but just not as good as the inbuilt prompts in G.722 format.
>  A bit of background for this, our next release will include integration into Azure’s Speech API which is pretty fantastic now. Im going to create my custom messages all now with TTS and I will likely rerecord all the inbuilt prompts as well. Incredible flexibility. Will also be doing voicemail transcription which is working great.
>  Im extremely thankful for the amazing toolbox we have.
>  Regards
> Michael Knill
>   From: Lonnie Abelbeck <li...@lo...>
> Date: Sunday, 8 June 2025 at 12:36 am
> To: AstLinux Users Mailing List <ast...@li...>
> Subject: Re: [Astlinux-users] Use of HD codecs for the Asterisk Record application
> For my internal phones, for many years...
> --
> dtmfmode=rfc2833
> disallow=all
> allow=g722
> allow=ulaw
> --
> 
> $ upgrade-asterisk-sounds show
> Installed: asterisk-moh-opsound-g722-2.03, asterisk-moh-opsound-ulaw-2.03, asterisk-core-sounds-en-g722-1.6.1, asterisk-core-sounds-en-ulaw-1.6.1, asterisk-extra-sounds-en-g722-1.5.2, asterisk-extra-sounds-en-ulaw-1.5.2
> 
> 
> Lonnie
> 
> 
> > On Jun 7, 2025, at 8:55 AM, Michael Keuter <li...@mk...> wrote:
> > 
> > Just a short info: 
> > I had sometimes problems with DTMF tones when using G.722. You might need to tweak the DTMF type.
> > 
> >> Am 07.06.2025 um 08:52 schrieb Michael Knill <mic...@ip...>:
> >> 
> >> Hi Group
> >> Not sure if someone has come across this before. I have decided to use G.722 for internal calls and alaw for external calls and all seems fine so far. All the internal sounds are clear and crisp at G.722
> >> The issue that I have come across is using the Record application which I want to record native G.722. It appears to be working fine e.g. it stores the file as {filename}.g722 and it plays fine however it certainly does not sound like a G.722 recorded call.
> >> Could this be because there is no format_g722.so included?
> >> Do I have any other options?
> >> Im getting to the stage where I don’t really care!
> >> 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
> > 
> > 
> > Michael
> > 
> > https://mksolutions.info
> > 
> > 
> > 
> > 
> > 
> > 
> > _______________________________________________
> > 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] Use of HD codecs for the Asterisk Record application

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

PS just thought I would reply to this post.

It appears that the Asterisk Record application does not natively record at G.722 (see below):

CLI> core show channel SIP/1410-0000029b
-- General --
           Name: SIP/1410-0000029b
           Type: SIP
       UniqueID: 39990-IPCBuild-CM1-1749719640.3701
       LinkedID: 39990-IPCBuild-CM1-1749719640.3701
      Caller ID: 1410
Caller ID Name: (N/A)
Connected Line ID: *480
Connected Line ID Name: AH Announcement
Eff. Connected Line ID: *480
Eff. Connected Line ID Name: AH Announcement
    DNID Digits: *7480
       Language: en_AI
          State: Up (6)
  NativeFormats: (g722)
    WriteFormat: slin
     ReadFormat: slin
WriteTranscode: Yes (slin@8000)->(g722@16000)
  ReadTranscode: Yes (g722@16000)->(slin@8000)
Time to Hangup: 0
   Elapsed Time: 0h0m8s
      Bridge ID: (Not bridged)
--   PBX   --
        Context: subFeature-Recordannounce
      Extension: start
       Priority: 3
     Call Group: 0
   Pickup Group: 0
    Application: Record
           Data: /mnt/kd/monitor/announce*480:g722,30,120,k
Call Identifer: [C-000002b2]
      Variables:
RECORDED_FILE=/mnt/kd/monitor/announce*480
GOSUB_RETVAL=
conname_dblookup=AH Announcement
DB_RESULT=AH Announcement
name_dblookup=
ARGC=1
ARG1=*480
SIPCALLID=0_3708201006@172.30.253.14<mailto:SIPCALLID=0_3708201006@172.30.253.14>
SIPDOMAIN=172.30.253.1
SIPURI=sip:1410@172.30.253.14:5060
-- Streams --
Name: audio-0
    Type: audio
    State: sendrecv
    Group: -1
    Formats: (g722)
    Metadata:

Rather annoying that I need to record everything in slin!

Regards
Michael Knill


From: Michael Knill <mic...@ip...>
Date: Sunday, 8 June 2025 at 10:14 am
To: AstLinux Users Mailing List <ast...@li...>
Subject: Re: [Astlinux-users] Use of HD codecs for the Asterisk Record application
Hi All

Thanks for the reply. No problems with DTMF and current Asterisk sounds. They are all working fine. PS I am setting SIP_CODEC=alaw when dialling externally so there is no transcoding

The problem is when I am recording messages for announcements etc. They are written as {filename}.g722 and can be listened to fine as G.722 but just don’t sound as good as I would have expected for a G.722 recording.
After doing further tests however, it does actually sound better than when recording in wav format but just not as good as the inbuilt prompts in G.722 format.

A bit of background for this, our next release will include integration into Azure’s Speech API which is pretty fantastic now. Im going to create my custom messages all now with TTS and I will likely rerecord all the inbuilt prompts as well. Incredible flexibility. Will also be doing voicemail transcription which is working great.

Im extremely thankful for the amazing toolbox we have.

Regards
Michael Knill


From: Lonnie Abelbeck <li...@lo...>
Date: Sunday, 8 June 2025 at 12:36 am
To: AstLinux Users Mailing List <ast...@li...>
Subject: Re: [Astlinux-users] Use of HD codecs for the Asterisk Record application
For my internal phones, for many years...
--
dtmfmode=rfc2833
disallow=all
allow=g722
allow=ulaw
--

$ upgrade-asterisk-sounds show
Installed: asterisk-moh-opsound-g722-2.03, asterisk-moh-opsound-ulaw-2.03, asterisk-core-sounds-en-g722-1.6.1, asterisk-core-sounds-en-ulaw-1.6.1, asterisk-extra-sounds-en-g722-1.5.2, asterisk-extra-sounds-en-ulaw-1.5.2


Lonnie


> On Jun 7, 2025, at 8:55 AM, Michael Keuter <li...@mk...> wrote:
>
> Just a short info:
> I had sometimes problems with DTMF tones when using G.722. You might need to tweak the DTMF type.
>
>> Am 07.06.2025 um 08:52 schrieb Michael Knill <mic...@ip...>:
>>
>> Hi Group
>> Not sure if someone has come across this before. I have decided to use G.722 for internal calls and alaw for external calls and all seems fine so far. All the internal sounds are clear and crisp at G.722
>> The issue that I have come across is using the Record application which I want to record native G.722. It appears to be working fine e.g. it stores the file as {filename}.g722 and it plays fine however it certainly does not sound like a G.722 recorded call.
>> Could this be because there is no format_g722.so included?
>> Do I have any other options?
>> Im getting to the stage where I don’t really care!
>> 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
>
>
> Michael
>
> https://mksolutions.info
>
>
>
>
>
>
> _______________________________________________
> 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] Use of HD codecs for the Asterisk Record application

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

Hi All

Thanks for the reply. No problems with DTMF and current Asterisk sounds. They are all working fine. PS I am setting SIP_CODEC=alaw when dialling externally so there is no transcoding

The problem is when I am recording messages for announcements etc. They are written as {filename}.g722 and can be listened to fine as G.722 but just don’t sound as good as I would have expected for a G.722 recording.
After doing further tests however, it does actually sound better than when recording in wav format but just not as good as the inbuilt prompts in G.722 format.

A bit of background for this, our next release will include integration into Azure’s Speech API which is pretty fantastic now. Im going to create my custom messages all now with TTS and I will likely rerecord all the inbuilt prompts as well. Incredible flexibility. Will also be doing voicemail transcription which is working great.

Im extremely thankful for the amazing toolbox we have.

Regards
Michael Knill


From: Lonnie Abelbeck <li...@lo...>
Date: Sunday, 8 June 2025 at 12:36 am
To: AstLinux Users Mailing List <ast...@li...>
Subject: Re: [Astlinux-users] Use of HD codecs for the Asterisk Record application
For my internal phones, for many years...
--
dtmfmode=rfc2833
disallow=all
allow=g722
allow=ulaw
--

$ upgrade-asterisk-sounds show
Installed: asterisk-moh-opsound-g722-2.03, asterisk-moh-opsound-ulaw-2.03, asterisk-core-sounds-en-g722-1.6.1, asterisk-core-sounds-en-ulaw-1.6.1, asterisk-extra-sounds-en-g722-1.5.2, asterisk-extra-sounds-en-ulaw-1.5.2


Lonnie


> On Jun 7, 2025, at 8:55 AM, Michael Keuter <li...@mk...> wrote:
>
> Just a short info:
> I had sometimes problems with DTMF tones when using G.722. You might need to tweak the DTMF type.
>
>> Am 07.06.2025 um 08:52 schrieb Michael Knill <mic...@ip...>:
>>
>> Hi Group
>> Not sure if someone has come across this before. I have decided to use G.722 for internal calls and alaw for external calls and all seems fine so far. All the internal sounds are clear and crisp at G.722
>> The issue that I have come across is using the Record application which I want to record native G.722. It appears to be working fine e.g. it stores the file as {filename}.g722 and it plays fine however it certainly does not sound like a G.722 recorded call.
>> Could this be because there is no format_g722.so included?
>> Do I have any other options?
>> Im getting to the stage where I don’t really care!
>> 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
>
>
> Michael
>
> https://mksolutions.info
>
>
>
>
>
>
> _______________________________________________
> 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] Use of HD codecs for the Asterisk Record application

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

For my internal phones, for many years...
--
dtmfmode=rfc2833
disallow=all
allow=g722
allow=ulaw
--

$ upgrade-asterisk-sounds show
Installed: asterisk-moh-opsound-g722-2.03, asterisk-moh-opsound-ulaw-2.03, asterisk-core-sounds-en-g722-1.6.1, asterisk-core-sounds-en-ulaw-1.6.1, asterisk-extra-sounds-en-g722-1.5.2, asterisk-extra-sounds-en-ulaw-1.5.2


Lonnie


> On Jun 7, 2025, at 8:55 AM, Michael Keuter <li...@mk...> wrote:
> 
> Just a short info: 
> I had sometimes problems with DTMF tones when using G.722. You might need to tweak the DTMF type.
> 
>> Am 07.06.2025 um 08:52 schrieb Michael Knill <mic...@ip...>:
>> 
>> Hi Group
>> Not sure if someone has come across this before. I have decided to use G.722 for internal calls and alaw for external calls and all seems fine so far. All the internal sounds are clear and crisp at G.722
>> The issue that I have come across is using the Record application which I want to record native G.722. It appears to be working fine e.g. it stores the file as {filename}.g722 and it plays fine however it certainly does not sound like a G.722 recorded call.
>> Could this be because there is no format_g722.so included?
>> Do I have any other options?
>> Im getting to the stage where I don’t really care!
>> 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
> 
> 
> Michael
> 
> https://mksolutions.info
> 
> 
> 
> 
> 
> 
> _______________________________________________
> 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] Use of HD codecs for the Asterisk Record application

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

Just a short info: 
I had sometimes problems with DTMF tones when using G.722. You might need to tweak the DTMF type.

> Am 07.06.2025 um 08:52 schrieb Michael Knill <mic...@ip...>:
> 
> Hi Group
>  Not sure if someone has come across this before. I have decided to use G.722 for internal calls and alaw for external calls and all seems fine so far. All the internal sounds are clear and crisp at G.722
> The issue that I have come across is using the Record application which I want to record native G.722. It appears to be working fine e.g. it stores the file as {filename}.g722 and it plays fine however it certainly does not sound like a G.722 recorded call.
>  Could this be because there is no format_g722.so included?
> Do I have any other options?
>  Im getting to the stage where I don’t really care!
>  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


Michael

https://mksolutions.info

[Astlinux-users] Use of HD codecs for the Asterisk Record application

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

Hi Group

Not sure if someone has come across this before. I have decided to use G.722 for internal calls and alaw for external calls and all seems fine so far. All the internal sounds are clear and crisp at G.722
The issue that I have come across is using the Record application which I want to record native G.722. It appears to be working fine e.g. it stores the file as {filename}.g722 and it plays fine however it certainly does not sound like a G.722 recorded call.

Could this be because there is no format_g722.so included?
Do I have any other options?

Im getting to the stage where I don’t really care!

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] New Protectli hardware

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

Thanks Lonnie for the heads up.

I could really only warrant the V1210 with NVMe however if its compatible: https://protectli.com/product/v1210/

Regards
Michael Knill


From: Lonnie Abelbeck <li...@lo...>
Date: Monday, 2 June 2025 at 2:14 am
To: AstLinux Users Mailing List <ast...@li...>
Subject: Re: [Astlinux-users] New Protectli hardware
Hi Michael (AU),

I recently purchased a "Protectli VP2430 CPU N150 NIC x4" [1]

Purchased directly from Protectli ($299 USD), with the coreboot+UEFI BIOS.

I tested with AstLinux 1.5.10. both 2.5“ SATA SSD and M.2 2280 NVMe, as well as genx86_64-serial and genx86_64 builds.  All worked well.

BTW, coreboot has come a long way from the early PC Engines days.

The Protectli VP2430 has now replaced my 7 year old Qotom Q530G6 Core i3 box as my edge router, VPN and PBX.  So far, so good.

With a 2.5“ SATA SSD installed, serial console, here is a little info...

(The NICs do not have a registered MAC vendor, only a generic one)
# mac2vendor 64:62:66
IEEE Registration Authority

(NVMe does not show as it is not installed)
# lspci
00:00.0 Host bridge: Intel Corporation Device 461c
00:02.0 VGA compatible controller: Intel Corporation Alder Lake-N [Intel Graphics]
00:0d.0 USB controller: Intel Corporation Device 464e
00:14.0 USB controller: Intel Corporation Alder Lake-N PCH USB 3.2 xHCI Host Controller
00:14.2 RAM memory: Intel Corporation Alder Lake-N PCH Shared SRAM
00:15.0 Serial bus controller: Intel Corporation Device 54e8
00:17.0 SATA controller: Intel Corporation Device 54d3
00:19.0 Serial bus controller: Intel Corporation Device 54c5
00:1a.0 SD Host controller: Intel Corporation Device 54c4
00:1c.0 PCI bridge: Intel Corporation Device 54b9
00:1c.2 PCI bridge: Intel Corporation Device 54ba
00:1c.3 PCI bridge: Intel Corporation Device 54bb
00:1c.6 PCI bridge: Intel Corporation Device 54be
00:1f.0 ISA bridge: Intel Corporation Alder Lake-N PCH eSPI Controller
00:1f.3 Audio device: Intel Corporation Alder Lake-N PCH High Definition Audio Controller
00:1f.4 SMBus: Intel Corporation Device 54a3
00:1f.5 Serial bus controller: Intel Corporation Device 54a4
01:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-V (rev 04)
02:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-V (rev 04)
03:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-V (rev 04)
04:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-V (rev 04)

# sensors
coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +36.0 C  (high = +105.0 C, crit = +105.0 C)
Core 0:        +35.0 C  (high = +105.0 C, crit = +105.0 C)
Core 1:        +35.0 C  (high = +105.0 C, crit = +105.0 C)
Core 2:        +35.0 C  (high = +105.0 C, crit = +105.0 C)
Core 3:        +35.0 C  (high = +105.0 C, crit = +105.0 C)


Lonnie

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


> 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 (AU),

I recently purchased a "Protectli VP2430 CPU N150 NIC x4" [1]

Purchased directly from Protectli ($299 USD), with the coreboot+UEFI BIOS.

I tested with AstLinux 1.5.10. both 2.5“ SATA SSD and M.2 2280 NVMe, as well as genx86_64-serial and genx86_64 builds.  All worked well.

BTW, coreboot has come a long way from the early PC Engines days.

The Protectli VP2430 has now replaced my 7 year old Qotom Q530G6 Core i3 box as my edge router, VPN and PBX.  So far, so good.

With a 2.5“ SATA SSD installed, serial console, here is a little info...

(The NICs do not have a registered MAC vendor, only a generic one)
# mac2vendor 64:62:66
IEEE Registration Authority

(NVMe does not show as it is not installed)
# lspci
00:00.0 Host bridge: Intel Corporation Device 461c
00:02.0 VGA compatible controller: Intel Corporation Alder Lake-N [Intel Graphics]
00:0d.0 USB controller: Intel Corporation Device 464e
00:14.0 USB controller: Intel Corporation Alder Lake-N PCH USB 3.2 xHCI Host Controller
00:14.2 RAM memory: Intel Corporation Alder Lake-N PCH Shared SRAM
00:15.0 Serial bus controller: Intel Corporation Device 54e8
00:17.0 SATA controller: Intel Corporation Device 54d3
00:19.0 Serial bus controller: Intel Corporation Device 54c5
00:1a.0 SD Host controller: Intel Corporation Device 54c4
00:1c.0 PCI bridge: Intel Corporation Device 54b9
00:1c.2 PCI bridge: Intel Corporation Device 54ba
00:1c.3 PCI bridge: Intel Corporation Device 54bb
00:1c.6 PCI bridge: Intel Corporation Device 54be
00:1f.0 ISA bridge: Intel Corporation Alder Lake-N PCH eSPI Controller
00:1f.3 Audio device: Intel Corporation Alder Lake-N PCH High Definition Audio Controller
00:1f.4 SMBus: Intel Corporation Device 54a3
00:1f.5 Serial bus controller: Intel Corporation Device 54a4
01:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-V (rev 04)
02:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-V (rev 04)
03:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-V (rev 04)
04:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-V (rev 04)

# sensors
coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +36.0 C  (high = +105.0 C, crit = +105.0 C)
Core 0:        +35.0 C  (high = +105.0 C, crit = +105.0 C)
Core 1:        +35.0 C  (high = +105.0 C, crit = +105.0 C)
Core 2:        +35.0 C  (high = +105.0 C, crit = +105.0 C)
Core 3:        +35.0 C  (high = +105.0 C, crit = +105.0 C)


Lonnie

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


> 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....

Re: [Astlinux-users] New Protectli hardware

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

As everything needs to be seamless, the only way to guarantee a clean shutdown is for the script to do a reboot after it deletes it.
But good to know its possible to do although I think its unlikely I will end up using a USB.

Regards
Michael Knill


From: Lonnie Abelbeck <li...@lo...>
Date: Thursday, 8 May 2025 at 12:10 pm
To: ast...@li... <ast...@li...>
Subject: Re: [Astlinux-users] New Protectli hardware
I suppose you could compare the number of NICs on the box with the number in the .rules file.

Or simply remove the .rules file on shutdown. :-)

Lonnie


On May 7, 2025, at 8:37 PM, Michael Knill <mic...@ip...> wrote:

Thanks Lonnie

Couldn’t you also check for a difference in the number of NIC’s?

Regards
Michael Knill


From: Lonnie Abelbeck <li...@lo...>
Date: Thursday, 8 May 2025 at 11:32 am
To: AstLinux Users Mailing List <ast...@li...>
Subject: Re: [Astlinux-users] New Protectli hardware
The test for "if the MAC’s are different" might be more difficult than you imagine as the USB drive could be plugged into different boxes with a different number of NICs.

Lonnie



> On May 7, 2025, at 7:02 PM, Michael Knill <mic...@ip...> wrote:
>
> 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....
> _______________________________________________
> 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...>]

I suppose you could compare the number of NICs on the box with the number in the .rules file.

Or simply remove the .rules file on shutdown. :-)

Lonnie

> On May 7, 2025, at 8:37 PM, Michael Knill <mic...@ip...> wrote:
> 
> 
> Thanks Lonnie
>  
> Couldn’t you also check for a difference in the number of NIC’s?
>  
> Regards
> Michael Knill
>  
>  
> From: Lonnie Abelbeck <li...@lo...>
> Date: Thursday, 8 May 2025 at 11:32 am
> To: AstLinux Users Mailing List <ast...@li...>
> Subject: Re: [Astlinux-users] New Protectli hardware
> 
> The test for "if the MAC’s are different" might be more difficult than you imagine as the USB drive could be plugged into different boxes with a different number of NICs.
> 
> Lonnie
> 
> 
> 
> > On May 7, 2025, at 7:02 PM, Michael Knill <mic...@ip...> wrote:
> >
> > 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....
> > _______________________________________________
> > 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

Couldn’t you also check for a difference in the number of NIC’s?

Regards
Michael Knill


From: Lonnie Abelbeck <li...@lo...>
Date: Thursday, 8 May 2025 at 11:32 am
To: AstLinux Users Mailing List <ast...@li...>
Subject: Re: [Astlinux-users] New Protectli hardware
The test for "if the MAC’s are different" might be more difficult than you imagine as the USB drive could be plugged into different boxes with a different number of NICs.

Lonnie



> On May 7, 2025, at 7:02 PM, Michael Knill <mic...@ip...> wrote:
>
> 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....
> _______________________________________________
> 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...>]

The test for "if the MAC’s are different" might be more difficult than you imagine as the USB drive could be plugged into different boxes with a different number of NICs.

Lonnie



> On May 7, 2025, at 7:02 PM, Michael Knill <mic...@ip...> wrote:
> 
> 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....
> _______________________________________________
> 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

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....