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
(18) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Lonnie A. <li...@lo...> - 2018-01-11 14:53:19
|
Josh, Ignore the WiKi docs about externally mounting the USB drive, adding rootdelay=10 as described to the KCMD line in the .run.conf file should work for you. Lonnie On Jan 11, 2018, at 8:47 AM, Josh Alberts <jm...@ho...> wrote: > Lonnie, > > I'm running this off the thinclient's internal flash drive, so unfortunately, it looks like this won't help me out. > > After going through the build process and upgrading, I can confirm that the changes I made don't cut out the error message I described. Even if it had, Michael's message makes me believe this wouldn't have solved my problem. > > From: Lonnie Abelbeck <li...@lo...> > Sent: Thursday, January 11, 2018 8:48 AM > To: AstLinux Developers Mailing List > Subject: Re: [Astlinux-devel] Boot Occasionally Freezing While Probing PS/2 Ports > > Hi Josh, > > Yes, if your flash storage is internally connected via USB then no rootdelay could explain what you are seeing. Here is a WiKi reference ... > > Boot via USB Flash Storage > https://doc.astlinux-project.org/userdoc:boot-usb-storage > userdoc:boot-usb-storage [AstLinux Documentation] > doc.astlinux-project.org > For production AstLinux installations, it is recommended to use flash storage connected off IDE, SATA or mSATA controllers, if at all possible. > > > Add rootdelay=10 as described to the KCMD line in the .run.conf file. If you can't remove the flash and mount it as described in the WiKi on a successful boot from the AstLinux CLI ... > -- > mount -o rw,remount /oldroot/cdrom > ## edit the /oldroot/cdrom/os/astlinux-nnnnnn.run.conf file > mount -o ro,remount /oldroot/cdrom > -- > > Or since you build your own "geni586" image, you could edit on your build system "project/astlinux/board/geni586/runnix.conf" file and without a clean build you can simply > -- > ./scripts/build > -- > and install the new image. > > Lonnie > > > On Jan 11, 2018, at 7:10 AM, Josh Alberts <jm...@ho...> wrote: > > > That's an interesting point, Michael. Do you think adding a "rootdelay" might help? If so, is it possible to add something to the KCMD line in the .run.conf file in an already-built environment? > > > > > > From: Michael Keuter <li...@mk...> > > Sent: Thursday, January 11, 2018 5:37 AM > > To: AstLinux Developers Mailing List > > Subject: Re: [Astlinux-devel] Boot Occasionally Freezing While Probing PS/2 Ports > > > > > > > Am 11.01.2018 um 04:25 schrieb Josh Alberts <jm...@ho...>: > > > > > > Hello again, > > > > > > I made a custom build for an HP t5700 thinclient with a Transmeta Crusoe processor. I got that figured out (thanks again, Michael!) but occasionally the machine gets hung up on booting, and this is the last thing on the screen: > > > > > > i8042: PNP: No PS/2 controller found. Probing ports directly. > > > > > > This thinclient has no PS/2 ports, so I figured I could just go ahead and try to remove PS/2 support to solve this issue. I commented out all of the lines under "Hardware I/O ports" in the following files that seemed relevant for my geni586 build: > > > > > > project/runnix-iso/geni586/linux.config > > > project/runnix/geni586/linux.config > > > project/astlinux/geni586/linux-smp.config > > > > > > Then, I went ahead and rm -rf'd my output folder and ran scripts/build geni586. Is this the proper method to remove PS/2 support? Moreover, should this approach solve my problem? Since it's an intermittent issue, it would be great to get some outside input rather than convincing myself after a few successful reboots that I've solved the problem. Thanks! > > > > > > Josh > > > > Hi Josh, > > > > I don't think that has something to do with the PS/2 ports. > > I looked at dmesg on my old Soekris net5501 (also no PS/2 ports): the same message as yours occurs, but then directly after it the CF card is loaded: > > > > ---- > > [ 0.448889] usbcore: registered new interface driver ums-sddr55 > > [ 0.449653] usbcore: registered new interface driver ums-usbat > > [ 0.451065] i8042: PNP: No PS/2 controller found. Probing ports directly. > > [ 0.479585] ata1.00: CFA: SanDisk SDCFH-1024, HDX 4.09, max MWDMA2 > > [ 0.480841] ata1.00: 2001888 sectors, multi 0: LBA > > [ 0.481907] ata1.00: configured for PIO4 > > [ 0.493398] scsi 0:0:0:0: Direct-Access ATA SanDisk SDCFH-10 4.09 PQ: 0 ANSI: 5 > > ---- > > > > Maybe your storage medium has temporary issues … > > > > Michael > > > > http://www.mksolutions.info > Individuelle Telefonie-Lösungen - mit Asterisk - mk ... > www.mksolutions.info > Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > > > Individuelle Telefonie-Lösungen - mit Asterisk - mk ... > > www.mksolutions.info > Individuelle Telefonie-Lösungen - mit Asterisk - mk ... > www.mksolutions.info > Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > > > Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > > > > > > > > > > > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > Astlinux-devel mailing list > > Ast...@li... > > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > > Astlinux-devel mailing list > > Ast...@li... > > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Josh A. <jm...@ho...> - 2018-01-11 14:47:28
|
Lonnie, I'm running this off the thinclient's internal flash drive, so unfortunately, it looks like this won't help me out. After going through the build process and upgrading, I can confirm that the changes I made don't cut out the error message I described. Even if it had, Michael's message makes me believe this wouldn't have solved my problem. ________________________________ From: Lonnie Abelbeck <li...@lo...> Sent: Thursday, January 11, 2018 8:48 AM To: AstLinux Developers Mailing List Subject: Re: [Astlinux-devel] Boot Occasionally Freezing While Probing PS/2 Ports Hi Josh, Yes, if your flash storage is internally connected via USB then no rootdelay could explain what you are seeing. Here is a WiKi reference ... Boot via USB Flash Storage https://doc.astlinux-project.org/userdoc:boot-usb-storage userdoc:boot-usb-storage [AstLinux Documentation]<https://doc.astlinux-project.org/userdoc:boot-usb-storage> doc.astlinux-project.org For production AstLinux installations, it is recommended to use flash storage connected off IDE, SATA or mSATA controllers, if at all possible. Add rootdelay=10 as described to the KCMD line in the .run.conf file. If you can't remove the flash and mount it as described in the WiKi on a successful boot from the AstLinux CLI ... -- mount -o rw,remount /oldroot/cdrom ## edit the /oldroot/cdrom/os/astlinux-nnnnnn.run.conf file mount -o ro,remount /oldroot/cdrom -- Or since you build your own "geni586" image, you could edit on your build system "project/astlinux/board/geni586/runnix.conf" file and without a clean build you can simply -- ./scripts/build -- and install the new image. Lonnie On Jan 11, 2018, at 7:10 AM, Josh Alberts <jm...@ho...> wrote: > That's an interesting point, Michael. Do you think adding a "rootdelay" might help? If so, is it possible to add something to the KCMD line in the .run.conf file in an already-built environment? > > > From: Michael Keuter <li...@mk...> > Sent: Thursday, January 11, 2018 5:37 AM > To: AstLinux Developers Mailing List > Subject: Re: [Astlinux-devel] Boot Occasionally Freezing While Probing PS/2 Ports > > > > Am 11.01.2018 um 04:25 schrieb Josh Alberts <jm...@ho...>: > > > > Hello again, > > > > I made a custom build for an HP t5700 thinclient with a Transmeta Crusoe processor. I got that figured out (thanks again, Michael!) but occasionally the machine gets hung up on booting, and this is the last thing on the screen: > > > > i8042: PNP: No PS/2 controller found. Probing ports directly. > > > > This thinclient has no PS/2 ports, so I figured I could just go ahead and try to remove PS/2 support to solve this issue. I commented out all of the lines under "Hardware I/O ports" in the following files that seemed relevant for my geni586 build: > > > > project/runnix-iso/geni586/linux.config > > project/runnix/geni586/linux.config > > project/astlinux/geni586/linux-smp.config > > > > Then, I went ahead and rm -rf'd my output folder and ran scripts/build geni586. Is this the proper method to remove PS/2 support? Moreover, should this approach solve my problem? Since it's an intermittent issue, it would be great to get some outside input rather than convincing myself after a few successful reboots that I've solved the problem. Thanks! > > > > Josh > > Hi Josh, > > I don't think that has something to do with the PS/2 ports. > I looked at dmesg on my old Soekris net5501 (also no PS/2 ports): the same message as yours occurs, but then directly after it the CF card is loaded: > > ---- > [ 0.448889] usbcore: registered new interface driver ums-sddr55 > [ 0.449653] usbcore: registered new interface driver ums-usbat > [ 0.451065] i8042: PNP: No PS/2 controller found. Probing ports directly. > [ 0.479585] ata1.00: CFA: SanDisk SDCFH-1024, HDX 4.09, max MWDMA2 > [ 0.480841] ata1.00: 2001888 sectors, multi 0: LBA > [ 0.481907] ata1.00: configured for PIO4 > [ 0.493398] scsi 0:0:0:0: Direct-Access ATA SanDisk SDCFH-10 4.09 PQ: 0 ANSI: 5 > ---- > > Maybe your storage medium has temporary issues … > > Michael > > http://www.mksolutions.info Individuelle Telefonie-Lösungen - mit Asterisk - mk ...<http://www.mksolutions.info/> www.mksolutions.info Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > Individuelle Telefonie-Lösungen - mit Asterisk - mk ... > www.mksolutions.info<http://www.mksolutions.info> Individuelle Telefonie-Lösungen - mit Asterisk - mk ...<http://www.mksolutions.info/> www.mksolutions.info Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > > > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Astlinux-devel mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Lonnie A. <li...@lo...> - 2018-01-11 13:48:22
|
Hi Josh, Yes, if your flash storage is internally connected via USB then no rootdelay could explain what you are seeing. Here is a WiKi reference ... Boot via USB Flash Storage https://doc.astlinux-project.org/userdoc:boot-usb-storage Add rootdelay=10 as described to the KCMD line in the .run.conf file. If you can't remove the flash and mount it as described in the WiKi on a successful boot from the AstLinux CLI ... -- mount -o rw,remount /oldroot/cdrom ## edit the /oldroot/cdrom/os/astlinux-nnnnnn.run.conf file mount -o ro,remount /oldroot/cdrom -- Or since you build your own "geni586" image, you could edit on your build system "project/astlinux/board/geni586/runnix.conf" file and without a clean build you can simply -- ./scripts/build -- and install the new image. Lonnie On Jan 11, 2018, at 7:10 AM, Josh Alberts <jm...@ho...> wrote: > That's an interesting point, Michael. Do you think adding a "rootdelay" might help? If so, is it possible to add something to the KCMD line in the .run.conf file in an already-built environment? > > > From: Michael Keuter <li...@mk...> > Sent: Thursday, January 11, 2018 5:37 AM > To: AstLinux Developers Mailing List > Subject: Re: [Astlinux-devel] Boot Occasionally Freezing While Probing PS/2 Ports > > > > Am 11.01.2018 um 04:25 schrieb Josh Alberts <jm...@ho...>: > > > > Hello again, > > > > I made a custom build for an HP t5700 thinclient with a Transmeta Crusoe processor. I got that figured out (thanks again, Michael!) but occasionally the machine gets hung up on booting, and this is the last thing on the screen: > > > > i8042: PNP: No PS/2 controller found. Probing ports directly. > > > > This thinclient has no PS/2 ports, so I figured I could just go ahead and try to remove PS/2 support to solve this issue. I commented out all of the lines under "Hardware I/O ports" in the following files that seemed relevant for my geni586 build: > > > > project/runnix-iso/geni586/linux.config > > project/runnix/geni586/linux.config > > project/astlinux/geni586/linux-smp.config > > > > Then, I went ahead and rm -rf'd my output folder and ran scripts/build geni586. Is this the proper method to remove PS/2 support? Moreover, should this approach solve my problem? Since it's an intermittent issue, it would be great to get some outside input rather than convincing myself after a few successful reboots that I've solved the problem. Thanks! > > > > Josh > > Hi Josh, > > I don't think that has something to do with the PS/2 ports. > I looked at dmesg on my old Soekris net5501 (also no PS/2 ports): the same message as yours occurs, but then directly after it the CF card is loaded: > > ---- > [ 0.448889] usbcore: registered new interface driver ums-sddr55 > [ 0.449653] usbcore: registered new interface driver ums-usbat > [ 0.451065] i8042: PNP: No PS/2 controller found. Probing ports directly. > [ 0.479585] ata1.00: CFA: SanDisk SDCFH-1024, HDX 4.09, max MWDMA2 > [ 0.480841] ata1.00: 2001888 sectors, multi 0: LBA > [ 0.481907] ata1.00: configured for PIO4 > [ 0.493398] scsi 0:0:0:0: Direct-Access ATA SanDisk SDCFH-10 4.09 PQ: 0 ANSI: 5 > ---- > > Maybe your storage medium has temporary issues … > > Michael > > http://www.mksolutions.info > Individuelle Telefonie-Lösungen - mit Asterisk - mk ... > www.mksolutions.info > Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > > > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Josh A. <jm...@ho...> - 2018-01-11 13:11:03
|
That's an interesting point, Michael. Do you think adding a "rootdelay" might help? If so, is it possible to add something to the KCMD line in the .run.conf file in an already-built environment? ________________________________ From: Michael Keuter <li...@mk...> Sent: Thursday, January 11, 2018 5:37 AM To: AstLinux Developers Mailing List Subject: Re: [Astlinux-devel] Boot Occasionally Freezing While Probing PS/2 Ports > Am 11.01.2018 um 04:25 schrieb Josh Alberts <jm...@ho...>: > > Hello again, > > I made a custom build for an HP t5700 thinclient with a Transmeta Crusoe processor. I got that figured out (thanks again, Michael!) but occasionally the machine gets hung up on booting, and this is the last thing on the screen: > > i8042: PNP: No PS/2 controller found. Probing ports directly. > > This thinclient has no PS/2 ports, so I figured I could just go ahead and try to remove PS/2 support to solve this issue. I commented out all of the lines under "Hardware I/O ports" in the following files that seemed relevant for my geni586 build: > > project/runnix-iso/geni586/linux.config > project/runnix/geni586/linux.config > project/astlinux/geni586/linux-smp.config > > Then, I went ahead and rm -rf'd my output folder and ran scripts/build geni586. Is this the proper method to remove PS/2 support? Moreover, should this approach solve my problem? Since it's an intermittent issue, it would be great to get some outside input rather than convincing myself after a few successful reboots that I've solved the problem. Thanks! > > Josh Hi Josh, I don't think that has something to do with the PS/2 ports. I looked at dmesg on my old Soekris net5501 (also no PS/2 ports): the same message as yours occurs, but then directly after it the CF card is loaded: ---- [ 0.448889] usbcore: registered new interface driver ums-sddr55 [ 0.449653] usbcore: registered new interface driver ums-usbat [ 0.451065] i8042: PNP: No PS/2 controller found. Probing ports directly. [ 0.479585] ata1.00: CFA: SanDisk SDCFH-1024, HDX 4.09, max MWDMA2 [ 0.480841] ata1.00: 2001888 sectors, multi 0: LBA [ 0.481907] ata1.00: configured for PIO4 [ 0.493398] scsi 0:0:0:0: Direct-Access ATA SanDisk SDCFH-10 4.09 PQ: 0 ANSI: 5 ---- Maybe your storage medium has temporary issues … Michael http://www.mksolutions.info Individuelle Telefonie-Lösungen - mit Asterisk - mk ...<http://www.mksolutions.info/> www.mksolutions.info Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Astlinux-devel mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Michael K. <li...@mk...> - 2018-01-11 10:37:56
|
> Am 11.01.2018 um 04:25 schrieb Josh Alberts <jm...@ho...>: > > Hello again, > > I made a custom build for an HP t5700 thinclient with a Transmeta Crusoe processor. I got that figured out (thanks again, Michael!) but occasionally the machine gets hung up on booting, and this is the last thing on the screen: > > i8042: PNP: No PS/2 controller found. Probing ports directly. > > This thinclient has no PS/2 ports, so I figured I could just go ahead and try to remove PS/2 support to solve this issue. I commented out all of the lines under "Hardware I/O ports" in the following files that seemed relevant for my geni586 build: > > project/runnix-iso/geni586/linux.config > project/runnix/geni586/linux.config > project/astlinux/geni586/linux-smp.config > > Then, I went ahead and rm -rf'd my output folder and ran scripts/build geni586. Is this the proper method to remove PS/2 support? Moreover, should this approach solve my problem? Since it's an intermittent issue, it would be great to get some outside input rather than convincing myself after a few successful reboots that I've solved the problem. Thanks! > > Josh Hi Josh, I don't think that has something to do with the PS/2 ports. I looked at dmesg on my old Soekris net5501 (also no PS/2 ports): the same message as yours occurs, but then directly after it the CF card is loaded: ---- [ 0.448889] usbcore: registered new interface driver ums-sddr55 [ 0.449653] usbcore: registered new interface driver ums-usbat [ 0.451065] i8042: PNP: No PS/2 controller found. Probing ports directly. [ 0.479585] ata1.00: CFA: SanDisk SDCFH-1024, HDX 4.09, max MWDMA2 [ 0.480841] ata1.00: 2001888 sectors, multi 0: LBA [ 0.481907] ata1.00: configured for PIO4 [ 0.493398] scsi 0:0:0:0: Direct-Access ATA SanDisk SDCFH-10 4.09 PQ: 0 ANSI: 5 ---- Maybe your storage medium has temporary issues … Michael http://www.mksolutions.info |
|
From: Josh A. <jm...@ho...> - 2018-01-11 03:25:56
|
Hello again, I made a custom build for an HP t5700 thinclient with a Transmeta Crusoe processor. I got that figured out (thanks again, Michael!) but occasionally the machine gets hung up on booting, and this is the last thing on the screen: i8042: PNP: No PS/2 controller found. Probing ports directly. This thinclient has no PS/2 ports, so I figured I could just go ahead and try to remove PS/2 support to solve this issue. I commented out all of the lines under "Hardware I/O ports" in the following files that seemed relevant for my geni586 build: project/runnix-iso/geni586/linux.config project/runnix/geni586/linux.config project/astlinux/geni586/linux-smp.config Then, I went ahead and rm -rf'd my output folder and ran scripts/build geni586. Is this the proper method to remove PS/2 support? Moreover, should this approach solve my problem? Since it's an intermittent issue, it would be great to get some outside input rather than convincing myself after a few successful reboots that I've solved the problem. Thanks! Josh |
|
From: Josh A. <jm...@ho...> - 2018-01-10 04:06:13
|
Thank you very much, Michael! That was exactly what I needed to do. Josh ________________________________ From: Michael Keuter <li...@mk...> Sent: Tuesday, January 9, 2018 4:33 PM To: AstLinux Developers Mailing List Subject: Re: [Astlinux-devel] Patching Dahdi in Custom Build > Am 09.01.2018 um 21:44 schrieb Josh Alberts <jm...@ho...>: > > Hello, > > I would like to make a custom build that removes a commented #define in dahdi-linux/include/dahdi/dahdi_config.h to enable EMPULSE support. I created a .patch file, placed it in trunk/package/dahdi-linux and ran build geni586. I hoped that the patch file might automatically get included in the build routine, but it did not. Can someone please explain to me what is the proper way to include a dahdi patch in a custom build? > > Thanks, > > Josh Be sure your patch is named similar to "dahdi-linux-2-somethinguseful-xyz.patch" like the existing patch. Look at "dahdi-linux.mk" for the schema. Michael http://www.mksolutions.info Individuelle Telefonie-Lösungen - mit Asterisk - mk ...<http://www.mksolutions.info/> www.mksolutions.info Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Astlinux-devel mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Michael K. <li...@mk...> - 2018-01-09 21:34:05
|
> Am 09.01.2018 um 21:44 schrieb Josh Alberts <jm...@ho...>: > > Hello, > > I would like to make a custom build that removes a commented #define in dahdi-linux/include/dahdi/dahdi_config.h to enable EMPULSE support. I created a .patch file, placed it in trunk/package/dahdi-linux and ran build geni586. I hoped that the patch file might automatically get included in the build routine, but it did not. Can someone please explain to me what is the proper way to include a dahdi patch in a custom build? > > Thanks, > > Josh Be sure your patch is named similar to "dahdi-linux-2-somethinguseful-xyz.patch" like the existing patch. Look at "dahdi-linux.mk" for the schema. Michael http://www.mksolutions.info |
|
From: Josh A. <jm...@ho...> - 2018-01-09 20:45:05
|
Hello, I would like to make a custom build that removes a commented #define in dahdi-linux/include/dahdi/dahdi_config.h to enable EMPULSE support. I created a .patch file, placed it in trunk/package/dahdi-linux and ran build geni586. I hoped that the patch file might automatically get included in the build routine, but it did not. Can someone please explain to me what is the proper way to include a dahdi patch in a custom build? Thanks, Josh |
|
From: Michael K. <mic...@ip...> - 2018-01-08 00:25:51
|
Hi Lonnie I suspect that start and answer may not be the same in some cases. Could we have a start and calldate column and one of them could be deleted depending on what you want to use? Regards Michael Knill -----Original Message----- From: Lonnie Abelbeck <li...@lo...> Reply-To: AstLinux Developers Mailing List <ast...@li...> Date: Monday, 8 January 2018 at 10:46 am To: AstLinux Developers Mailing List <ast...@li...> Subject: Re: [Astlinux-devel] CDR Table for Asterisk 13 > PS would it be worth using the native start column rather than the custom calldate column so we don't need to add an alias? The calldate column is historical. I'm inclined to leave it as is. Who knows what 3'rd party script might want "calldate". I guess "start" could point to "answer" if that was preferred as it is now. Lonnie On Jan 7, 2018, at 4:49 PM, Michael Knill <mic...@ip...> wrote: > We have built a script which I will use in my upgrade script but I didn't realise I could also do it in the SQL Tab if I needed to so that's cool. > Its pretty much a once only task so CLI is fine. > PS would it be worth using the native start column rather than the custom calldate column so we don't need to add an alias? > > Regards > Michael Knill > > -----Original Message----- > From: Lonnie Abelbeck <li...@lo...> > Reply-To: AstLinux Developers Mailing List <ast...@li...> > Date: Monday, 8 January 2018 at 2:35 am > To: AstLinux Developers Mailing List <ast...@li...> > Subject: Re: [Astlinux-devel] CDR Table for Asterisk 13 > > Hi Michael, > > Interesting, Asterisk 11.25.3 properly fills in the following using cdr_adaptive_odbc.so > -- > 'answer' TEXT > 'end' TEXT > 'linkedid' TEXT > 'peeraccount' TEXT > 'sequence' TEXT > -- > Tip -> Use "module reload cdr_adaptive_odbc.so" to apply any SQL table changes. > > I guess it is simpler for users/admins to delete unused columns/fields rather than add them using the SQL-Data tab, so adding these 5 fields by default is probably a good thing. > > BTW, this only effects new installs when /mnt/kd/cdr-sqlite3/cdr-odbc.sqlite3 does not exist. > >> How would you plan on them being added by an administrator? All manual? > > SQL-Data tab -> CDR ODBC -> [table] cdr -> Structure > > There you can add and delete CDR columns/fields . > > Lonnie > > > On Jan 7, 2018, at 1:34 AM, Michael Knill <mic...@ip...> wrote: > >> Thanks Lonnie >> >> I don't see any reason why you wouldn't create all the fields for 11 as well so you don't need to add them later. >> Happy for actual fields created to be customised but it's a bit harder when that have already been created in init.d. >> How would you plan on them being added by an administrator? All manual? >> >> Regards >> Michael Knill >> >> -----Original Message----- >> From: Lonnie Abelbeck <li...@lo...> >> Reply-To: AstLinux Developers Mailing List <ast...@li...> >> Date: Sunday, 7 January 2018 at 3:57 pm >> To: AstLinux Developers Mailing List <ast...@li...> >> Subject: Re: [Astlinux-devel] CDR Table for Asterisk 13 >> >> Hi Michael, >> >> Perfectly clear now, without the default /mnt/kd/cdr-sqlite3/cdr-odbc.sqlite3 containing all the fields, the cdr_adaptive_odbc.conf will skip those missing fields. >> >> So, the missing fields are: >> -- >> 'answer' TEXT >> 'end' TEXT >> 'linkedid' TEXT >> 'peeraccount' TEXT >> 'sequence' REAL >> -- >> agree ? >> all 5 appended at the end of the current fields ? >> >> Hmmm, I wonder if these added fields should also be included for initial Asterisk 11 installations so later upgrades to Asterisk 13 will populate the added fields ? >> >> The drawback is these 5 extra fields, would all be empty in Asterisk 11 and the full "cdr" SQL-Data tab would not be very pretty. >> >> Do Asterisk 13 users always want all 5 extra fields ? Possibly we should simply allow users (administrators) add the fields they want with Asterisk 13 ? >> >> Comments ? >> >> Lonnie >> >> >> >> On Jan 6, 2018, at 9:57 PM, Michael Knill <mic...@ip...> wrote: >> >>> So sorry Lonnie for not being clear. >>> This is when you are logging to sqlight3. You create the database and table on startup in init.d/asterisk if cdr-odbc.sqlite3 is not there. >>> Im thinking however that init.d/asterisk should add the extra fields into the created database table if the Asterisk version is > 12. >>> >>> Regards >>> Michael Knill >>> -----Original Message----- >>> From: Lonnie Abelbeck <li...@lo...> >>> Reply-To: AstLinux Developers Mailing List <ast...@li...> >>> Date: Sunday, 7 January 2018 at 7:11 am >>> To: AstLinux Developers Mailing List <ast...@li...> >>> Subject: Re: [Astlinux-devel] CDR Table for Asterisk 13 >>> >>> Hi Michael, >>> >>> AFAIF, all the CDR logged fields are a part of of you asterisk *.conf files. >>> >>> If not, please explain in the finest detail so I understand. >>> >>> Lonnie >>> >>> >>> >>> On Jan 6, 2018, at 2:04 PM, Michael Knill <mic...@ip...> wrote: >>> >>>> Hi Lonnie >>>> >>>> Unfortunately, because of the change to the way CDR’s are generated, the new fields are important. >>>> Would it be possible in init.d/asterisk to check the Asterisk version and add the extra fields when using >12. >>>> >>>> What do you think? >>>> >>>> Regards >>>> Michael Knill >>>> >>>> Sent from my iPhone so please excuse my brevity. >>>> >>>>> On 7 Jan 2018, at 12:29 am, Lonnie Abelbeck <li...@lo...> wrote: >>>>> >>>>> >>>>>> On Jan 5, 2018, at 9:25 PM, Michael Knill <mic...@ip...> wrote: >>>>>> >>>>>> Hi Devs >>>>>> >>>>>> I have recently found out that a number of Asterisk CDR changes were made in Asterisk 12 including a number of new CDR fields: >>>>>> https://wiki.asterisk.org/wiki/display/AST/Asterisk+12+CDR+Specification >>>>>> >>>>>> We will therefore need to update the automatically created cdr schema to add the new fields! >>>>>> >>>>>> Regards >>>>>> Michael Knill >>>>> >>>>> Michael, is this a question or comment ? >>>>> >>>>> Yes the Asterisk CDR innards were changed with Asterisk 12-13, but are basically backward compatible with the Asterisk 11 configs. >>>>> >>>>> Lonnie >> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Astlinux-devel mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-devel >> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Astlinux-devel mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Astlinux-devel mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Lonnie A. <li...@lo...> - 2018-01-07 23:46:18
|
> PS would it be worth using the native start column rather than the custom calldate column so we don't need to add an alias? The calldate column is historical. I'm inclined to leave it as is. Who knows what 3'rd party script might want "calldate". I guess "start" could point to "answer" if that was preferred as it is now. Lonnie On Jan 7, 2018, at 4:49 PM, Michael Knill <mic...@ip...> wrote: > We have built a script which I will use in my upgrade script but I didn't realise I could also do it in the SQL Tab if I needed to so that's cool. > Its pretty much a once only task so CLI is fine. > PS would it be worth using the native start column rather than the custom calldate column so we don't need to add an alias? > > Regards > Michael Knill > > -----Original Message----- > From: Lonnie Abelbeck <li...@lo...> > Reply-To: AstLinux Developers Mailing List <ast...@li...> > Date: Monday, 8 January 2018 at 2:35 am > To: AstLinux Developers Mailing List <ast...@li...> > Subject: Re: [Astlinux-devel] CDR Table for Asterisk 13 > > Hi Michael, > > Interesting, Asterisk 11.25.3 properly fills in the following using cdr_adaptive_odbc.so > -- > 'answer' TEXT > 'end' TEXT > 'linkedid' TEXT > 'peeraccount' TEXT > 'sequence' TEXT > -- > Tip -> Use "module reload cdr_adaptive_odbc.so" to apply any SQL table changes. > > I guess it is simpler for users/admins to delete unused columns/fields rather than add them using the SQL-Data tab, so adding these 5 fields by default is probably a good thing. > > BTW, this only effects new installs when /mnt/kd/cdr-sqlite3/cdr-odbc.sqlite3 does not exist. > >> How would you plan on them being added by an administrator? All manual? > > SQL-Data tab -> CDR ODBC -> [table] cdr -> Structure > > There you can add and delete CDR columns/fields . > > Lonnie > > > On Jan 7, 2018, at 1:34 AM, Michael Knill <mic...@ip...> wrote: > >> Thanks Lonnie >> >> I don't see any reason why you wouldn't create all the fields for 11 as well so you don't need to add them later. >> Happy for actual fields created to be customised but it's a bit harder when that have already been created in init.d. >> How would you plan on them being added by an administrator? All manual? >> >> Regards >> Michael Knill >> >> -----Original Message----- >> From: Lonnie Abelbeck <li...@lo...> >> Reply-To: AstLinux Developers Mailing List <ast...@li...> >> Date: Sunday, 7 January 2018 at 3:57 pm >> To: AstLinux Developers Mailing List <ast...@li...> >> Subject: Re: [Astlinux-devel] CDR Table for Asterisk 13 >> >> Hi Michael, >> >> Perfectly clear now, without the default /mnt/kd/cdr-sqlite3/cdr-odbc.sqlite3 containing all the fields, the cdr_adaptive_odbc.conf will skip those missing fields. >> >> So, the missing fields are: >> -- >> 'answer' TEXT >> 'end' TEXT >> 'linkedid' TEXT >> 'peeraccount' TEXT >> 'sequence' REAL >> -- >> agree ? >> all 5 appended at the end of the current fields ? >> >> Hmmm, I wonder if these added fields should also be included for initial Asterisk 11 installations so later upgrades to Asterisk 13 will populate the added fields ? >> >> The drawback is these 5 extra fields, would all be empty in Asterisk 11 and the full "cdr" SQL-Data tab would not be very pretty. >> >> Do Asterisk 13 users always want all 5 extra fields ? Possibly we should simply allow users (administrators) add the fields they want with Asterisk 13 ? >> >> Comments ? >> >> Lonnie >> >> >> >> On Jan 6, 2018, at 9:57 PM, Michael Knill <mic...@ip...> wrote: >> >>> So sorry Lonnie for not being clear. >>> This is when you are logging to sqlight3. You create the database and table on startup in init.d/asterisk if cdr-odbc.sqlite3 is not there. >>> Im thinking however that init.d/asterisk should add the extra fields into the created database table if the Asterisk version is > 12. >>> >>> Regards >>> Michael Knill >>> -----Original Message----- >>> From: Lonnie Abelbeck <li...@lo...> >>> Reply-To: AstLinux Developers Mailing List <ast...@li...> >>> Date: Sunday, 7 January 2018 at 7:11 am >>> To: AstLinux Developers Mailing List <ast...@li...> >>> Subject: Re: [Astlinux-devel] CDR Table for Asterisk 13 >>> >>> Hi Michael, >>> >>> AFAIF, all the CDR logged fields are a part of of you asterisk *.conf files. >>> >>> If not, please explain in the finest detail so I understand. >>> >>> Lonnie >>> >>> >>> >>> On Jan 6, 2018, at 2:04 PM, Michael Knill <mic...@ip...> wrote: >>> >>>> Hi Lonnie >>>> >>>> Unfortunately, because of the change to the way CDR’s are generated, the new fields are important. >>>> Would it be possible in init.d/asterisk to check the Asterisk version and add the extra fields when using >12. >>>> >>>> What do you think? >>>> >>>> Regards >>>> Michael Knill >>>> >>>> Sent from my iPhone so please excuse my brevity. >>>> >>>>> On 7 Jan 2018, at 12:29 am, Lonnie Abelbeck <li...@lo...> wrote: >>>>> >>>>> >>>>>> On Jan 5, 2018, at 9:25 PM, Michael Knill <mic...@ip...> wrote: >>>>>> >>>>>> Hi Devs >>>>>> >>>>>> I have recently found out that a number of Asterisk CDR changes were made in Asterisk 12 including a number of new CDR fields: >>>>>> https://wiki.asterisk.org/wiki/display/AST/Asterisk+12+CDR+Specification >>>>>> >>>>>> We will therefore need to update the automatically created cdr schema to add the new fields! >>>>>> >>>>>> Regards >>>>>> Michael Knill >>>>> >>>>> Michael, is this a question or comment ? >>>>> >>>>> Yes the Asterisk CDR innards were changed with Asterisk 12-13, but are basically backward compatible with the Asterisk 11 configs. >>>>> >>>>> Lonnie >> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Astlinux-devel mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-devel >> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Astlinux-devel mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Michael K. <mic...@ip...> - 2018-01-07 22:49:53
|
We have built a script which I will use in my upgrade script but I didn't realise I could also do it in the SQL Tab if I needed to so that's cool. Its pretty much a once only task so CLI is fine. PS would it be worth using the native start column rather than the custom calldate column so we don't need to add an alias? Regards Michael Knill -----Original Message----- From: Lonnie Abelbeck <li...@lo...> Reply-To: AstLinux Developers Mailing List <ast...@li...> Date: Monday, 8 January 2018 at 2:35 am To: AstLinux Developers Mailing List <ast...@li...> Subject: Re: [Astlinux-devel] CDR Table for Asterisk 13 Hi Michael, Interesting, Asterisk 11.25.3 properly fills in the following using cdr_adaptive_odbc.so -- 'answer' TEXT 'end' TEXT 'linkedid' TEXT 'peeraccount' TEXT 'sequence' TEXT -- Tip -> Use "module reload cdr_adaptive_odbc.so" to apply any SQL table changes. I guess it is simpler for users/admins to delete unused columns/fields rather than add them using the SQL-Data tab, so adding these 5 fields by default is probably a good thing. BTW, this only effects new installs when /mnt/kd/cdr-sqlite3/cdr-odbc.sqlite3 does not exist. > How would you plan on them being added by an administrator? All manual? SQL-Data tab -> CDR ODBC -> [table] cdr -> Structure There you can add and delete CDR columns/fields . Lonnie On Jan 7, 2018, at 1:34 AM, Michael Knill <mic...@ip...> wrote: > Thanks Lonnie > > I don't see any reason why you wouldn't create all the fields for 11 as well so you don't need to add them later. > Happy for actual fields created to be customised but it's a bit harder when that have already been created in init.d. > How would you plan on them being added by an administrator? All manual? > > Regards > Michael Knill > > -----Original Message----- > From: Lonnie Abelbeck <li...@lo...> > Reply-To: AstLinux Developers Mailing List <ast...@li...> > Date: Sunday, 7 January 2018 at 3:57 pm > To: AstLinux Developers Mailing List <ast...@li...> > Subject: Re: [Astlinux-devel] CDR Table for Asterisk 13 > > Hi Michael, > > Perfectly clear now, without the default /mnt/kd/cdr-sqlite3/cdr-odbc.sqlite3 containing all the fields, the cdr_adaptive_odbc.conf will skip those missing fields. > > So, the missing fields are: > -- > 'answer' TEXT > 'end' TEXT > 'linkedid' TEXT > 'peeraccount' TEXT > 'sequence' REAL > -- > agree ? > all 5 appended at the end of the current fields ? > > Hmmm, I wonder if these added fields should also be included for initial Asterisk 11 installations so later upgrades to Asterisk 13 will populate the added fields ? > > The drawback is these 5 extra fields, would all be empty in Asterisk 11 and the full "cdr" SQL-Data tab would not be very pretty. > > Do Asterisk 13 users always want all 5 extra fields ? Possibly we should simply allow users (administrators) add the fields they want with Asterisk 13 ? > > Comments ? > > Lonnie > > > > On Jan 6, 2018, at 9:57 PM, Michael Knill <mic...@ip...> wrote: > >> So sorry Lonnie for not being clear. >> This is when you are logging to sqlight3. You create the database and table on startup in init.d/asterisk if cdr-odbc.sqlite3 is not there. >> Im thinking however that init.d/asterisk should add the extra fields into the created database table if the Asterisk version is > 12. >> >> Regards >> Michael Knill >> -----Original Message----- >> From: Lonnie Abelbeck <li...@lo...> >> Reply-To: AstLinux Developers Mailing List <ast...@li...> >> Date: Sunday, 7 January 2018 at 7:11 am >> To: AstLinux Developers Mailing List <ast...@li...> >> Subject: Re: [Astlinux-devel] CDR Table for Asterisk 13 >> >> Hi Michael, >> >> AFAIF, all the CDR logged fields are a part of of you asterisk *.conf files. >> >> If not, please explain in the finest detail so I understand. >> >> Lonnie >> >> >> >> On Jan 6, 2018, at 2:04 PM, Michael Knill <mic...@ip...> wrote: >> >>> Hi Lonnie >>> >>> Unfortunately, because of the change to the way CDR’s are generated, the new fields are important. >>> Would it be possible in init.d/asterisk to check the Asterisk version and add the extra fields when using >12. >>> >>> What do you think? >>> >>> Regards >>> Michael Knill >>> >>> Sent from my iPhone so please excuse my brevity. >>> >>>> On 7 Jan 2018, at 12:29 am, Lonnie Abelbeck <li...@lo...> wrote: >>>> >>>> >>>>> On Jan 5, 2018, at 9:25 PM, Michael Knill <mic...@ip...> wrote: >>>>> >>>>> Hi Devs >>>>> >>>>> I have recently found out that a number of Asterisk CDR changes were made in Asterisk 12 including a number of new CDR fields: >>>>> https://wiki.asterisk.org/wiki/display/AST/Asterisk+12+CDR+Specification >>>>> >>>>> We will therefore need to update the automatically created cdr schema to add the new fields! >>>>> >>>>> Regards >>>>> Michael Knill >>>> >>>> Michael, is this a question or comment ? >>>> >>>> Yes the Asterisk CDR innards were changed with Asterisk 12-13, but are basically backward compatible with the Asterisk 11 configs. >>>> >>>> Lonnie > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Astlinux-devel mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Lonnie A. <li...@lo...> - 2018-01-07 20:39:53
|
Added ... asterisk, init.d script, add extra default CDR fields... https://github.com/astlinux-project/astlinux/commit/b38ffb22e947ac25a768d13218d448bd7d583b85 Lonnie On Jan 7, 2018, at 9:34 AM, Lonnie Abelbeck <li...@lo...> wrote: > Hi Michael, > > Interesting, Asterisk 11.25.3 properly fills in the following using cdr_adaptive_odbc.so > -- > 'answer' TEXT > 'end' TEXT > 'linkedid' TEXT > 'peeraccount' TEXT > 'sequence' TEXT > -- > Tip -> Use "module reload cdr_adaptive_odbc.so" to apply any SQL table changes. > > I guess it is simpler for users/admins to delete unused columns/fields rather than add them using the SQL-Data tab, so adding these 5 fields by default is probably a good thing. > > BTW, this only effects new installs when /mnt/kd/cdr-sqlite3/cdr-odbc.sqlite3 does not exist. > >> How would you plan on them being added by an administrator? All manual? > > SQL-Data tab -> CDR ODBC -> [table] cdr -> Structure > > There you can add and delete CDR columns/fields . > > Lonnie > > > On Jan 7, 2018, at 1:34 AM, Michael Knill <mic...@ip...> wrote: > >> Thanks Lonnie >> >> I don't see any reason why you wouldn't create all the fields for 11 as well so you don't need to add them later. >> Happy for actual fields created to be customised but it's a bit harder when that have already been created in init.d. >> How would you plan on them being added by an administrator? All manual? >> >> Regards >> Michael Knill >> >> -----Original Message----- >> From: Lonnie Abelbeck <li...@lo...> >> Reply-To: AstLinux Developers Mailing List <ast...@li...> >> Date: Sunday, 7 January 2018 at 3:57 pm >> To: AstLinux Developers Mailing List <ast...@li...> >> Subject: Re: [Astlinux-devel] CDR Table for Asterisk 13 >> >> Hi Michael, >> >> Perfectly clear now, without the default /mnt/kd/cdr-sqlite3/cdr-odbc.sqlite3 containing all the fields, the cdr_adaptive_odbc.conf will skip those missing fields. >> >> So, the missing fields are: >> -- >> 'answer' TEXT >> 'end' TEXT >> 'linkedid' TEXT >> 'peeraccount' TEXT >> 'sequence' REAL >> -- >> agree ? >> all 5 appended at the end of the current fields ? >> >> Hmmm, I wonder if these added fields should also be included for initial Asterisk 11 installations so later upgrades to Asterisk 13 will populate the added fields ? >> >> The drawback is these 5 extra fields, would all be empty in Asterisk 11 and the full "cdr" SQL-Data tab would not be very pretty. >> >> Do Asterisk 13 users always want all 5 extra fields ? Possibly we should simply allow users (administrators) add the fields they want with Asterisk 13 ? >> >> Comments ? >> >> Lonnie >> >> >> >> On Jan 6, 2018, at 9:57 PM, Michael Knill <mic...@ip...> wrote: >> >>> So sorry Lonnie for not being clear. >>> This is when you are logging to sqlight3. You create the database and table on startup in init.d/asterisk if cdr-odbc.sqlite3 is not there. >>> Im thinking however that init.d/asterisk should add the extra fields into the created database table if the Asterisk version is > 12. >>> >>> Regards >>> Michael Knill >>> -----Original Message----- >>> From: Lonnie Abelbeck <li...@lo...> >>> Reply-To: AstLinux Developers Mailing List <ast...@li...> >>> Date: Sunday, 7 January 2018 at 7:11 am >>> To: AstLinux Developers Mailing List <ast...@li...> >>> Subject: Re: [Astlinux-devel] CDR Table for Asterisk 13 >>> >>> Hi Michael, >>> >>> AFAIF, all the CDR logged fields are a part of of you asterisk *.conf files. >>> >>> If not, please explain in the finest detail so I understand. >>> >>> Lonnie >>> >>> >>> >>> On Jan 6, 2018, at 2:04 PM, Michael Knill <mic...@ip...> wrote: >>> >>>> Hi Lonnie >>>> >>>> Unfortunately, because of the change to the way CDR’s are generated, the new fields are important. >>>> Would it be possible in init.d/asterisk to check the Asterisk version and add the extra fields when using >12. >>>> >>>> What do you think? >>>> >>>> Regards >>>> Michael Knill >>>> >>>> Sent from my iPhone so please excuse my brevity. >>>> >>>>> On 7 Jan 2018, at 12:29 am, Lonnie Abelbeck <li...@lo...> wrote: >>>>> >>>>> >>>>>> On Jan 5, 2018, at 9:25 PM, Michael Knill <mic...@ip...> wrote: >>>>>> >>>>>> Hi Devs >>>>>> >>>>>> I have recently found out that a number of Asterisk CDR changes were made in Asterisk 12 including a number of new CDR fields: >>>>>> https://wiki.asterisk.org/wiki/display/AST/Asterisk+12+CDR+Specification >>>>>> >>>>>> We will therefore need to update the automatically created cdr schema to add the new fields! >>>>>> >>>>>> Regards >>>>>> Michael Knill >>>>> >>>>> Michael, is this a question or comment ? >>>>> >>>>> Yes the Asterisk CDR innards were changed with Asterisk 12-13, but are basically backward compatible with the Asterisk 11 configs. >>>>> >>>>> Lonnie >> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Astlinux-devel mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-devel >> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Astlinux-devel mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Lonnie A. <li...@lo...> - 2018-01-07 15:34:23
|
Hi Michael, Interesting, Asterisk 11.25.3 properly fills in the following using cdr_adaptive_odbc.so -- 'answer' TEXT 'end' TEXT 'linkedid' TEXT 'peeraccount' TEXT 'sequence' TEXT -- Tip -> Use "module reload cdr_adaptive_odbc.so" to apply any SQL table changes. I guess it is simpler for users/admins to delete unused columns/fields rather than add them using the SQL-Data tab, so adding these 5 fields by default is probably a good thing. BTW, this only effects new installs when /mnt/kd/cdr-sqlite3/cdr-odbc.sqlite3 does not exist. > How would you plan on them being added by an administrator? All manual? SQL-Data tab -> CDR ODBC -> [table] cdr -> Structure There you can add and delete CDR columns/fields . Lonnie On Jan 7, 2018, at 1:34 AM, Michael Knill <mic...@ip...> wrote: > Thanks Lonnie > > I don't see any reason why you wouldn't create all the fields for 11 as well so you don't need to add them later. > Happy for actual fields created to be customised but it's a bit harder when that have already been created in init.d. > How would you plan on them being added by an administrator? All manual? > > Regards > Michael Knill > > -----Original Message----- > From: Lonnie Abelbeck <li...@lo...> > Reply-To: AstLinux Developers Mailing List <ast...@li...> > Date: Sunday, 7 January 2018 at 3:57 pm > To: AstLinux Developers Mailing List <ast...@li...> > Subject: Re: [Astlinux-devel] CDR Table for Asterisk 13 > > Hi Michael, > > Perfectly clear now, without the default /mnt/kd/cdr-sqlite3/cdr-odbc.sqlite3 containing all the fields, the cdr_adaptive_odbc.conf will skip those missing fields. > > So, the missing fields are: > -- > 'answer' TEXT > 'end' TEXT > 'linkedid' TEXT > 'peeraccount' TEXT > 'sequence' REAL > -- > agree ? > all 5 appended at the end of the current fields ? > > Hmmm, I wonder if these added fields should also be included for initial Asterisk 11 installations so later upgrades to Asterisk 13 will populate the added fields ? > > The drawback is these 5 extra fields, would all be empty in Asterisk 11 and the full "cdr" SQL-Data tab would not be very pretty. > > Do Asterisk 13 users always want all 5 extra fields ? Possibly we should simply allow users (administrators) add the fields they want with Asterisk 13 ? > > Comments ? > > Lonnie > > > > On Jan 6, 2018, at 9:57 PM, Michael Knill <mic...@ip...> wrote: > >> So sorry Lonnie for not being clear. >> This is when you are logging to sqlight3. You create the database and table on startup in init.d/asterisk if cdr-odbc.sqlite3 is not there. >> Im thinking however that init.d/asterisk should add the extra fields into the created database table if the Asterisk version is > 12. >> >> Regards >> Michael Knill >> -----Original Message----- >> From: Lonnie Abelbeck <li...@lo...> >> Reply-To: AstLinux Developers Mailing List <ast...@li...> >> Date: Sunday, 7 January 2018 at 7:11 am >> To: AstLinux Developers Mailing List <ast...@li...> >> Subject: Re: [Astlinux-devel] CDR Table for Asterisk 13 >> >> Hi Michael, >> >> AFAIF, all the CDR logged fields are a part of of you asterisk *.conf files. >> >> If not, please explain in the finest detail so I understand. >> >> Lonnie >> >> >> >> On Jan 6, 2018, at 2:04 PM, Michael Knill <mic...@ip...> wrote: >> >>> Hi Lonnie >>> >>> Unfortunately, because of the change to the way CDR’s are generated, the new fields are important. >>> Would it be possible in init.d/asterisk to check the Asterisk version and add the extra fields when using >12. >>> >>> What do you think? >>> >>> Regards >>> Michael Knill >>> >>> Sent from my iPhone so please excuse my brevity. >>> >>>> On 7 Jan 2018, at 12:29 am, Lonnie Abelbeck <li...@lo...> wrote: >>>> >>>> >>>>> On Jan 5, 2018, at 9:25 PM, Michael Knill <mic...@ip...> wrote: >>>>> >>>>> Hi Devs >>>>> >>>>> I have recently found out that a number of Asterisk CDR changes were made in Asterisk 12 including a number of new CDR fields: >>>>> https://wiki.asterisk.org/wiki/display/AST/Asterisk+12+CDR+Specification >>>>> >>>>> We will therefore need to update the automatically created cdr schema to add the new fields! >>>>> >>>>> Regards >>>>> Michael Knill >>>> >>>> Michael, is this a question or comment ? >>>> >>>> Yes the Asterisk CDR innards were changed with Asterisk 12-13, but are basically backward compatible with the Asterisk 11 configs. >>>> >>>> Lonnie > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Michael K. <mic...@ip...> - 2018-01-07 07:34:52
|
Thanks Lonnie I don't see any reason why you wouldn't create all the fields for 11 as well so you don't need to add them later. Happy for actual fields created to be customised but it's a bit harder when that have already been created in init.d. How would you plan on them being added by an administrator? All manual? Regards Michael Knill -----Original Message----- From: Lonnie Abelbeck <li...@lo...> Reply-To: AstLinux Developers Mailing List <ast...@li...> Date: Sunday, 7 January 2018 at 3:57 pm To: AstLinux Developers Mailing List <ast...@li...> Subject: Re: [Astlinux-devel] CDR Table for Asterisk 13 Hi Michael, Perfectly clear now, without the default /mnt/kd/cdr-sqlite3/cdr-odbc.sqlite3 containing all the fields, the cdr_adaptive_odbc.conf will skip those missing fields. So, the missing fields are: -- 'answer' TEXT 'end' TEXT 'linkedid' TEXT 'peeraccount' TEXT 'sequence' REAL -- agree ? all 5 appended at the end of the current fields ? Hmmm, I wonder if these added fields should also be included for initial Asterisk 11 installations so later upgrades to Asterisk 13 will populate the added fields ? The drawback is these 5 extra fields, would all be empty in Asterisk 11 and the full "cdr" SQL-Data tab would not be very pretty. Do Asterisk 13 users always want all 5 extra fields ? Possibly we should simply allow users (administrators) add the fields they want with Asterisk 13 ? Comments ? Lonnie On Jan 6, 2018, at 9:57 PM, Michael Knill <mic...@ip...> wrote: > So sorry Lonnie for not being clear. > This is when you are logging to sqlight3. You create the database and table on startup in init.d/asterisk if cdr-odbc.sqlite3 is not there. > Im thinking however that init.d/asterisk should add the extra fields into the created database table if the Asterisk version is > 12. > > Regards > Michael Knill > -----Original Message----- > From: Lonnie Abelbeck <li...@lo...> > Reply-To: AstLinux Developers Mailing List <ast...@li...> > Date: Sunday, 7 January 2018 at 7:11 am > To: AstLinux Developers Mailing List <ast...@li...> > Subject: Re: [Astlinux-devel] CDR Table for Asterisk 13 > > Hi Michael, > > AFAIF, all the CDR logged fields are a part of of you asterisk *.conf files. > > If not, please explain in the finest detail so I understand. > > Lonnie > > > > On Jan 6, 2018, at 2:04 PM, Michael Knill <mic...@ip...> wrote: > >> Hi Lonnie >> >> Unfortunately, because of the change to the way CDR’s are generated, the new fields are important. >> Would it be possible in init.d/asterisk to check the Asterisk version and add the extra fields when using >12. >> >> What do you think? >> >> Regards >> Michael Knill >> >> Sent from my iPhone so please excuse my brevity. >> >>> On 7 Jan 2018, at 12:29 am, Lonnie Abelbeck <li...@lo...> wrote: >>> >>> >>>> On Jan 5, 2018, at 9:25 PM, Michael Knill <mic...@ip...> wrote: >>>> >>>> Hi Devs >>>> >>>> I have recently found out that a number of Asterisk CDR changes were made in Asterisk 12 including a number of new CDR fields: >>>> https://wiki.asterisk.org/wiki/display/AST/Asterisk+12+CDR+Specification >>>> >>>> We will therefore need to update the automatically created cdr schema to add the new fields! >>>> >>>> Regards >>>> Michael Knill >>> >>> Michael, is this a question or comment ? >>> >>> Yes the Asterisk CDR innards were changed with Asterisk 12-13, but are basically backward compatible with the Asterisk 11 configs. >>> >>> Lonnie ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Astlinux-devel mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Lonnie A. <li...@lo...> - 2018-01-07 04:57:34
|
Hi Michael, Perfectly clear now, without the default /mnt/kd/cdr-sqlite3/cdr-odbc.sqlite3 containing all the fields, the cdr_adaptive_odbc.conf will skip those missing fields. So, the missing fields are: -- 'answer' TEXT 'end' TEXT 'linkedid' TEXT 'peeraccount' TEXT 'sequence' REAL -- agree ? all 5 appended at the end of the current fields ? Hmmm, I wonder if these added fields should also be included for initial Asterisk 11 installations so later upgrades to Asterisk 13 will populate the added fields ? The drawback is these 5 extra fields, would all be empty in Asterisk 11 and the full "cdr" SQL-Data tab would not be very pretty. Do Asterisk 13 users always want all 5 extra fields ? Possibly we should simply allow users (administrators) add the fields they want with Asterisk 13 ? Comments ? Lonnie On Jan 6, 2018, at 9:57 PM, Michael Knill <mic...@ip...> wrote: > So sorry Lonnie for not being clear. > This is when you are logging to sqlight3. You create the database and table on startup in init.d/asterisk if cdr-odbc.sqlite3 is not there. > Im thinking however that init.d/asterisk should add the extra fields into the created database table if the Asterisk version is > 12. > > Regards > Michael Knill > -----Original Message----- > From: Lonnie Abelbeck <li...@lo...> > Reply-To: AstLinux Developers Mailing List <ast...@li...> > Date: Sunday, 7 January 2018 at 7:11 am > To: AstLinux Developers Mailing List <ast...@li...> > Subject: Re: [Astlinux-devel] CDR Table for Asterisk 13 > > Hi Michael, > > AFAIF, all the CDR logged fields are a part of of you asterisk *.conf files. > > If not, please explain in the finest detail so I understand. > > Lonnie > > > > On Jan 6, 2018, at 2:04 PM, Michael Knill <mic...@ip...> wrote: > >> Hi Lonnie >> >> Unfortunately, because of the change to the way CDR’s are generated, the new fields are important. >> Would it be possible in init.d/asterisk to check the Asterisk version and add the extra fields when using >12. >> >> What do you think? >> >> Regards >> Michael Knill >> >> Sent from my iPhone so please excuse my brevity. >> >>> On 7 Jan 2018, at 12:29 am, Lonnie Abelbeck <li...@lo...> wrote: >>> >>> >>>> On Jan 5, 2018, at 9:25 PM, Michael Knill <mic...@ip...> wrote: >>>> >>>> Hi Devs >>>> >>>> I have recently found out that a number of Asterisk CDR changes were made in Asterisk 12 including a number of new CDR fields: >>>> https://wiki.asterisk.org/wiki/display/AST/Asterisk+12+CDR+Specification >>>> >>>> We will therefore need to update the automatically created cdr schema to add the new fields! >>>> >>>> Regards >>>> Michael Knill >>> >>> Michael, is this a question or comment ? >>> >>> Yes the Asterisk CDR innards were changed with Asterisk 12-13, but are basically backward compatible with the Asterisk 11 configs. >>> >>> Lonnie |
|
From: Michael K. <mic...@ip...> - 2018-01-07 03:57:56
|
So sorry Lonnie for not being clear. This is when you are logging to sqlight3. You create the database and table on startup in init.d/asterisk if cdr-odbc.sqlite3 is not there. Im thinking however that init.d/asterisk should add the extra fields into the created database table if the Asterisk version is > 12. Regards Michael Knill -----Original Message----- From: Lonnie Abelbeck <li...@lo...> Reply-To: AstLinux Developers Mailing List <ast...@li...> Date: Sunday, 7 January 2018 at 7:11 am To: AstLinux Developers Mailing List <ast...@li...> Subject: Re: [Astlinux-devel] CDR Table for Asterisk 13 Hi Michael, AFAIF, all the CDR logged fields are a part of of you asterisk *.conf files. If not, please explain in the finest detail so I understand. Lonnie On Jan 6, 2018, at 2:04 PM, Michael Knill <mic...@ip...> wrote: > Hi Lonnie > > Unfortunately, because of the change to the way CDR’s are generated, the new fields are important. > Would it be possible in init.d/asterisk to check the Asterisk version and add the extra fields when using >12. > > What do you think? > > Regards > Michael Knill > > Sent from my iPhone so please excuse my brevity. > >> On 7 Jan 2018, at 12:29 am, Lonnie Abelbeck <li...@lo...> wrote: >> >> >>> On Jan 5, 2018, at 9:25 PM, Michael Knill <mic...@ip...> wrote: >>> >>> Hi Devs >>> >>> I have recently found out that a number of Asterisk CDR changes were made in Asterisk 12 including a number of new CDR fields: >>> https://wiki.asterisk.org/wiki/display/AST/Asterisk+12+CDR+Specification >>> >>> We will therefore need to update the automatically created cdr schema to add the new fields! >>> >>> Regards >>> Michael Knill >> >> Michael, is this a question or comment ? >> >> Yes the Asterisk CDR innards were changed with Asterisk 12-13, but are basically backward compatible with the Asterisk 11 configs. >> >> Lonnie >> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Astlinux-devel mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-devel > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Astlinux-devel mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Lonnie A. <li...@lo...> - 2018-01-06 20:11:17
|
Hi Michael, AFAIF, all the CDR logged fields are a part of of you asterisk *.conf files. If not, please explain in the finest detail so I understand. Lonnie On Jan 6, 2018, at 2:04 PM, Michael Knill <mic...@ip...> wrote: > Hi Lonnie > > Unfortunately, because of the change to the way CDR’s are generated, the new fields are important. > Would it be possible in init.d/asterisk to check the Asterisk version and add the extra fields when using >12. > > What do you think? > > Regards > Michael Knill > > Sent from my iPhone so please excuse my brevity. > >> On 7 Jan 2018, at 12:29 am, Lonnie Abelbeck <li...@lo...> wrote: >> >> >>> On Jan 5, 2018, at 9:25 PM, Michael Knill <mic...@ip...> wrote: >>> >>> Hi Devs >>> >>> I have recently found out that a number of Asterisk CDR changes were made in Asterisk 12 including a number of new CDR fields: >>> https://wiki.asterisk.org/wiki/display/AST/Asterisk+12+CDR+Specification >>> >>> We will therefore need to update the automatically created cdr schema to add the new fields! >>> >>> Regards >>> Michael Knill >> >> Michael, is this a question or comment ? >> >> Yes the Asterisk CDR innards were changed with Asterisk 12-13, but are basically backward compatible with the Asterisk 11 configs. >> >> Lonnie >> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Astlinux-devel mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-devel > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Michael K. <mic...@ip...> - 2018-01-06 20:04:25
|
Hi Lonnie Unfortunately, because of the change to the way CDR’s are generated, the new fields are important. Would it be possible in init.d/asterisk to check the Asterisk version and add the extra fields when using >12. What do you think? Regards Michael Knill Sent from my iPhone so please excuse my brevity. > On 7 Jan 2018, at 12:29 am, Lonnie Abelbeck <li...@lo...> wrote: > > >> On Jan 5, 2018, at 9:25 PM, Michael Knill <mic...@ip...> wrote: >> >> Hi Devs >> >> I have recently found out that a number of Asterisk CDR changes were made in Asterisk 12 including a number of new CDR fields: >> https://wiki.asterisk.org/wiki/display/AST/Asterisk+12+CDR+Specification >> >> We will therefore need to update the automatically created cdr schema to add the new fields! >> >> Regards >> Michael Knill > > Michael, is this a question or comment ? > > Yes the Asterisk CDR innards were changed with Asterisk 12-13, but are basically backward compatible with the Asterisk 11 configs. > > Lonnie > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Lonnie A. <li...@lo...> - 2018-01-06 13:28:48
|
On Jan 5, 2018, at 9:25 PM, Michael Knill <mic...@ip...> wrote: > Hi Devs > > I have recently found out that a number of Asterisk CDR changes were made in Asterisk 12 including a number of new CDR fields: > https://wiki.asterisk.org/wiki/display/AST/Asterisk+12+CDR+Specification > > We will therefore need to update the automatically created cdr schema to add the new fields! > > Regards > Michael Knill Michael, is this a question or comment ? Yes the Asterisk CDR innards were changed with Asterisk 12-13, but are basically backward compatible with the Asterisk 11 configs. Lonnie |
|
From: Michael K. <mic...@ip...> - 2018-01-06 03:25:57
|
Hi Devs I have recently found out that a number of Asterisk CDR changes were made in Asterisk 12 including a number of new CDR fields: https://wiki.asterisk.org/wiki/display/AST/Asterisk+12+CDR+Specification We will therefore need to update the automatically created cdr schema to add the new fields! Regards Michael Knill |
|
From: Lonnie A. <li...@lo...> - 2017-12-20 03:40:25
|
Sure, I can do that tomorrow. There no doubt is a way to take a listening_ip=IP/NM and generate an interface name and then an index, but it would have be done for all supported platforms. Lonnie On Dec 19, 2017, at 8:58 PM, David Kerr <Da...@Ke...> wrote: > Do you think this worth opening a issue at miniupnpd's github repository? I'd vote yes. > > David > > On Tue, Dec 19, 2017 at 7:33 PM, Lonnie Abelbeck <li...@lo...> wrote: > Fixed in: > https://github.com/astlinux-project/astlinux/commit/a5f4e362ee1e5c2f6b337e727ab62d42654526f1 > > > On Dec 19, 2017, at 6:04 PM, Lonnie Abelbeck <li...@lo...> wrote: > > > Hi David, > > > > I figured it out ... long story short, if we define "listening_ip=" with the interface name rather than IP/NM > > -- old > > listening_ip=192.168.101.1/255.255.255.0 > > -- new > > listening_ip=eth1 > > -- > > No more warnings. > > > > The new interface matching code only works if "listening_ip=" is an interface name, otherwise it defaults to "0" as in "interface index not matching 0 != 7" > > > > Ref: https://github.com/miniupnp/miniupnp/blob/master/miniupnpd/miniupnpd.conf#L8 > > -- > > # LAN network interfaces IPs / networks > > # There can be multiple listening IPs for SSDP traffic, in that case > > # use multiple 'listening_ip=...' lines, one for each network interface. > > # It can be IP address or network interface name (ie. "eth0") > > # It is mandatory to use the network interface name in order to enable IPv6 > > # HTTP is available on all interfaces. > > # When MULTIPLE_EXTERNAL_IP is enabled, the external IP > > # address associated with the subnet follows. For example: > > # listening_ip=192.168.0.1/24 88.22.44.13 > > #listening_ip=192.168.0.1/24 > > #listening_ip=10.5.0.0/16 > > #listening_ip=eth0 > > -- > > > > BTW, I also tested VLAN's with listening_ip= and it works. > > > > While this is a regression in miniupnpd, the configuration fix is simple enough and would be needed if we every wanted to enable IPv6. > > > > I'll make the appropriate changes to our miniupnpd init.d script. > > > > Lonnie > > > > > > On Dec 19, 2017, at 1:30 PM, David Kerr <Da...@Ke...> wrote: > > > >> For reference, here is my .conf file... > >> > >> ## Auto generated file. Do not edit. > >> ext_ifname=eth0 > >> listening_ip= > >> 192.168.17.1/255.255.255.0 > >> http_port=5000 > >> enable_natpmp=yes > >> enable_upnp=yes > >> lease_file=/mnt/kd/upnp.leases > >> bitrate_up=1000000 > >> bitrate_down=15000000 > >> secure_mode=yes > >> min_lifetime=120 > >> max_lifetime=86400 > >> system_uptime=yes > >> notify_interval=60 > >> clean_ruleset_interval=600 > >> uuid=b30041e7-8d39-4bc1-a554-8f6d1b51e50f > >> serial=000001 > >> friendly_name=AstLinux > >> Router > >> model_name=AstLinux Router > >> model_description=astlinux-1.3-5e29e2 > >> model_number=astlinux-1.3-5e29e2 > >> allow 1024-65535 > >> 192.168.17.0/24 > >> 0-65535 > >> deny 0-65535 > >> 0.0.0.0/0 0-65535 > >> > >> > >> > >> On Tue, Dec 19, 2017 at 1:12 PM, Michael Keuter <li...@mk...> wrote: > >> > >>> Am 19.12.2017 um 18:57 schrieb Lonnie Abelbeck <li...@lo...>: > >>> > >>> David and Michael, > >>> > >>> Do you both have UPnP enabled alone or part of NAT-PMP/PCP ? > >>> > >>> It seems without UPnP the error does not occur. Such as with [ NAT-PMP/PCP only ] . > >>> > >>> Lonnie > >> > >> I have enabled "NAT-PMP/PCP & UPnP" on "1st LAN" on my router. > >> > >>> On Dec 19, 2017, at 10:05 AM, David Kerr <Da...@Ke...> wrote: > >>> > >>>> Since miniupnpd version was bumped this week my syslog is getting flooded with warning messages... > >>>> > >>>> Dec 19 10:37:07 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7 > >>>> Dec 19 10:37:07 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7 > >>>> Dec 19 10:37:07 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7 > >>>> Dec 19 10:37:07 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7 > >>>> Dec 19 10:37:08 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7 > >>>> Dec 19 10:37:08 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7 > >>>> Dec 19 10:37:18 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7 > >>>> Dec 19 10:37:18 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7 > >>>> Dec 19 10:37:28 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7 > >>>> Dec 19 10:37:28 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7 > >>>> Dec 19 10:37:32 pbx daemon.notice miniupnpd[3936]: shutting down MiniUPnPd > >>>> Dec 19 10:37:33 pbx daemon.notice miniupnpd[27970]: HTTP listening on port 5000 > >>>> Dec 19 10:37:33 pbx daemon.notice miniupnpd[27970]: Listening for NAT-PMP/PCP traffic on port 5351 > >>>> Dec 19 10:37:36 pbx daemon.warn miniupnpd[27970]: interface index not matching 0 != 7 > >>>> Dec 19 10:37:36 pbx daemon.warn miniupnpd[27970]: interface index not matching 0 != 7 > >>>> Dec 19 10:37:36 pbx daemon.warn miniupnpd[27970]: interface index not matching 0 != 7 > >>>> Dec 19 10:37:36 pbx daemon.warn miniupnpd[27970]: interface index not matching 0 != 7 > >>>> Dec 19 10:37:36 pbx daemon.warn miniupnpd[27970]: interface index not matching 0 != 7 > >>>> > >>>> > >>>> Totally flooded... I am going to have to revert to previous version. > >>>> Is anyone else seeing this? > >>>> > >>>> Cause is this update... > >>>> https://github.com/miniupnp/miniupnp/commit/50d21a38d0719682f276173efd705ccbe78aca3d#diff-daa89c3563f327bfe2e660cddc141ce7 > >>>> > >>>> Any ideas? The only thing I can think of is whether this has to do with my use of a bridge on my internal lan. So "listening_ip" address is on br0 interface rather than on a regular ethernet interface. > >>>> > >>>> Any thoughts? > >>>> David > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: David K. <da...@ke...> - 2017-12-20 02:59:26
|
Do you think this worth opening a issue at miniupnpd's github repository? I'd vote yes. David On Tue, Dec 19, 2017 at 7:33 PM, Lonnie Abelbeck <li...@lo...> wrote: > Fixed in: > https://github.com/astlinux-project/astlinux/commit/ > a5f4e362ee1e5c2f6b337e727ab62d42654526f1 > > > On Dec 19, 2017, at 6:04 PM, Lonnie Abelbeck <li...@lo...> > wrote: > > > Hi David, > > > > I figured it out ... long story short, if we define "listening_ip=" with > the interface name rather than IP/NM > > -- old > > listening_ip=192.168.101.1/255.255.255.0 > > -- new > > listening_ip=eth1 > > -- > > No more warnings. > > > > The new interface matching code only works if "listening_ip=" is an > interface name, otherwise it defaults to "0" as in "interface index not > matching 0 != 7" > > > > Ref: https://github.com/miniupnp/miniupnp/blob/master/ > miniupnpd/miniupnpd.conf#L8 > > -- > > # LAN network interfaces IPs / networks > > # There can be multiple listening IPs for SSDP traffic, in that case > > # use multiple 'listening_ip=...' lines, one for each network interface. > > # It can be IP address or network interface name (ie. "eth0") > > # It is mandatory to use the network interface name in order to enable > IPv6 > > # HTTP is available on all interfaces. > > # When MULTIPLE_EXTERNAL_IP is enabled, the external IP > > # address associated with the subnet follows. For example: > > # listening_ip=192.168.0.1/24 88.22.44.13 > > #listening_ip=192.168.0.1/24 > > #listening_ip=10.5.0.0/16 > > #listening_ip=eth0 > > -- > > > > BTW, I also tested VLAN's with listening_ip= and it works. > > > > While this is a regression in miniupnpd, the configuration fix is simple > enough and would be needed if we every wanted to enable IPv6. > > > > I'll make the appropriate changes to our miniupnpd init.d script. > > > > Lonnie > > > > > > On Dec 19, 2017, at 1:30 PM, David Kerr <Da...@Ke...> wrote: > > > >> For reference, here is my .conf file... > >> > >> ## Auto generated file. Do not edit. > >> ext_ifname=eth0 > >> listening_ip= > >> 192.168.17.1/255.255.255.0 > >> http_port=5000 > >> enable_natpmp=yes > >> enable_upnp=yes > >> lease_file=/mnt/kd/upnp.leases > >> bitrate_up=1000000 > >> bitrate_down=15000000 > >> secure_mode=yes > >> min_lifetime=120 > >> max_lifetime=86400 > >> system_uptime=yes > >> notify_interval=60 > >> clean_ruleset_interval=600 > >> uuid=b30041e7-8d39-4bc1-a554-8f6d1b51e50f > >> serial=000001 > >> friendly_name=AstLinux > >> Router > >> model_name=AstLinux Router > >> model_description=astlinux-1.3-5e29e2 > >> model_number=astlinux-1.3-5e29e2 > >> allow 1024-65535 > >> 192.168.17.0/24 > >> 0-65535 > >> deny 0-65535 > >> 0.0.0.0/0 0-65535 > >> > >> > >> > >> On Tue, Dec 19, 2017 at 1:12 PM, Michael Keuter <li...@mk...> > wrote: > >> > >>> Am 19.12.2017 um 18:57 schrieb Lonnie Abelbeck < > li...@lo...>: > >>> > >>> David and Michael, > >>> > >>> Do you both have UPnP enabled alone or part of NAT-PMP/PCP ? > >>> > >>> It seems without UPnP the error does not occur. Such as with [ > NAT-PMP/PCP only ] . > >>> > >>> Lonnie > >> > >> I have enabled "NAT-PMP/PCP & UPnP" on "1st LAN" on my router. > >> > >>> On Dec 19, 2017, at 10:05 AM, David Kerr <Da...@Ke...> wrote: > >>> > >>>> Since miniupnpd version was bumped this week my syslog is getting > flooded with warning messages... > >>>> > >>>> Dec 19 10:37:07 pbx daemon.warn miniupnpd[3936]: interface index not > matching 0 != 7 > >>>> Dec 19 10:37:07 pbx daemon.warn miniupnpd[3936]: interface index not > matching 0 != 7 > >>>> Dec 19 10:37:07 pbx daemon.warn miniupnpd[3936]: interface index not > matching 0 != 7 > >>>> Dec 19 10:37:07 pbx daemon.warn miniupnpd[3936]: interface index not > matching 0 != 7 > >>>> Dec 19 10:37:08 pbx daemon.warn miniupnpd[3936]: interface index not > matching 0 != 7 > >>>> Dec 19 10:37:08 pbx daemon.warn miniupnpd[3936]: interface index not > matching 0 != 7 > >>>> Dec 19 10:37:18 pbx daemon.warn miniupnpd[3936]: interface index not > matching 0 != 7 > >>>> Dec 19 10:37:18 pbx daemon.warn miniupnpd[3936]: interface index not > matching 0 != 7 > >>>> Dec 19 10:37:28 pbx daemon.warn miniupnpd[3936]: interface index not > matching 0 != 7 > >>>> Dec 19 10:37:28 pbx daemon.warn miniupnpd[3936]: interface index not > matching 0 != 7 > >>>> Dec 19 10:37:32 pbx daemon.notice miniupnpd[3936]: shutting down > MiniUPnPd > >>>> Dec 19 10:37:33 pbx daemon.notice miniupnpd[27970]: HTTP listening on > port 5000 > >>>> Dec 19 10:37:33 pbx daemon.notice miniupnpd[27970]: Listening for > NAT-PMP/PCP traffic on port 5351 > >>>> Dec 19 10:37:36 pbx daemon.warn miniupnpd[27970]: interface index not > matching 0 != 7 > >>>> Dec 19 10:37:36 pbx daemon.warn miniupnpd[27970]: interface index not > matching 0 != 7 > >>>> Dec 19 10:37:36 pbx daemon.warn miniupnpd[27970]: interface index not > matching 0 != 7 > >>>> Dec 19 10:37:36 pbx daemon.warn miniupnpd[27970]: interface index not > matching 0 != 7 > >>>> Dec 19 10:37:36 pbx daemon.warn miniupnpd[27970]: interface index not > matching 0 != 7 > >>>> > >>>> > >>>> Totally flooded... I am going to have to revert to previous version. > >>>> Is anyone else seeing this? > >>>> > >>>> Cause is this update... > >>>> https://github.com/miniupnp/miniupnp/commit/ > 50d21a38d0719682f276173efd705ccbe78aca3d#diff- > daa89c3563f327bfe2e660cddc141ce7 > >>>> > >>>> Any ideas? The only thing I can think of is whether this has to do > with my use of a bridge on my internal lan. So "listening_ip" address is > on br0 interface rather than on a regular ethernet interface. > >>>> > >>>> Any thoughts? > >>>> David > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > |
|
From: Lonnie A. <li...@lo...> - 2017-12-20 00:33:25
|
Fixed in: https://github.com/astlinux-project/astlinux/commit/a5f4e362ee1e5c2f6b337e727ab62d42654526f1 On Dec 19, 2017, at 6:04 PM, Lonnie Abelbeck <li...@lo...> wrote: > Hi David, > > I figured it out ... long story short, if we define "listening_ip=" with the interface name rather than IP/NM > -- old > listening_ip=192.168.101.1/255.255.255.0 > -- new > listening_ip=eth1 > -- > No more warnings. > > The new interface matching code only works if "listening_ip=" is an interface name, otherwise it defaults to "0" as in "interface index not matching 0 != 7" > > Ref: https://github.com/miniupnp/miniupnp/blob/master/miniupnpd/miniupnpd.conf#L8 > -- > # LAN network interfaces IPs / networks > # There can be multiple listening IPs for SSDP traffic, in that case > # use multiple 'listening_ip=...' lines, one for each network interface. > # It can be IP address or network interface name (ie. "eth0") > # It is mandatory to use the network interface name in order to enable IPv6 > # HTTP is available on all interfaces. > # When MULTIPLE_EXTERNAL_IP is enabled, the external IP > # address associated with the subnet follows. For example: > # listening_ip=192.168.0.1/24 88.22.44.13 > #listening_ip=192.168.0.1/24 > #listening_ip=10.5.0.0/16 > #listening_ip=eth0 > -- > > BTW, I also tested VLAN's with listening_ip= and it works. > > While this is a regression in miniupnpd, the configuration fix is simple enough and would be needed if we every wanted to enable IPv6. > > I'll make the appropriate changes to our miniupnpd init.d script. > > Lonnie > > > On Dec 19, 2017, at 1:30 PM, David Kerr <Da...@Ke...> wrote: > >> For reference, here is my .conf file... >> >> ## Auto generated file. Do not edit. >> ext_ifname=eth0 >> listening_ip= >> 192.168.17.1/255.255.255.0 >> http_port=5000 >> enable_natpmp=yes >> enable_upnp=yes >> lease_file=/mnt/kd/upnp.leases >> bitrate_up=1000000 >> bitrate_down=15000000 >> secure_mode=yes >> min_lifetime=120 >> max_lifetime=86400 >> system_uptime=yes >> notify_interval=60 >> clean_ruleset_interval=600 >> uuid=b30041e7-8d39-4bc1-a554-8f6d1b51e50f >> serial=000001 >> friendly_name=AstLinux >> Router >> model_name=AstLinux Router >> model_description=astlinux-1.3-5e29e2 >> model_number=astlinux-1.3-5e29e2 >> allow 1024-65535 >> 192.168.17.0/24 >> 0-65535 >> deny 0-65535 >> 0.0.0.0/0 0-65535 >> >> >> >> On Tue, Dec 19, 2017 at 1:12 PM, Michael Keuter <li...@mk...> wrote: >> >>> Am 19.12.2017 um 18:57 schrieb Lonnie Abelbeck <li...@lo...>: >>> >>> David and Michael, >>> >>> Do you both have UPnP enabled alone or part of NAT-PMP/PCP ? >>> >>> It seems without UPnP the error does not occur. Such as with [ NAT-PMP/PCP only ] . >>> >>> Lonnie >> >> I have enabled "NAT-PMP/PCP & UPnP" on "1st LAN" on my router. >> >>> On Dec 19, 2017, at 10:05 AM, David Kerr <Da...@Ke...> wrote: >>> >>>> Since miniupnpd version was bumped this week my syslog is getting flooded with warning messages... >>>> >>>> Dec 19 10:37:07 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7 >>>> Dec 19 10:37:07 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7 >>>> Dec 19 10:37:07 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7 >>>> Dec 19 10:37:07 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7 >>>> Dec 19 10:37:08 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7 >>>> Dec 19 10:37:08 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7 >>>> Dec 19 10:37:18 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7 >>>> Dec 19 10:37:18 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7 >>>> Dec 19 10:37:28 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7 >>>> Dec 19 10:37:28 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7 >>>> Dec 19 10:37:32 pbx daemon.notice miniupnpd[3936]: shutting down MiniUPnPd >>>> Dec 19 10:37:33 pbx daemon.notice miniupnpd[27970]: HTTP listening on port 5000 >>>> Dec 19 10:37:33 pbx daemon.notice miniupnpd[27970]: Listening for NAT-PMP/PCP traffic on port 5351 >>>> Dec 19 10:37:36 pbx daemon.warn miniupnpd[27970]: interface index not matching 0 != 7 >>>> Dec 19 10:37:36 pbx daemon.warn miniupnpd[27970]: interface index not matching 0 != 7 >>>> Dec 19 10:37:36 pbx daemon.warn miniupnpd[27970]: interface index not matching 0 != 7 >>>> Dec 19 10:37:36 pbx daemon.warn miniupnpd[27970]: interface index not matching 0 != 7 >>>> Dec 19 10:37:36 pbx daemon.warn miniupnpd[27970]: interface index not matching 0 != 7 >>>> >>>> >>>> Totally flooded... I am going to have to revert to previous version. >>>> Is anyone else seeing this? >>>> >>>> Cause is this update... >>>> https://github.com/miniupnp/miniupnp/commit/50d21a38d0719682f276173efd705ccbe78aca3d#diff-daa89c3563f327bfe2e660cddc141ce7 >>>> >>>> Any ideas? The only thing I can think of is whether this has to do with my use of a bridge on my internal lan. So "listening_ip" address is on br0 interface rather than on a regular ethernet interface. >>>> >>>> Any thoughts? >>>> David |
|
From: Lonnie A. <li...@lo...> - 2017-12-20 00:04:41
|
Hi David, I figured it out ... long story short, if we define "listening_ip=" with the interface name rather than IP/NM -- old listening_ip=192.168.101.1/255.255.255.0 -- new listening_ip=eth1 -- No more warnings. The new interface matching code only works if "listening_ip=" is an interface name, otherwise it defaults to "0" as in "interface index not matching 0 != 7" Ref: https://github.com/miniupnp/miniupnp/blob/master/miniupnpd/miniupnpd.conf#L8 -- # LAN network interfaces IPs / networks # There can be multiple listening IPs for SSDP traffic, in that case # use multiple 'listening_ip=...' lines, one for each network interface. # It can be IP address or network interface name (ie. "eth0") # It is mandatory to use the network interface name in order to enable IPv6 # HTTP is available on all interfaces. # When MULTIPLE_EXTERNAL_IP is enabled, the external IP # address associated with the subnet follows. For example: # listening_ip=192.168.0.1/24 88.22.44.13 #listening_ip=192.168.0.1/24 #listening_ip=10.5.0.0/16 #listening_ip=eth0 -- BTW, I also tested VLAN's with listening_ip= and it works. While this is a regression in miniupnpd, the configuration fix is simple enough and would be needed if we every wanted to enable IPv6. I'll make the appropriate changes to our miniupnpd init.d script. Lonnie On Dec 19, 2017, at 1:30 PM, David Kerr <Da...@Ke...> wrote: > For reference, here is my .conf file... > > ## Auto generated file. Do not edit. > ext_ifname=eth0 > listening_ip= > 192.168.17.1/255.255.255.0 > http_port=5000 > enable_natpmp=yes > enable_upnp=yes > lease_file=/mnt/kd/upnp.leases > bitrate_up=1000000 > bitrate_down=15000000 > secure_mode=yes > min_lifetime=120 > max_lifetime=86400 > system_uptime=yes > notify_interval=60 > clean_ruleset_interval=600 > uuid=b30041e7-8d39-4bc1-a554-8f6d1b51e50f > serial=000001 > friendly_name=AstLinux > Router > model_name=AstLinux Router > model_description=astlinux-1.3-5e29e2 > model_number=astlinux-1.3-5e29e2 > allow 1024-65535 > 192.168.17.0/24 > 0-65535 > deny 0-65535 > 0.0.0.0/0 0-65535 > > > > On Tue, Dec 19, 2017 at 1:12 PM, Michael Keuter <li...@mk...> wrote: > > > Am 19.12.2017 um 18:57 schrieb Lonnie Abelbeck <li...@lo...>: > > > > David and Michael, > > > > Do you both have UPnP enabled alone or part of NAT-PMP/PCP ? > > > > It seems without UPnP the error does not occur. Such as with [ NAT-PMP/PCP only ] . > > > > Lonnie > > I have enabled "NAT-PMP/PCP & UPnP" on "1st LAN" on my router. > > > On Dec 19, 2017, at 10:05 AM, David Kerr <Da...@Ke...> wrote: > > > >> Since miniupnpd version was bumped this week my syslog is getting flooded with warning messages... > >> > >> Dec 19 10:37:07 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7 > >> Dec 19 10:37:07 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7 > >> Dec 19 10:37:07 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7 > >> Dec 19 10:37:07 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7 > >> Dec 19 10:37:08 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7 > >> Dec 19 10:37:08 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7 > >> Dec 19 10:37:18 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7 > >> Dec 19 10:37:18 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7 > >> Dec 19 10:37:28 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7 > >> Dec 19 10:37:28 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7 > >> Dec 19 10:37:32 pbx daemon.notice miniupnpd[3936]: shutting down MiniUPnPd > >> Dec 19 10:37:33 pbx daemon.notice miniupnpd[27970]: HTTP listening on port 5000 > >> Dec 19 10:37:33 pbx daemon.notice miniupnpd[27970]: Listening for NAT-PMP/PCP traffic on port 5351 > >> Dec 19 10:37:36 pbx daemon.warn miniupnpd[27970]: interface index not matching 0 != 7 > >> Dec 19 10:37:36 pbx daemon.warn miniupnpd[27970]: interface index not matching 0 != 7 > >> Dec 19 10:37:36 pbx daemon.warn miniupnpd[27970]: interface index not matching 0 != 7 > >> Dec 19 10:37:36 pbx daemon.warn miniupnpd[27970]: interface index not matching 0 != 7 > >> Dec 19 10:37:36 pbx daemon.warn miniupnpd[27970]: interface index not matching 0 != 7 > >> > >> > >> Totally flooded... I am going to have to revert to previous version. > >> Is anyone else seeing this? > >> > >> Cause is this update... > >> https://github.com/miniupnp/miniupnp/commit/50d21a38d0719682f276173efd705ccbe78aca3d#diff-daa89c3563f327bfe2e660cddc141ce7 > >> > >> Any ideas? The only thing I can think of is whether this has to do with my use of a bridge on my internal lan. So "listening_ip" address is on br0 interface rather than on a regular ethernet interface. > >> > >> Any thoughts? > >> David > > Michael > > http://www.mksolutions.info > > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > 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.
