Menu
▾
▴
astlinux-devel — The AstLinux development environment, compilation, etc
You can subscribe to this list here.
| 2008 |
Jan
|
Feb
|
Mar
(41) |
Apr
(35) |
May
(18) |
Jun
(5) |
Jul
(4) |
Aug
(37) |
Sep
(9) |
Oct
(20) |
Nov
(50) |
Dec
(217) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
(212) |
Feb
(76) |
Mar
(113) |
Apr
(88) |
May
(130) |
Jun
(54) |
Jul
(208) |
Aug
(223) |
Sep
(112) |
Oct
(63) |
Nov
(131) |
Dec
(103) |
| 2010 |
Jan
(247) |
Feb
(130) |
Mar
(43) |
Apr
(92) |
May
(40) |
Jun
(43) |
Jul
(43) |
Aug
(80) |
Sep
(44) |
Oct
(74) |
Nov
(21) |
Dec
(46) |
| 2011 |
Jan
(36) |
Feb
(11) |
Mar
(21) |
Apr
(33) |
May
(4) |
Jun
(12) |
Jul
(5) |
Aug
(20) |
Sep
|
Oct
(64) |
Nov
(26) |
Dec
(71) |
| 2012 |
Jan
(13) |
Feb
(24) |
Mar
(11) |
Apr
(2) |
May
(10) |
Jun
(5) |
Jul
(13) |
Aug
(7) |
Sep
(26) |
Oct
(22) |
Nov
(17) |
Dec
(16) |
| 2013 |
Jan
(6) |
Feb
(6) |
Mar
(6) |
Apr
(8) |
May
(20) |
Jun
|
Jul
(1) |
Aug
(4) |
Sep
(18) |
Oct
(3) |
Nov
(14) |
Dec
(33) |
| 2014 |
Jan
(26) |
Feb
(6) |
Mar
(69) |
Apr
(10) |
May
|
Jun
(8) |
Jul
(18) |
Aug
(22) |
Sep
(19) |
Oct
(17) |
Nov
|
Dec
(4) |
| 2015 |
Jan
(14) |
Feb
(18) |
Mar
|
Apr
|
May
(26) |
Jun
(8) |
Jul
(9) |
Aug
(10) |
Sep
(15) |
Oct
(2) |
Nov
(30) |
Dec
(33) |
| 2016 |
Jan
(1) |
Feb
(24) |
Mar
(19) |
Apr
(1) |
May
|
Jun
(3) |
Jul
(1) |
Aug
(1) |
Sep
(20) |
Oct
(5) |
Nov
(14) |
Dec
(4) |
| 2017 |
Jan
(15) |
Feb
(35) |
Mar
(10) |
Apr
(9) |
May
(14) |
Jun
(33) |
Jul
(1) |
Aug
(27) |
Sep
(7) |
Oct
|
Nov
(10) |
Dec
(15) |
| 2018 |
Jan
(29) |
Feb
|
Mar
(2) |
Apr
(1) |
May
(11) |
Jun
|
Jul
(1) |
Aug
(8) |
Sep
(11) |
Oct
(22) |
Nov
(9) |
Dec
(13) |
| 2019 |
Jan
(1) |
Feb
(7) |
Mar
(3) |
Apr
(21) |
May
(34) |
Jun
(36) |
Jul
(18) |
Aug
(17) |
Sep
(19) |
Oct
(8) |
Nov
(3) |
Dec
|
| 2020 |
Jan
|
Feb
(4) |
Mar
(8) |
Apr
(29) |
May
(50) |
Jun
(8) |
Jul
(2) |
Aug
(10) |
Sep
(1) |
Oct
(7) |
Nov
(9) |
Dec
(19) |
| 2021 |
Jan
(2) |
Feb
(9) |
Mar
(6) |
Apr
(21) |
May
(13) |
Jun
(11) |
Jul
(2) |
Aug
(1) |
Sep
(3) |
Oct
(26) |
Nov
(2) |
Dec
(16) |
| 2022 |
Jan
(8) |
Feb
(7) |
Mar
(1) |
Apr
(13) |
May
(1) |
Jun
(4) |
Jul
(4) |
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
(1) |
| 2023 |
Jan
(2) |
Feb
(3) |
Mar
(16) |
Apr
|
May
(2) |
Jun
(1) |
Jul
(4) |
Aug
(13) |
Sep
(8) |
Oct
(6) |
Nov
(4) |
Dec
|
| 2024 |
Jan
(3) |
Feb
(3) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(5) |
Aug
|
Sep
(1) |
Oct
|
Nov
(5) |
Dec
|
| 2025 |
Jan
(4) |
Feb
(2) |
Mar
|
Apr
(11) |
May
(1) |
Jun
(9) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Lonnie A. <li...@lo...> - 2025-06-20 11:15:41
|
> Is it safe to switch an existing installed VM to UEFI and just reboot? "poweroff" AstLinux in the VM, switch the VM to "BIOS: UEFI", then Start the VM. I have an AstLinux VM with UEFI enabled mostly for testing. I almost always use SSH when interacting. Also, I seem to recall Proxmox issues a warning about temporary efi vars or some such ... you can ignore that. Lonnie > On Jun 19, 2025, at 10:38 PM, David Kerr <da...@ke...> wrote: > > Thanks Lonnie, > Looks like I was wrong on the color, I do get that. But I would like to have a higher resolution. So, if I use UEFI bios then I should get that? I've always installed Astlinux with the default SeaBIOS (on Proxmox). Is it safe to switch an existing installed VM to UEFI and just reboot? > > David > > <image.png> > > On Thu, Jun 19, 2025 at 9:06 PM Lonnie Abelbeck <li...@lo...> wrote: > Hi David, > > The VNC console has been color whenever I use it. Not sure how that could be B/W. > > Note that if you use UEFI the screen will be higher resolution, for example [1]. > > Though it has always seemed to be a fixed window size, just a lower resolution with Legacy BIOS. > > Lonnie > > [1] > > > > > > On Jun 19, 2025, at 5:09 PM, David Kerr <Da...@Ke...> wrote: > > > > Running Astlinux in a VM and using VNC (Proxmox) console, the text display is a very confined 80x24 and black-and-white. Every other text-based VM that I fire up, I can resize the VNC window and the number of rows/columns expands, and text colors are shown. > > > > Is it possible to have Astlinux do the same? > > > > Thanks > > David > > _______________________________________________ > > Astlinux-devel mailing list > > Ast...@li... > > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: David K. <da...@ke...> - 2025-06-20 03:39:03
|
Thanks Lonnie, Looks like I was wrong on the color, I do get that. But I would like to have a higher resolution. So, if I use UEFI bios then I should get that? I've always installed Astlinux with the default SeaBIOS (on Proxmox). Is it safe to switch an existing installed VM to UEFI and just reboot? David [image: image.png] On Thu, Jun 19, 2025 at 9:06 PM Lonnie Abelbeck <li...@lo...> wrote: > Hi David, > > The VNC console has been color whenever I use it. Not sure how that could > be B/W. > > Note that if you use UEFI the screen will be higher resolution, for > example [1]. > > Though it has always seemed to be a fixed window size, just a lower > resolution with Legacy BIOS. > > Lonnie > > [1] > > > > > > On Jun 19, 2025, at 5:09 PM, David Kerr <Da...@Ke...> wrote: > > > > Running Astlinux in a VM and using VNC (Proxmox) console, the text > display is a very confined 80x24 and black-and-white. Every other > text-based VM that I fire up, I can resize the VNC window and the number of > rows/columns expands, and text colors are shown. > > > > Is it possible to have Astlinux do the same? > > > > Thanks > > David > > _______________________________________________ > > Astlinux-devel mailing list > > Ast...@li... > > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > |
|
From: Lonnie A. <li...@lo...> - 2025-06-20 01:06:28
|
Hi David, The VNC console has been color whenever I use it. Not sure how that could be B/W. Note that if you use UEFI the screen will be higher resolution, for example [1]. Though it has always seemed to be a fixed window size, just a lower resolution with Legacy BIOS. Lonnie [1] |
|
From: David K. <da...@ke...> - 2025-06-19 22:10:10
|
Running Astlinux in a VM and using VNC (Proxmox) console, the text display is a very confined 80x24 and black-and-white. Every other text-based VM that I fire up, I can resize the VNC window and the number of rows/columns expands, and text colors are shown. Is it possible to have Astlinux do the same? Thanks David |
|
From: David K. <da...@ke...> - 2025-06-15 20:16:39
|
Thanks Lonnie. Build underway again. David On Sun, Jun 15, 2025 at 1:47 PM Lonnie Abelbeck <li...@lo...> wrote: > Hi David, > > Thanks for the info. > > Yes, the https://ne.di.unimi.it URL now forwards to the github site [2], > not the autoconf download. > > I made a commit [1] to use our ne-3.3.4.tar.gz copy, and the next release > we can use the github tag. > > Thanks David! > > Lonnie > > [1] > https://github.com/astlinux-project/astlinux/commit/fead6b59f4de4a350030615cdcf3ed92b5aa1b6c > > [2] > -- > $ curl -LI https://ne.di.unimi.it/ > HTTP/1.1 302 Found > Date: Sun, 15 Jun 2025 17:32:55 GMT > Server: Apache/2.4.62 (Fedora Linux) OpenSSL/3.2.2 mod_jk/1.2.48 > Location: http://github.com/vigna/ne/ > Content-Type: text/html; charset=iso-8859-1 > > HTTP/1.1 301 Moved Permanently > Content-Length: 0 > Location: https://github.com/vigna/ne/ > > HTTP/2 200 date: Sun, 15 Jun 2025 17:32:55 GMT > content-type: text/html; charset=utf-8 > vary: X-PJAX, X-PJAX-Container, Turbo-Visit, Turbo-Frame, > X-Requested-With,Accept-Encoding, Accept, X-Requested-With > etag: W/"f2c215b4cca5b2f293019cf300168950" > ... > -- > > > > > On Jun 15, 2025, at 10:35 AM, David Kerr <Da...@Ke...> wrote: > > > > Trying to build astlinux today and I am getting this error... > > > > >>> ne 3.3.4 Extracting > > gzip -d -c /home/david/github/astlinux/dl/ne-3.3.4.tar.gz | tar > --strip-components=1 -C /home/david/github/astlinux/output/build/ne-3.3.4 > -xf - > > > > gzip: /home/david/github/astlinux/dl/ne-3.3.4.tar.gz: not in gzip format > > tar: This does not look like a tar archive > > tar: Exiting with failure status due to previous errors > > make: *** [package/Makefile.package.in:248: > /home/david/github/astlinux/output/build/ne-3.3.4/.stamp_extracted] Error 2 > > > > and... > > > > [0.707s] 1 david@Astlinux-dev:~/github/astlinux$ ls -la > /home/david/github/astlinux/dl/ne-* > > -rw-rw-r-- 1 david david 284094 Jun 15 11:21 > /home/david/github/astlinux/dl/ne-3.3.4.tar.gz > > -rw-rw-r-- 1 david david 61 Mar 24 11:13 > /home/david/github/astlinux/dl/ne-3.3.4.tar.gz.sha1 > > > > Anyone else seeing this? Suggestions? > > > > Thanks > > David > > _______________________________________________ > > Astlinux-devel mailing list > > Ast...@li... > > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > |
|
From: Lonnie A. <li...@lo...> - 2025-06-15 17:46:54
|
Hi David, Thanks for the info. Yes, the https://ne.di.unimi.it URL now forwards to the github site [2], not the autoconf download. I made a commit [1] to use our ne-3.3.4.tar.gz copy, and the next release we can use the github tag. Thanks David! Lonnie [1] https://github.com/astlinux-project/astlinux/commit/fead6b59f4de4a350030615cdcf3ed92b5aa1b6c [2] -- $ curl -LI https://ne.di.unimi.it/ HTTP/1.1 302 Found Date: Sun, 15 Jun 2025 17:32:55 GMT Server: Apache/2.4.62 (Fedora Linux) OpenSSL/3.2.2 mod_jk/1.2.48 Location: http://github.com/vigna/ne/ Content-Type: text/html; charset=iso-8859-1 HTTP/1.1 301 Moved Permanently Content-Length: 0 Location: https://github.com/vigna/ne/ HTTP/2 200 date: Sun, 15 Jun 2025 17:32:55 GMT content-type: text/html; charset=utf-8 vary: X-PJAX, X-PJAX-Container, Turbo-Visit, Turbo-Frame, X-Requested-With,Accept-Encoding, Accept, X-Requested-With etag: W/"f2c215b4cca5b2f293019cf300168950" ... -- > On Jun 15, 2025, at 10:35 AM, David Kerr <Da...@Ke...> wrote: > > Trying to build astlinux today and I am getting this error... > > >>> ne 3.3.4 Extracting > gzip -d -c /home/david/github/astlinux/dl/ne-3.3.4.tar.gz | tar --strip-components=1 -C /home/david/github/astlinux/output/build/ne-3.3.4 -xf - > > gzip: /home/david/github/astlinux/dl/ne-3.3.4.tar.gz: not in gzip format > tar: This does not look like a tar archive > tar: Exiting with failure status due to previous errors > make: *** [package/Makefile.package.in:248: /home/david/github/astlinux/output/build/ne-3.3.4/.stamp_extracted] Error 2 > > and... > > [0.707s] 1 david@Astlinux-dev:~/github/astlinux$ ls -la /home/david/github/astlinux/dl/ne-* > -rw-rw-r-- 1 david david 284094 Jun 15 11:21 /home/david/github/astlinux/dl/ne-3.3.4.tar.gz > -rw-rw-r-- 1 david david 61 Mar 24 11:13 /home/david/github/astlinux/dl/ne-3.3.4.tar.gz.sha1 > > Anyone else seeing this? Suggestions? > > Thanks > David > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: David K. <da...@ke...> - 2025-06-15 16:05:45
|
Trying to build astlinux today and I am getting this error... >>> ne 3.3.4 Extracting gzip -d -c /home/david/github/astlinux/dl/ne-3.3.4.tar.gz | tar --strip-components=1 -C /home/david/github/astlinux/output/build/ne-3.3.4 -xf - gzip: /home/david/github/astlinux/dl/ne-3.3.4.tar.gz: not in gzip format tar: This does not look like a tar archive tar: Exiting with failure status due to previous errors make: *** [package/Makefile.package.in:248: /home/david/github/astlinux/output/build/ne-3.3.4/.stamp_extracted] Error 2 and... [0.707s] 1 david@Astlinux-dev:~/github/astlinux$ ls -la /home/david/github/astlinux/dl/ne-* -rw-rw-r-- 1 david david 284094 Jun 15 11:21 /home/david/github/astlinux/dl/ne-3.3.4.tar.gz -rw-rw-r-- 1 david david 61 Mar 24 11:13 /home/david/github/astlinux/dl/ne-3.3.4.tar.gz.sha1 Anyone else seeing this? Suggestions? Thanks David |
|
From: Lonnie A. <li...@lo...> - 2025-06-02 12:22:26
|
Hi David, Good to hear the binary tailscale package on astlinux works well. It does look like tailscale uses the go.lang version of WireGuard, not the kernel version. As for the odd reverse iperf3 stats with tailscale, my only theory is there may a multi-homed network path that iperf3 is using, so not all the iperf3 data is going over tailscale. Only a guess. Looking only at sending (kernel/Go.lang) 450/330 and 3.75/2.0 there is a quite significant difference when speed is needed. If simple connectivity is only required then the difference is not noticeable. Thanks for the testing. Lonnie > On Jun 1, 2025, at 5:34 PM, David Kerr <Da...@Ke...> wrote: > > I tested the binary tailscale package on astlinux and it works well. I started with a remote hosted VM Ubuntu 24.04 (on RackNerd... they are dirt cheap). I installed both wireguard and tailscale onto this VM, and started the iperf3 server. I then ran tailscale on my astlinux gateway and then from astlinux ran iperf3 client. > > Without any tunneling the speed was 700 Mbps sending and 800 Mbps receiving. This is probably running into rate throttling at the remote hosting provider (my native speedtest is 2.5Gbps over fiber). > Running over wireguard the speed dropped to 450 Mbps sending, 400 Mbps receiving. > Running over tailscale the speed was 330 Mbps sending, 400 Mbps receiving. > > Thus for all practical purposes, there really isn't much difference between tailscale and wireguard. Tailscale is notably slower in upload (from astlinux) direction, but equivalent for download. > > My astlinux is running as a VM on proxmox. I decided to create a LXC container on proxmox and in that run both wireguard and tailscale. This eliminates any physical networking... all traffic will be over linux bridge / virtio. And repeated iperf3 tests from astlinux. > > Without any tunneling the speed was 70 Gbps sending and 90 Gbps receiving. Wow! > Running over wireguard the speed dropped to 3.75 Gpps sending, 3.75 Gpps receiving. Thus the CPU load for encryption/decryption is clear. > Running over tailscale the speed was 2 Gbps sending, 6 Gps receiving. Er, what? This was consistent over multiple runs. > > I have observed differences in speed when running iperf3 in "reverse" mode, but nothing like what I saw here with tailscale. > > David > > On Sun, Apr 27, 2025 at 4:24 PM David Kerr <da...@ke...> wrote: > Thanks for the suggestion, I might just try that. > > I have observed in the past that go-lang produces very large binaries. I think it binds in all the dependencies it needs and does not link to external libraries. > > I was not aware that tailscale does not use the kernel Wireguard, that is a pity. I'll have to run a few iPerf3's and compare. > > Tailscale is really easy to setup, so I have found myself using it more and more. > > David > > On Sun, Apr 27, 2025 at 2:15 PM Lonnie Abelbeck <li...@lo...> wrote: > > > On Apr 27, 2025, at 12:12 PM, David Kerr <Da...@Ke...> wrote: > > > > How easy would it be to add the tailscale package to AstLinux? The package was added to buildroot a few months ago... > > > > https://gitlab.com/buildroot.org/buildroot/-/commit/0f34e78818c9bc28a7a0e590bb73d72e616919f4 > > > > But I'm worried that AstLinix has not kept up-to-date with buildroot's package and makefile syntax/capabilities. So I thought I would ask here before I spend any time trying to make it work. > > > > Thanks, > > David > > Indeed, our Buildroot does not support building go-lang packages from source. > > An option is to use precompiled "amd64" binaries [1] [2] > --==-- > minipc ~ # cd /mnt/kd > minipc kd # mkdir tailscale > minipc kd # cd tailscale/ > minipc tailscale # curl -O https://pkgs.tailscale.com/stable/tailscale_1.82.5_amd64.tgz > > minipc tailscale # tar xzvf tailscale_1.82.5_amd64.tgz > tailscale_1.82.5_amd64/ > tailscale_1.82.5_amd64/tailscaled > tailscale_1.82.5_amd64/tailscale > tailscale_1.82.5_amd64/systemd/ > tailscale_1.82.5_amd64/systemd/tailscaled.service > tailscale_1.82.5_amd64/systemd/tailscaled.defaults > > minipc tailscale # ls -l tailscale_1.82.5_amd64/tailscale* > -rwxr-xr-x 1 root root 20590744 Apr 17 15:00 tailscale_1.82.5_amd64/tailscale > -rwxr-xr-x 1 root root 38472562 Apr 17 15:00 tailscale_1.82.5_amd64/tailscaled > --==-- > > Note the two binaries are almost 60 MB, about the compressed AstLinux size! > > Also note that tailscale uses the slower go-lang version of WireGuard, not the kernel version. > > For AstLinux use, I would stick with the native, kernel based WireGuard. But you may be able to get the precompiled "amd64" binaries to work. > > Lonnie > > [1] https://pkgs.tailscale.com/stable/#static > > [2] > > minipc tailscale # tailscale_1.82.5_amd64/tailscaled -version > 1.82.5 > tailscale commit: dec88625eafdcac4dfae8f592705919184ec4df7 > other commit: ec2eb973098fbcd878430fcda1496ca04b9b7328 > go version: go1.24.2 > > > minipc tailscale # tailscale_1.82.5_amd64/tailscale --help > The easiest, most secure way to use WireGuard. > > USAGE > tailscale [flags] <subcommand> [command flags] > > For help on subcommands, add --help after: "tailscale status --help". > > This CLI is still under active development. Commands and flags will > change in the future. > > SUBCOMMANDS > up Connect to Tailscale, logging in if needed > down Disconnect from Tailscale > set Change specified preferences > login Log in to a Tailscale account > logout Disconnect from Tailscale and expire current node key > switch Switch to a different Tailscale account > configure Configure the host to enable more Tailscale features > syspolicy Diagnose the MDM and system policy configuration > netcheck Print an analysis of local network conditions > ip Show Tailscale IP addresses > dns Diagnose the internal DNS forwarder > status Show state of tailscaled and its connections > metrics Show Tailscale metrics > ping Ping a host at the Tailscale layer, see how it routed > nc Connect to a port on a host, connected to stdin/stdout > ssh SSH to a Tailscale machine > funnel Serve content and local servers on the internet > serve Serve content and local servers on your tailnet > version Print Tailscale version > web Run a web server for controlling Tailscale > file Send or receive files > bugreport Print a shareable identifier to help diagnose issues > cert Get TLS certs > lock Manage tailnet lock > licenses Get open source license information > exit-node Show machines on your tailnet configured as exit nodes > update Update Tailscale to the latest/different version > whois Show the machine and user associated with a Tailscale IP (v4 or v6) > drive Share a directory with your tailnet > completion Shell tab-completion scripts > > FLAGS > --socket value > path to tailscaled socket (default /var/run/tailscale/tailscaled.sock) > > > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: David K. <da...@ke...> - 2025-06-01 23:06:17
|
I tested the binary tailscale package on astlinux and it works well. I started with a remote hosted VM Ubuntu 24.04 (on RackNerd... they are dirt cheap). I installed both wireguard and tailscale onto this VM, and started the iperf3 server. I then ran tailscale on my astlinux gateway and then from astlinux ran iperf3 client. Without any tunneling the speed was 700 Mbps sending and 800 Mbps receiving. This is probably running into rate throttling at the remote hosting provider (my native speedtest is 2.5Gbps over fiber). Running over wireguard the speed dropped to 450 Mbps sending, 400 Mbps receiving. Running over tailscale the speed was 330 Mbps sending, 400 Mbps receiving. Thus for all practical purposes, there really isn't much difference between tailscale and wireguard. Tailscale is notably slower in upload (from astlinux) direction, but equivalent for download. My astlinux is running as a VM on proxmox. I decided to create a LXC container on proxmox and in that run both wireguard and tailscale. This eliminates any physical networking... all traffic will be over linux bridge / virtio. And repeated iperf3 tests from astlinux. Without any tunneling the speed was 70 Gbps sending and 90 Gbps receiving. Wow! Running over wireguard the speed dropped to 3.75 Gpps sending, 3.75 Gpps receiving. Thus the CPU load for encryption/decryption is clear. Running over tailscale the speed was 2 Gbps sending, 6 Gps receiving. Er, what? This was consistent over multiple runs. I have observed differences in speed when running iperf3 in "reverse" mode, but nothing like what I saw here with tailscale. David On Sun, Apr 27, 2025 at 4:24 PM David Kerr <da...@ke...> wrote: > Thanks for the suggestion, I might just try that. > > I have observed in the past that go-lang produces very large binaries. I > think it binds in all the dependencies it needs and does not link to > external libraries. > > I was not aware that tailscale does not use the kernel Wireguard, that is > a pity. I'll have to run a few iPerf3's and compare. > > Tailscale is really easy to setup, so I have found myself using it more > and more. > > David > > On Sun, Apr 27, 2025 at 2:15 PM Lonnie Abelbeck <li...@lo...> > wrote: > >> >> > On Apr 27, 2025, at 12:12 PM, David Kerr <Da...@Ke...> wrote: >> > >> > How easy would it be to add the tailscale package to AstLinux? The >> package was added to buildroot a few months ago... >> > >> > >> https://gitlab.com/buildroot.org/buildroot/-/commit/0f34e78818c9bc28a7a0e590bb73d72e616919f4 >> > >> > But I'm worried that AstLinix has not kept up-to-date with buildroot's >> package and makefile syntax/capabilities. So I thought I would ask here >> before I spend any time trying to make it work. >> > >> > Thanks, >> > David >> >> Indeed, our Buildroot does not support building go-lang packages from >> source. >> >> An option is to use precompiled "amd64" binaries [1] [2] >> --==-- >> minipc ~ # cd /mnt/kd >> minipc kd # mkdir tailscale >> minipc kd # cd tailscale/ >> minipc tailscale # curl -O >> https://pkgs.tailscale.com/stable/tailscale_1.82.5_amd64.tgz >> >> minipc tailscale # tar xzvf tailscale_1.82.5_amd64.tgz >> tailscale_1.82.5_amd64/ >> tailscale_1.82.5_amd64/tailscaled >> tailscale_1.82.5_amd64/tailscale >> tailscale_1.82.5_amd64/systemd/ >> tailscale_1.82.5_amd64/systemd/tailscaled.service >> tailscale_1.82.5_amd64/systemd/tailscaled.defaults >> >> minipc tailscale # ls -l tailscale_1.82.5_amd64/tailscale* >> -rwxr-xr-x 1 root root 20590744 Apr 17 15:00 >> tailscale_1.82.5_amd64/tailscale >> -rwxr-xr-x 1 root root 38472562 Apr 17 15:00 >> tailscale_1.82.5_amd64/tailscaled >> --==-- >> >> Note the two binaries are almost 60 MB, about the compressed AstLinux >> size! >> >> Also note that tailscale uses the slower go-lang version of WireGuard, >> not the kernel version. >> >> For AstLinux use, I would stick with the native, kernel based WireGuard. >> But you may be able to get the precompiled "amd64" binaries to work. >> >> Lonnie >> >> [1] https://pkgs.tailscale.com/stable/#static >> >> [2] >> >> minipc tailscale # tailscale_1.82.5_amd64/tailscaled -version >> 1.82.5 >> tailscale commit: dec88625eafdcac4dfae8f592705919184ec4df7 >> other commit: ec2eb973098fbcd878430fcda1496ca04b9b7328 >> go version: go1.24.2 >> >> >> minipc tailscale # tailscale_1.82.5_amd64/tailscale --help >> The easiest, most secure way to use WireGuard. >> >> USAGE >> tailscale [flags] <subcommand> [command flags] >> >> For help on subcommands, add --help after: "tailscale status --help". >> >> This CLI is still under active development. Commands and flags will >> change in the future. >> >> SUBCOMMANDS >> up Connect to Tailscale, logging in if needed >> down Disconnect from Tailscale >> set Change specified preferences >> login Log in to a Tailscale account >> logout Disconnect from Tailscale and expire current node key >> switch Switch to a different Tailscale account >> configure Configure the host to enable more Tailscale features >> syspolicy Diagnose the MDM and system policy configuration >> netcheck Print an analysis of local network conditions >> ip Show Tailscale IP addresses >> dns Diagnose the internal DNS forwarder >> status Show state of tailscaled and its connections >> metrics Show Tailscale metrics >> ping Ping a host at the Tailscale layer, see how it routed >> nc Connect to a port on a host, connected to stdin/stdout >> ssh SSH to a Tailscale machine >> funnel Serve content and local servers on the internet >> serve Serve content and local servers on your tailnet >> version Print Tailscale version >> web Run a web server for controlling Tailscale >> file Send or receive files >> bugreport Print a shareable identifier to help diagnose issues >> cert Get TLS certs >> lock Manage tailnet lock >> licenses Get open source license information >> exit-node Show machines on your tailnet configured as exit nodes >> update Update Tailscale to the latest/different version >> whois Show the machine and user associated with a Tailscale IP >> (v4 or v6) >> drive Share a directory with your tailnet >> completion Shell tab-completion scripts >> >> FLAGS >> --socket value >> path to tailscaled socket (default >> /var/run/tailscale/tailscaled.sock) >> >> >> >> >> _______________________________________________ >> Astlinux-devel mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-devel >> > |
|
From: Ramesh GK <ram...@ho...> - 2025-05-27 09:53:36
|
Hi lonnie, I had to change the approach slightly and it happened to be aligning with your suggestion to use kernel-5.10.x with cip. Thought of letting you know that it is a good suggestion but with a slight change to earlier approach as attached. thanks, ramesh gk ________________________________ From: Ramesh GK <ram...@ho...> Sent: Sunday, April 27, 2025 1:42 PM To: AstLinux Developers Mailing List <ast...@li...> Subject: Re: [Astlinux-devel] remembering kristen kielhofner hi lonnie, i do agree with your suggestion however the approach i am taking is earth surface model which means i can only stick with kernel-x.0.x series and has a restriction of how many patches that can be added to the kernel too. so far it is 101 based on kernel-3.0.101 but 255 is maximum based on hardware limitation that the kernel version will show only 255 in the headers even if the patches are more than x.x.255. i have to look at the option of adding patches only if the released kernel version needs a fix otherwise respect that the released kernel version is good. please find attached the reference model of the approach i am using in maintaining multiple kernel-x.0.x versions and there is a limit of 9 kernel versions in a row and it is a transition for users too and if certain users are not able to upgrade because of linux kernel removing support for their hardware, the users can still sustain. based on the previous trend kernel-x.0.x version is getting released every 4-5yrs but it may come down too. the main goal is do not touch the kernel once it is finalized and update software only as patches because my solution is having large size issue of approximate size of a cd which may grow beyond as well. i am looking at the long term sustainable model from end users perspective because it is in the middle of a router and a desktop which was the idea that started from astlinux but for home users only to reduce the number of different types of devices in the home. thanks ramesh gk ________________________________ From: Lonnie Abelbeck <li...@lo...> Sent: Sunday, April 27, 2025 7:43 AM To: AstLinux Developers Mailing List <ast...@li...> Subject: Re: [Astlinux-devel] remembering kristen kielhofner Hi Ramesh, It was a shock to hear of Kristian's passing. We have a short remembrance here "AstLinux History:" [1] Starting with AstLinux 1.5.10 (to be tagged shortly), we switched to using the "Civil Infrastructure Platform" SLTS v5.10 kernel [2] That might be a better kernel choice for your project than using Linux 6.0.19 as the CIP kernel is actively updated. Lonnie [1] https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astlinux-project.org%2Fabout.html&data=05%7C02%7C%7Cba9bbfa8f63f4a3525a608dd8580cee7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638813510480595099%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Om8aLxhgmFj1vASwBL3vm9an%2BVarYM4Xl4bypczNxq8%3D&reserved=0<https://www.astlinux-project.org/about.html> [2] https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.linuxfoundation.org%2Fcivilinfrastructureplatform%2Fstart&data=05%7C02%7C%7Cba9bbfa8f63f4a3525a608dd8580cee7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638813510480628816%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=vpMqoSBgAQKQMq%2Bpo3z0UBupzBhCVpfZRAqV6RwgUpY%3D&reserved=0<https://wiki.linuxfoundation.org/civilinfrastructureplatform/start> > On Apr 26, 2025, at 11:32 PM, Ramesh GK <ram...@ho...> wrote: > > hi lonnie, > > hope the team is doing great. i am using kernel-6.0.19 in remembrance of kristen kielhofner in mhtgw project. > > i would definitely need some help when time comes and will keep posted. > > thanks > ramesh gk > > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fastlinux-devel&data=05%7C02%7C%7Cba9bbfa8f63f4a3525a608dd8580cee7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638813510480643961%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Tgrhcf7zGDx%2BuvMJrkCmRAfhujCOH2X9zVN44sK2Lcg%3D&reserved=0<https://lists.sourceforge.net/lists/listinfo/astlinux-devel> _______________________________________________ Astlinux-devel mailing list Ast...@li... https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fastlinux-devel&data=05%7C02%7C%7Cba9bbfa8f63f4a3525a608dd8580cee7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638813510480658084%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=cggAHaPchJ4aWiG6MedvWU1GMvEJoxp3jCwCF%2FsMTn8%3D&reserved=0<https://lists.sourceforge.net/lists/listinfo/astlinux-devel> |
|
From: Michael K. <mic...@ip...> - 2025-04-30 23:29:23
|
Thanks Lonnie So could it be possible to support some ARM hardware in the future? This would be quite interesting e.g. Rasberry Pi? Regards Michael Knill From: Lonnie Abelbeck <li...@lo...> Date: Thursday, 1 May 2025 at 8:40 am To: AstLinux Developers Mailing List <ast...@li...> Subject: Re: [Astlinux-devel] Announcing AstLinux Release: 1.5.10 Hi Michael, The current CIP [1] kernel basically tracks the current upstream 5.10.y kernel. I performed a diff between the two and they were basically the same for x86_64. The CIP kernel does support some ARM platforms that the standard kernel does not. The current standard 5.10.y kernel is EOL Dec, 2026, the CIP kernel will continue to be supported until Jan, 2031. Lonnie [1] https://wiki.linuxfoundation.org/civilinfrastructureplatform/start > On Apr 30, 2025, at 5:08 PM, Michael Knill <mic...@ip...> wrote: > > Thanks Lonnie > Just wondering what the impact of moving to the ‘Civil Infrastructure Platform’ Linux Kernel would be, if any. Apologies for my lack of understanding here. > Regards > Michael Knill > From: Lonnie Abelbeck <li...@lo...> > Date: Thursday, 1 May 2025 at 6:08 am > To: AstLinux Users Mailing List <ast...@li...> > Cc: AstLinux Developers Mailing List <ast...@li...> > Subject: [Astlinux-devel] Announcing AstLinux Release: 1.5.10 > Announcing AstLinux Release: 1.5.10 > > More Info: AstLinux Project > https://www.astlinux-project.org/ > > New Documentation Topics: > Qotom Q10922H6 Intel N100 Fanless Appliance [1] > MeLE QuieterDL Intel N100 Fanless Mini PC [2] > UTM (macOS Apple Silicon) [3] > > AstLinux 1.5.10 Highlights: > * Asterisk Versions: 16.30.0, 18.26.1, 20.13.0 > > * Linux Kernel 5.10.236-cip59, security and bug fixes (Switch to using the "Civil Infrastructure Platform" SLTS v5.10 kernel) > * RUNNIX, version bump to runnix-0.6.22 > * r8125, version 9.015.00, Realtek RTL8125 2.5-Gigabit Ethernet Network Driver > * OpenSSH, version 8.4p1, security fix: CVE-2025-26465 > * libcurl (curl) version bump to 8.13.0, security fix: CVE-2025-0167, CVE-2025-0665, CVE-2025-0725 > * expat, version bump to 2.7.1, security fixes: CVE-2024-8176 > * htop, version bump to 3.4.1 > * keepalived, version bump to 2.3.3 > * kmod, version bump to 34.2 > * Monit, version bump to 5.35.1 > * msmtp, version bump to 1.8.28 > * sqlite, version bump to 3.49.1 > * tarsnap, version bump to 1.0.41, "Trust No One" encrypted backups using the Tarsnap Backup service > * virtiofs, for genx86_64-vm builds, Proxmox 8.4 and later supports this feature via QEMU on the host > * vnStat, version bump to 2.13 > * ca-certificates, update trusted root certificates 2025-02-25 > * Time Zone Database update, tzdata2025b and php-timezonedb-2025.2 > * Asterisk '16se' (stable edition) version 16.30.0 is the last Asterisk 16.x "Legacy" version, built --without-pjproject and --without-dahdi > * Package upgrades providing important security and bug fixes > > Full ChangeLog: > https://raw.githubusercontent.com/astlinux-project/astlinux/1.5.10/docs/ChangeLog.txt > > All users are encouraged to upgrade, read the ChangeLog for the details. > > AstLinux Team > > [1] https://doc.astlinux-project.org/userdoc:board_qotom_q10922h6 > [2] https://doc.astlinux-project.org/userdoc:board_mele_quieterdl > [3] https://doc.astlinux-project.org/userdoc:guest_vm_utm > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel _______________________________________________ Astlinux-devel mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Lonnie A. <li...@lo...> - 2025-04-30 22:37:22
|
Hi Michael, The current CIP [1] kernel basically tracks the current upstream 5.10.y kernel. I performed a diff between the two and they were basically the same for x86_64. The CIP kernel does support some ARM platforms that the standard kernel does not. The current standard 5.10.y kernel is EOL Dec, 2026, the CIP kernel will continue to be supported until Jan, 2031. Lonnie [1] https://wiki.linuxfoundation.org/civilinfrastructureplatform/start > On Apr 30, 2025, at 5:08 PM, Michael Knill <mic...@ip...> wrote: > > Thanks Lonnie > Just wondering what the impact of moving to the ‘Civil Infrastructure Platform’ Linux Kernel would be, if any. Apologies for my lack of understanding here. > Regards > Michael Knill > From: Lonnie Abelbeck <li...@lo...> > Date: Thursday, 1 May 2025 at 6:08 am > To: AstLinux Users Mailing List <ast...@li...> > Cc: AstLinux Developers Mailing List <ast...@li...> > Subject: [Astlinux-devel] Announcing AstLinux Release: 1.5.10 > Announcing AstLinux Release: 1.5.10 > > More Info: AstLinux Project > https://www.astlinux-project.org/ > > New Documentation Topics: > Qotom Q10922H6 Intel N100 Fanless Appliance [1] > MeLE QuieterDL Intel N100 Fanless Mini PC [2] > UTM (macOS Apple Silicon) [3] > > AstLinux 1.5.10 Highlights: > * Asterisk Versions: 16.30.0, 18.26.1, 20.13.0 > > * Linux Kernel 5.10.236-cip59, security and bug fixes (Switch to using the "Civil Infrastructure Platform" SLTS v5.10 kernel) > * RUNNIX, version bump to runnix-0.6.22 > * r8125, version 9.015.00, Realtek RTL8125 2.5-Gigabit Ethernet Network Driver > * OpenSSH, version 8.4p1, security fix: CVE-2025-26465 > * libcurl (curl) version bump to 8.13.0, security fix: CVE-2025-0167, CVE-2025-0665, CVE-2025-0725 > * expat, version bump to 2.7.1, security fixes: CVE-2024-8176 > * htop, version bump to 3.4.1 > * keepalived, version bump to 2.3.3 > * kmod, version bump to 34.2 > * Monit, version bump to 5.35.1 > * msmtp, version bump to 1.8.28 > * sqlite, version bump to 3.49.1 > * tarsnap, version bump to 1.0.41, "Trust No One" encrypted backups using the Tarsnap Backup service > * virtiofs, for genx86_64-vm builds, Proxmox 8.4 and later supports this feature via QEMU on the host > * vnStat, version bump to 2.13 > * ca-certificates, update trusted root certificates 2025-02-25 > * Time Zone Database update, tzdata2025b and php-timezonedb-2025.2 > * Asterisk '16se' (stable edition) version 16.30.0 is the last Asterisk 16.x "Legacy" version, built --without-pjproject and --without-dahdi > * Package upgrades providing important security and bug fixes > > Full ChangeLog: > https://raw.githubusercontent.com/astlinux-project/astlinux/1.5.10/docs/ChangeLog.txt > > All users are encouraged to upgrade, read the ChangeLog for the details. > > AstLinux Team > > [1] https://doc.astlinux-project.org/userdoc:board_qotom_q10922h6 > [2] https://doc.astlinux-project.org/userdoc:board_mele_quieterdl > [3] https://doc.astlinux-project.org/userdoc:guest_vm_utm > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Michael K. <mic...@ip...> - 2025-04-30 22:23:35
|
Thanks Lonnie Just wondering what the impact of moving to the ‘Civil Infrastructure Platform’ Linux Kernel would be, if any. Apologies for my lack of understanding here. Regards Michael Knill From: Lonnie Abelbeck <li...@lo...> Date: Thursday, 1 May 2025 at 6:08 am To: AstLinux Users Mailing List <ast...@li...> Cc: AstLinux Developers Mailing List <ast...@li...> Subject: [Astlinux-devel] Announcing AstLinux Release: 1.5.10 Announcing AstLinux Release: 1.5.10 More Info: AstLinux Project https://www.astlinux-project.org/ New Documentation Topics: Qotom Q10922H6 Intel N100 Fanless Appliance [1] MeLE QuieterDL Intel N100 Fanless Mini PC [2] UTM (macOS Apple Silicon) [3] AstLinux 1.5.10 Highlights: * Asterisk Versions: 16.30.0, 18.26.1, 20.13.0 * Linux Kernel 5.10.236-cip59, security and bug fixes (Switch to using the "Civil Infrastructure Platform" SLTS v5.10 kernel) * RUNNIX, version bump to runnix-0.6.22 * r8125, version 9.015.00, Realtek RTL8125 2.5-Gigabit Ethernet Network Driver * OpenSSH, version 8.4p1, security fix: CVE-2025-26465 * libcurl (curl) version bump to 8.13.0, security fix: CVE-2025-0167, CVE-2025-0665, CVE-2025-0725 * expat, version bump to 2.7.1, security fixes: CVE-2024-8176 * htop, version bump to 3.4.1 * keepalived, version bump to 2.3.3 * kmod, version bump to 34.2 * Monit, version bump to 5.35.1 * msmtp, version bump to 1.8.28 * sqlite, version bump to 3.49.1 * tarsnap, version bump to 1.0.41, "Trust No One" encrypted backups using the Tarsnap Backup service * virtiofs, for genx86_64-vm builds, Proxmox 8.4 and later supports this feature via QEMU on the host * vnStat, version bump to 2.13 * ca-certificates, update trusted root certificates 2025-02-25 * Time Zone Database update, tzdata2025b and php-timezonedb-2025.2 * Asterisk '16se' (stable edition) version 16.30.0 is the last Asterisk 16.x "Legacy" version, built --without-pjproject and --without-dahdi * Package upgrades providing important security and bug fixes Full ChangeLog: https://raw.githubusercontent.com/astlinux-project/astlinux/1.5.10/docs/ChangeLog.txt All users are encouraged to upgrade, read the ChangeLog for the details. AstLinux Team [1] https://doc.astlinux-project.org/userdoc:board_qotom_q10922h6 [2] https://doc.astlinux-project.org/userdoc:board_mele_quieterdl [3] https://doc.astlinux-project.org/userdoc:guest_vm_utm _______________________________________________ Astlinux-devel mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Lonnie A. <li...@lo...> - 2025-04-30 20:05:08
|
Announcing AstLinux Release: 1.5.10 More Info: AstLinux Project https://www.astlinux-project.org/ New Documentation Topics: Qotom Q10922H6 Intel N100 Fanless Appliance [1] MeLE QuieterDL Intel N100 Fanless Mini PC [2] UTM (macOS Apple Silicon) [3] AstLinux 1.5.10 Highlights: * Asterisk Versions: 16.30.0, 18.26.1, 20.13.0 * Linux Kernel 5.10.236-cip59, security and bug fixes (Switch to using the "Civil Infrastructure Platform" SLTS v5.10 kernel) * RUNNIX, version bump to runnix-0.6.22 * r8125, version 9.015.00, Realtek RTL8125 2.5-Gigabit Ethernet Network Driver * OpenSSH, version 8.4p1, security fix: CVE-2025-26465 * libcurl (curl) version bump to 8.13.0, security fix: CVE-2025-0167, CVE-2025-0665, CVE-2025-0725 * expat, version bump to 2.7.1, security fixes: CVE-2024-8176 * htop, version bump to 3.4.1 * keepalived, version bump to 2.3.3 * kmod, version bump to 34.2 * Monit, version bump to 5.35.1 * msmtp, version bump to 1.8.28 * sqlite, version bump to 3.49.1 * tarsnap, version bump to 1.0.41, "Trust No One" encrypted backups using the Tarsnap Backup service * virtiofs, for genx86_64-vm builds, Proxmox 8.4 and later supports this feature via QEMU on the host * vnStat, version bump to 2.13 * ca-certificates, update trusted root certificates 2025-02-25 * Time Zone Database update, tzdata2025b and php-timezonedb-2025.2 * Asterisk '16se' (stable edition) version 16.30.0 is the last Asterisk 16.x "Legacy" version, built --without-pjproject and --without-dahdi * Package upgrades providing important security and bug fixes Full ChangeLog: https://raw.githubusercontent.com/astlinux-project/astlinux/1.5.10/docs/ChangeLog.txt All users are encouraged to upgrade, read the ChangeLog for the details. AstLinux Team [1] https://doc.astlinux-project.org/userdoc:board_qotom_q10922h6 [2] https://doc.astlinux-project.org/userdoc:board_mele_quieterdl [3] https://doc.astlinux-project.org/userdoc:guest_vm_utm |
|
From: Michael K. <li...@mk...> - 2025-04-29 19:49:20
|
Hi David, I just found out, that there is a Tailscale package for the Synology DiskStation available. > Am 27.04.2025 um 22:24 schrieb David Kerr <da...@ke...>: > > Thanks for the suggestion, I might just try that. > > I have observed in the past that go-lang produces very large binaries. I think it binds in all the dependencies it needs and does not link to external libraries. > > I was not aware that tailscale does not use the kernel Wireguard, that is a pity. I'll have to run a few iPerf3's and compare. > > Tailscale is really easy to setup, so I have found myself using it more and more. > > David > > On Sun, Apr 27, 2025 at 2:15 PM Lonnie Abelbeck <li...@lo...> wrote: > > > On Apr 27, 2025, at 12:12 PM, David Kerr <Da...@Ke...> wrote: > > > > How easy would it be to add the tailscale package to AstLinux? The package was added to buildroot a few months ago... > > > > https://gitlab.com/buildroot.org/buildroot/-/commit/0f34e78818c9bc28a7a0e590bb73d72e616919f4 > > > > But I'm worried that AstLinix has not kept up-to-date with buildroot's package and makefile syntax/capabilities. So I thought I would ask here before I spend any time trying to make it work. > > > > Thanks, > > David > > Indeed, our Buildroot does not support building go-lang packages from source. > > An option is to use precompiled "amd64" binaries [1] [2] > --==-- > minipc ~ # cd /mnt/kd > minipc kd # mkdir tailscale > minipc kd # cd tailscale/ > minipc tailscale # curl -O https://pkgs.tailscale.com/stable/tailscale_1.82.5_amd64.tgz > > minipc tailscale # tar xzvf tailscale_1.82.5_amd64.tgz > tailscale_1.82.5_amd64/ > tailscale_1.82.5_amd64/tailscaled > tailscale_1.82.5_amd64/tailscale > tailscale_1.82.5_amd64/systemd/ > tailscale_1.82.5_amd64/systemd/tailscaled.service > tailscale_1.82.5_amd64/systemd/tailscaled.defaults > > minipc tailscale # ls -l tailscale_1.82.5_amd64/tailscale* > -rwxr-xr-x 1 root root 20590744 Apr 17 15:00 tailscale_1.82.5_amd64/tailscale > -rwxr-xr-x 1 root root 38472562 Apr 17 15:00 tailscale_1.82.5_amd64/tailscaled > --==-- > > Note the two binaries are almost 60 MB, about the compressed AstLinux size! > > Also note that tailscale uses the slower go-lang version of WireGuard, not the kernel version. > > For AstLinux use, I would stick with the native, kernel based WireGuard. But you may be able to get the precompiled "amd64" binaries to work. > > Lonnie > > [1] https://pkgs.tailscale.com/stable/#static > > [2] > > minipc tailscale # tailscale_1.82.5_amd64/tailscaled -version > 1.82.5 > tailscale commit: dec88625eafdcac4dfae8f592705919184ec4df7 > other commit: ec2eb973098fbcd878430fcda1496ca04b9b7328 > go version: go1.24.2 > > > minipc tailscale # tailscale_1.82.5_amd64/tailscale --help > The easiest, most secure way to use WireGuard. > > USAGE > tailscale [flags] <subcommand> [command flags] > > For help on subcommands, add --help after: "tailscale status --help". > > This CLI is still under active development. Commands and flags will > change in the future. > > SUBCOMMANDS > up Connect to Tailscale, logging in if needed > down Disconnect from Tailscale > set Change specified preferences > login Log in to a Tailscale account > logout Disconnect from Tailscale and expire current node key > switch Switch to a different Tailscale account > configure Configure the host to enable more Tailscale features > syspolicy Diagnose the MDM and system policy configuration > netcheck Print an analysis of local network conditions > ip Show Tailscale IP addresses > dns Diagnose the internal DNS forwarder > status Show state of tailscaled and its connections > metrics Show Tailscale metrics > ping Ping a host at the Tailscale layer, see how it routed > nc Connect to a port on a host, connected to stdin/stdout > ssh SSH to a Tailscale machine > funnel Serve content and local servers on the internet > serve Serve content and local servers on your tailnet > version Print Tailscale version > web Run a web server for controlling Tailscale > file Send or receive files > bugreport Print a shareable identifier to help diagnose issues > cert Get TLS certs > lock Manage tailnet lock > licenses Get open source license information > exit-node Show machines on your tailnet configured as exit nodes > update Update Tailscale to the latest/different version > whois Show the machine and user associated with a Tailscale IP (v4 or v6) > drive Share a directory with your tailnet > completion Shell tab-completion scripts > > FLAGS > --socket value > path to tailscaled socket (default /var/run/tailscale/tailscaled.sock) Michael https://mksolutions.info |
|
From: David K. <da...@ke...> - 2025-04-27 20:24:36
|
Thanks for the suggestion, I might just try that. I have observed in the past that go-lang produces very large binaries. I think it binds in all the dependencies it needs and does not link to external libraries. I was not aware that tailscale does not use the kernel Wireguard, that is a pity. I'll have to run a few iPerf3's and compare. Tailscale is really easy to setup, so I have found myself using it more and more. David On Sun, Apr 27, 2025 at 2:15 PM Lonnie Abelbeck <li...@lo...> wrote: > > > On Apr 27, 2025, at 12:12 PM, David Kerr <Da...@Ke...> wrote: > > > > How easy would it be to add the tailscale package to AstLinux? The > package was added to buildroot a few months ago... > > > > > https://gitlab.com/buildroot.org/buildroot/-/commit/0f34e78818c9bc28a7a0e590bb73d72e616919f4 > > > > But I'm worried that AstLinix has not kept up-to-date with buildroot's > package and makefile syntax/capabilities. So I thought I would ask here > before I spend any time trying to make it work. > > > > Thanks, > > David > > Indeed, our Buildroot does not support building go-lang packages from > source. > > An option is to use precompiled "amd64" binaries [1] [2] > --==-- > minipc ~ # cd /mnt/kd > minipc kd # mkdir tailscale > minipc kd # cd tailscale/ > minipc tailscale # curl -O > https://pkgs.tailscale.com/stable/tailscale_1.82.5_amd64.tgz > > minipc tailscale # tar xzvf tailscale_1.82.5_amd64.tgz > tailscale_1.82.5_amd64/ > tailscale_1.82.5_amd64/tailscaled > tailscale_1.82.5_amd64/tailscale > tailscale_1.82.5_amd64/systemd/ > tailscale_1.82.5_amd64/systemd/tailscaled.service > tailscale_1.82.5_amd64/systemd/tailscaled.defaults > > minipc tailscale # ls -l tailscale_1.82.5_amd64/tailscale* > -rwxr-xr-x 1 root root 20590744 Apr 17 15:00 > tailscale_1.82.5_amd64/tailscale > -rwxr-xr-x 1 root root 38472562 Apr 17 15:00 > tailscale_1.82.5_amd64/tailscaled > --==-- > > Note the two binaries are almost 60 MB, about the compressed AstLinux size! > > Also note that tailscale uses the slower go-lang version of WireGuard, not > the kernel version. > > For AstLinux use, I would stick with the native, kernel based WireGuard. > But you may be able to get the precompiled "amd64" binaries to work. > > Lonnie > > [1] https://pkgs.tailscale.com/stable/#static > > [2] > > minipc tailscale # tailscale_1.82.5_amd64/tailscaled -version > 1.82.5 > tailscale commit: dec88625eafdcac4dfae8f592705919184ec4df7 > other commit: ec2eb973098fbcd878430fcda1496ca04b9b7328 > go version: go1.24.2 > > > minipc tailscale # tailscale_1.82.5_amd64/tailscale --help > The easiest, most secure way to use WireGuard. > > USAGE > tailscale [flags] <subcommand> [command flags] > > For help on subcommands, add --help after: "tailscale status --help". > > This CLI is still under active development. Commands and flags will > change in the future. > > SUBCOMMANDS > up Connect to Tailscale, logging in if needed > down Disconnect from Tailscale > set Change specified preferences > login Log in to a Tailscale account > logout Disconnect from Tailscale and expire current node key > switch Switch to a different Tailscale account > configure Configure the host to enable more Tailscale features > syspolicy Diagnose the MDM and system policy configuration > netcheck Print an analysis of local network conditions > ip Show Tailscale IP addresses > dns Diagnose the internal DNS forwarder > status Show state of tailscaled and its connections > metrics Show Tailscale metrics > ping Ping a host at the Tailscale layer, see how it routed > nc Connect to a port on a host, connected to stdin/stdout > ssh SSH to a Tailscale machine > funnel Serve content and local servers on the internet > serve Serve content and local servers on your tailnet > version Print Tailscale version > web Run a web server for controlling Tailscale > file Send or receive files > bugreport Print a shareable identifier to help diagnose issues > cert Get TLS certs > lock Manage tailnet lock > licenses Get open source license information > exit-node Show machines on your tailnet configured as exit nodes > update Update Tailscale to the latest/different version > whois Show the machine and user associated with a Tailscale IP (v4 > or v6) > drive Share a directory with your tailnet > completion Shell tab-completion scripts > > FLAGS > --socket value > path to tailscaled socket (default > /var/run/tailscale/tailscaled.sock) > > > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > |
|
From: Lonnie A. <li...@lo...> - 2025-04-27 18:15:04
|
> On Apr 27, 2025, at 12:12 PM, David Kerr <Da...@Ke...> wrote: > > How easy would it be to add the tailscale package to AstLinux? The package was added to buildroot a few months ago... > > https://gitlab.com/buildroot.org/buildroot/-/commit/0f34e78818c9bc28a7a0e590bb73d72e616919f4 > > But I'm worried that AstLinix has not kept up-to-date with buildroot's package and makefile syntax/capabilities. So I thought I would ask here before I spend any time trying to make it work. > > Thanks, > David Indeed, our Buildroot does not support building go-lang packages from source. An option is to use precompiled "amd64" binaries [1] [2] --==-- minipc ~ # cd /mnt/kd minipc kd # mkdir tailscale minipc kd # cd tailscale/ minipc tailscale # curl -O https://pkgs.tailscale.com/stable/tailscale_1.82.5_amd64.tgz minipc tailscale # tar xzvf tailscale_1.82.5_amd64.tgz tailscale_1.82.5_amd64/ tailscale_1.82.5_amd64/tailscaled tailscale_1.82.5_amd64/tailscale tailscale_1.82.5_amd64/systemd/ tailscale_1.82.5_amd64/systemd/tailscaled.service tailscale_1.82.5_amd64/systemd/tailscaled.defaults minipc tailscale # ls -l tailscale_1.82.5_amd64/tailscale* -rwxr-xr-x 1 root root 20590744 Apr 17 15:00 tailscale_1.82.5_amd64/tailscale -rwxr-xr-x 1 root root 38472562 Apr 17 15:00 tailscale_1.82.5_amd64/tailscaled --==-- Note the two binaries are almost 60 MB, about the compressed AstLinux size! Also note that tailscale uses the slower go-lang version of WireGuard, not the kernel version. For AstLinux use, I would stick with the native, kernel based WireGuard. But you may be able to get the precompiled "amd64" binaries to work. Lonnie [1] https://pkgs.tailscale.com/stable/#static [2] minipc tailscale # tailscale_1.82.5_amd64/tailscaled -version 1.82.5 tailscale commit: dec88625eafdcac4dfae8f592705919184ec4df7 other commit: ec2eb973098fbcd878430fcda1496ca04b9b7328 go version: go1.24.2 minipc tailscale # tailscale_1.82.5_amd64/tailscale --help The easiest, most secure way to use WireGuard. USAGE tailscale [flags] <subcommand> [command flags] For help on subcommands, add --help after: "tailscale status --help". This CLI is still under active development. Commands and flags will change in the future. SUBCOMMANDS up Connect to Tailscale, logging in if needed down Disconnect from Tailscale set Change specified preferences login Log in to a Tailscale account logout Disconnect from Tailscale and expire current node key switch Switch to a different Tailscale account configure Configure the host to enable more Tailscale features syspolicy Diagnose the MDM and system policy configuration netcheck Print an analysis of local network conditions ip Show Tailscale IP addresses dns Diagnose the internal DNS forwarder status Show state of tailscaled and its connections metrics Show Tailscale metrics ping Ping a host at the Tailscale layer, see how it routed nc Connect to a port on a host, connected to stdin/stdout ssh SSH to a Tailscale machine funnel Serve content and local servers on the internet serve Serve content and local servers on your tailnet version Print Tailscale version web Run a web server for controlling Tailscale file Send or receive files bugreport Print a shareable identifier to help diagnose issues cert Get TLS certs lock Manage tailnet lock licenses Get open source license information exit-node Show machines on your tailnet configured as exit nodes update Update Tailscale to the latest/different version whois Show the machine and user associated with a Tailscale IP (v4 or v6) drive Share a directory with your tailnet completion Shell tab-completion scripts FLAGS --socket value path to tailscaled socket (default /var/run/tailscale/tailscaled.sock) |
|
From: Ramesh GK <ram...@ho...> - 2025-04-27 17:58:58
|
hi lonnie, i do agree with your suggestion however the approach i am taking is earth surface model which means i can only stick with kernel-x.0.x series and has a restriction of how many patches that can be added to the kernel too. so far it is 101 based on kernel-3.0.101 but 255 is maximum based on hardware limitation that the kernel version will show only 255 in the headers even if the patches are more than x.x.255. i have to look at the option of adding patches only if the released kernel version needs a fix otherwise respect that the released kernel version is good. please find attached the reference model of the approach i am using in maintaining multiple kernel-x.0.x versions and there is a limit of 9 kernel versions in a row and it is a transition for users too and if certain users are not able to upgrade because of linux kernel removing support for their hardware, the users can still sustain. based on the previous trend kernel-x.0.x version is getting released every 4-5yrs but it may come down too. the main goal is do not touch the kernel once it is finalized and update software only as patches because my solution is having large size issue of approximate size of a cd which may grow beyond as well. i am looking at the long term sustainable model from end users perspective because it is in the middle of a router and a desktop which was the idea that started from astlinux but for home users only to reduce the number of different types of devices in the home. thanks ramesh gk ________________________________ From: Lonnie Abelbeck <li...@lo...> Sent: Sunday, April 27, 2025 7:43 AM To: AstLinux Developers Mailing List <ast...@li...> Subject: Re: [Astlinux-devel] remembering kristen kielhofner Hi Ramesh, It was a shock to hear of Kristian's passing. We have a short remembrance here "AstLinux History:" [1] Starting with AstLinux 1.5.10 (to be tagged shortly), we switched to using the "Civil Infrastructure Platform" SLTS v5.10 kernel [2] That might be a better kernel choice for your project than using Linux 6.0.19 as the CIP kernel is actively updated. Lonnie [1] https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astlinux-project.org%2Fabout.html&data=05%7C02%7C%7Cba9bbfa8f63f4a3525a608dd8580cee7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638813510480595099%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Om8aLxhgmFj1vASwBL3vm9an%2BVarYM4Xl4bypczNxq8%3D&reserved=0<https://www.astlinux-project.org/about.html> [2] https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.linuxfoundation.org%2Fcivilinfrastructureplatform%2Fstart&data=05%7C02%7C%7Cba9bbfa8f63f4a3525a608dd8580cee7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638813510480628816%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=vpMqoSBgAQKQMq%2Bpo3z0UBupzBhCVpfZRAqV6RwgUpY%3D&reserved=0<https://wiki.linuxfoundation.org/civilinfrastructureplatform/start> > On Apr 26, 2025, at 11:32 PM, Ramesh GK <ram...@ho...> wrote: > > hi lonnie, > > hope the team is doing great. i am using kernel-6.0.19 in remembrance of kristen kielhofner in mhtgw project. > > i would definitely need some help when time comes and will keep posted. > > thanks > ramesh gk > > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fastlinux-devel&data=05%7C02%7C%7Cba9bbfa8f63f4a3525a608dd8580cee7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638813510480643961%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Tgrhcf7zGDx%2BuvMJrkCmRAfhujCOH2X9zVN44sK2Lcg%3D&reserved=0<https://lists.sourceforge.net/lists/listinfo/astlinux-devel> _______________________________________________ Astlinux-devel mailing list Ast...@li... https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fastlinux-devel&data=05%7C02%7C%7Cba9bbfa8f63f4a3525a608dd8580cee7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638813510480658084%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=cggAHaPchJ4aWiG6MedvWU1GMvEJoxp3jCwCF%2FsMTn8%3D&reserved=0<https://lists.sourceforge.net/lists/listinfo/astlinux-devel> |
|
From: David K. <da...@ke...> - 2025-04-27 17:42:08
|
How easy would it be to add the tailscale package to AstLinux? The package was added to buildroot a few months ago... https://gitlab.com/buildroot.org/buildroot/-/commit/0f34e78818c9bc28a7a0e590bb73d72e616919f4 But I'm worried that AstLinix has not kept up-to-date with buildroot's package and makefile syntax/capabilities. So I thought I would ask here before I spend any time trying to make it work. Thanks, David |
|
From: Lonnie A. <li...@lo...> - 2025-04-27 11:43:44
|
Hi Ramesh, It was a shock to hear of Kristian's passing. We have a short remembrance here "AstLinux History:" [1] Starting with AstLinux 1.5.10 (to be tagged shortly), we switched to using the "Civil Infrastructure Platform" SLTS v5.10 kernel [2] That might be a better kernel choice for your project than using Linux 6.0.19 as the CIP kernel is actively updated. Lonnie [1] https://www.astlinux-project.org/about.html [2] https://wiki.linuxfoundation.org/civilinfrastructureplatform/start > On Apr 26, 2025, at 11:32 PM, Ramesh GK <ram...@ho...> wrote: > > hi lonnie, > > hope the team is doing great. i am using kernel-6.0.19 in remembrance of kristen kielhofner in mhtgw project. > > i would definitely need some help when time comes and will keep posted. > > thanks > ramesh gk > > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Ramesh GK <ram...@ho...> - 2025-04-27 04:32:24
|
hi lonnie, hope the team is doing great. i am using kernel-6.0.19 in remembrance of kristen kielhofner in mhtgw project. i would definitely need some help when time comes and will keep posted. thanks ramesh gk |
|
From: Ramesh GK <ram...@ho...> - 2025-02-13 19:58:44
|
shiva garu showed astlinux using kexec without doing a full restart is the first rock hitting earth story which is being reversed and kernel-6.1.x cannot be used for the same reason. shiva garu showed even if kexec approach is removed, kristian kielhofner still has that reverse story and hence kernel-6.1.x cannot be used. just would like to give that heads up. Please follow your best instincts if not following my suggestion. shiva garu showed kernel-6.1.x is where rust is added to kernel and ramesh can use it in debian because it has a different story altogether however astlinux cannot use it because each kernel is an entire earth with rock story reversal which does good for end users. Thanks Ramesh GK 408.462.0408 ________________________________ From: Ramesh GK <ram...@ho...> Sent: Thursday, February 13, 2025 2:36 PM To: AstLinux Developers Mailing List <ast...@li...> Subject: reg: kernel for astlinux hi kris/lonnie, just would like to give a heads up that please do not use kernel-6.1.x for astlinux release and it is very important so users of astlinux are not impacted and is applicable only to astlinux. Thanks Ramesh GK 408.462.0408 ________________________________ From: Ramesh GK <ram...@ho...> Sent: Monday, March 13, 2023 6:32 PM To: AstLinux Developers Mailing List <ast...@li...> Subject: Re: [Astlinux-devel] Error during ex-vi build Hi Lonnie, Makes sense. Thanks for the insight. Thanks Ramesh GK 408.462.0408 ________________________________ From: Lonnie Abelbeck <li...@lo...> Sent: Monday, March 13, 2023 6:26 PM To: AstLinux Developers Mailing List <ast...@li...> Subject: Re: [Astlinux-devel] Error during ex-vi build Hi Ramesh, We (AstLinux) always build with BR2_JLEVEL=1 in the .config, so we have not seen your intermittently failing issue. Lonnie > On Mar 13, 2023, at 5:20 PM, Ramesh GK <ram...@ho...> wrote: > > Hi Lonnie, > > I observed the build is failing intermittently. For now I had to additionally add MAKE1 to the build command and it appears to be compiling properly. > > Not sure why it is behaving differently between buildroot 2011.x and 2019.x versions but thought of sharing the info just in case it might help. > > Thanks > Ramesh GK > 408.462.0408 > > From: Ramesh GK <ram...@ho...> > Sent: Monday, March 13, 2023 4:05 PM > To: AstLinux Developers Mailing List <ast...@li...> > Subject: Re: [Astlinux-devel] Error during ex-vi build > > Yes, agreed. > > Thanks > Ramesh GK > 408.462.0408 > > From: Lonnie Abelbeck <li...@lo...> > Sent: Sunday, March 12, 2023 7:38 PM > To: AstLinux Developers Mailing List <ast...@li...> > Subject: Re: [Astlinux-devel] Error during ex-vi build > > Hi Ramesh, thanks for tracking that down. > > In AstLinux those dependencies are satisfied when ex-vi is built, so it has always worked. > > Lonnie > > > > > On Mar 12, 2023, at 5:37 PM, Ramesh GK <ram...@ho...> wrote: > > > > Hi Lonnie, > > > > I found the cause of the issue from this thread and did some independent testing with that package only. Thought of sharing this info. > > > > https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgnats.netbsd.org%2F51345&data=05%7C01%7C%7C0847d040615243e26e6d08db24120e95%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638143432229507334%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=r1U30zS%2B89YnDbyt5PWLV%2FXyPjP6F17EPwrU3qfOLVs%3D&reserved=0<http://gnats.netbsd.org/51345> > > > > ex-vi requires the below dependencies to identify the library "uxre" > > > > host-pkgconf host-ncurses ncurses > > > > Thanks > > Ramesh GK > > 408.462.0408 > > > > > > From: Lonnie Abelbeck <li...@lo...> > > Sent: Sunday, February 5, 2023 7:51 AM > > To: AstLinux Developers Mailing List <ast...@li...> > > Subject: Re: [Astlinux-devel] Error during ex-vi build > > > > Hi Ramesh, > > > > For reference, here is ex-vi building on Debian 11 with the next pre-1.5.0 version, toolchain: glibc 2.31, binutils 2.35.1, gcc 9.4.0, using crosstool-ng-1.25.0 > > -- > > In file included from ex_vput.c:82: > > ex_vput.c: In function 'vinschar': > > ex.h:554:57: warning: implicit declaration of function 'wcwidth' [-Wimplicit-function-declaration] > > 554 | #define colsc(c) (mb_cur_max > 1 && ((c)&0177) != (c) ? wcwidth(c) : 1) > > | ^~~~~~~ > > ex_vput.c:593:11: note: in expansion of macro 'colsc' > > 593 | insmc1 = colsc(c) - 1; > > | ^~~~~ > > /home/dev/astlinux/trunk/output/host/usr/bin/x86_64-unknown-linux-gnu-gcc -DCHDIR -DFASTTAG -DUCVISUAL -DMB -DBIT8 -DTIOCGWINSZ -DVMUNIX -DEXRECOVER=\"/usr/local/libexec/exrecover\" -DEXPRESERVE=\"/usr/local/libexec/expreserve\" -I./libuxre -DUXRE -c ex_vwind.c > > /home/dev/astlinux/trunk/output/host/usr/bin/x86_64-unknown-linux-gnu-gcc -DCHDIR -DFASTTAG -DUCVISUAL -DMB -DBIT8 -DTIOCGWINSZ -DVMUNIX -DEXRECOVER=\"/usr/local/libexec/exrecover\" -DEXPRESERVE=\"/usr/local/libexec/expreserve\" -I./libuxre -DUXRE -c printf.c > > /home/dev/astlinux/trunk/output/host/usr/bin/x86_64-unknown-linux-gnu-gcc -DCHDIR -DFASTTAG -DUCVISUAL -DMB -DBIT8 -DTIOCGWINSZ -DVMUNIX -DEXRECOVER=\"/usr/local/libexec/exrecover\" -DEXPRESERVE=\"/usr/local/libexec/expreserve\" -I./libuxre -DUXRE -c ex_version.c > > /home/dev/astlinux/trunk/output/host/usr/bin/x86_64-unknown-linux-gnu-gcc -o ex ex.o ex_addr.o ex_cmds.o ex_cmds2.o ex_cmdsub.o ex_data.o ex_extern.o ex_get.o ex_io.o ex_put.o ex_re.o ex_set.o ex_subr.o ex_tagio.o ex_temp.o ex_tty.o ex_unix.o ex_v.o ex_vadj.o ex_vget.o ex_vmain.o ex_voper.o ex_vops.o ex_vops2.o ex_vops3.o ex_vput.o ex_vwind.o printf.o ex_version.o mapmalloc.o -Llibterm -lncurses -L./libuxre -luxre > > size ex > > text data bss dec hex filename > > 234182 5144 171800 411126 645f6 ex > > make[1]: Leaving directory '/home/dev/astlinux/trunk/output/build/ex-vi-050325' > > -- > > > > Quick look, many CFLAGS (passed as FEATURES="...") are missing from your build. Also note the "-I./libuxre -DUXRE" in the gcc's above. > > > > Lonnie > > > > > > > On Feb 5, 2023, at 12:41 AM, Ramesh GK <ram...@ho...> wrote: > > > > > > Hi Lonnie et al, > > > > > > I moved my build system to slackware64 14.2 live and facing an issue with building ex-vi. I tried to find this library but could not able to get more info. please let know if you have any insight on this. > > > > > > --- > > > /mnt/rdisk/builds/buildroot-2022-build-x86_64-generic-4.4cip-5-2023.02/mht/host/bin/x86_64-mht-linux-gnu-gcc -o exrecover exrecover.o mapmalloc.o > > > In file included from ex_vops.c:82:0: > > > ex_vops.c: In function ‘vchange’: > > > ex.h:554:57: warning: implicit declaration of function ‘wcwidth’ [-Wimplicit-function-declaration] > > > #define colsc(c) (mb_cur_max > 1 && ((c)&0177) != (c) ? wcwidth(c) : 1) > > > ^ > > > ex_vops.c:678:7: note: in expansion of macro ‘colsc’ > > > if (colsc(c) > 1) > > > ^ > > > In file included from ex_vput.c:82:0: > > > ex_vput.c: In function ‘vinschar’: > > > /mnt/rdisk/builds/buildroot-2022-build-x86_64-generic-4.4cip-5-2023.02/mht/host/bin/x86_64-mht-linux-gnu-gcc -DVMUNIX -I. -c regfree.c > > > ex.h:554:57: warning: implicit declaration of function ‘wcwidth’ [-Wimplicit-function-declaration] > > > #define colsc(c) (mb_cur_max > 1 && ((c)&0177) != (c) ? wcwidth(c) : 1) > > > ^ > > > ex_vput.c:593:11: note: in expansion of macro ‘colsc’ > > > insmc1 = colsc(c) - 1; > > > ^ > > > /mnt/rdisk/builds/buildroot-2022-build-x86_64-generic-4.4cip-5-2023.02/mht/host/bin/x86_64-mht-linux-gnu-gcc -DVMUNIX -I. -c regnfa.c > > > /mnt/rdisk/builds/buildroot-2022-build-x86_64-generic-4.4cip-5-2023.02/mht/host/bin/x86_64-mht-linux-gnu-gcc -o expreserve expreserve.o > > > /mnt/rdisk/builds/buildroot-2022-build-x86_64-generic-4.4cip-5-2023.02/mht/host/bin/x86_64-mht-linux-gnu-gcc -DVMUNIX -I. -c regparse.c > > > /mnt/rdisk/builds/buildroot-2022-build-x86_64-generic-4.4cip-5-2023.02/mht/host/bin/x86_64-mht-linux-gnu-gcc -DVMUNIX -I. -c stubs.c > > > /mnt/rdisk/builds/buildroot-2022-build-x86_64-generic-4.4cip-5-2023.02/mht/host/bin/x86_64-mht-linux-gnu-gcc -o ex ex.o ex_addr.o ex_cmds.o ex_cmds2.o ex_cmdsub.o ex_data.o ex_extern.o ex_get.o ex_io.o ex_put.o ex_re.o ex_set.o ex_subr.o ex_tagio.o ex_temp.o ex_tty.o ex_unix.o ex_v.o ex_vadj.o ex_vget.o ex_vmain.o ex_voper.o ex_vops.o ex_vops2.o ex_vops3.o ex_vput.o ex_vwind.o printf.o ex_version.o mapmalloc.o -Llibterm -lncurses -L./libuxre -luxre > > > /mnt/rdisk/toolchains/br-2022-x86_64-4.4.302-cip72-5.5.0/x86_64-mht-linux-gnu/bin/../lib/gcc/x86_64-mht-linux-gnu/5.5.0/../../../../x86_64-mht-linux-gnu/bin/ld: cannot find -luxre > > > collect2: error: ld returned 1 exit status > > > Makefile:267: recipe for target 'ex' failed > > > make[2]: *** [ex] Error 1 > > > make[2]: *** Waiting for unfinished jobs.... > > > ar cr libuxre.a bracket.o _collelem.o _collmult.o regcomp.o regdfa.o regerror.o regexec.o regfree.o regnfa.o regparse.o stubs.o > > > package/pkg-generic.mk:302: recipe for target '/mnt/rdisk/builds/buildroot-2022-build-x86_64-generic-4.4cip-5-2023.02/mht/build/ex-vi-050325/.stamp_built' failed > > > make[1]: *** [/mnt/rdisk/builds/buildroot-2022-build-x86_64-generic-4.4cip-5-2023.02/mht/build/ex-vi-050325/.stamp_built] Error 2 > > > Makefile:23: recipe for target '_all' failed > > > make: *** [_all] Error 2 > > > --- > > > > > > Thanks > > > Ramesh GK > > > 408.462.0408 > > > > > > _______________________________________________ > > > Astlinux-devel mailing list > > > Ast...@li... > > > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fastlinux-devel&data=05%7C01%7C%7C0847d040615243e26e6d08db24120e95%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638143432229507334%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vF0uxYfM%2B9HZY5sGQqTvWHfW5uIF78iYAFNZf6Et3%2F0%3D&reserved=0<https://lists.sourceforge.net/lists/listinfo/astlinux-devel> > > > > > > > > _______________________________________________ > > Astlinux-devel mailing list > > Ast...@li... > > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fastlinux-devel&data=05%7C01%7C%7C0847d040615243e26e6d08db24120e95%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638143432229507334%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vF0uxYfM%2B9HZY5sGQqTvWHfW5uIF78iYAFNZf6Et3%2F0%3D&reserved=0<https://lists.sourceforge.net/lists/listinfo/astlinux-devel> > > _______________________________________________ > > Astlinux-devel mailing list > > Ast...@li... > > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fastlinux-devel&data=05%7C01%7C%7C0847d040615243e26e6d08db24120e95%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638143432229507334%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vF0uxYfM%2B9HZY5sGQqTvWHfW5uIF78iYAFNZf6Et3%2F0%3D&reserved=0<https://lists.sourceforge.net/lists/listinfo/astlinux-devel> > > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fastlinux-devel&data=05%7C01%7C%7C0847d040615243e26e6d08db24120e95%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638143432229507334%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vF0uxYfM%2B9HZY5sGQqTvWHfW5uIF78iYAFNZf6Et3%2F0%3D&reserved=0<https://lists.sourceforge.net/lists/listinfo/astlinux-devel> > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fastlinux-devel&data=05%7C01%7C%7C0847d040615243e26e6d08db24120e95%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638143432229507334%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vF0uxYfM%2B9HZY5sGQqTvWHfW5uIF78iYAFNZf6Et3%2F0%3D&reserved=0<https://lists.sourceforge.net/lists/listinfo/astlinux-devel> _______________________________________________ Astlinux-devel mailing list Ast...@li... https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fastlinux-devel&data=05%7C01%7C%7C0847d040615243e26e6d08db24120e95%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638143432229507334%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vF0uxYfM%2B9HZY5sGQqTvWHfW5uIF78iYAFNZf6Et3%2F0%3D&reserved=0<https://lists.sourceforge.net/lists/listinfo/astlinux-devel> |
|
From: Ramesh GK <ram...@ho...> - 2025-02-13 19:51:28
|
hi kris/lonnie, just would like to give a heads up that please do not use kernel-6.1.x for astlinux release and it is very important so users of astlinux are not impacted and is applicable only to astlinux. Thanks Ramesh GK 408.462.0408 ________________________________ From: Ramesh GK <ram...@ho...> Sent: Monday, March 13, 2023 6:32 PM To: AstLinux Developers Mailing List <ast...@li...> Subject: Re: [Astlinux-devel] Error during ex-vi build Hi Lonnie, Makes sense. Thanks for the insight. Thanks Ramesh GK 408.462.0408 ________________________________ From: Lonnie Abelbeck <li...@lo...> Sent: Monday, March 13, 2023 6:26 PM To: AstLinux Developers Mailing List <ast...@li...> Subject: Re: [Astlinux-devel] Error during ex-vi build Hi Ramesh, We (AstLinux) always build with BR2_JLEVEL=1 in the .config, so we have not seen your intermittently failing issue. Lonnie > On Mar 13, 2023, at 5:20 PM, Ramesh GK <ram...@ho...> wrote: > > Hi Lonnie, > > I observed the build is failing intermittently. For now I had to additionally add MAKE1 to the build command and it appears to be compiling properly. > > Not sure why it is behaving differently between buildroot 2011.x and 2019.x versions but thought of sharing the info just in case it might help. > > Thanks > Ramesh GK > 408.462.0408 > > From: Ramesh GK <ram...@ho...> > Sent: Monday, March 13, 2023 4:05 PM > To: AstLinux Developers Mailing List <ast...@li...> > Subject: Re: [Astlinux-devel] Error during ex-vi build > > Yes, agreed. > > Thanks > Ramesh GK > 408.462.0408 > > From: Lonnie Abelbeck <li...@lo...> > Sent: Sunday, March 12, 2023 7:38 PM > To: AstLinux Developers Mailing List <ast...@li...> > Subject: Re: [Astlinux-devel] Error during ex-vi build > > Hi Ramesh, thanks for tracking that down. > > In AstLinux those dependencies are satisfied when ex-vi is built, so it has always worked. > > Lonnie > > > > > On Mar 12, 2023, at 5:37 PM, Ramesh GK <ram...@ho...> wrote: > > > > Hi Lonnie, > > > > I found the cause of the issue from this thread and did some independent testing with that package only. Thought of sharing this info. > > > > https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgnats.netbsd.org%2F51345&data=05%7C01%7C%7C0847d040615243e26e6d08db24120e95%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638143432229507334%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=r1U30zS%2B89YnDbyt5PWLV%2FXyPjP6F17EPwrU3qfOLVs%3D&reserved=0<http://gnats.netbsd.org/51345> > > > > ex-vi requires the below dependencies to identify the library "uxre" > > > > host-pkgconf host-ncurses ncurses > > > > Thanks > > Ramesh GK > > 408.462.0408 > > > > > > From: Lonnie Abelbeck <li...@lo...> > > Sent: Sunday, February 5, 2023 7:51 AM > > To: AstLinux Developers Mailing List <ast...@li...> > > Subject: Re: [Astlinux-devel] Error during ex-vi build > > > > Hi Ramesh, > > > > For reference, here is ex-vi building on Debian 11 with the next pre-1.5.0 version, toolchain: glibc 2.31, binutils 2.35.1, gcc 9.4.0, using crosstool-ng-1.25.0 > > -- > > In file included from ex_vput.c:82: > > ex_vput.c: In function 'vinschar': > > ex.h:554:57: warning: implicit declaration of function 'wcwidth' [-Wimplicit-function-declaration] > > 554 | #define colsc(c) (mb_cur_max > 1 && ((c)&0177) != (c) ? wcwidth(c) : 1) > > | ^~~~~~~ > > ex_vput.c:593:11: note: in expansion of macro 'colsc' > > 593 | insmc1 = colsc(c) - 1; > > | ^~~~~ > > /home/dev/astlinux/trunk/output/host/usr/bin/x86_64-unknown-linux-gnu-gcc -DCHDIR -DFASTTAG -DUCVISUAL -DMB -DBIT8 -DTIOCGWINSZ -DVMUNIX -DEXRECOVER=\"/usr/local/libexec/exrecover\" -DEXPRESERVE=\"/usr/local/libexec/expreserve\" -I./libuxre -DUXRE -c ex_vwind.c > > /home/dev/astlinux/trunk/output/host/usr/bin/x86_64-unknown-linux-gnu-gcc -DCHDIR -DFASTTAG -DUCVISUAL -DMB -DBIT8 -DTIOCGWINSZ -DVMUNIX -DEXRECOVER=\"/usr/local/libexec/exrecover\" -DEXPRESERVE=\"/usr/local/libexec/expreserve\" -I./libuxre -DUXRE -c printf.c > > /home/dev/astlinux/trunk/output/host/usr/bin/x86_64-unknown-linux-gnu-gcc -DCHDIR -DFASTTAG -DUCVISUAL -DMB -DBIT8 -DTIOCGWINSZ -DVMUNIX -DEXRECOVER=\"/usr/local/libexec/exrecover\" -DEXPRESERVE=\"/usr/local/libexec/expreserve\" -I./libuxre -DUXRE -c ex_version.c > > /home/dev/astlinux/trunk/output/host/usr/bin/x86_64-unknown-linux-gnu-gcc -o ex ex.o ex_addr.o ex_cmds.o ex_cmds2.o ex_cmdsub.o ex_data.o ex_extern.o ex_get.o ex_io.o ex_put.o ex_re.o ex_set.o ex_subr.o ex_tagio.o ex_temp.o ex_tty.o ex_unix.o ex_v.o ex_vadj.o ex_vget.o ex_vmain.o ex_voper.o ex_vops.o ex_vops2.o ex_vops3.o ex_vput.o ex_vwind.o printf.o ex_version.o mapmalloc.o -Llibterm -lncurses -L./libuxre -luxre > > size ex > > text data bss dec hex filename > > 234182 5144 171800 411126 645f6 ex > > make[1]: Leaving directory '/home/dev/astlinux/trunk/output/build/ex-vi-050325' > > -- > > > > Quick look, many CFLAGS (passed as FEATURES="...") are missing from your build. Also note the "-I./libuxre -DUXRE" in the gcc's above. > > > > Lonnie > > > > > > > On Feb 5, 2023, at 12:41 AM, Ramesh GK <ram...@ho...> wrote: > > > > > > Hi Lonnie et al, > > > > > > I moved my build system to slackware64 14.2 live and facing an issue with building ex-vi. I tried to find this library but could not able to get more info. please let know if you have any insight on this. > > > > > > --- > > > /mnt/rdisk/builds/buildroot-2022-build-x86_64-generic-4.4cip-5-2023.02/mht/host/bin/x86_64-mht-linux-gnu-gcc -o exrecover exrecover.o mapmalloc.o > > > In file included from ex_vops.c:82:0: > > > ex_vops.c: In function ‘vchange’: > > > ex.h:554:57: warning: implicit declaration of function ‘wcwidth’ [-Wimplicit-function-declaration] > > > #define colsc(c) (mb_cur_max > 1 && ((c)&0177) != (c) ? wcwidth(c) : 1) > > > ^ > > > ex_vops.c:678:7: note: in expansion of macro ‘colsc’ > > > if (colsc(c) > 1) > > > ^ > > > In file included from ex_vput.c:82:0: > > > ex_vput.c: In function ‘vinschar’: > > > /mnt/rdisk/builds/buildroot-2022-build-x86_64-generic-4.4cip-5-2023.02/mht/host/bin/x86_64-mht-linux-gnu-gcc -DVMUNIX -I. -c regfree.c > > > ex.h:554:57: warning: implicit declaration of function ‘wcwidth’ [-Wimplicit-function-declaration] > > > #define colsc(c) (mb_cur_max > 1 && ((c)&0177) != (c) ? wcwidth(c) : 1) > > > ^ > > > ex_vput.c:593:11: note: in expansion of macro ‘colsc’ > > > insmc1 = colsc(c) - 1; > > > ^ > > > /mnt/rdisk/builds/buildroot-2022-build-x86_64-generic-4.4cip-5-2023.02/mht/host/bin/x86_64-mht-linux-gnu-gcc -DVMUNIX -I. -c regnfa.c > > > /mnt/rdisk/builds/buildroot-2022-build-x86_64-generic-4.4cip-5-2023.02/mht/host/bin/x86_64-mht-linux-gnu-gcc -o expreserve expreserve.o > > > /mnt/rdisk/builds/buildroot-2022-build-x86_64-generic-4.4cip-5-2023.02/mht/host/bin/x86_64-mht-linux-gnu-gcc -DVMUNIX -I. -c regparse.c > > > /mnt/rdisk/builds/buildroot-2022-build-x86_64-generic-4.4cip-5-2023.02/mht/host/bin/x86_64-mht-linux-gnu-gcc -DVMUNIX -I. -c stubs.c > > > /mnt/rdisk/builds/buildroot-2022-build-x86_64-generic-4.4cip-5-2023.02/mht/host/bin/x86_64-mht-linux-gnu-gcc -o ex ex.o ex_addr.o ex_cmds.o ex_cmds2.o ex_cmdsub.o ex_data.o ex_extern.o ex_get.o ex_io.o ex_put.o ex_re.o ex_set.o ex_subr.o ex_tagio.o ex_temp.o ex_tty.o ex_unix.o ex_v.o ex_vadj.o ex_vget.o ex_vmain.o ex_voper.o ex_vops.o ex_vops2.o ex_vops3.o ex_vput.o ex_vwind.o printf.o ex_version.o mapmalloc.o -Llibterm -lncurses -L./libuxre -luxre > > > /mnt/rdisk/toolchains/br-2022-x86_64-4.4.302-cip72-5.5.0/x86_64-mht-linux-gnu/bin/../lib/gcc/x86_64-mht-linux-gnu/5.5.0/../../../../x86_64-mht-linux-gnu/bin/ld: cannot find -luxre > > > collect2: error: ld returned 1 exit status > > > Makefile:267: recipe for target 'ex' failed > > > make[2]: *** [ex] Error 1 > > > make[2]: *** Waiting for unfinished jobs.... > > > ar cr libuxre.a bracket.o _collelem.o _collmult.o regcomp.o regdfa.o regerror.o regexec.o regfree.o regnfa.o regparse.o stubs.o > > > package/pkg-generic.mk:302: recipe for target '/mnt/rdisk/builds/buildroot-2022-build-x86_64-generic-4.4cip-5-2023.02/mht/build/ex-vi-050325/.stamp_built' failed > > > make[1]: *** [/mnt/rdisk/builds/buildroot-2022-build-x86_64-generic-4.4cip-5-2023.02/mht/build/ex-vi-050325/.stamp_built] Error 2 > > > Makefile:23: recipe for target '_all' failed > > > make: *** [_all] Error 2 > > > --- > > > > > > Thanks > > > Ramesh GK > > > 408.462.0408 > > > > > > _______________________________________________ > > > Astlinux-devel mailing list > > > Ast...@li... > > > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fastlinux-devel&data=05%7C01%7C%7C0847d040615243e26e6d08db24120e95%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638143432229507334%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vF0uxYfM%2B9HZY5sGQqTvWHfW5uIF78iYAFNZf6Et3%2F0%3D&reserved=0<https://lists.sourceforge.net/lists/listinfo/astlinux-devel> > > > > > > > > _______________________________________________ > > Astlinux-devel mailing list > > Ast...@li... > > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fastlinux-devel&data=05%7C01%7C%7C0847d040615243e26e6d08db24120e95%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638143432229507334%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vF0uxYfM%2B9HZY5sGQqTvWHfW5uIF78iYAFNZf6Et3%2F0%3D&reserved=0<https://lists.sourceforge.net/lists/listinfo/astlinux-devel> > > _______________________________________________ > > Astlinux-devel mailing list > > Ast...@li... > > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fastlinux-devel&data=05%7C01%7C%7C0847d040615243e26e6d08db24120e95%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638143432229507334%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vF0uxYfM%2B9HZY5sGQqTvWHfW5uIF78iYAFNZf6Et3%2F0%3D&reserved=0<https://lists.sourceforge.net/lists/listinfo/astlinux-devel> > > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fastlinux-devel&data=05%7C01%7C%7C0847d040615243e26e6d08db24120e95%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638143432229507334%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vF0uxYfM%2B9HZY5sGQqTvWHfW5uIF78iYAFNZf6Et3%2F0%3D&reserved=0<https://lists.sourceforge.net/lists/listinfo/astlinux-devel> > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fastlinux-devel&data=05%7C01%7C%7C0847d040615243e26e6d08db24120e95%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638143432229507334%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vF0uxYfM%2B9HZY5sGQqTvWHfW5uIF78iYAFNZf6Et3%2F0%3D&reserved=0<https://lists.sourceforge.net/lists/listinfo/astlinux-devel> _______________________________________________ Astlinux-devel mailing list Ast...@li... https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fastlinux-devel&data=05%7C01%7C%7C0847d040615243e26e6d08db24120e95%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638143432229507334%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vF0uxYfM%2B9HZY5sGQqTvWHfW5uIF78iYAFNZf6Et3%2F0%3D&reserved=0<https://lists.sourceforge.net/lists/listinfo/astlinux-devel> |
|
From: Lonnie A. <li...@lo...> - 2025-01-30 20:32:24
|
Announcing AstLinux Release: 1.5.6 More Info: AstLinux Project https://www.astlinux-project.org/ AstLinux 1.5.6 Highlights: * Asterisk Versions: 16.30.0, 18.26.1, 20.11.1 * Linux Kernel 5.10.233, security and bug fixes * RUNNIX, version bump to runnix-0.6.20 * r8125, version 9.014.01, Realtek RTL8125 2.5-Gigabit Ethernet Network Driver * OpenSSL, version 1.1.1w, security fixes: CVE-2023-5678, CVE-2024-0727, CVE-2024-2511, CVE-2024-4741, CVE-2024-5535, CVE-2024-9143 * libcurl (curl) version bump to 8.11.1, security fix: CVE-2024-9681, CVE-2024-11053 * expat, version bump to 2.6.4, security fixes: CVE-2024-45490, CVE-2024-45491, CVE-2024-45492, CVE-2024-50602 * iperf3, version bump to 3.18, security fix: CVE-2024-53580 * php, version 7.2.34, add security fixes: CVE-2024-8925, CVE-2024-8927, CVE-2024-8932, CVE-2024-11234, CVE-2024-11236 * unbound, version bump to 1.22.0, security fix: CVE-2024-8508 * chrony, version bump to 4.6.1 * kexec, version bump to 2.0.30 * Monit, version bump to 5.34.4 * s3fs, version bump to 1.95 * screen, version bump to 5.0.0 * sqlite, version bump to 3.47.2 * unionfs (fuse), version bump to 3.6 * ca-certificates, update trusted root certificates 2024-12-31 * mac2vendor, oui.txt database snapshot 2025-01-10 * Time Zone Database update, tzdata2025a and php-timezonedb-2025.1 * Asterisk '16se' (stable edition) version 16.30.0 is the last Asterisk 16.x "Legacy" version, built --without-pjproject and --without-dahdi * Package upgrades providing important security and bug fixes Full ChangeLog: https://raw.githubusercontent.com/astlinux-project/astlinux/1.5.6/docs/ChangeLog.txt All users are encouraged to upgrade, read the ChangeLog for the details. AstLinux Team _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Michael K. <mic...@ip...> - 2025-01-03 23:10:14
|
Thanks Lonnie for the info. Will probably just ignore it then. Regards Michael Knill From: Lonnie Abelbeck <li...@lo...> Date: Friday, 3 January 2025 at 9:20 am To: AstLinux Developers Mailing List <ast...@li...> Subject: Re: [Astlinux-devel] ipset not working for udp Hi Michael, > Im assuming it is keeping the conntrack entry in place but I don’t know how to remove it dynamically. You are correct. While there exists a "conntrack-tools" package (complex requirements), we have never built or included it into AstLinux. In that package there is a "conntrack" command where you can selectively list and flush entries. Many years ago I looked into this, but never came up with a good solution using the "conntrack" command. Often the solace in understanding what is going on was sufficient. The Adaptive Ban plugin inserts an ADAPTIVE_BAN_CHAIN within the main INPUT chain which occurs before the BASE_INPUT_CHAIN, so to be immune to the conntrack entries. In the BASE_INPUT_CHAIN, it contains the rule: -- ACCEPT all -- anywhere anywhere ctstate ESTABLISHED -- which matches, and allows active conntrack entries. Not an ideal solution... but if you inserted (iptables -I INPUT ...) a rule to the top of the main INPUT chain to block UDP/5060 traffic for the removed external host IPv4 address, that would supersede the BASE_INPUT_CHAIN conntrack match. Example to block UDP/5060 from host 1.2.3.4 -- iptables -I INPUT -s 1.2.3.4 -p udp --dport 5060 -j DROP -- Note that any such rule would be temporary until the firewall was restarted or system rebooted, but as long as it was in effect for the UDP TTL then the conntrack entry would expire and all is well. Or, simply take solace in understanding what is going on. Lonnie > On Jan 2, 2025, at 2:12 PM, Michael Knill <mic...@ip...> wrote: > > Hi Devs. Seasons greeting to all. > I want to use ipset in the firewall for our new softswitch to restrict UDP SIP 5060 access to the ipset list only. Note this is in addition to a permit ACL on the SIP peer in Asterisk. > My custom-rules configuration is as follows: > ###### > if ! ipset list udp_sip_hosts &>/dev/null; then > ipset restore </mnt/kd/ipset_udp_sip_hosts.conf > fi > # Allow UDP 5060 traffic from udp_sip_hosts ipset > RULE="-m set --match-set udp_sip_hosts src -p udp --dport 5060 -j ACCEPT" > # Check if the rule already exists > if ! iptables -C EXT_INPUT_CHAIN $RULE 2>/dev/null; then > # Add the rule if it does not exist > iptables -A EXT_INPUT_CHAIN $RULE > fi > ###### > We populate the ipset list and ipset_udp_sip_hosts.conf from our GUI. > It all seems to work as expected however when we remove an address from the ipset list it remains open even after a firewall restart. Rebooting the system removes it! > Im assuming it is keeping the conntrack entry in place but I don’t know how to remove it dynamically. > Any help would be greatly appreciated. > Regards > Michael Knill > Managing Director > D: +61 2 6189 1360 > P: +61 2 6140 4656 > E: mic...@ip... > W: ipcsolutions.com.au > <image001.png>Smarter Business Communications > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel _______________________________________________ Astlinux-devel mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
28 messages has been excluded from this view by a project administrator.
