Menu
▾
▴
astlinux-users — AstLinux Users Mailing List
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
(2) |
Nov
(1) |
Dec
(20) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
(91) |
Feb
(111) |
Mar
(226) |
Apr
(65) |
May
(197) |
Jun
(202) |
Jul
(92) |
Aug
(87) |
Sep
(120) |
Oct
(133) |
Nov
(89) |
Dec
(155) |
| 2008 |
Jan
(251) |
Feb
(136) |
Mar
(174) |
Apr
(149) |
May
(56) |
Jun
(32) |
Jul
(36) |
Aug
(171) |
Sep
(245) |
Oct
(244) |
Nov
(218) |
Dec
(272) |
| 2009 |
Jan
(113) |
Feb
(119) |
Mar
(192) |
Apr
(117) |
May
(93) |
Jun
(46) |
Jul
(80) |
Aug
(54) |
Sep
(109) |
Oct
(70) |
Nov
(145) |
Dec
(110) |
| 2010 |
Jan
(137) |
Feb
(87) |
Mar
(45) |
Apr
(157) |
May
(58) |
Jun
(99) |
Jul
(188) |
Aug
(136) |
Sep
(101) |
Oct
(100) |
Nov
(61) |
Dec
(60) |
| 2011 |
Jan
(84) |
Feb
(43) |
Mar
(70) |
Apr
(17) |
May
(69) |
Jun
(28) |
Jul
(43) |
Aug
(21) |
Sep
(151) |
Oct
(120) |
Nov
(84) |
Dec
(101) |
| 2012 |
Jan
(119) |
Feb
(82) |
Mar
(70) |
Apr
(115) |
May
(66) |
Jun
(131) |
Jul
(70) |
Aug
(65) |
Sep
(66) |
Oct
(86) |
Nov
(197) |
Dec
(81) |
| 2013 |
Jan
(65) |
Feb
(48) |
Mar
(32) |
Apr
(68) |
May
(98) |
Jun
(59) |
Jul
(41) |
Aug
(52) |
Sep
(42) |
Oct
(37) |
Nov
(10) |
Dec
(27) |
| 2014 |
Jan
(61) |
Feb
(34) |
Mar
(30) |
Apr
(52) |
May
(45) |
Jun
(40) |
Jul
(28) |
Aug
(9) |
Sep
(39) |
Oct
(69) |
Nov
(55) |
Dec
(19) |
| 2015 |
Jan
(13) |
Feb
(21) |
Mar
(5) |
Apr
(14) |
May
(30) |
Jun
(51) |
Jul
(31) |
Aug
(12) |
Sep
(29) |
Oct
(15) |
Nov
(24) |
Dec
(16) |
| 2016 |
Jan
(62) |
Feb
(76) |
Mar
(30) |
Apr
(43) |
May
(46) |
Jun
(62) |
Jul
(21) |
Aug
(49) |
Sep
(67) |
Oct
(27) |
Nov
(26) |
Dec
(38) |
| 2017 |
Jan
(7) |
Feb
(12) |
Mar
(69) |
Apr
(59) |
May
(54) |
Jun
(40) |
Jul
(76) |
Aug
(82) |
Sep
(92) |
Oct
(51) |
Nov
(32) |
Dec
(30) |
| 2018 |
Jan
(22) |
Feb
(25) |
Mar
(34) |
Apr
(35) |
May
(37) |
Jun
(21) |
Jul
(69) |
Aug
(55) |
Sep
(17) |
Oct
(67) |
Nov
(9) |
Dec
(5) |
| 2019 |
Jan
(19) |
Feb
(12) |
Mar
(15) |
Apr
(19) |
May
|
Jun
(27) |
Jul
(27) |
Aug
(25) |
Sep
(25) |
Oct
(27) |
Nov
(10) |
Dec
(14) |
| 2020 |
Jan
(22) |
Feb
(20) |
Mar
(36) |
Apr
(40) |
May
(52) |
Jun
(35) |
Jul
(21) |
Aug
(32) |
Sep
(71) |
Oct
(27) |
Nov
(11) |
Dec
(16) |
| 2021 |
Jan
(16) |
Feb
(21) |
Mar
(21) |
Apr
(27) |
May
(17) |
Jun
|
Jul
(2) |
Aug
(22) |
Sep
(23) |
Oct
(7) |
Nov
(11) |
Dec
(28) |
| 2022 |
Jan
(23) |
Feb
(18) |
Mar
(9) |
Apr
(15) |
May
(15) |
Jun
(7) |
Jul
(8) |
Aug
(15) |
Sep
(1) |
Oct
|
Nov
(11) |
Dec
(10) |
| 2023 |
Jan
(14) |
Feb
(10) |
Mar
(11) |
Apr
(13) |
May
(2) |
Jun
(30) |
Jul
(1) |
Aug
(15) |
Sep
(13) |
Oct
(3) |
Nov
(25) |
Dec
(5) |
| 2024 |
Jan
(3) |
Feb
(10) |
Mar
(9) |
Apr
|
May
(1) |
Jun
(15) |
Jul
(7) |
Aug
(10) |
Sep
(3) |
Oct
(8) |
Nov
(6) |
Dec
(15) |
| 2025 |
Jan
(3) |
Feb
(1) |
Mar
(7) |
Apr
(5) |
May
(13) |
Jun
(16) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Tahiro H. <ta...@ha...> - 2023-05-29 06:04:16
|
Dear whom it may concern. I've recently got my hands on a OpenVox B400P ISDN BRI card. It seems that DAHDI included with Astlinux isn't built to support the card and I'm now trying to figure out how to build the image with the support included. It's been a while since I started fiddling with OSS and I have been fairly comfortable building stuff from sources although I am not yet able to write my own Makefile and so on. Any ideas on how I should get started? P.S.-I have managed to build the toolchain and Astlinux image by default config for Asterisk 18.x. Regards. |
|
From: Gonzalo <gon...@ho...> - 2023-04-30 13:50:55
|
Thanks Ionel, I also do astlinux backups via scp to a remote NAS that way. What I've set up now are automated backups from local laptops into a disk directly plugged to the Astlinux box. The disk is powered on at specific times, then Astlinux mounts the disk, rsyncs some folders in the laptops into it and then umounts the disk and powers it off until the next scheduled backup. It's a cheap solution giving a second life to an old disk and it's working well so far. Regards. El 30 de abril de 2023 12:42:18 UTC, ast...@li... escribió: >Send Astlinux-users mailing list submissions to > ast...@li... > >To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/astlinux-users >or, via email, send a message with subject or body 'help' to > ast...@li... > >You can reach the person managing the list at > ast...@li... > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of Astlinux-users digest..." > > >Today's Topics: > > 1. Re: USB disk automount in Astlinux (Ionel Chila) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Sat, 29 Apr 2023 08:15:27 -0500 >From: Ionel Chila <ion...@me...> >To: AstLinux Users Mailing List <ast...@li...> >Subject: Re: [Astlinux-users] USB disk automount in Astlinux >Message-ID: <C6C...@me...> >Content-Type: text/plain; charset="us-ascii" > >Gonzalo > >I backup my PBX in 2 places. > >1. I have a permanent USB disk mounted as /mnt/kd/USB/ and a script in the crontab takes care of the backup: > >0 4 * * * tar czf /mnt/kd/USB/backup.`date "+%Y-%m-%d"`.tar.gz $(ls -1 /mnt/kd/ | sed -e "s/^cdr-.*//" -e "s/^USB$//" -e "s/^monitor$//" -e "s/^voicemail$//") -C /mnt/kd > > >2. My NAS running UnRaid also pulls a backup from the USB drive remotely via scp. You need to do the ssh key setup and so it does not prompt you for password. I do pull backups remotely from all my IOT and other devices. > >#!/bin/bash >scp -r exile@192.168.0.15:/mnt/kd/USB/*gz /mnt/user/IOT-BKP/AST-PBX/ > > > > > >> On Apr 29, 2023, at 4:52 AM, Gonzalo <gon...@ho...> wrote: >> >> Hi, >> >> Thank you Ionel and Lonnie. >> >> The idea was to mount the disk not only at startup but each time the disk is plugged and keep it switched off most of the time but I'll have to mount it with a custom script instead of automatically. >> I have a remote controlled switch which I use to power on the disk each time I want to perform a backup. >> >> Regards. >> _______________________________________________ >> 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.... > >-------------- next part -------------- >An HTML attachment was scrubbed... > >------------------------------ > > > >------------------------------ > >Subject: Digest Footer > >_______________________________________________ >Astlinux-users mailing list >Ast...@li... >https://lists.sourceforge.net/lists/listinfo/astlinux-users > > >------------------------------ > >End of Astlinux-users Digest, Vol 198, Issue 6 >********************************************** |
|
From: Ionel C. <ion...@me...> - 2023-04-29 13:15:49
|
Gonzalo I backup my PBX in 2 places. 1. I have a permanent USB disk mounted as /mnt/kd/USB/ and a script in the crontab takes care of the backup: 0 4 * * * tar czf /mnt/kd/USB/backup.`date "+%Y-%m-%d"`.tar.gz $(ls -1 /mnt/kd/ | sed -e "s/^cdr-.*//" -e "s/^USB$//" -e "s/^monitor$//" -e "s/^voicemail$//") -C /mnt/kd 2. My NAS running UnRaid also pulls a backup from the USB drive remotely via scp. You need to do the ssh key setup and so it does not prompt you for password. I do pull backups remotely from all my IOT and other devices. #!/bin/bash scp -r exile@192.168.0.15:/mnt/kd/USB/*gz /mnt/user/IOT-BKP/AST-PBX/ > On Apr 29, 2023, at 4:52 AM, Gonzalo <gon...@ho...> wrote: > > Hi, > > Thank you Ionel and Lonnie. > > The idea was to mount the disk not only at startup but each time the disk is plugged and keep it switched off most of the time but I'll have to mount it with a custom script instead of automatically. > I have a remote controlled switch which I use to power on the disk each time I want to perform a backup. > > Regards. > _______________________________________________ > 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: Lonnie A. <li...@lo...> - 2023-04-29 11:58:30
|
> The idea was to mount the disk not only at startup but each time the disk is plugged and keep it switched off most of the time but I'll have to mount it with a custom script instead of automatically. Gonzalo, Make certain you 'umount' before unplugging or powering down the USB disk. Periodic network/cloud backups also work well. BTW, AstLinux supports a 'wol-host' command to wake a network device that supports Wake-on-LAN ... some testing is required for particular hardware. -- Usage: wol-host [options...] ipv4_addr|name Options: --mac MAC Manually define the MAC address, aa:bb:cc:dd:ee:ff, default none/auto-lookup -p pass Append aa:bb:cc:dd[:ee:ff] password to the WoL packet, default none -P, --ping Follow WoL packet with a series of ICMP (ping) packets to host. -t secs Max time (in secs) to send ping packets, default 180 -v Verbose mode -h, --help Show this help text -- So, if everything works correctly, an AstLinux script could initiate a backup by first sending a WoL packet to wake a network file server, perform the backup and then let the network file server sleep after a period of inactivity. Lonnie > On Apr 29, 2023, at 4:52 AM, Gonzalo <gon...@ho...> wrote: > > Hi, > > Thank you Ionel and Lonnie. > > The idea was to mount the disk not only at startup but each time the disk is plugged and keep it switched off most of the time but I'll have to mount it with a custom script instead of automatically. > I have a remote controlled switch which I use to power on the disk each time I want to perform a backup. > > Regards. > _______________________________________________ > 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: Gonzalo <gon...@ho...> - 2023-04-29 09:53:15
|
Hi, Thank you Ionel and Lonnie. The idea was to mount the disk not only at startup but each time the disk is plugged and keep it switched off most of the time but I'll have to mount it with a custom script instead of automatically. I have a remote controlled switch which I use to power on the disk each time I want to perform a backup. Regards. |
|
From: Ionel C. <ion...@me...> - 2023-04-29 01:36:33
|
Yes I do LOL. How did that get in there? When? How many years ago :) I had this PBX for like 15 years or so. Told you I am an idiot :) HOME-PBX durep # cat /mnt/kd/rc.local ## disk_dev="/dev/sdb1" disk_mnt="/mnt/kd/USB" mkdir -p "$disk_mnt" echo "$disk_dev $disk_mnt ext3 noauto,noatime 0 0" >> /tmp/etc/fstab e2fsck -y "$disk_dev" >/dev/null echo "Mounting device '$disk_dev' at '$disk_mnt'" mount "$disk_mnt" >/dev/null ## HOME-PBX durep # > On Apr 28, 2023, at 8:32 PM, Lonnie Abelbeck <li...@lo...> wrote: > > /mnt/kd/rc.local |
|
From: Lonnie A. <li...@lo...> - 2023-04-29 01:32:34
|
Ionel, are you certain you don't have a 'mount' command in either /mnt/kd/rc.local or /mnt/kd/rc.elocal ? Lonnie > On Apr 28, 2023, at 7:13 PM, Ionel Chila via Astlinux-users <ast...@li...> wrote: > > Lonnie, I got nothing in /etc/udev/rules.d LOL. > > The fstab is the only thing I changed and it works fine every reboot > > I guess old school Linux :) Sorry for providing the wrong guidance :) > > > [ 1.684661] usb-storage 1-3:1.0: USB Mass Storage device detected > [ 1.685122] scsi host4: usb-storage 1-3:1.0 > [ 2.715504] scsi 4:0:0:0: Direct-Access SanDisk Ultra Fit 1.00 PQ: 0 ANSI: 6 > [ 2.716621] sd 4:0:0:0: [sdb] 240254976 512-byte logical blocks: (123 GB/115 GiB) > [ 2.717849] sd 4:0:0:0: [sdb] Write Protect is off > [ 2.717906] sd 4:0:0:0: [sdb] Mode Sense: 43 00 00 00 > [ 2.718997] sd 4:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA > [ 2.736198] sdb: sdb1 > [ 2.739593] sd 4:0:0:0: [sdb] Attached SCSI removable disk > [ 6.112418] EXT4-fs (sda2): mounted filesystem without journal. Opts: (null) > [ 6.692360] EXT4-fs (sda2): mounted filesystem without journal. Opts: (null) > [ 6.735574] udevd[182]: starting version 3.2.11 > [ 6.737703] random: udevd: uninitialized urandom read (16 bytes read) > [ 6.738816] random: udevd: uninitialized urandom read (16 bytes read) > [ 6.739044] random: udevd: uninitialized urandom read (16 bytes read) > [ 6.755549] udevd[183]: starting eudev-3.2.11 > [ 6.775029] 8139too: 8139too Fast Ethernet driver 0.9.28 > [ 6.783055] VMware vmxnet3 virtual NIC driver - version 1.5.0.0-k-NAPI > [ 6.799976] e1000: Intel(R) PRO/1000 Network Driver > [ 6.800028] e1000: Copyright (c) 1999-2006 Intel Corporation. > [ 6.807499] e1000e: Intel(R) PRO/1000 Network Driver > [ 6.807552] e1000e: Copyright(c) 1999 - 2015 Intel Corporation. > [ 6.807973] e1000e 0000:01:00.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode > [ 6.849361] e1000e 0000:01:00.0 0000:01:00.0 (uninitialized): registered PHC clock > [ 6.894442] e1000e 0000:01:00.0 eth0: (PCI Express:2.5GT/s:Width x1) 00:22:4d:9f:68:57 > [ 6.894514] e1000e 0000:01:00.0 eth0: Intel(R) PRO/1000 Network Connection > [ 6.894580] e1000e 0000:01:00.0 eth0: MAC: 3, PHY: 8, PBA No: FFFFFF-0FF > [ 6.904842] igb: Intel(R) Gigabit Ethernet Network Driver > [ 6.904894] igb: Copyright (c) 2007-2014 Intel Corporation. > [ 6.930470] Intel(R) 2.5G Ethernet Linux Driver > [ 6.930519] Copyright(c) 2018 Intel Corporation. > [ 12.783015] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null) > [ 17.855384] random: crng init done > [ 17.855438] random: 5 urandom warning(s) missed due to ratelimiting > [ 18.429089] dahdi: loading out-of-tree module taints kernel. > [ 18.430757] dahdi: Version: 3.2.0 > [ 18.432068] dahdi: Telephony Interface Registered on major 196 > [ 22.500961] wctdm24xxp 0000:02:00.0: Port 1: Installed -- AUTO FXO (FCC mode) > [ 22.501025] wctdm24xxp 0000:02:00.0: Port 2: Installed -- AUTO FXS/DPO > [ 22.501070] wctdm24xxp 0000:02:00.0: Port 3: Installed -- AUTO FXS/DPO > [ 22.501115] wctdm24xxp 0000:02:00.0: Port 4: Installed -- AUTO FXS/DPO > [ 22.502438] wctdm24xxp 0000:02:00.0: Found a Wildcard TDM: Wildcard TDM410P (0 BRI spans, 4 analog channels) > [ 22.511330] dahdi_echocan_oslec: Registered echo canceler 'OSLEC' > [ 22.522642] dahdi_echocan_mg2: Registered echo canceler 'MG2' > [ 23.793592] w83627ehf: Found W83627DHG-P chip at 0x290 > [ 25.210820] e1000e 0000:01:00.0 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx > [ 28.547237] EXT4-fs (sdb1): mounting ext3 file system using the ext4 subsystem > [ 28.693669] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) > [ 33.390794] sched: RT throttling activated > > > HOME-PBX etc # df -h > Filesystem Size Used Available Use% Mounted on > /dev/root 10.5M 9.5M 393.0K 96% /oldroot > devtmpfs 512.0K 0 512.0K 0% /dev > none 144.7M 144.7M 0 100% / > none 9.8M 152.0K 9.6M 2% /tmp > none 9.8M 312.0K 9.5M 3% /var > none 512.0K 0 512.0K 0% /dev/shm > none 512.0K 0 512.0K 0% /mnt/unionfs > /dev/sda2 983.1M 309.7M 623.4M 33% /mnt/asturw > none 144.7M 144.7M 0 100% /mnt/unionfs/asturo/etc > unionfs 1.1G 454.4M 623.4M 42% /mnt/unionfs/union/etc > unionfs 1.1G 454.4M 623.4M 42% /etc > none 144.7M 144.7M 0 100% /mnt/unionfs/asturo/stat > unionfs 1.1G 454.4M 623.4M 42% /mnt/unionfs/union/stat > unionfs 1.1G 454.4M 623.4M 42% /stat > /dev/sda3 57.5G 25.9G 28.6G 48% /mnt/kd > /dev/sda1 191.7M 130.4M 61.3M 68% /oldroot/cdrom > /dev/sdb1 112.2G 6.6G 99.9G 6% /mnt/kd/USB > HOME-PBX etc # > > >> On Apr 28, 2023, at 6:58 PM, Lonnie Abelbeck <li...@lo...> wrote: >> >> /etc/udev/rules.d > > _______________________________________________ > 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: Ionel C. <ion...@me...> - 2023-04-29 00:13:57
|
Lonnie, I got nothing in /etc/udev/rules.d LOL. The fstab is the only thing I changed and it works fine every reboot I guess old school Linux :) Sorry for providing the wrong guidance :) [ 1.684661] usb-storage 1-3:1.0: USB Mass Storage device detected [ 1.685122] scsi host4: usb-storage 1-3:1.0 [ 2.715504] scsi 4:0:0:0: Direct-Access SanDisk Ultra Fit 1.00 PQ: 0 ANSI: 6 [ 2.716621] sd 4:0:0:0: [sdb] 240254976 512-byte logical blocks: (123 GB/115 GiB) [ 2.717849] sd 4:0:0:0: [sdb] Write Protect is off [ 2.717906] sd 4:0:0:0: [sdb] Mode Sense: 43 00 00 00 [ 2.718997] sd 4:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 2.736198] sdb: sdb1 [ 2.739593] sd 4:0:0:0: [sdb] Attached SCSI removable disk [ 6.112418] EXT4-fs (sda2): mounted filesystem without journal. Opts: (null) [ 6.692360] EXT4-fs (sda2): mounted filesystem without journal. Opts: (null) [ 6.735574] udevd[182]: starting version 3.2.11 [ 6.737703] random: udevd: uninitialized urandom read (16 bytes read) [ 6.738816] random: udevd: uninitialized urandom read (16 bytes read) [ 6.739044] random: udevd: uninitialized urandom read (16 bytes read) [ 6.755549] udevd[183]: starting eudev-3.2.11 [ 6.775029] 8139too: 8139too Fast Ethernet driver 0.9.28 [ 6.783055] VMware vmxnet3 virtual NIC driver - version 1.5.0.0-k-NAPI [ 6.799976] e1000: Intel(R) PRO/1000 Network Driver [ 6.800028] e1000: Copyright (c) 1999-2006 Intel Corporation. [ 6.807499] e1000e: Intel(R) PRO/1000 Network Driver [ 6.807552] e1000e: Copyright(c) 1999 - 2015 Intel Corporation. [ 6.807973] e1000e 0000:01:00.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode [ 6.849361] e1000e 0000:01:00.0 0000:01:00.0 (uninitialized): registered PHC clock [ 6.894442] e1000e 0000:01:00.0 eth0: (PCI Express:2.5GT/s:Width x1) 00:22:4d:9f:68:57 [ 6.894514] e1000e 0000:01:00.0 eth0: Intel(R) PRO/1000 Network Connection [ 6.894580] e1000e 0000:01:00.0 eth0: MAC: 3, PHY: 8, PBA No: FFFFFF-0FF [ 6.904842] igb: Intel(R) Gigabit Ethernet Network Driver [ 6.904894] igb: Copyright (c) 2007-2014 Intel Corporation. [ 6.930470] Intel(R) 2.5G Ethernet Linux Driver [ 6.930519] Copyright(c) 2018 Intel Corporation. [ 12.783015] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null) [ 17.855384] random: crng init done [ 17.855438] random: 5 urandom warning(s) missed due to ratelimiting [ 18.429089] dahdi: loading out-of-tree module taints kernel. [ 18.430757] dahdi: Version: 3.2.0 [ 18.432068] dahdi: Telephony Interface Registered on major 196 [ 22.500961] wctdm24xxp 0000:02:00.0: Port 1: Installed -- AUTO FXO (FCC mode) [ 22.501025] wctdm24xxp 0000:02:00.0: Port 2: Installed -- AUTO FXS/DPO [ 22.501070] wctdm24xxp 0000:02:00.0: Port 3: Installed -- AUTO FXS/DPO [ 22.501115] wctdm24xxp 0000:02:00.0: Port 4: Installed -- AUTO FXS/DPO [ 22.502438] wctdm24xxp 0000:02:00.0: Found a Wildcard TDM: Wildcard TDM410P (0 BRI spans, 4 analog channels) [ 22.511330] dahdi_echocan_oslec: Registered echo canceler 'OSLEC' [ 22.522642] dahdi_echocan_mg2: Registered echo canceler 'MG2' [ 23.793592] w83627ehf: Found W83627DHG-P chip at 0x290 [ 25.210820] e1000e 0000:01:00.0 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 28.547237] EXT4-fs (sdb1): mounting ext3 file system using the ext4 subsystem [ 28.693669] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) [ 33.390794] sched: RT throttling activated HOME-PBX etc # df -h Filesystem Size Used Available Use% Mounted on /dev/root 10.5M 9.5M 393.0K 96% /oldroot devtmpfs 512.0K 0 512.0K 0% /dev none 144.7M 144.7M 0 100% / none 9.8M 152.0K 9.6M 2% /tmp none 9.8M 312.0K 9.5M 3% /var none 512.0K 0 512.0K 0% /dev/shm none 512.0K 0 512.0K 0% /mnt/unionfs /dev/sda2 983.1M 309.7M 623.4M 33% /mnt/asturw none 144.7M 144.7M 0 100% /mnt/unionfs/asturo/etc unionfs 1.1G 454.4M 623.4M 42% /mnt/unionfs/union/etc unionfs 1.1G 454.4M 623.4M 42% /etc none 144.7M 144.7M 0 100% /mnt/unionfs/asturo/stat unionfs 1.1G 454.4M 623.4M 42% /mnt/unionfs/union/stat unionfs 1.1G 454.4M 623.4M 42% /stat /dev/sda3 57.5G 25.9G 28.6G 48% /mnt/kd /dev/sda1 191.7M 130.4M 61.3M 68% /oldroot/cdrom /dev/sdb1 112.2G 6.6G 99.9G 6% /mnt/kd/USB HOME-PBX etc # > On Apr 28, 2023, at 6:58 PM, Lonnie Abelbeck <li...@lo...> wrote: > > /etc/udev/rules.d |
|
From: Lonnie A. <li...@lo...> - 2023-04-28 23:59:13
|
Ionel, Did you have to edit/add anything to /etc/udev/rules.d to make that work? Puzzled. Gonzalo, If you only wanted it to mount on startup, create /mnt/kd/rc.local and make script executable (vfat example). -- /mnt/kd/rc.local -- #!/bin/sh DISK="/dev/sdb1" DISK_MP="/tmp/USB" mkdir -p "$DISK_MP" if [ -e "$DISK" ]; then mount -t vfat $DISK $DISK_MP fi -- Make the script executable # chmod +x /mnt/kd/rc.local Now, on each reboot, the USB drive will be mounted if it exists. AstLinux does not support any automount functionally. Lonnie > On Apr 28, 2023, at 5:55 PM, Ionel Chila via Astlinux-users <ast...@li...> wrote: > > A line in /etc/fstab will do the trick. Figure out what what dev is your USB drive and the partition type and change the line accordingly > > My example below is for my 256G USB drive I use for backing up my configs > > /dev/sdb1 /mnt/kd/USB ext3 noauto,noatime 0 0 > > > > >> On Apr 28, 2023, at 5:34 PM, Gonzalo <gon...@ho...> wrote: >> >> Hi, >> >> What would be the best way to configure automount for an external usb disk in Astlinux? >> >> The goal is to get the disk mounted automatically on a fixed path every time the disk is plugged into Astlinux box. >> >> Thanks. >> _______________________________________________ >> Astlinux-users mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-users >> >> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Ionel C. <ion...@me...> - 2023-04-28 22:56:21
|
A line in /etc/fstab will do the trick. Figure out what what dev is your USB drive and the partition type and change the line accordingly My example below is for my 256G USB drive I use for backing up my configs /dev/sdb1 /mnt/kd/USB ext3 noauto,noatime 0 0 > On Apr 28, 2023, at 5:34 PM, Gonzalo <gon...@ho...> wrote: > > Hi, > > What would be the best way to configure automount for an external usb disk in Astlinux? > > The goal is to get the disk mounted automatically on a fixed path every time the disk is plugged into Astlinux box. > > Thanks. > _______________________________________________ > 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: Gonzalo <gon...@ho...> - 2023-04-28 22:34:35
|
Hi, What would be the best way to configure automount for an external usb disk in Astlinux? The goal is to get the disk mounted automatically on a fixed path every time the disk is plugged into Astlinux box. Thanks. |
|
From: Ionel C. <ion...@me...> - 2023-04-23 15:33:49
|
Thanks much Lonnie. These are some awesome ideas. I will try some and report back. Cheers Ionel > On Apr 22, 2023, at 1:38 PM, Lonnie Abelbeck <li...@lo...> wrote: > > Hi Ionel, > >> Is it possible to create a rule and say only this “extension” can log in and everything else drop? > > No, that would require some sort of deep inspection at the firewall level. > > A couple of ideas... > > 1) Using 'sipgrep' from the AstLinux CLI, have your brother call you and see what the "User-Agent:" header is: > -- > User-Agent: _______ > -- > Then using the "sip-user-agent" firewall plugin [1] in whitelist mode, define SIP_USER_AGENT_PASS_TYPES > > For example: > -- > SIP_USER_AGENT_PASS_TYPES="_______" > -- > > That should reduce a lot of of 5060 spam. > > Note -> If you have other external SIP endpoints you would need to add (space separate) their User-Agent to SIP_USER_AGENT_PASS_TYPES as well. > > > 2) If your brother's network can perform dynamic DNS, then the "DynDNS Host Open plugin" could be used on only allow your brother, and then remove the "Pass EXT->Local UDP 0/0 5060" firewall rule. > > For example: > -- > DYNDNS_HOST_OPEN_UDP="xxxxx.duckdns.org~5060" > -- > > 3) If your brother's IP address does not change much, say it is "1.2.3.4" perform a > -- > whois 1.2.3.4 | grep '^CIDR:' > -- > and use that CIDR instead of 0/0 in the UDP 5060 firewall rule. Something like "Pass EXT->Local UDP 1.2.0.0/16 5060" > > > Lonnie > > > [1] https://doc.astlinux-project.org/userdoc:tt_firewall_plugins#sip-user-agent > > > >> On Apr 22, 2023, at 12:05 PM, Ionel Chila via Astlinux-users <ast...@li...> wrote: >> >> I had to open port 5060 to the internet for my brother PAP2-NA to get in. Initially I started getting a lot of brute force attacks but the “adaptive-ban” plugins took care of it. Now I am getting a different type of attacks? See logs bellow. >> >> I do have a firewall from UDMP-SE and this PBX is on a DMZ. I forward port 5060 on my WAN to this PBX. >> >> Is it possible to create a rule and say only this “extension” can log in and everything else drop? For instance the PAP2-NA extension is 505 for the purpose of this exercise. >> >> Thanks in advance >> Ionel >> >> >> Apr 22 10:55:29 HOME-PBX local0.warn asterisk[1092]: WARNING[1285]: chan_sip.c:4151 in retrans_pkt: Retransmission timeout reached on transmission 1447810443-1891497107-14325089 for seqno 2 (Critical Response) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions >> Packet timed out after 32000ms with no response >> Apr 22 10:56:26 HOME-PBX local0.notice asterisk[1092]: NOTICE[1285][C-00000027]: chan_sip.c:19672 in send_check_user_failure_response: Failed to authenticate device < >> sip:9998@192.168.0.15:5060 >>> ;tag=1922473623 for INVITE, code = -1 >> Apr 22 10:56:58 HOME-PBX local0.warn asterisk[1092]: WARNING[1285]: chan_sip.c:4151 in retrans_pkt: Retransmission timeout reached on transmission 1920380597-2112014333-1667702904 for seqno 2 (Critical Response) -- See >> https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions >> Packet timed out after 32000ms with no response >> Apr 22 10:57:38 HOME-PBX local0.warn asterisk[1092]: WARNING[1285]: chan_sip.c:4210 in retrans_pkt: Timeout on 1138283951-307500403-1980426376 on non-critical invite transaction. >> Apr 22 10:57:55 HOME-PBX local0.notice asterisk[1092]: NOTICE[1285][C-00000029]: chan_sip.c:19672 in send_check_user_failure_response: Failed to authenticate device < >> sip:9998@192.168.0.15:5060 >>> ;tag=739451700 for INVITE, code = -1 >> Apr 22 10:58:27 HOME-PBX local0.warn asterisk[1092]: WARNING[1285]: chan_sip.c:4151 in retrans_pkt: Retransmission timeout reached on transmission 76533194-1510649679-2136561043 for seqno 2 (Critical Response) -- See >> https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions >> Packet timed out after 32000ms with no response >> Apr 22 11:02:56 HOME-PBX local0.warn asterisk[1092]: WARNING[1285]: chan_sip.c:4210 in retrans_pkt: Timeout on 2133735229-376621693-426493952 on non-critical invite transaction. >> Apr 22 11:03:00 HOME-PBX local0.notice asterisk[1092]: NOTICE[1285][C-0000002b]: chan_sip.c:19672 in send_check_user_failure_response: Failed to authenticate device < >> sip:8889@192.168.0.15:5060 >>> ;tag=595665381 for INVITE, code = -1 >> Apr 22 11:03:32 HOME-PBX local0.warn asterisk[1092]: WARNING[1285]: chan_sip.c:4151 in retrans_pkt: Retransmission timeout reached on transmission 1076661996-1742674713-465326551 for seqno 2 (Critical Response) -- See >> https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions >> Packet timed out after 32000ms with no response >> Apr 22 11:04:30 HOME-PBX local0.notice asterisk[1092]: NOTICE[1285][C-0000002c]: chan_sip.c:19672 in send_check_user_failure_response: Failed to authenticate device < >> sip:8889@192.168.0.15:5060 >>> ;tag=43636851 for INVITE, code = -1 >> Apr 22 11:05:02 HOME-PBX local0.warn asterisk[1092]: WARNING[1285]: chan_sip.c:4151 in retrans_pkt: Retransmission timeout reached on transmission 1728888031-387023100-315880286 for seqno 2 (Critical Response) -- See >> https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions >> Packet timed out after 32000ms with no response >> Apr 22 11:05:59 HOME-PBX local0.notice asterisk[1092]: NOTICE[1285][C-0000002d]: chan_sip.c:19672 in send_check_user_failure_response: Failed to authenticate device < >> sip:8889@192.168.0.15:5060 >>> ;tag=1367210315 for INVITE, code = -1 >> Apr 22 11:06:31 HOME-PBX local0.warn asterisk[1092]: WARNING[1285]: chan_sip.c:4151 in retrans_pkt: Retransmission timeout reached on transmission 2061695187-795614543-1485048389 for seqno 2 (Critical Response) -- See >> https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions >> Packet timed out after 32000ms with no response >> Apr 22 11:07:27 HOME-PBX local0.notice asterisk[1092]: NOTICE[1285][C-0000002e]: chan_sip.c:19672 in send_check_user_failure_response: Failed to authenticate device < >> sip:8889@192.168.0.15:5060 >>> ;tag=277172302 for INVITE, code = -1 >> Apr 22 11:07:59 HOME-PBX local0.warn asterisk[1092]: WARNING[1285]: chan_sip.c:4151 in retrans_pkt: Retransmission timeout reached on transmission 1019652159-463033238-1026431883 for seqno 2 (Critical Response) -- See >> https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions >> Packet timed out after 32000ms with no response >> Apr 22 11:08:57 HOME-PBX local0.notice asterisk[1092]: NOTICE[1285][C-0000002f]: chan_sip.c:19672 in send_check_user_failure_response: Failed to authenticate device < >> sip:8889@192.168.0.15:5060 >>> ;tag=1163877947 for INVITE, code = -1 >> Apr 22 11:09:29 HOME-PBX local0.warn asterisk[1092]: WARNING[1285]: chan_sip.c:4151 in retrans_pkt: Retransmission timeout reached on transmission 469319743-1015333260-1652986992 for seqno 2 (Critical Response) -- See >> https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions >> Packet timed out after 32000ms with no response >> Apr 22 11:12:44 HOME-PBX local0.warn asterisk[1092]: WARNING[1285]: chan_sip.c:4210 in retrans_pkt: Timeout on 160522783-725134999-814499190 on non-critical invite transaction. >> Apr 22 11:13:27 HOME-PBX local0.notice asterisk[1092]: NOTICE[1285]: chan_sip.c:30575 in sip_poke_noanswer: Peer '204' is now UNREACHABLE! Last qualify: 48 >> >> _______________________________________________ >> Astlinux-users mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-users >> >> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Lonnie A. <li...@lo...> - 2023-04-22 18:38:41
|
Hi Ionel, > Is it possible to create a rule and say only this “extension” can log in and everything else drop? No, that would require some sort of deep inspection at the firewall level. A couple of ideas... 1) Using 'sipgrep' from the AstLinux CLI, have your brother call you and see what the "User-Agent:" header is: -- User-Agent: _______ -- Then using the "sip-user-agent" firewall plugin [1] in whitelist mode, define SIP_USER_AGENT_PASS_TYPES For example: -- SIP_USER_AGENT_PASS_TYPES="_______" -- That should reduce a lot of of 5060 spam. Note -> If you have other external SIP endpoints you would need to add (space separate) their User-Agent to SIP_USER_AGENT_PASS_TYPES as well. 2) If your brother's network can perform dynamic DNS, then the "DynDNS Host Open plugin" could be used on only allow your brother, and then remove the "Pass EXT->Local UDP 0/0 5060" firewall rule. For example: -- DYNDNS_HOST_OPEN_UDP="xxxxx.duckdns.org~5060" -- 3) If your brother's IP address does not change much, say it is "1.2.3.4" perform a -- whois 1.2.3.4 | grep '^CIDR:' -- and use that CIDR instead of 0/0 in the UDP 5060 firewall rule. Something like "Pass EXT->Local UDP 1.2.0.0/16 5060" Lonnie [1] https://doc.astlinux-project.org/userdoc:tt_firewall_plugins#sip-user-agent > On Apr 22, 2023, at 12:05 PM, Ionel Chila via Astlinux-users <ast...@li...> wrote: > > I had to open port 5060 to the internet for my brother PAP2-NA to get in. Initially I started getting a lot of brute force attacks but the “adaptive-ban” plugins took care of it. Now I am getting a different type of attacks? See logs bellow. > > I do have a firewall from UDMP-SE and this PBX is on a DMZ. I forward port 5060 on my WAN to this PBX. > > Is it possible to create a rule and say only this “extension” can log in and everything else drop? For instance the PAP2-NA extension is 505 for the purpose of this exercise. > > Thanks in advance > Ionel > > > Apr 22 10:55:29 HOME-PBX local0.warn asterisk[1092]: WARNING[1285]: chan_sip.c:4151 in retrans_pkt: Retransmission timeout reached on transmission 1447810443-1891497107-14325089 for seqno 2 (Critical Response) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions > Packet timed out after 32000ms with no response > Apr 22 10:56:26 HOME-PBX local0.notice asterisk[1092]: NOTICE[1285][C-00000027]: chan_sip.c:19672 in send_check_user_failure_response: Failed to authenticate device < > sip:9998@192.168.0.15:5060 >> ;tag=1922473623 for INVITE, code = -1 > Apr 22 10:56:58 HOME-PBX local0.warn asterisk[1092]: WARNING[1285]: chan_sip.c:4151 in retrans_pkt: Retransmission timeout reached on transmission 1920380597-2112014333-1667702904 for seqno 2 (Critical Response) -- See > https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions > Packet timed out after 32000ms with no response > Apr 22 10:57:38 HOME-PBX local0.warn asterisk[1092]: WARNING[1285]: chan_sip.c:4210 in retrans_pkt: Timeout on 1138283951-307500403-1980426376 on non-critical invite transaction. > Apr 22 10:57:55 HOME-PBX local0.notice asterisk[1092]: NOTICE[1285][C-00000029]: chan_sip.c:19672 in send_check_user_failure_response: Failed to authenticate device < > sip:9998@192.168.0.15:5060 >> ;tag=739451700 for INVITE, code = -1 > Apr 22 10:58:27 HOME-PBX local0.warn asterisk[1092]: WARNING[1285]: chan_sip.c:4151 in retrans_pkt: Retransmission timeout reached on transmission 76533194-1510649679-2136561043 for seqno 2 (Critical Response) -- See > https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions > Packet timed out after 32000ms with no response > Apr 22 11:02:56 HOME-PBX local0.warn asterisk[1092]: WARNING[1285]: chan_sip.c:4210 in retrans_pkt: Timeout on 2133735229-376621693-426493952 on non-critical invite transaction. > Apr 22 11:03:00 HOME-PBX local0.notice asterisk[1092]: NOTICE[1285][C-0000002b]: chan_sip.c:19672 in send_check_user_failure_response: Failed to authenticate device < > sip:8889@192.168.0.15:5060 >> ;tag=595665381 for INVITE, code = -1 > Apr 22 11:03:32 HOME-PBX local0.warn asterisk[1092]: WARNING[1285]: chan_sip.c:4151 in retrans_pkt: Retransmission timeout reached on transmission 1076661996-1742674713-465326551 for seqno 2 (Critical Response) -- See > https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions > Packet timed out after 32000ms with no response > Apr 22 11:04:30 HOME-PBX local0.notice asterisk[1092]: NOTICE[1285][C-0000002c]: chan_sip.c:19672 in send_check_user_failure_response: Failed to authenticate device < > sip:8889@192.168.0.15:5060 >> ;tag=43636851 for INVITE, code = -1 > Apr 22 11:05:02 HOME-PBX local0.warn asterisk[1092]: WARNING[1285]: chan_sip.c:4151 in retrans_pkt: Retransmission timeout reached on transmission 1728888031-387023100-315880286 for seqno 2 (Critical Response) -- See > https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions > Packet timed out after 32000ms with no response > Apr 22 11:05:59 HOME-PBX local0.notice asterisk[1092]: NOTICE[1285][C-0000002d]: chan_sip.c:19672 in send_check_user_failure_response: Failed to authenticate device < > sip:8889@192.168.0.15:5060 >> ;tag=1367210315 for INVITE, code = -1 > Apr 22 11:06:31 HOME-PBX local0.warn asterisk[1092]: WARNING[1285]: chan_sip.c:4151 in retrans_pkt: Retransmission timeout reached on transmission 2061695187-795614543-1485048389 for seqno 2 (Critical Response) -- See > https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions > Packet timed out after 32000ms with no response > Apr 22 11:07:27 HOME-PBX local0.notice asterisk[1092]: NOTICE[1285][C-0000002e]: chan_sip.c:19672 in send_check_user_failure_response: Failed to authenticate device < > sip:8889@192.168.0.15:5060 >> ;tag=277172302 for INVITE, code = -1 > Apr 22 11:07:59 HOME-PBX local0.warn asterisk[1092]: WARNING[1285]: chan_sip.c:4151 in retrans_pkt: Retransmission timeout reached on transmission 1019652159-463033238-1026431883 for seqno 2 (Critical Response) -- See > https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions > Packet timed out after 32000ms with no response > Apr 22 11:08:57 HOME-PBX local0.notice asterisk[1092]: NOTICE[1285][C-0000002f]: chan_sip.c:19672 in send_check_user_failure_response: Failed to authenticate device < > sip:8889@192.168.0.15:5060 >> ;tag=1163877947 for INVITE, code = -1 > Apr 22 11:09:29 HOME-PBX local0.warn asterisk[1092]: WARNING[1285]: chan_sip.c:4151 in retrans_pkt: Retransmission timeout reached on transmission 469319743-1015333260-1652986992 for seqno 2 (Critical Response) -- See > https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions > Packet timed out after 32000ms with no response > Apr 22 11:12:44 HOME-PBX local0.warn asterisk[1092]: WARNING[1285]: chan_sip.c:4210 in retrans_pkt: Timeout on 160522783-725134999-814499190 on non-critical invite transaction. > Apr 22 11:13:27 HOME-PBX local0.notice asterisk[1092]: NOTICE[1285]: chan_sip.c:30575 in sip_poke_noanswer: Peer '204' is now UNREACHABLE! Last qualify: 48 > > _______________________________________________ > 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: Ionel C. <ion...@me...> - 2023-04-22 17:22:01
|
I had to open port 5060 to the internet for my brother PAP2-NA to get in. Initially I started getting a lot of brute force attacks but the “adaptive-ban” plugins took care of it. Now I am getting a different type of attacks? See logs bellow. I do have a firewall from UDMP-SE and this PBX is on a DMZ. I forward port 5060 on my WAN to this PBX. Is it possible to create a rule and say only this “extension” can log in and everything else drop? For instance the PAP2-NA extension is 505 for the purpose of this exercise. Thanks in advance Ionel Apr 22 10:55:29 HOME-PBX local0.warn asterisk[1092]: WARNING[1285]: chan_sip.c:4151 in retrans_pkt: Retransmission timeout reached on transmission 1447810443-1891497107-14325089 for seqno 2 (Critical Response) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions Packet timed out after 32000ms with no response Apr 22 10:56:26 HOME-PBX local0.notice asterisk[1092]: NOTICE[1285][C-00000027]: chan_sip.c:19672 in send_check_user_failure_response: Failed to authenticate device <sip:9998@192.168.0.15:5060>;tag=1922473623 for INVITE, code = -1 Apr 22 10:56:58 HOME-PBX local0.warn asterisk[1092]: WARNING[1285]: chan_sip.c:4151 in retrans_pkt: Retransmission timeout reached on transmission 1920380597-2112014333-1667702904 for seqno 2 (Critical Response) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions Packet timed out after 32000ms with no response Apr 22 10:57:38 HOME-PBX local0.warn asterisk[1092]: WARNING[1285]: chan_sip.c:4210 in retrans_pkt: Timeout on 1138283951-307500403-1980426376 on non-critical invite transaction. Apr 22 10:57:55 HOME-PBX local0.notice asterisk[1092]: NOTICE[1285][C-00000029]: chan_sip.c:19672 in send_check_user_failure_response: Failed to authenticate device <sip:9998@192.168.0.15:5060>;tag=739451700 for INVITE, code = -1 Apr 22 10:58:27 HOME-PBX local0.warn asterisk[1092]: WARNING[1285]: chan_sip.c:4151 in retrans_pkt: Retransmission timeout reached on transmission 76533194-1510649679-2136561043 for seqno 2 (Critical Response) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions Packet timed out after 32000ms with no response Apr 22 11:02:56 HOME-PBX local0.warn asterisk[1092]: WARNING[1285]: chan_sip.c:4210 in retrans_pkt: Timeout on 2133735229-376621693-426493952 on non-critical invite transaction. Apr 22 11:03:00 HOME-PBX local0.notice asterisk[1092]: NOTICE[1285][C-0000002b]: chan_sip.c:19672 in send_check_user_failure_response: Failed to authenticate device <sip:8889@192.168.0.15:5060>;tag=595665381 for INVITE, code = -1 Apr 22 11:03:32 HOME-PBX local0.warn asterisk[1092]: WARNING[1285]: chan_sip.c:4151 in retrans_pkt: Retransmission timeout reached on transmission 1076661996-1742674713-465326551 for seqno 2 (Critical Response) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions Packet timed out after 32000ms with no response Apr 22 11:04:30 HOME-PBX local0.notice asterisk[1092]: NOTICE[1285][C-0000002c]: chan_sip.c:19672 in send_check_user_failure_response: Failed to authenticate device <sip:8889@192.168.0.15:5060>;tag=43636851 for INVITE, code = -1 Apr 22 11:05:02 HOME-PBX local0.warn asterisk[1092]: WARNING[1285]: chan_sip.c:4151 in retrans_pkt: Retransmission timeout reached on transmission 1728888031-387023100-315880286 for seqno 2 (Critical Response) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions Packet timed out after 32000ms with no response Apr 22 11:05:59 HOME-PBX local0.notice asterisk[1092]: NOTICE[1285][C-0000002d]: chan_sip.c:19672 in send_check_user_failure_response: Failed to authenticate device <sip:8889@192.168.0.15:5060>;tag=1367210315 for INVITE, code = -1 Apr 22 11:06:31 HOME-PBX local0.warn asterisk[1092]: WARNING[1285]: chan_sip.c:4151 in retrans_pkt: Retransmission timeout reached on transmission 2061695187-795614543-1485048389 for seqno 2 (Critical Response) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions Packet timed out after 32000ms with no response Apr 22 11:07:27 HOME-PBX local0.notice asterisk[1092]: NOTICE[1285][C-0000002e]: chan_sip.c:19672 in send_check_user_failure_response: Failed to authenticate device <sip:8889@192.168.0.15:5060>;tag=277172302 for INVITE, code = -1 Apr 22 11:07:59 HOME-PBX local0.warn asterisk[1092]: WARNING[1285]: chan_sip.c:4151 in retrans_pkt: Retransmission timeout reached on transmission 1019652159-463033238-1026431883 for seqno 2 (Critical Response) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions Packet timed out after 32000ms with no response Apr 22 11:08:57 HOME-PBX local0.notice asterisk[1092]: NOTICE[1285][C-0000002f]: chan_sip.c:19672 in send_check_user_failure_response: Failed to authenticate device <sip:8889@192.168.0.15:5060>;tag=1163877947 for INVITE, code = -1 Apr 22 11:09:29 HOME-PBX local0.warn asterisk[1092]: WARNING[1285]: chan_sip.c:4151 in retrans_pkt: Retransmission timeout reached on transmission 469319743-1015333260-1652986992 for seqno 2 (Critical Response) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions Packet timed out after 32000ms with no response Apr 22 11:12:44 HOME-PBX local0.warn asterisk[1092]: WARNING[1285]: chan_sip.c:4210 in retrans_pkt: Timeout on 160522783-725134999-814499190 on non-critical invite transaction. Apr 22 11:13:27 HOME-PBX local0.notice asterisk[1092]: NOTICE[1285]: chan_sip.c:30575 in sip_poke_noanswer: Peer '204' is now UNREACHABLE! Last qualify: 48 |
|
From: Michael K. <mic...@ip...> - 2023-03-30 19:54:02
|
Ah thanks Lonnie That looks a better way of doing it. Regards Michael Knill From: Lonnie Abelbeck <li...@lo...> Date: Friday, 31 March 2023 at 1:01 am To: AstLinux Users Mailing List <ast...@li...> Subject: Re: [Astlinux-users] Stopping logging of Crontab Hi Michael, The (busybox) crond daemon has a syslog level setting which defaults to 8, the least verbose log level. So no help there. Using the filter for the Status Tab, is a reasonable idea. Personally, when executing shell commands on a regular interval of seconds/minutes, I prefer to use a bash shell script and the sleep builtin. (Using the sleep builtin keeps from spawning a new process whenever 'sleep' is called). The simplest example of this is the 'msmtpqueue' bash script [1] Basic code setup and loop: -- #!/bin/bash LOCKFILE="/var/lock/foobar.lock" # Robust 'bash' method of creating/testing for a lockfile if ! ( set -o noclobber; echo "$$" > "$LOCKFILE" ) 2>/dev/null; then echo "foobar: already running, lockfile \"$LOCKFILE\" exists, process id: $(cat "$LOCKFILE")." return 9 fi # Load 'sleep' builtin if it exists if [ -f /usr/lib/bash/sleep ]; then enable -f /usr/lib/bash/sleep sleep fi #seconds to wait wait=300 trap 'rm -f "$LOCKFILE"; exit $?' INT TERM EXIT while true; do # do stuff sleep $wait done rm -f "$LOCKFILE" trap - INT TERM EXIT -- Look at the actual code [1] for finer details. Another fairly simple example, asterisk-sip-monitor [2] which adds a PID file that can be removed to exit the script. Lonnie [1] https://github.com/astlinux-project/astlinux/blob/master/package/msmtp/msmtpqueue.sh [2] https://github.com/astlinux-project/astlinux/blob/master/package/asterisk/asterisk-sip-monitor > On Mar 29, 2023, at 11:39 PM, Michael Knill <mic...@ip...> wrote: > > Short of putting in a filter for the Status Tab, is there any way to stop Crontab logging to Syslog. > I now have a process that is run every 10 minutes and its annoying that it logs to Syslog each time. > > Regards > > Michael Knill > Managing Director > > D: +61 2 6189 1360 > P: +61 2 6140 4656 > E: mic...@ip... > W: ipcsolutions.com.au > _______________________________________________ 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: Lonnie A. <li...@lo...> - 2023-03-30 14:01:20
|
Hi Michael, The (busybox) crond daemon has a syslog level setting which defaults to 8, the least verbose log level. So no help there. Using the filter for the Status Tab, is a reasonable idea. Personally, when executing shell commands on a regular interval of seconds/minutes, I prefer to use a bash shell script and the sleep builtin. (Using the sleep builtin keeps from spawning a new process whenever 'sleep' is called). The simplest example of this is the 'msmtpqueue' bash script [1] Basic code setup and loop: -- #!/bin/bash LOCKFILE="/var/lock/foobar.lock" # Robust 'bash' method of creating/testing for a lockfile if ! ( set -o noclobber; echo "$$" > "$LOCKFILE" ) 2>/dev/null; then echo "foobar: already running, lockfile \"$LOCKFILE\" exists, process id: $(cat "$LOCKFILE")." return 9 fi # Load 'sleep' builtin if it exists if [ -f /usr/lib/bash/sleep ]; then enable -f /usr/lib/bash/sleep sleep fi #seconds to wait wait=300 trap 'rm -f "$LOCKFILE"; exit $?' INT TERM EXIT while true; do # do stuff sleep $wait done rm -f "$LOCKFILE" trap - INT TERM EXIT -- Look at the actual code [1] for finer details. Another fairly simple example, asterisk-sip-monitor [2] which adds a PID file that can be removed to exit the script. Lonnie [1] https://github.com/astlinux-project/astlinux/blob/master/package/msmtp/msmtpqueue.sh [2] https://github.com/astlinux-project/astlinux/blob/master/package/asterisk/asterisk-sip-monitor > On Mar 29, 2023, at 11:39 PM, Michael Knill <mic...@ip...> wrote: > > Short of putting in a filter for the Status Tab, is there any way to stop Crontab logging to Syslog. > I now have a process that is run every 10 minutes and its annoying that it logs to Syslog each time. > > Regards > > Michael Knill > Managing Director > > D: +61 2 6189 1360 > P: +61 2 6140 4656 > E: mic...@ip... > W: ipcsolutions.com.au > |
|
From: Michael K. <li...@mk...> - 2023-03-30 08:16:19
|
> Am 30.03.2023 um 10:08 schrieb Michael Keuter <li...@mk...>: > > > >> Am 30.03.2023 um 06:39 schrieb Michael Knill <mic...@ip...>: >> >> Short of putting in a filter for the Status Tab, is there any way to stop Crontab logging to Syslog. >> I now have a process that is run every 10 minutes and its annoying that it logs to Syslog each time. >> >> Regards >> >> Michael Knill >> Managing Director > > I have not tested this, but maybe it works: > > https://unix.stackexchange.com/questions/204431/skip-syslog-rsyslog-logging-of-certain-cron-jobs > > Michael No, it does NOT work :-(. Michael http://www.mksolutions.info |
|
From: Michael K. <li...@mk...> - 2023-03-30 08:09:02
|
> Am 30.03.2023 um 06:39 schrieb Michael Knill <mic...@ip...>: > > Short of putting in a filter for the Status Tab, is there any way to stop Crontab logging to Syslog. > I now have a process that is run every 10 minutes and its annoying that it logs to Syslog each time. > > Regards > > Michael Knill > Managing Director I have not tested this, but maybe it works: https://unix.stackexchange.com/questions/204431/skip-syslog-rsyslog-logging-of-certain-cron-jobs Michael http://www.mksolutions.info |
|
From: Michael K. <mic...@ip...> - 2023-03-30 04:40:25
|
Short of putting in a filter for the Status Tab, is there any way to stop Crontab logging to Syslog. I now have a process that is run every 10 minutes and its annoying that it logs to Syslog each time. Regards Michael Knill Managing Director D: +61 2 6189 1360<tel:+61261891360> P: +61 2 6140 4656<tel:+61261404656> E: mic...@ip...<mailto:mic...@ip...> W: ipcsolutions.com.au<https://ipcsolutions.com.au/> [Icon Description automatically generated] Smarter Business Communications |
|
From: Michael K. <mic...@ip...> - 2023-03-24 03:25:59
|
Yay we have Stretto now authenticating to OpenLDAP in Astlinux. Regards Michael Knill From: Michael Knill <mic...@ip...> Date: Thursday, 23 March 2023 at 3:51 pm To: AstLinux Users Mailing List <ast...@li...> Subject: Re: [Astlinux-users] LDAP Authentication on Astlinux Hi Lonnie Yes thoroughly actually. We may be getting there slowly. Not knowing a great deal about LDAP and slapd is making progress slow. Our main problem appears to be LDAPS currently as LDAP seems to work. Regards Michael Knill From: Lonnie Abelbeck <li...@lo...> Date: Thursday, 23 March 2023 at 12:29 pm To: AstLinux Users Mailing List <ast...@li...> Subject: Re: [Astlinux-users] LDAP Authentication on Astlinux Hi Michael, Have you read this ... LDAP Server Configuration https://doc.astlinux-project.org/userdoc:tt-ldap-server You need ACME certs for LDAPS. I know nothing about modern Bria, hope they support LDAPS properly. It has been a long time since we implemented LDAP, you will most likely have to figure out the details. Good luck. :-) Lonnie > On Mar 22, 2023, at 7:36 PM, Michael Knill <mic...@ip...> wrote: > > Hi All > > I need to set up LDAPS authentication on Astlinux for Stretto Authentication (Bria) and just wondering how I would do this. > I have set up LDAP fine for just telephone numbers but not passwords. > Sorry that I am an LDAP noob. > > Regards > > Michael Knill > Managing Director > > D: +61 2 6189 1360 > P: +61 2 6140 4656 > E: mic...@ip... > W: ipcsolutions.com.au > > <image001.png> > Smarter Business Communications > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Michael K. <mic...@ip...> - 2023-03-23 04:51:32
|
Hi Lonnie Yes thoroughly actually. We may be getting there slowly. Not knowing a great deal about LDAP and slapd is making progress slow. Our main problem appears to be LDAPS currently as LDAP seems to work. Regards Michael Knill From: Lonnie Abelbeck <li...@lo...> Date: Thursday, 23 March 2023 at 12:29 pm To: AstLinux Users Mailing List <ast...@li...> Subject: Re: [Astlinux-users] LDAP Authentication on Astlinux Hi Michael, Have you read this ... LDAP Server Configuration https://doc.astlinux-project.org/userdoc:tt-ldap-server You need ACME certs for LDAPS. I know nothing about modern Bria, hope they support LDAPS properly. It has been a long time since we implemented LDAP, you will most likely have to figure out the details. Good luck. :-) Lonnie > On Mar 22, 2023, at 7:36 PM, Michael Knill <mic...@ip...> wrote: > > Hi All > > I need to set up LDAPS authentication on Astlinux for Stretto Authentication (Bria) and just wondering how I would do this. > I have set up LDAP fine for just telephone numbers but not passwords. > Sorry that I am an LDAP noob. > > Regards > > Michael Knill > Managing Director > > D: +61 2 6189 1360 > P: +61 2 6140 4656 > E: mic...@ip... > W: ipcsolutions.com.au > > <image001.png> > Smarter Business Communications > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Lonnie A. <li...@lo...> - 2023-03-23 01:29:13
|
Hi Michael, Have you read this ... LDAP Server Configuration https://doc.astlinux-project.org/userdoc:tt-ldap-server You need ACME certs for LDAPS. I know nothing about modern Bria, hope they support LDAPS properly. It has been a long time since we implemented LDAP, you will most likely have to figure out the details. Good luck. :-) Lonnie > On Mar 22, 2023, at 7:36 PM, Michael Knill <mic...@ip...> wrote: > > Hi All > > I need to set up LDAPS authentication on Astlinux for Stretto Authentication (Bria) and just wondering how I would do this. > I have set up LDAP fine for just telephone numbers but not passwords. > Sorry that I am an LDAP noob. > > Regards > > Michael Knill > Managing Director > > D: +61 2 6189 1360 > P: +61 2 6140 4656 > E: mic...@ip... > W: ipcsolutions.com.au > > <image001.png> > Smarter Business Communications > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Michael K. <mic...@ip...> - 2023-03-23 00:37:20
|
Hi All I need to set up LDAPS authentication on Astlinux for Stretto Authentication (Bria) and just wondering how I would do this. I have set up LDAP fine for just telephone numbers but not passwords. Sorry that I am an LDAP noob. Regards Michael Knill Managing Director D: +61 2 6189 1360<tel:+61261891360> P: +61 2 6140 4656<tel:+61261404656> E: mic...@ip...<mailto:mic...@ip...> W: ipcsolutions.com.au<https://ipcsolutions.com.au/> [Icon Description automatically generated] Smarter Business Communications |
|
From: Lonnie A. <li...@lo...> - 2023-03-13 13:28:34
|
Hi, We have added a new addition to our "Generic x86_64" hardware list, under "Mini PC Hardware" ... Bmax B1 Plus Celeron N3350 Fanless Mini PC [1] https://doc.astlinux-project.org/userdoc:board_bmax_b1_plus The Bmax B1 Plus Mini PC can be purchased new for ~$100 USD. The value proposition is key, running AstLinux quite nicely, albeit with a single ethernet interface. Alternatively, similarly priced Mini PCs with SATA storage or reused thin clients may have a similar value proposition. I personally purchased the Bmax B1 Plus via Amazon for $95 USD (after discount and coupon), the only additionally cost was a Silicon Power 128GB A55 M.2 type 2280 SATA SSD for $15 USD. The Bmax B1 Plus has onboard soldered 6 GB of RAM, N3350 dual core 2400 MHz CPU. The Bmax B1 Plus is fanless, and only draws 3 Watts when idle. The Bmax B1 Plus initial setup requires some BIOS configuration [1], disabling eMMC support is key and will prevent booting to Windows. Then boot via USB (FAT32/Master-Boot-Record formatted) containing the AstLinux Installer ISO files. Install to the internal M.2 type 2280 SATA SSD. The M.2 SATA SSD is trivial to install, and the BIOS is not limited like some Mini PCs are. Both Legacy and UEFI are supported with Linux, but UEFI is the default. Summary: The Bmax B1 Plus runs AstLinux well, and coupled with configuring LXC containers and its 6 GB of RAM, this box offers a lot at a very competitive price. Think of it as AstLinux features (Asterisk, Firewall, VPN, etc.) coupled with LXC x86_64 RaspberryPi-like replacement features. Surprisingly, even with the Realtek NIC, the little box can serve as a WireGuard VPN endpoint at near 1 Gbps line speed. The single ethernet interface is the primary drawback, but VLANs are your friend, allowing LXC containers to use an internal bridged VLAN and/or support an internal LAN (VLAN) network for phones/devices while connected to a managed ethernet switch. Lonnie |
|
From: Lonnie A. <li...@lo...> - 2023-03-09 01:29:05
|
Announcing AstLinux Release: 1.5.0 More Info: AstLinux Project https://www.astlinux-project.org/ New 1.5.x series based on Linux Kernel 5.10: * Toolchain: glibc 2.31, binutils 2.35.1, gcc 9.4.0, using crosstool-ng-1.25.0 * Filesystem: use ext4 driver instead of ext2. Enable feature 'extra_isize' for new installs, without journal * Network Drivers: wireguard, igb, igc and e1000e drivers are now native with the 5.10 kernel * DAHDI: dahdi-linux 3.2.0 and dahdi-tools 3.2.0 AstLinux 1.5.0 Highlights: * Asterisk Versions: 13.38.3, 16.30.0, 18.16.0 * Linux Kernel 5.10.162, security and bug fixes * RUNNIX, version bump to runnix-0.6.14 * OpenSSL, version bump to 1.1.1t, security fixes: CVE-2023-0286, CVE-2023-0215, CVE-2022-4450, CVE-2022-4304 * LibreTLS, version bump to 3.7.0 * libcurl (curl) version bump to 7.88.1, security fixes: CVE-2022-43551, CVE-2022-43552, CVE-2023-23914, CVE-2023-23915, CVE-2023-23916 * pjsip version 2.12.1, backport security fixes: CVE-2022-23537, CVE-2022-23547 * e2fsprogs, version bump to 1.46.6 * htop, version bump to 3.2.2 * libpcap, version bump to 1.10.3 * libsrtp, version bump to 2.5.0 * Monit, version bump to 5.33.0 * set-kcmd-cstate, new command to manage whether 'processor.max_cstate=1' is passed to the kernel or not (default) * sqlite, version bump to 3.40.1 * stunnel, version bump to 5.68 * sudo, version 1.8.32, add security fix: CVE-2023-22809 * tiff, version bump to 4.5.0, security fixes: many, add patch for CVE-2022-48281 * tcpdump, version 4.99.3 * unbound, version bump to 1.17.1 * Asterisk '13se' (stable edition) version 13.38.3 is the last Asterisk 13.x "Legacy" version, built --without-pjproject * Package upgrades providing important security and bug fixes Full ChangeLog: https://raw.githubusercontent.com/astlinux-project/astlinux/1.5.0/docs/ChangeLog.txt All users are encouraged to upgrade, read the ChangeLog for the details. AstLinux Team |
63 messages has been excluded from this view by a project administrator.
