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...> - 2019-07-01 21:26:53
|
Ahhh, so the Huawei supports the Qualcomm QMI protocol, interesting. So using qmi-network is how the wireless provider's APN settings are set. Truly a shame this usb_modeswitch nonsense is needed every time the USB is connected rather than setting it persistently in the device. Lonnie > On Jul 1, 2019, at 3:18 PM, Michael Knill <mic...@ip...> wrote: > > Hmm I think this answers my question: > > https://forum.openwrt.org/t/wwan-huawei-e8372/16564 > > Last post! > > Regards > Michael Knill > > On 2/7/19, 6:13 am, "Michael Knill" <mic...@ip...> wrote: > > Hi thanks Lonnie > > Hmm I thought that it does register as a network device. On OpenWRT it comes up as an Ethernet port and when you set up the device you set DHCP, IP Address, Firewall etc. just like a 4G router. > I wouldn't have thought you would be able to do that with a serial device that requires AT commands e.g. a modem. > > Anyway we may have a play at some stage and I wont bother you with this any more. > > Regards > Michael Knill > > On 1/7/19, 10:28 pm, "Lonnie Abelbeck" <li...@lo...> wrote: > > I found this reference for the "Huawei E8372" device: > > https://gist.github.com/guseppiguliano/614055d0bc260f5ea305d71439a03790 > > This looks like the worst case scenario. > 1) The USB device defaults to a USB mass storage device > 2) The usb_modeswitch program is needed to "switch" it to data mode > 3) Then the device operates as a /dev/ttyUSB0 serial device > 4) Finally the PPP protocol is used to establish a network connection using the serial device. > > Now you understand why we like the Netgear LB1120 as a standalone network device :-) (I know, not AU compatible). > > I don't think your "Huawei E8372" is USB_NET_CDCETHER compatible. > > It would be nice if a USB 4G/LTE dongle would simply register as a network device, but how would the 4G/LTE provider's specific configuration be set ? This is normally done via the PPP setup with old style AT commands. Possibly a small built-in web server on the USB device could be locally reachable via the network for such configuration. > > Lonnie > > > >> On Jul 1, 2019, at 6:58 AM, Michael Knill <mic...@ip...> wrote: >> >> I'm reading that it may use the 'cdc-ether' driver. >> https://forums.whirlpool.net.au/archive/2755550 >> >> But I'm a bit out of my depth here. >> >> Regards >> Michael Knill >> >> On 1/7/19, 9:38 pm, "Michael Keuter" <li...@mk...> wrote: >> >> >>> Am 01.07.2019 um 12:57 schrieb Michael Knill <mic...@ip...>: >>> >>> Sorry for dragging this up again but... >>> I have purchased 20 of Huawei E8372h-608 USB LTE modem/routers which work fine in OpenWRT and also just plugging into my Mac. In OpenWRT it registers as an Ethernet port and provides an address via DHCP from the router. As you mentioned below it shouldn't be too hard to support this architecture in Astlinux as its just a USB Ethernet port (like virtually all laptops now). >>> It just seems so pointless installing another Linux based router (OpenWRT) to support this device. >> >> Hi Michael, >> >> can you figure out which driver is used in OpenWRT (or in another Linux). Maybe we just need to enable another driver (which is currently disabled) in AstLinux. >> The Linux kernel version could also be interesting. >> >> lsmod >> lsusb (-v) >> >> I found this: >> https://trick77.com/setting-up-huawei-e3276-150-4g-lte-usb-modem-ubuntu-server-desktop/ >> >> There is a driver "cdc_ether" mentioned. >> In "make linux-menuconfig/Device Drivers/Network Device Support/USB Network Adapters" there are a few enabled, but not "CDC Ethernet Support". >> >> But it can be, that all the additional USB-modeswitch stuff is needed as well (it means the device first appears as an USB CD-ROM!), which is a pain in … >> We tried that years ago. >> >>> I'm just wondering how hard it would be to get this working in Astlinux? I realise I will probably need to roll my own. >>> >>> Regards >>> Michael Knill >>> >>> From: Michael Knill <mic...@ip...> >>> Reply-To: AstLinux Developers Mailing List <ast...@li...> >>> Date: Saturday, 29 December 2018 at 9:19 pm >>> To: AstLinux Developers Mailing List <ast...@li...> >>> Subject: Re: [Astlinux-devel] 4G/LTE support by Astlinux on PC Engines APU >>> >>> Hi thanks Lonnie >>> >>> I think I will keep with the current preferred solution. Had to ask though! >>> >>> Regards >>> Michael Knill >>> >>> From: lists <li...@lo...> >>> Reply-To: AstLinux Developers Mailing List <ast...@li...> >>> Date: Friday, 28 December 2018 at 1:39 pm >>> To: AstLinux Developers Mailing List <ast...@li...> >>> Subject: Re: [Astlinux-devel] 4G/LTE support by Astlinux on PC Engines APU >>> >>> Looks like they register as USB serial devices that require the old school AT command settings followed by a PPP session. Not something I’m personally interested in digging through ATM. >>> >>> Does this approach save much money ? The Netgear LB1120 vs. a mini pcie card and antenna ... plus you have to locate the APU3 for good signal. >>> >>> >>> >>> BTW, there appear a few of these modems register as usb ethernet devices, that would be far more straight-forward to support, not sure if any are mini-pcie or not ... of course cell carrier support is also needed. >>> >>> Lonnie >>> >>> >>> On Dec 27, 2018, at 8:06 PM, Michael Knill <mic...@ip...> wrote: >>> >>>> I suspect that the best option is the APU3 which is actually targeted for 3G/LTE support with dual SIM slots and antenna connections in the case. >>>> https://www.pcengines.ch/apu3c2.htm >>>> https://pcengines.ch/howto.htm#3G >>>> >>>> Working solutions using Voyage Linux and PFSense: >>>> https://txlab.wordpress.com/2017/05/19/two-lte-modems-with-pc-engines-apu3/ >>>> https://teklager.se/en/knowledge-base/apu-4g-lte-modem-configuration/ >>>> >>>> Would be awesome to get working. >>>> >>>> Regards >>>> Michael Knill >>>> >>>> On 28/12/18, 12:19 pm, "Lonnie Abelbeck" <li...@lo...> wrote: >>>> >>>> Hi Michael, >>>> >>>> >>>> >>>>> How hard would it be to add 4G support into Astlinux? >>>> >>>> For the special case of the PC Engines APU2, I'm not sure what form of miniPCI express card works and what kernel support it would require. >>>> >>>> Do you have a reference ? >>>> >>>> Lonnie >>>> >>>>> On Dec 27, 2018, at 7:20 PM, Michael Knill <mic...@ip...> wrote: >>>>> >>>>> Hi Devs >>>>> >>>>> I know this has been sort of discussed before however I intend on pretty much providing 4G backup on all my new installs and would love an all in one Astlinux solution. >>>>> Yes I can get separate devices but consider a pretty standard install: >>>>> • 1 x VDSL Modem >>>>> • 1 x Astlinux Appliance >>>>> • 1 x WAP >>>>> • 1 x 4G router >>>>> >>>>> Its all a bit overkill when you can buy a single device to do all the above (from a network perspective obviously). >>>>> I could maybe combine the 4G and WAP functionality on a single device if I could do something funky with VLAN’s to split the functionality. >>>>> >>>>> How hard would it be to add 4G support into Astlinux? >>>>> >>>>> Regards >>>>> Michael Knill >> >> Michael >> >> http://www.mksolutions.info >> >> >> >> >> >> _______________________________________________ >> Astlinux-devel mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-devel >> >> >> >> _______________________________________________ >> Astlinux-devel mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Michael K. <li...@mk...> - 2019-07-01 20:19:59
|
> Am 01.07.2019 um 22:12 schrieb Michael Knill <mic...@ip...>: > > Hi thanks Lonnie > > Hmm I thought that it does register as a network device. On OpenWRT it comes up as an Ethernet port and when you set up the device you set DHCP, IP Address, Firewall etc. just like a 4G router. That's possibly because OpenWRT has installed usb_modeswitch and there are some udev rules related to that USB vendor ID. Check out "lsusb" on OpenWRT and on AstLinux, I guess they will show different device IDs. > I wouldn't have thought you would be able to do that with a serial device that requires AT commands e.g. a modem. No, that can be different parts of this multi-purpose USB device, USB-serial-port and USB-network-adapter :-). > Anyway we may have a play at some stage and I wont bother you with this any more. > > Regards > Michael Knill > > On 1/7/19, 10:28 pm, "Lonnie Abelbeck" <li...@lo...> wrote: > > I found this reference for the "Huawei E8372" device: > > https://gist.github.com/guseppiguliano/614055d0bc260f5ea305d71439a03790 > > This looks like the worst case scenario. > 1) The USB device defaults to a USB mass storage device > 2) The usb_modeswitch program is needed to "switch" it to data mode > 3) Then the device operates as a /dev/ttyUSB0 serial device > 4) Finally the PPP protocol is used to establish a network connection using the serial device. > > Now you understand why we like the Netgear LB1120 as a standalone network device :-) (I know, not AU compatible). > > I don't think your "Huawei E8372" is USB_NET_CDCETHER compatible. > > It would be nice if a USB 4G/LTE dongle would simply register as a network device, but how would the 4G/LTE provider's specific configuration be set ? This is normally done via the PPP setup with old style AT commands. Possibly a small built-in web server on the USB device could be locally reachable via the network for such configuration. > > Lonnie > > > >> On Jul 1, 2019, at 6:58 AM, Michael Knill <mic...@ip...> wrote: >> >> I'm reading that it may use the 'cdc-ether' driver. >> https://forums.whirlpool.net.au/archive/2755550 >> >> But I'm a bit out of my depth here. >> >> Regards >> Michael Knill >> >> On 1/7/19, 9:38 pm, "Michael Keuter" <li...@mk...> wrote: >> >> >>> Am 01.07.2019 um 12:57 schrieb Michael Knill <mic...@ip...>: >>> >>> Sorry for dragging this up again but... >>> I have purchased 20 of Huawei E8372h-608 USB LTE modem/routers which work fine in OpenWRT and also just plugging into my Mac. In OpenWRT it registers as an Ethernet port and provides an address via DHCP from the router. As you mentioned below it shouldn't be too hard to support this architecture in Astlinux as its just a USB Ethernet port (like virtually all laptops now). >>> It just seems so pointless installing another Linux based router (OpenWRT) to support this device. >> >> Hi Michael, >> >> can you figure out which driver is used in OpenWRT (or in another Linux). Maybe we just need to enable another driver (which is currently disabled) in AstLinux. >> The Linux kernel version could also be interesting. >> >> lsmod >> lsusb (-v) >> >> I found this: >> https://trick77.com/setting-up-huawei-e3276-150-4g-lte-usb-modem-ubuntu-server-desktop/ >> >> There is a driver "cdc_ether" mentioned. >> In "make linux-menuconfig/Device Drivers/Network Device Support/USB Network Adapters" there are a few enabled, but not "CDC Ethernet Support". >> >> But it can be, that all the additional USB-modeswitch stuff is needed as well (it means the device first appears as an USB CD-ROM!), which is a pain in … >> We tried that years ago. >> >>> I'm just wondering how hard it would be to get this working in Astlinux? I realise I will probably need to roll my own. >>> >>> Regards >>> Michael Knill >>> >>> From: Michael Knill <mic...@ip...> >>> Reply-To: AstLinux Developers Mailing List <ast...@li...> >>> Date: Saturday, 29 December 2018 at 9:19 pm >>> To: AstLinux Developers Mailing List <ast...@li...> >>> Subject: Re: [Astlinux-devel] 4G/LTE support by Astlinux on PC Engines APU >>> >>> Hi thanks Lonnie >>> >>> I think I will keep with the current preferred solution. Had to ask though! >>> >>> Regards >>> Michael Knill >>> >>> From: lists <li...@lo...> >>> Reply-To: AstLinux Developers Mailing List <ast...@li...> >>> Date: Friday, 28 December 2018 at 1:39 pm >>> To: AstLinux Developers Mailing List <ast...@li...> >>> Subject: Re: [Astlinux-devel] 4G/LTE support by Astlinux on PC Engines APU >>> >>> Looks like they register as USB serial devices that require the old school AT command settings followed by a PPP session. Not something I’m personally interested in digging through ATM. >>> >>> Does this approach save much money ? The Netgear LB1120 vs. a mini pcie card and antenna ... plus you have to locate the APU3 for good signal. >>> >>> >>> >>> BTW, there appear a few of these modems register as usb ethernet devices, that would be far more straight-forward to support, not sure if any are mini-pcie or not ... of course cell carrier support is also needed. >>> >>> Lonnie >>> >>> >>> On Dec 27, 2018, at 8:06 PM, Michael Knill <mic...@ip...> wrote: >>> >>>> I suspect that the best option is the APU3 which is actually targeted for 3G/LTE support with dual SIM slots and antenna connections in the case. >>>> https://www.pcengines.ch/apu3c2.htm >>>> https://pcengines.ch/howto.htm#3G >>>> >>>> Working solutions using Voyage Linux and PFSense: >>>> https://txlab.wordpress.com/2017/05/19/two-lte-modems-with-pc-engines-apu3/ >>>> https://teklager.se/en/knowledge-base/apu-4g-lte-modem-configuration/ >>>> >>>> Would be awesome to get working. >>>> >>>> Regards >>>> Michael Knill >>>> >>>> On 28/12/18, 12:19 pm, "Lonnie Abelbeck" <li...@lo...> wrote: >>>> >>>> Hi Michael, >>>> >>>> >>>> >>>>> How hard would it be to add 4G support into Astlinux? >>>> >>>> For the special case of the PC Engines APU2, I'm not sure what form of miniPCI express card works and what kernel support it would require. >>>> >>>> Do you have a reference ? >>>> >>>> Lonnie >>>> >>>>> On Dec 27, 2018, at 7:20 PM, Michael Knill <mic...@ip...> wrote: >>>>> >>>>> Hi Devs >>>>> >>>>> I know this has been sort of discussed before however I intend on pretty much providing 4G backup on all my new installs and would love an all in one Astlinux solution. >>>>> Yes I can get separate devices but consider a pretty standard install: >>>>> • 1 x VDSL Modem >>>>> • 1 x Astlinux Appliance >>>>> • 1 x WAP >>>>> • 1 x 4G router >>>>> >>>>> Its all a bit overkill when you can buy a single device to do all the above (from a network perspective obviously). >>>>> I could maybe combine the 4G and WAP functionality on a single device if I could do something funky with VLAN’s to split the functionality. >>>>> >>>>> How hard would it be to add 4G support into Astlinux? >>>>> >>>>> Regards >>>>> Michael Knill Michael http://www.mksolutions.info |
|
From: Michael K. <mic...@ip...> - 2019-07-01 20:18:14
|
Hmm I think this answers my question: https://forum.openwrt.org/t/wwan-huawei-e8372/16564 Last post! Regards Michael Knill On 2/7/19, 6:13 am, "Michael Knill" <mic...@ip...> wrote: Hi thanks Lonnie Hmm I thought that it does register as a network device. On OpenWRT it comes up as an Ethernet port and when you set up the device you set DHCP, IP Address, Firewall etc. just like a 4G router. I wouldn't have thought you would be able to do that with a serial device that requires AT commands e.g. a modem. Anyway we may have a play at some stage and I wont bother you with this any more. Regards Michael Knill On 1/7/19, 10:28 pm, "Lonnie Abelbeck" <li...@lo...> wrote: I found this reference for the "Huawei E8372" device: https://gist.github.com/guseppiguliano/614055d0bc260f5ea305d71439a03790 This looks like the worst case scenario. 1) The USB device defaults to a USB mass storage device 2) The usb_modeswitch program is needed to "switch" it to data mode 3) Then the device operates as a /dev/ttyUSB0 serial device 4) Finally the PPP protocol is used to establish a network connection using the serial device. Now you understand why we like the Netgear LB1120 as a standalone network device :-) (I know, not AU compatible). I don't think your "Huawei E8372" is USB_NET_CDCETHER compatible. It would be nice if a USB 4G/LTE dongle would simply register as a network device, but how would the 4G/LTE provider's specific configuration be set ? This is normally done via the PPP setup with old style AT commands. Possibly a small built-in web server on the USB device could be locally reachable via the network for such configuration. Lonnie > On Jul 1, 2019, at 6:58 AM, Michael Knill <mic...@ip...> wrote: > > I'm reading that it may use the 'cdc-ether' driver. > https://forums.whirlpool.net.au/archive/2755550 > > But I'm a bit out of my depth here. > > Regards > Michael Knill > > On 1/7/19, 9:38 pm, "Michael Keuter" <li...@mk...> wrote: > > >> Am 01.07.2019 um 12:57 schrieb Michael Knill <mic...@ip...>: >> >> Sorry for dragging this up again but... >> I have purchased 20 of Huawei E8372h-608 USB LTE modem/routers which work fine in OpenWRT and also just plugging into my Mac. In OpenWRT it registers as an Ethernet port and provides an address via DHCP from the router. As you mentioned below it shouldn't be too hard to support this architecture in Astlinux as its just a USB Ethernet port (like virtually all laptops now). >> It just seems so pointless installing another Linux based router (OpenWRT) to support this device. > > Hi Michael, > > can you figure out which driver is used in OpenWRT (or in another Linux). Maybe we just need to enable another driver (which is currently disabled) in AstLinux. > The Linux kernel version could also be interesting. > > lsmod > lsusb (-v) > > I found this: > https://trick77.com/setting-up-huawei-e3276-150-4g-lte-usb-modem-ubuntu-server-desktop/ > > There is a driver "cdc_ether" mentioned. > In "make linux-menuconfig/Device Drivers/Network Device Support/USB Network Adapters" there are a few enabled, but not "CDC Ethernet Support". > > But it can be, that all the additional USB-modeswitch stuff is needed as well (it means the device first appears as an USB CD-ROM!), which is a pain in … > We tried that years ago. > >> I'm just wondering how hard it would be to get this working in Astlinux? I realise I will probably need to roll my own. >> >> Regards >> Michael Knill >> >> From: Michael Knill <mic...@ip...> >> Reply-To: AstLinux Developers Mailing List <ast...@li...> >> Date: Saturday, 29 December 2018 at 9:19 pm >> To: AstLinux Developers Mailing List <ast...@li...> >> Subject: Re: [Astlinux-devel] 4G/LTE support by Astlinux on PC Engines APU >> >> Hi thanks Lonnie >> >> I think I will keep with the current preferred solution. Had to ask though! >> >> Regards >> Michael Knill >> >> From: lists <li...@lo...> >> Reply-To: AstLinux Developers Mailing List <ast...@li...> >> Date: Friday, 28 December 2018 at 1:39 pm >> To: AstLinux Developers Mailing List <ast...@li...> >> Subject: Re: [Astlinux-devel] 4G/LTE support by Astlinux on PC Engines APU >> >> Looks like they register as USB serial devices that require the old school AT command settings followed by a PPP session. Not something I’m personally interested in digging through ATM. >> >> Does this approach save much money ? The Netgear LB1120 vs. a mini pcie card and antenna ... plus you have to locate the APU3 for good signal. >> >> >> >> BTW, there appear a few of these modems register as usb ethernet devices, that would be far more straight-forward to support, not sure if any are mini-pcie or not ... of course cell carrier support is also needed. >> >> Lonnie >> >> >> On Dec 27, 2018, at 8:06 PM, Michael Knill <mic...@ip...> wrote: >> >>> I suspect that the best option is the APU3 which is actually targeted for 3G/LTE support with dual SIM slots and antenna connections in the case. >>> https://www.pcengines.ch/apu3c2.htm >>> https://pcengines.ch/howto.htm#3G >>> >>> Working solutions using Voyage Linux and PFSense: >>> https://txlab.wordpress.com/2017/05/19/two-lte-modems-with-pc-engines-apu3/ >>> https://teklager.se/en/knowledge-base/apu-4g-lte-modem-configuration/ >>> >>> Would be awesome to get working. >>> >>> Regards >>> Michael Knill >>> >>> On 28/12/18, 12:19 pm, "Lonnie Abelbeck" <li...@lo...> wrote: >>> >>> Hi Michael, >>> >>> >>> >>>> How hard would it be to add 4G support into Astlinux? >>> >>> For the special case of the PC Engines APU2, I'm not sure what form of miniPCI express card works and what kernel support it would require. >>> >>> Do you have a reference ? >>> >>> Lonnie >>> >>>> On Dec 27, 2018, at 7:20 PM, Michael Knill <mic...@ip...> wrote: >>>> >>>> Hi Devs >>>> >>>> I know this has been sort of discussed before however I intend on pretty much providing 4G backup on all my new installs and would love an all in one Astlinux solution. >>>> Yes I can get separate devices but consider a pretty standard install: >>>> • 1 x VDSL Modem >>>> • 1 x Astlinux Appliance >>>> • 1 x WAP >>>> • 1 x 4G router >>>> >>>> Its all a bit overkill when you can buy a single device to do all the above (from a network perspective obviously). >>>> I could maybe combine the 4G and WAP functionality on a single device if I could do something funky with VLAN’s to split the functionality. >>>> >>>> How hard would it be to add 4G support into Astlinux? >>>> >>>> Regards >>>> Michael Knill > > Michael > > http://www.mksolutions.info > > > > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel _______________________________________________ Astlinux-devel mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-devel _______________________________________________ Astlinux-devel mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Michael K. <mic...@ip...> - 2019-07-01 20:12:44
|
Hi thanks Lonnie
Hmm I thought that it does register as a network device. On OpenWRT it comes up as an Ethernet port and when you set up the device you set DHCP, IP Address, Firewall etc. just like a 4G router.
I wouldn't have thought you would be able to do that with a serial device that requires AT commands e.g. a modem.
Anyway we may have a play at some stage and I wont bother you with this any more.
Regards
Michael Knill
On 1/7/19, 10:28 pm, "Lonnie Abelbeck" <li...@lo...> wrote:
I found this reference for the "Huawei E8372" device:
https://gist.github.com/guseppiguliano/614055d0bc260f5ea305d71439a03790
This looks like the worst case scenario.
1) The USB device defaults to a USB mass storage device
2) The usb_modeswitch program is needed to "switch" it to data mode
3) Then the device operates as a /dev/ttyUSB0 serial device
4) Finally the PPP protocol is used to establish a network connection using the serial device.
Now you understand why we like the Netgear LB1120 as a standalone network device :-) (I know, not AU compatible).
I don't think your "Huawei E8372" is USB_NET_CDCETHER compatible.
It would be nice if a USB 4G/LTE dongle would simply register as a network device, but how would the 4G/LTE provider's specific configuration be set ? This is normally done via the PPP setup with old style AT commands. Possibly a small built-in web server on the USB device could be locally reachable via the network for such configuration.
Lonnie
> On Jul 1, 2019, at 6:58 AM, Michael Knill <mic...@ip...> wrote:
>
> I'm reading that it may use the 'cdc-ether' driver.
> https://forums.whirlpool.net.au/archive/2755550
>
> But I'm a bit out of my depth here.
>
> Regards
> Michael Knill
>
> On 1/7/19, 9:38 pm, "Michael Keuter" <li...@mk...> wrote:
>
>
>> Am 01.07.2019 um 12:57 schrieb Michael Knill <mic...@ip...>:
>>
>> Sorry for dragging this up again but...
>> I have purchased 20 of Huawei E8372h-608 USB LTE modem/routers which work fine in OpenWRT and also just plugging into my Mac. In OpenWRT it registers as an Ethernet port and provides an address via DHCP from the router. As you mentioned below it shouldn't be too hard to support this architecture in Astlinux as its just a USB Ethernet port (like virtually all laptops now).
>> It just seems so pointless installing another Linux based router (OpenWRT) to support this device.
>
> Hi Michael,
>
> can you figure out which driver is used in OpenWRT (or in another Linux). Maybe we just need to enable another driver (which is currently disabled) in AstLinux.
> The Linux kernel version could also be interesting.
>
> lsmod
> lsusb (-v)
>
> I found this:
> https://trick77.com/setting-up-huawei-e3276-150-4g-lte-usb-modem-ubuntu-server-desktop/
>
> There is a driver "cdc_ether" mentioned.
> In "make linux-menuconfig/Device Drivers/Network Device Support/USB Network Adapters" there are a few enabled, but not "CDC Ethernet Support".
>
> But it can be, that all the additional USB-modeswitch stuff is needed as well (it means the device first appears as an USB CD-ROM!), which is a pain in …
> We tried that years ago.
>
>> I'm just wondering how hard it would be to get this working in Astlinux? I realise I will probably need to roll my own.
>>
>> Regards
>> Michael Knill
>>
>> From: Michael Knill <mic...@ip...>
>> Reply-To: AstLinux Developers Mailing List <ast...@li...>
>> Date: Saturday, 29 December 2018 at 9:19 pm
>> To: AstLinux Developers Mailing List <ast...@li...>
>> Subject: Re: [Astlinux-devel] 4G/LTE support by Astlinux on PC Engines APU
>>
>> Hi thanks Lonnie
>>
>> I think I will keep with the current preferred solution. Had to ask though!
>>
>> Regards
>> Michael Knill
>>
>> From: lists <li...@lo...>
>> Reply-To: AstLinux Developers Mailing List <ast...@li...>
>> Date: Friday, 28 December 2018 at 1:39 pm
>> To: AstLinux Developers Mailing List <ast...@li...>
>> Subject: Re: [Astlinux-devel] 4G/LTE support by Astlinux on PC Engines APU
>>
>> Looks like they register as USB serial devices that require the old school AT command settings followed by a PPP session. Not something I’m personally interested in digging through ATM.
>>
>> Does this approach save much money ? The Netgear LB1120 vs. a mini pcie card and antenna ... plus you have to locate the APU3 for good signal.
>>
>>
>>
>> BTW, there appear a few of these modems register as usb ethernet devices, that would be far more straight-forward to support, not sure if any are mini-pcie or not ... of course cell carrier support is also needed.
>>
>> Lonnie
>>
>>
>> On Dec 27, 2018, at 8:06 PM, Michael Knill <mic...@ip...> wrote:
>>
>>> I suspect that the best option is the APU3 which is actually targeted for 3G/LTE support with dual SIM slots and antenna connections in the case.
>>> https://www.pcengines.ch/apu3c2.htm
>>> https://pcengines.ch/howto.htm#3G
>>>
>>> Working solutions using Voyage Linux and PFSense:
>>> https://txlab.wordpress.com/2017/05/19/two-lte-modems-with-pc-engines-apu3/
>>> https://teklager.se/en/knowledge-base/apu-4g-lte-modem-configuration/
>>>
>>> Would be awesome to get working.
>>>
>>> Regards
>>> Michael Knill
>>>
>>> On 28/12/18, 12:19 pm, "Lonnie Abelbeck" <li...@lo...> wrote:
>>>
>>> Hi Michael,
>>>
>>>
>>>
>>>> How hard would it be to add 4G support into Astlinux?
>>>
>>> For the special case of the PC Engines APU2, I'm not sure what form of miniPCI express card works and what kernel support it would require.
>>>
>>> Do you have a reference ?
>>>
>>> Lonnie
>>>
>>>> On Dec 27, 2018, at 7:20 PM, Michael Knill <mic...@ip...> wrote:
>>>>
>>>> Hi Devs
>>>>
>>>> I know this has been sort of discussed before however I intend on pretty much providing 4G backup on all my new installs and would love an all in one Astlinux solution.
>>>> Yes I can get separate devices but consider a pretty standard install:
>>>> • 1 x VDSL Modem
>>>> • 1 x Astlinux Appliance
>>>> • 1 x WAP
>>>> • 1 x 4G router
>>>>
>>>> Its all a bit overkill when you can buy a single device to do all the above (from a network perspective obviously).
>>>> I could maybe combine the 4G and WAP functionality on a single device if I could do something funky with VLAN’s to split the functionality.
>>>>
>>>> How hard would it be to add 4G support into Astlinux?
>>>>
>>>> Regards
>>>> Michael Knill
>
> Michael
>
> http://www.mksolutions.info
>
>
>
>
>
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>
>
>
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
_______________________________________________
Astlinux-devel mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-devel
|
|
From: Michael K. <mic...@ip...> - 2019-07-01 20:11:17
|
Thanks Michael
This is what I have installed in OpenWRT:
kmod-usb-core
kmod-usb-net
kmod-usb-net-cdc-ether
kmod-usb-net-cdc-mbim
kmod-usb-net-cdc-ncm
kmod-usb-net-huawei-cdc-ncm
kmod-usb-net-qmi-wwan
kmod-usb-net-rndis
kmod-usb-serial
kmod-usb-serial-option
kmod-usb-serial-wwan
kmod-usb-wdm
libusb-1.0
usb-modeswitch
I suspect I don't need them all but I think your are correct about usb-modeswitch.
I also wonder if I need CONFIG_USB_NET_HUAWEI_CDC_NCM?
Anyway we may have a play but I wont bother you with this anymore.
Thanks again for your help.
Regards
Michael Knill
On 1/7/19, 10:15 pm, "Michael Keuter" <li...@mk...> wrote:
> Am 01.07.2019 um 14:11 schrieb Michael Knill <mic...@ip...>:
>
> Thanks Michael. I will give it a try!
>
> Regards
> Michael Knill
But it can be that, despite the driver available, the device appears as a CD-ROM (or USB mass storage) device. Then USB-modeswitch is needed.
Or that there are more drivers needed. Look at:
https://github.com/astlinux-project/astlinux/blob/master/project/astlinux/genx86_64/linux-smp.config
Under "# USB Network Adapters".
> On 1/7/19, 10:08 pm, "Michael Keuter" <li...@mk...> wrote:
>
>
>> Am 01.07.2019 um 13:58 schrieb Michael Knill <mic...@ip...>:
>>
>> I'm reading that it may use the 'cdc-ether' driver.
>> https://forums.whirlpool.net.au/archive/2755550
>>
>> But I'm a bit out of my depth here.
>>
>> Regards
>> Michael Knill
>
> If you can build AstLinux for yourself, just edit:
> "project/astlinux/genx86_64/linux-smp.config" and replace "# CONFIG_USB_NET_CDCETHER is not set" with "CONFIG_USB_NET_CDCETHER=m" and rebuild.
>
>>
>> On 1/7/19, 9:38 pm, "Michael Keuter" <li...@mk...> wrote:
>>
>>
>>> Am 01.07.2019 um 12:57 schrieb Michael Knill <mic...@ip...>:
>>>
>>> Sorry for dragging this up again but...
>>> I have purchased 20 of Huawei E8372h-608 USB LTE modem/routers which work fine in OpenWRT and also just plugging into my Mac. In OpenWRT it registers as an Ethernet port and provides an address via DHCP from the router. As you mentioned below it shouldn't be too hard to support this architecture in Astlinux as its just a USB Ethernet port (like virtually all laptops now).
>>> It just seems so pointless installing another Linux based router (OpenWRT) to support this device.
>>
>> Hi Michael,
>>
>> can you figure out which driver is used in OpenWRT (or in another Linux). Maybe we just need to enable another driver (which is currently disabled) in AstLinux.
>> The Linux kernel version could also be interesting.
>>
>> lsmod
>> lsusb (-v)
>>
>> I found this:
>> https://trick77.com/setting-up-huawei-e3276-150-4g-lte-usb-modem-ubuntu-server-desktop/
>>
>> There is a driver "cdc_ether" mentioned.
>> In "make linux-menuconfig/Device Drivers/Network Device Support/USB Network Adapters" there are a few enabled, but not "CDC Ethernet Support".
>>
>> But it can be, that all the additional USB-modeswitch stuff is needed as well (it means the device first appears as an USB CD-ROM!), which is a pain in …
>> We tried that years ago.
>>
>>> I'm just wondering how hard it would be to get this working in Astlinux? I realise I will probably need to roll my own.
>>>
>>> Regards
>>> Michael Knill
>>>
>>> From: Michael Knill <mic...@ip...>
>>> Reply-To: AstLinux Developers Mailing List <ast...@li...>
>>> Date: Saturday, 29 December 2018 at 9:19 pm
>>> To: AstLinux Developers Mailing List <ast...@li...>
>>> Subject: Re: [Astlinux-devel] 4G/LTE support by Astlinux on PC Engines APU
>>>
>>> Hi thanks Lonnie
>>>
>>> I think I will keep with the current preferred solution. Had to ask though!
>>>
>>> Regards
>>> Michael Knill
>>>
>>> From: lists <li...@lo...>
>>> Reply-To: AstLinux Developers Mailing List <ast...@li...>
>>> Date: Friday, 28 December 2018 at 1:39 pm
>>> To: AstLinux Developers Mailing List <ast...@li...>
>>> Subject: Re: [Astlinux-devel] 4G/LTE support by Astlinux on PC Engines APU
>>>
>>> Looks like they register as USB serial devices that require the old school AT command settings followed by a PPP session. Not something I’m personally interested in digging through ATM.
>>>
>>> Does this approach save much money ? The Netgear LB1120 vs. a mini pcie card and antenna ... plus you have to locate the APU3 for good signal.
>>>
>>>
>>>
>>> BTW, there appear a few of these modems register as usb ethernet devices, that would be far more straight-forward to support, not sure if any are mini-pcie or not ... of course cell carrier support is also needed.
>>>
>>> Lonnie
>>>
>>>
>>> On Dec 27, 2018, at 8:06 PM, Michael Knill <mic...@ip...> wrote:
>>>
>>>> I suspect that the best option is the APU3 which is actually targeted for 3G/LTE support with dual SIM slots and antenna connections in the case.
>>>> https://www.pcengines.ch/apu3c2.htm
>>>> https://pcengines.ch/howto.htm#3G
>>>>
>>>> Working solutions using Voyage Linux and PFSense:
>>>> https://txlab.wordpress.com/2017/05/19/two-lte-modems-with-pc-engines-apu3/
>>>> https://teklager.se/en/knowledge-base/apu-4g-lte-modem-configuration/
>>>>
>>>> Would be awesome to get working.
>>>>
>>>> Regards
>>>> Michael Knill
>>>>
>>>> On 28/12/18, 12:19 pm, "Lonnie Abelbeck" <li...@lo...> wrote:
>>>>
>>>> Hi Michael,
>>>>
>>>>
>>>>
>>>>> How hard would it be to add 4G support into Astlinux?
>>>>
>>>> For the special case of the PC Engines APU2, I'm not sure what form of miniPCI express card works and what kernel support it would require.
>>>>
>>>> Do you have a reference ?
>>>>
>>>> Lonnie
>>>>
>>>>> On Dec 27, 2018, at 7:20 PM, Michael Knill <mic...@ip...> wrote:
>>>>>
>>>>> Hi Devs
>>>>>
>>>>> I know this has been sort of discussed before however I intend on pretty much providing 4G backup on all my new installs and would love an all in one Astlinux solution.
>>>>> Yes I can get separate devices but consider a pretty standard install:
>>>>> • 1 x VDSL Modem
>>>>> • 1 x Astlinux Appliance
>>>>> • 1 x WAP
>>>>> • 1 x 4G router
>>>>>
>>>>> Its all a bit overkill when you can buy a single device to do all the above (from a network perspective obviously).
>>>>> I could maybe combine the 4G and WAP functionality on a single device if I could do something funky with VLAN’s to split the functionality.
>>>>>
>>>>> How hard would it be to add 4G support into Astlinux?
>>>>>
>>>>> Regards
>>>>> Michael Knill
Michael
http://www.mksolutions.info
_______________________________________________
Astlinux-devel mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-devel
|
|
From: Lonnie A. <li...@lo...> - 2019-07-01 12:27:54
|
I found this reference for the "Huawei E8372" device: https://gist.github.com/guseppiguliano/614055d0bc260f5ea305d71439a03790 This looks like the worst case scenario. 1) The USB device defaults to a USB mass storage device 2) The usb_modeswitch program is needed to "switch" it to data mode 3) Then the device operates as a /dev/ttyUSB0 serial device 4) Finally the PPP protocol is used to establish a network connection using the serial device. Now you understand why we like the Netgear LB1120 as a standalone network device :-) (I know, not AU compatible). I don't think your "Huawei E8372" is USB_NET_CDCETHER compatible. It would be nice if a USB 4G/LTE dongle would simply register as a network device, but how would the 4G/LTE provider's specific configuration be set ? This is normally done via the PPP setup with old style AT commands. Possibly a small built-in web server on the USB device could be locally reachable via the network for such configuration. Lonnie > On Jul 1, 2019, at 6:58 AM, Michael Knill <mic...@ip...> wrote: > > I'm reading that it may use the 'cdc-ether' driver. > https://forums.whirlpool.net.au/archive/2755550 > > But I'm a bit out of my depth here. > > Regards > Michael Knill > > On 1/7/19, 9:38 pm, "Michael Keuter" <li...@mk...> wrote: > > >> Am 01.07.2019 um 12:57 schrieb Michael Knill <mic...@ip...>: >> >> Sorry for dragging this up again but... >> I have purchased 20 of Huawei E8372h-608 USB LTE modem/routers which work fine in OpenWRT and also just plugging into my Mac. In OpenWRT it registers as an Ethernet port and provides an address via DHCP from the router. As you mentioned below it shouldn't be too hard to support this architecture in Astlinux as its just a USB Ethernet port (like virtually all laptops now). >> It just seems so pointless installing another Linux based router (OpenWRT) to support this device. > > Hi Michael, > > can you figure out which driver is used in OpenWRT (or in another Linux). Maybe we just need to enable another driver (which is currently disabled) in AstLinux. > The Linux kernel version could also be interesting. > > lsmod > lsusb (-v) > > I found this: > https://trick77.com/setting-up-huawei-e3276-150-4g-lte-usb-modem-ubuntu-server-desktop/ > > There is a driver "cdc_ether" mentioned. > In "make linux-menuconfig/Device Drivers/Network Device Support/USB Network Adapters" there are a few enabled, but not "CDC Ethernet Support". > > But it can be, that all the additional USB-modeswitch stuff is needed as well (it means the device first appears as an USB CD-ROM!), which is a pain in … > We tried that years ago. > >> I'm just wondering how hard it would be to get this working in Astlinux? I realise I will probably need to roll my own. >> >> Regards >> Michael Knill >> >> From: Michael Knill <mic...@ip...> >> Reply-To: AstLinux Developers Mailing List <ast...@li...> >> Date: Saturday, 29 December 2018 at 9:19 pm >> To: AstLinux Developers Mailing List <ast...@li...> >> Subject: Re: [Astlinux-devel] 4G/LTE support by Astlinux on PC Engines APU >> >> Hi thanks Lonnie >> >> I think I will keep with the current preferred solution. Had to ask though! >> >> Regards >> Michael Knill >> >> From: lists <li...@lo...> >> Reply-To: AstLinux Developers Mailing List <ast...@li...> >> Date: Friday, 28 December 2018 at 1:39 pm >> To: AstLinux Developers Mailing List <ast...@li...> >> Subject: Re: [Astlinux-devel] 4G/LTE support by Astlinux on PC Engines APU >> >> Looks like they register as USB serial devices that require the old school AT command settings followed by a PPP session. Not something I’m personally interested in digging through ATM. >> >> Does this approach save much money ? The Netgear LB1120 vs. a mini pcie card and antenna ... plus you have to locate the APU3 for good signal. >> >> >> >> BTW, there appear a few of these modems register as usb ethernet devices, that would be far more straight-forward to support, not sure if any are mini-pcie or not ... of course cell carrier support is also needed. >> >> Lonnie >> >> >> On Dec 27, 2018, at 8:06 PM, Michael Knill <mic...@ip...> wrote: >> >>> I suspect that the best option is the APU3 which is actually targeted for 3G/LTE support with dual SIM slots and antenna connections in the case. >>> https://www.pcengines.ch/apu3c2.htm >>> https://pcengines.ch/howto.htm#3G >>> >>> Working solutions using Voyage Linux and PFSense: >>> https://txlab.wordpress.com/2017/05/19/two-lte-modems-with-pc-engines-apu3/ >>> https://teklager.se/en/knowledge-base/apu-4g-lte-modem-configuration/ >>> >>> Would be awesome to get working. >>> >>> Regards >>> Michael Knill >>> >>> On 28/12/18, 12:19 pm, "Lonnie Abelbeck" <li...@lo...> wrote: >>> >>> Hi Michael, >>> >>> >>> >>>> How hard would it be to add 4G support into Astlinux? >>> >>> For the special case of the PC Engines APU2, I'm not sure what form of miniPCI express card works and what kernel support it would require. >>> >>> Do you have a reference ? >>> >>> Lonnie >>> >>>> On Dec 27, 2018, at 7:20 PM, Michael Knill <mic...@ip...> wrote: >>>> >>>> Hi Devs >>>> >>>> I know this has been sort of discussed before however I intend on pretty much providing 4G backup on all my new installs and would love an all in one Astlinux solution. >>>> Yes I can get separate devices but consider a pretty standard install: >>>> • 1 x VDSL Modem >>>> • 1 x Astlinux Appliance >>>> • 1 x WAP >>>> • 1 x 4G router >>>> >>>> Its all a bit overkill when you can buy a single device to do all the above (from a network perspective obviously). >>>> I could maybe combine the 4G and WAP functionality on a single device if I could do something funky with VLAN’s to split the functionality. >>>> >>>> How hard would it be to add 4G support into Astlinux? >>>> >>>> Regards >>>> Michael Knill > > Michael > > http://www.mksolutions.info > > > > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Michael K. <li...@mk...> - 2019-07-01 12:15:46
|
> Am 01.07.2019 um 14:11 schrieb Michael Knill <mic...@ip...>: > > Thanks Michael. I will give it a try! > > Regards > Michael Knill But it can be that, despite the driver available, the device appears as a CD-ROM (or USB mass storage) device. Then USB-modeswitch is needed. Or that there are more drivers needed. Look at: https://github.com/astlinux-project/astlinux/blob/master/project/astlinux/genx86_64/linux-smp.config Under "# USB Network Adapters". > On 1/7/19, 10:08 pm, "Michael Keuter" <li...@mk...> wrote: > > >> Am 01.07.2019 um 13:58 schrieb Michael Knill <mic...@ip...>: >> >> I'm reading that it may use the 'cdc-ether' driver. >> https://forums.whirlpool.net.au/archive/2755550 >> >> But I'm a bit out of my depth here. >> >> Regards >> Michael Knill > > If you can build AstLinux for yourself, just edit: > "project/astlinux/genx86_64/linux-smp.config" and replace "# CONFIG_USB_NET_CDCETHER is not set" with "CONFIG_USB_NET_CDCETHER=m" and rebuild. > >> >> On 1/7/19, 9:38 pm, "Michael Keuter" <li...@mk...> wrote: >> >> >>> Am 01.07.2019 um 12:57 schrieb Michael Knill <mic...@ip...>: >>> >>> Sorry for dragging this up again but... >>> I have purchased 20 of Huawei E8372h-608 USB LTE modem/routers which work fine in OpenWRT and also just plugging into my Mac. In OpenWRT it registers as an Ethernet port and provides an address via DHCP from the router. As you mentioned below it shouldn't be too hard to support this architecture in Astlinux as its just a USB Ethernet port (like virtually all laptops now). >>> It just seems so pointless installing another Linux based router (OpenWRT) to support this device. >> >> Hi Michael, >> >> can you figure out which driver is used in OpenWRT (or in another Linux). Maybe we just need to enable another driver (which is currently disabled) in AstLinux. >> The Linux kernel version could also be interesting. >> >> lsmod >> lsusb (-v) >> >> I found this: >> https://trick77.com/setting-up-huawei-e3276-150-4g-lte-usb-modem-ubuntu-server-desktop/ >> >> There is a driver "cdc_ether" mentioned. >> In "make linux-menuconfig/Device Drivers/Network Device Support/USB Network Adapters" there are a few enabled, but not "CDC Ethernet Support". >> >> But it can be, that all the additional USB-modeswitch stuff is needed as well (it means the device first appears as an USB CD-ROM!), which is a pain in … >> We tried that years ago. >> >>> I'm just wondering how hard it would be to get this working in Astlinux? I realise I will probably need to roll my own. >>> >>> Regards >>> Michael Knill >>> >>> From: Michael Knill <mic...@ip...> >>> Reply-To: AstLinux Developers Mailing List <ast...@li...> >>> Date: Saturday, 29 December 2018 at 9:19 pm >>> To: AstLinux Developers Mailing List <ast...@li...> >>> Subject: Re: [Astlinux-devel] 4G/LTE support by Astlinux on PC Engines APU >>> >>> Hi thanks Lonnie >>> >>> I think I will keep with the current preferred solution. Had to ask though! >>> >>> Regards >>> Michael Knill >>> >>> From: lists <li...@lo...> >>> Reply-To: AstLinux Developers Mailing List <ast...@li...> >>> Date: Friday, 28 December 2018 at 1:39 pm >>> To: AstLinux Developers Mailing List <ast...@li...> >>> Subject: Re: [Astlinux-devel] 4G/LTE support by Astlinux on PC Engines APU >>> >>> Looks like they register as USB serial devices that require the old school AT command settings followed by a PPP session. Not something I’m personally interested in digging through ATM. >>> >>> Does this approach save much money ? The Netgear LB1120 vs. a mini pcie card and antenna ... plus you have to locate the APU3 for good signal. >>> >>> >>> >>> BTW, there appear a few of these modems register as usb ethernet devices, that would be far more straight-forward to support, not sure if any are mini-pcie or not ... of course cell carrier support is also needed. >>> >>> Lonnie >>> >>> >>> On Dec 27, 2018, at 8:06 PM, Michael Knill <mic...@ip...> wrote: >>> >>>> I suspect that the best option is the APU3 which is actually targeted for 3G/LTE support with dual SIM slots and antenna connections in the case. >>>> https://www.pcengines.ch/apu3c2.htm >>>> https://pcengines.ch/howto.htm#3G >>>> >>>> Working solutions using Voyage Linux and PFSense: >>>> https://txlab.wordpress.com/2017/05/19/two-lte-modems-with-pc-engines-apu3/ >>>> https://teklager.se/en/knowledge-base/apu-4g-lte-modem-configuration/ >>>> >>>> Would be awesome to get working. >>>> >>>> Regards >>>> Michael Knill >>>> >>>> On 28/12/18, 12:19 pm, "Lonnie Abelbeck" <li...@lo...> wrote: >>>> >>>> Hi Michael, >>>> >>>> >>>> >>>>> How hard would it be to add 4G support into Astlinux? >>>> >>>> For the special case of the PC Engines APU2, I'm not sure what form of miniPCI express card works and what kernel support it would require. >>>> >>>> Do you have a reference ? >>>> >>>> Lonnie >>>> >>>>> On Dec 27, 2018, at 7:20 PM, Michael Knill <mic...@ip...> wrote: >>>>> >>>>> Hi Devs >>>>> >>>>> I know this has been sort of discussed before however I intend on pretty much providing 4G backup on all my new installs and would love an all in one Astlinux solution. >>>>> Yes I can get separate devices but consider a pretty standard install: >>>>> • 1 x VDSL Modem >>>>> • 1 x Astlinux Appliance >>>>> • 1 x WAP >>>>> • 1 x 4G router >>>>> >>>>> Its all a bit overkill when you can buy a single device to do all the above (from a network perspective obviously). >>>>> I could maybe combine the 4G and WAP functionality on a single device if I could do something funky with VLAN’s to split the functionality. >>>>> >>>>> How hard would it be to add 4G support into Astlinux? >>>>> >>>>> Regards >>>>> Michael Knill Michael http://www.mksolutions.info |
|
From: Michael K. <mic...@ip...> - 2019-07-01 12:11:15
|
Thanks Michael. I will give it a try!
Regards
Michael Knill
On 1/7/19, 10:08 pm, "Michael Keuter" <li...@mk...> wrote:
> Am 01.07.2019 um 13:58 schrieb Michael Knill <mic...@ip...>:
>
> I'm reading that it may use the 'cdc-ether' driver.
> https://forums.whirlpool.net.au/archive/2755550
>
> But I'm a bit out of my depth here.
>
> Regards
> Michael Knill
If you can build AstLinux for yourself, just edit:
"project/astlinux/genx86_64/linux-smp.config" and replace "# CONFIG_USB_NET_CDCETHER is not set" with "CONFIG_USB_NET_CDCETHER=m" and rebuild.
>
> On 1/7/19, 9:38 pm, "Michael Keuter" <li...@mk...> wrote:
>
>
>> Am 01.07.2019 um 12:57 schrieb Michael Knill <mic...@ip...>:
>>
>> Sorry for dragging this up again but...
>> I have purchased 20 of Huawei E8372h-608 USB LTE modem/routers which work fine in OpenWRT and also just plugging into my Mac. In OpenWRT it registers as an Ethernet port and provides an address via DHCP from the router. As you mentioned below it shouldn't be too hard to support this architecture in Astlinux as its just a USB Ethernet port (like virtually all laptops now).
>> It just seems so pointless installing another Linux based router (OpenWRT) to support this device.
>
> Hi Michael,
>
> can you figure out which driver is used in OpenWRT (or in another Linux). Maybe we just need to enable another driver (which is currently disabled) in AstLinux.
> The Linux kernel version could also be interesting.
>
> lsmod
> lsusb (-v)
>
> I found this:
> https://trick77.com/setting-up-huawei-e3276-150-4g-lte-usb-modem-ubuntu-server-desktop/
>
> There is a driver "cdc_ether" mentioned.
> In "make linux-menuconfig/Device Drivers/Network Device Support/USB Network Adapters" there are a few enabled, but not "CDC Ethernet Support".
>
> But it can be, that all the additional USB-modeswitch stuff is needed as well (it means the device first appears as an USB CD-ROM!), which is a pain in …
> We tried that years ago.
>
>> I'm just wondering how hard it would be to get this working in Astlinux? I realise I will probably need to roll my own.
>>
>> Regards
>> Michael Knill
>>
>> From: Michael Knill <mic...@ip...>
>> Reply-To: AstLinux Developers Mailing List <ast...@li...>
>> Date: Saturday, 29 December 2018 at 9:19 pm
>> To: AstLinux Developers Mailing List <ast...@li...>
>> Subject: Re: [Astlinux-devel] 4G/LTE support by Astlinux on PC Engines APU
>>
>> Hi thanks Lonnie
>>
>> I think I will keep with the current preferred solution. Had to ask though!
>>
>> Regards
>> Michael Knill
>>
>> From: lists <li...@lo...>
>> Reply-To: AstLinux Developers Mailing List <ast...@li...>
>> Date: Friday, 28 December 2018 at 1:39 pm
>> To: AstLinux Developers Mailing List <ast...@li...>
>> Subject: Re: [Astlinux-devel] 4G/LTE support by Astlinux on PC Engines APU
>>
>> Looks like they register as USB serial devices that require the old school AT command settings followed by a PPP session. Not something I’m personally interested in digging through ATM.
>>
>> Does this approach save much money ? The Netgear LB1120 vs. a mini pcie card and antenna ... plus you have to locate the APU3 for good signal.
>>
>>
>>
>> BTW, there appear a few of these modems register as usb ethernet devices, that would be far more straight-forward to support, not sure if any are mini-pcie or not ... of course cell carrier support is also needed.
>>
>> Lonnie
>>
>>
>> On Dec 27, 2018, at 8:06 PM, Michael Knill <mic...@ip...> wrote:
>>
>>> I suspect that the best option is the APU3 which is actually targeted for 3G/LTE support with dual SIM slots and antenna connections in the case.
>>> https://www.pcengines.ch/apu3c2.htm
>>> https://pcengines.ch/howto.htm#3G
>>>
>>> Working solutions using Voyage Linux and PFSense:
>>> https://txlab.wordpress.com/2017/05/19/two-lte-modems-with-pc-engines-apu3/
>>> https://teklager.se/en/knowledge-base/apu-4g-lte-modem-configuration/
>>>
>>> Would be awesome to get working.
>>>
>>> Regards
>>> Michael Knill
>>>
>>> On 28/12/18, 12:19 pm, "Lonnie Abelbeck" <li...@lo...> wrote:
>>>
>>> Hi Michael,
>>>
>>>
>>>
>>>> How hard would it be to add 4G support into Astlinux?
>>>
>>> For the special case of the PC Engines APU2, I'm not sure what form of miniPCI express card works and what kernel support it would require.
>>>
>>> Do you have a reference ?
>>>
>>> Lonnie
>>>
>>>> On Dec 27, 2018, at 7:20 PM, Michael Knill <mic...@ip...> wrote:
>>>>
>>>> Hi Devs
>>>>
>>>> I know this has been sort of discussed before however I intend on pretty much providing 4G backup on all my new installs and would love an all in one Astlinux solution.
>>>> Yes I can get separate devices but consider a pretty standard install:
>>>> • 1 x VDSL Modem
>>>> • 1 x Astlinux Appliance
>>>> • 1 x WAP
>>>> • 1 x 4G router
>>>>
>>>> Its all a bit overkill when you can buy a single device to do all the above (from a network perspective obviously).
>>>> I could maybe combine the 4G and WAP functionality on a single device if I could do something funky with VLAN’s to split the functionality.
>>>>
>>>> How hard would it be to add 4G support into Astlinux?
>>>>
>>>> Regards
>>>> Michael Knill
Michael
http://www.mksolutions.info
_______________________________________________
Astlinux-devel mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-devel
|
|
From: Michael K. <li...@mk...> - 2019-07-01 12:08:17
|
> Am 01.07.2019 um 13:58 schrieb Michael Knill <mic...@ip...>: > > I'm reading that it may use the 'cdc-ether' driver. > https://forums.whirlpool.net.au/archive/2755550 > > But I'm a bit out of my depth here. > > Regards > Michael Knill If you can build AstLinux for yourself, just edit: "project/astlinux/genx86_64/linux-smp.config" and replace "# CONFIG_USB_NET_CDCETHER is not set" with "CONFIG_USB_NET_CDCETHER=m" and rebuild. > > On 1/7/19, 9:38 pm, "Michael Keuter" <li...@mk...> wrote: > > >> Am 01.07.2019 um 12:57 schrieb Michael Knill <mic...@ip...>: >> >> Sorry for dragging this up again but... >> I have purchased 20 of Huawei E8372h-608 USB LTE modem/routers which work fine in OpenWRT and also just plugging into my Mac. In OpenWRT it registers as an Ethernet port and provides an address via DHCP from the router. As you mentioned below it shouldn't be too hard to support this architecture in Astlinux as its just a USB Ethernet port (like virtually all laptops now). >> It just seems so pointless installing another Linux based router (OpenWRT) to support this device. > > Hi Michael, > > can you figure out which driver is used in OpenWRT (or in another Linux). Maybe we just need to enable another driver (which is currently disabled) in AstLinux. > The Linux kernel version could also be interesting. > > lsmod > lsusb (-v) > > I found this: > https://trick77.com/setting-up-huawei-e3276-150-4g-lte-usb-modem-ubuntu-server-desktop/ > > There is a driver "cdc_ether" mentioned. > In "make linux-menuconfig/Device Drivers/Network Device Support/USB Network Adapters" there are a few enabled, but not "CDC Ethernet Support". > > But it can be, that all the additional USB-modeswitch stuff is needed as well (it means the device first appears as an USB CD-ROM!), which is a pain in … > We tried that years ago. > >> I'm just wondering how hard it would be to get this working in Astlinux? I realise I will probably need to roll my own. >> >> Regards >> Michael Knill >> >> From: Michael Knill <mic...@ip...> >> Reply-To: AstLinux Developers Mailing List <ast...@li...> >> Date: Saturday, 29 December 2018 at 9:19 pm >> To: AstLinux Developers Mailing List <ast...@li...> >> Subject: Re: [Astlinux-devel] 4G/LTE support by Astlinux on PC Engines APU >> >> Hi thanks Lonnie >> >> I think I will keep with the current preferred solution. Had to ask though! >> >> Regards >> Michael Knill >> >> From: lists <li...@lo...> >> Reply-To: AstLinux Developers Mailing List <ast...@li...> >> Date: Friday, 28 December 2018 at 1:39 pm >> To: AstLinux Developers Mailing List <ast...@li...> >> Subject: Re: [Astlinux-devel] 4G/LTE support by Astlinux on PC Engines APU >> >> Looks like they register as USB serial devices that require the old school AT command settings followed by a PPP session. Not something I’m personally interested in digging through ATM. >> >> Does this approach save much money ? The Netgear LB1120 vs. a mini pcie card and antenna ... plus you have to locate the APU3 for good signal. >> >> >> >> BTW, there appear a few of these modems register as usb ethernet devices, that would be far more straight-forward to support, not sure if any are mini-pcie or not ... of course cell carrier support is also needed. >> >> Lonnie >> >> >> On Dec 27, 2018, at 8:06 PM, Michael Knill <mic...@ip...> wrote: >> >>> I suspect that the best option is the APU3 which is actually targeted for 3G/LTE support with dual SIM slots and antenna connections in the case. >>> https://www.pcengines.ch/apu3c2.htm >>> https://pcengines.ch/howto.htm#3G >>> >>> Working solutions using Voyage Linux and PFSense: >>> https://txlab.wordpress.com/2017/05/19/two-lte-modems-with-pc-engines-apu3/ >>> https://teklager.se/en/knowledge-base/apu-4g-lte-modem-configuration/ >>> >>> Would be awesome to get working. >>> >>> Regards >>> Michael Knill >>> >>> On 28/12/18, 12:19 pm, "Lonnie Abelbeck" <li...@lo...> wrote: >>> >>> Hi Michael, >>> >>> >>> >>>> How hard would it be to add 4G support into Astlinux? >>> >>> For the special case of the PC Engines APU2, I'm not sure what form of miniPCI express card works and what kernel support it would require. >>> >>> Do you have a reference ? >>> >>> Lonnie >>> >>>> On Dec 27, 2018, at 7:20 PM, Michael Knill <mic...@ip...> wrote: >>>> >>>> Hi Devs >>>> >>>> I know this has been sort of discussed before however I intend on pretty much providing 4G backup on all my new installs and would love an all in one Astlinux solution. >>>> Yes I can get separate devices but consider a pretty standard install: >>>> • 1 x VDSL Modem >>>> • 1 x Astlinux Appliance >>>> • 1 x WAP >>>> • 1 x 4G router >>>> >>>> Its all a bit overkill when you can buy a single device to do all the above (from a network perspective obviously). >>>> I could maybe combine the 4G and WAP functionality on a single device if I could do something funky with VLAN’s to split the functionality. >>>> >>>> How hard would it be to add 4G support into Astlinux? >>>> >>>> Regards >>>> Michael Knill Michael http://www.mksolutions.info |
|
From: Michael K. <mic...@ip...> - 2019-07-01 11:58:53
|
I'm reading that it may use the 'cdc-ether' driver. https://forums.whirlpool.net.au/archive/2755550 But I'm a bit out of my depth here. Regards Michael Knill On 1/7/19, 9:38 pm, "Michael Keuter" <li...@mk...> wrote: > Am 01.07.2019 um 12:57 schrieb Michael Knill <mic...@ip...>: > > Sorry for dragging this up again but... > I have purchased 20 of Huawei E8372h-608 USB LTE modem/routers which work fine in OpenWRT and also just plugging into my Mac. In OpenWRT it registers as an Ethernet port and provides an address via DHCP from the router. As you mentioned below it shouldn't be too hard to support this architecture in Astlinux as its just a USB Ethernet port (like virtually all laptops now). > It just seems so pointless installing another Linux based router (OpenWRT) to support this device. Hi Michael, can you figure out which driver is used in OpenWRT (or in another Linux). Maybe we just need to enable another driver (which is currently disabled) in AstLinux. The Linux kernel version could also be interesting. lsmod lsusb (-v) I found this: https://trick77.com/setting-up-huawei-e3276-150-4g-lte-usb-modem-ubuntu-server-desktop/ There is a driver "cdc_ether" mentioned. In "make linux-menuconfig/Device Drivers/Network Device Support/USB Network Adapters" there are a few enabled, but not "CDC Ethernet Support". But it can be, that all the additional USB-modeswitch stuff is needed as well (it means the device first appears as an USB CD-ROM!), which is a pain in … We tried that years ago. > I'm just wondering how hard it would be to get this working in Astlinux? I realise I will probably need to roll my own. > > Regards > Michael Knill > > From: Michael Knill <mic...@ip...> > Reply-To: AstLinux Developers Mailing List <ast...@li...> > Date: Saturday, 29 December 2018 at 9:19 pm > To: AstLinux Developers Mailing List <ast...@li...> > Subject: Re: [Astlinux-devel] 4G/LTE support by Astlinux on PC Engines APU > > Hi thanks Lonnie > > I think I will keep with the current preferred solution. Had to ask though! > > Regards > Michael Knill > > From: lists <li...@lo...> > Reply-To: AstLinux Developers Mailing List <ast...@li...> > Date: Friday, 28 December 2018 at 1:39 pm > To: AstLinux Developers Mailing List <ast...@li...> > Subject: Re: [Astlinux-devel] 4G/LTE support by Astlinux on PC Engines APU > > Looks like they register as USB serial devices that require the old school AT command settings followed by a PPP session. Not something I’m personally interested in digging through ATM. > > Does this approach save much money ? The Netgear LB1120 vs. a mini pcie card and antenna ... plus you have to locate the APU3 for good signal. > > > > BTW, there appear a few of these modems register as usb ethernet devices, that would be far more straight-forward to support, not sure if any are mini-pcie or not ... of course cell carrier support is also needed. > > Lonnie > > > On Dec 27, 2018, at 8:06 PM, Michael Knill <mic...@ip...> wrote: > >> I suspect that the best option is the APU3 which is actually targeted for 3G/LTE support with dual SIM slots and antenna connections in the case. >> https://www.pcengines.ch/apu3c2.htm >> https://pcengines.ch/howto.htm#3G >> >> Working solutions using Voyage Linux and PFSense: >> https://txlab.wordpress.com/2017/05/19/two-lte-modems-with-pc-engines-apu3/ >> https://teklager.se/en/knowledge-base/apu-4g-lte-modem-configuration/ >> >> Would be awesome to get working. >> >> Regards >> Michael Knill >> >> On 28/12/18, 12:19 pm, "Lonnie Abelbeck" <li...@lo...> wrote: >> >> Hi Michael, >> >> >> >>> How hard would it be to add 4G support into Astlinux? >> >> For the special case of the PC Engines APU2, I'm not sure what form of miniPCI express card works and what kernel support it would require. >> >> Do you have a reference ? >> >> Lonnie >> >>> On Dec 27, 2018, at 7:20 PM, Michael Knill <mic...@ip...> wrote: >>> >>> Hi Devs >>> >>> I know this has been sort of discussed before however I intend on pretty much providing 4G backup on all my new installs and would love an all in one Astlinux solution. >>> Yes I can get separate devices but consider a pretty standard install: >>> • 1 x VDSL Modem >>> • 1 x Astlinux Appliance >>> • 1 x WAP >>> • 1 x 4G router >>> >>> Its all a bit overkill when you can buy a single device to do all the above (from a network perspective obviously). >>> I could maybe combine the 4G and WAP functionality on a single device if I could do something funky with VLAN’s to split the functionality. >>> >>> How hard would it be to add 4G support into Astlinux? >>> >>> Regards >>> Michael Knill Michael http://www.mksolutions.info _______________________________________________ Astlinux-devel mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Michael K. <li...@mk...> - 2019-07-01 11:38:11
|
> Am 01.07.2019 um 12:57 schrieb Michael Knill <mic...@ip...>: > > Sorry for dragging this up again but... > I have purchased 20 of Huawei E8372h-608 USB LTE modem/routers which work fine in OpenWRT and also just plugging into my Mac. In OpenWRT it registers as an Ethernet port and provides an address via DHCP from the router. As you mentioned below it shouldn't be too hard to support this architecture in Astlinux as its just a USB Ethernet port (like virtually all laptops now). > It just seems so pointless installing another Linux based router (OpenWRT) to support this device. Hi Michael, can you figure out which driver is used in OpenWRT (or in another Linux). Maybe we just need to enable another driver (which is currently disabled) in AstLinux. The Linux kernel version could also be interesting. lsmod lsusb (-v) I found this: https://trick77.com/setting-up-huawei-e3276-150-4g-lte-usb-modem-ubuntu-server-desktop/ There is a driver "cdc_ether" mentioned. In "make linux-menuconfig/Device Drivers/Network Device Support/USB Network Adapters" there are a few enabled, but not "CDC Ethernet Support". But it can be, that all the additional USB-modeswitch stuff is needed as well (it means the device first appears as an USB CD-ROM!), which is a pain in … We tried that years ago. > I'm just wondering how hard it would be to get this working in Astlinux? I realise I will probably need to roll my own. > > Regards > Michael Knill > > From: Michael Knill <mic...@ip...> > Reply-To: AstLinux Developers Mailing List <ast...@li...> > Date: Saturday, 29 December 2018 at 9:19 pm > To: AstLinux Developers Mailing List <ast...@li...> > Subject: Re: [Astlinux-devel] 4G/LTE support by Astlinux on PC Engines APU > > Hi thanks Lonnie > > I think I will keep with the current preferred solution. Had to ask though! > > Regards > Michael Knill > > From: lists <li...@lo...> > Reply-To: AstLinux Developers Mailing List <ast...@li...> > Date: Friday, 28 December 2018 at 1:39 pm > To: AstLinux Developers Mailing List <ast...@li...> > Subject: Re: [Astlinux-devel] 4G/LTE support by Astlinux on PC Engines APU > > Looks like they register as USB serial devices that require the old school AT command settings followed by a PPP session. Not something I’m personally interested in digging through ATM. > > Does this approach save much money ? The Netgear LB1120 vs. a mini pcie card and antenna ... plus you have to locate the APU3 for good signal. > > > > BTW, there appear a few of these modems register as usb ethernet devices, that would be far more straight-forward to support, not sure if any are mini-pcie or not ... of course cell carrier support is also needed. > > Lonnie > > > On Dec 27, 2018, at 8:06 PM, Michael Knill <mic...@ip...> wrote: > >> I suspect that the best option is the APU3 which is actually targeted for 3G/LTE support with dual SIM slots and antenna connections in the case. >> https://www.pcengines.ch/apu3c2.htm >> https://pcengines.ch/howto.htm#3G >> >> Working solutions using Voyage Linux and PFSense: >> https://txlab.wordpress.com/2017/05/19/two-lte-modems-with-pc-engines-apu3/ >> https://teklager.se/en/knowledge-base/apu-4g-lte-modem-configuration/ >> >> Would be awesome to get working. >> >> Regards >> Michael Knill >> >> On 28/12/18, 12:19 pm, "Lonnie Abelbeck" <li...@lo...> wrote: >> >> Hi Michael, >> >> >> >>> How hard would it be to add 4G support into Astlinux? >> >> For the special case of the PC Engines APU2, I'm not sure what form of miniPCI express card works and what kernel support it would require. >> >> Do you have a reference ? >> >> Lonnie >> >>> On Dec 27, 2018, at 7:20 PM, Michael Knill <mic...@ip...> wrote: >>> >>> Hi Devs >>> >>> I know this has been sort of discussed before however I intend on pretty much providing 4G backup on all my new installs and would love an all in one Astlinux solution. >>> Yes I can get separate devices but consider a pretty standard install: >>> • 1 x VDSL Modem >>> • 1 x Astlinux Appliance >>> • 1 x WAP >>> • 1 x 4G router >>> >>> Its all a bit overkill when you can buy a single device to do all the above (from a network perspective obviously). >>> I could maybe combine the 4G and WAP functionality on a single device if I could do something funky with VLAN’s to split the functionality. >>> >>> How hard would it be to add 4G support into Astlinux? >>> >>> Regards >>> Michael Knill Michael http://www.mksolutions.info |
|
From: Michael K. <mic...@ip...> - 2019-07-01 10:57:18
|
Sorry for dragging this up again but... I have purchased 20 of Huawei E8372h-608 USB LTE modem/routers which work fine in OpenWRT and also just plugging into my Mac. In OpenWRT it registers as an Ethernet port and provides an address via DHCP from the router. As you mentioned below it shouldn't be too hard to support this architecture in Astlinux as its just a USB Ethernet port (like virtually all laptops now). It just seems so pointless installing another Linux based router (OpenWRT) to support this device. I'm just wondering how hard it would be to get this working in Astlinux? I realise I will probably need to roll my own. Regards Michael Knill From: Michael Knill <mic...@ip...> Reply-To: AstLinux Developers Mailing List <ast...@li...> Date: Saturday, 29 December 2018 at 9:19 pm To: AstLinux Developers Mailing List <ast...@li...> Subject: Re: [Astlinux-devel] 4G/LTE support by Astlinux on PC Engines APU Hi thanks Lonnie I think I will keep with the current preferred solution. Had to ask though! Regards Michael Knill From: lists <li...@lo...> Reply-To: AstLinux Developers Mailing List <ast...@li...> Date: Friday, 28 December 2018 at 1:39 pm To: AstLinux Developers Mailing List <ast...@li...> Subject: Re: [Astlinux-devel] 4G/LTE support by Astlinux on PC Engines APU Looks like they register as USB serial devices that require the old school AT command settings followed by a PPP session. Not something I’m personally interested in digging through ATM. Does this approach save much money ? The Netgear LB1120 vs. a mini pcie card and antenna ... plus you have to locate the APU3 for good signal. BTW, there appear a few of these modems register as usb ethernet devices, that would be far more straight-forward to support, not sure if any are mini-pcie or not ... of course cell carrier support is also needed. Lonnie On Dec 27, 2018, at 8:06 PM, Michael Knill <mic...@ip...<mailto:mic...@ip...>> wrote: I suspect that the best option is the APU3 which is actually targeted for 3G/LTE support with dual SIM slots and antenna connections in the case. https://www.pcengines.ch/apu3c2.htm https://pcengines.ch/howto.htm#3G Working solutions using Voyage Linux and PFSense: https://txlab.wordpress.com/2017/05/19/two-lte-modems-with-pc-engines-apu3/ https://teklager.se/en/knowledge-base/apu-4g-lte-modem-configuration/ Would be awesome to get working. Regards Michael Knill On 28/12/18, 12:19 pm, "Lonnie Abelbeck" <li...@lo...<mailto:li...@lo...>> wrote: Hi Michael, How hard would it be to add 4G support into Astlinux? For the special case of the PC Engines APU2, I'm not sure what form of miniPCI express card works and what kernel support it would require. Do you have a reference ? Lonnie On Dec 27, 2018, at 7:20 PM, Michael Knill <mic...@ip...<mailto:mic...@ip...>> wrote: Hi Devs I know this has been sort of discussed before however I intend on pretty much providing 4G backup on all my new installs and would love an all in one Astlinux solution. Yes I can get separate devices but consider a pretty standard install: • 1 x VDSL Modem • 1 x Astlinux Appliance • 1 x WAP • 1 x 4G router Its all a bit overkill when you can buy a single device to do all the above (from a network perspective obviously). I could maybe combine the 4G and WAP functionality on a single device if I could do something funky with VLAN’s to split the functionality. How hard would it be to add 4G support into Astlinux? Regards Michael Knill _______________________________________________ Astlinux-devel mailing list Ast...@li...<mailto:Ast...@li...> https://lists.sourceforge.net/lists/listinfo/astlinux-devel _______________________________________________ Astlinux-devel mailing list Ast...@li...<mailto:Ast...@li...> https://lists.sourceforge.net/lists/listinfo/astlinux-devel _______________________________________________ Astlinux-devel mailing list Ast...@li...<mailto:Ast...@li...> https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Michael K. <li...@mk...> - 2019-06-30 17:34:55
|
> Am 30.06.2019 um 18:38 schrieb Bill Lewis <wr...@gm...>: > > I created a .bashrc for root, logged back in and it didn't work. > Then when I rebooted, the file was deleted. > > I changed /etc/profile, and changes there don't see to affect > root either. I'm coming in through ssh. > > Were can I put these things for the root user? > > <<< > # don't put duplicate lines or lines starting with space in the history. > # See bash(1) for more options > HISTCONTROL=ignoreboth > > # append to the history file, don't overwrite it > shopt -s histappend > > # for setting history length see HISTSIZE and HISTFILESIZE in bash(1) > HISTSIZE=1000 > HISTFILESIZE=2000 > >>> > > Thanks, > Bill That is because "/root" is on temporary storage by default. But you ca create "/mnt/kd/root", copy over the stuff from your root user and reboot. Then it will be permanent. Michael http://www.mksolutions.info |
|
From: Bill L. <wr...@gm...> - 2019-06-30 16:38:37
|
I created a .bashrc for root, logged back in and it didn't work. Then when I rebooted, the file was deleted. I changed /etc/profile, and changes there don't see to affect root either. I'm coming in through ssh. Were can I put these things for the root user? <<< # don't put duplicate lines or lines starting with space in the history. # See bash(1) for more options HISTCONTROL=ignoreboth # append to the history file, don't overwrite it shopt -s histappend # for setting history length see HISTSIZE and HISTFILESIZE in bash(1) HISTSIZE=1000 HISTFILESIZE=2000 >>> Thanks, Bill |
|
From: Bill L. <wr...@gm...> - 2019-06-30 16:34:36
|
On 6/21/2019 2:10 PM, Lonnie Abelbeck wrote: > > >> On Jun 21, 2019, at 12:58 PM, Bill Lewis <wr...@gm...> wrote: >> >> On 6/21/2019 1:38 PM, Lonnie Abelbeck wrote: >>>> On Jun 21, 2019, at 11:02 AM, Bill Lewis <wr...@gm...> wrote: >>>> >>>> Hello all, >>>> >>>> Lately, for a few weeks, my system has randomly been acting up, with msgs like these in the log: >>>> >>>> Jun 20 21:12:52 pbx local0.warn asterisk[418]: WARNING[510]: chan_iax2.c:3591 in __attempt_transmit: Max retries exceeded to host 69.61.216.189 on IAX2/69.61.216.189:4569-10578 (type = 6, subclass = 11, ts=20019, seqno=3) >>>> >>>> This is on the C*Net network. >>>> The incoming caller hears just dead air when this happens. >>>> >>>> It fixes itself eventually, and then comes back again in a few days. >>>> >>>> Happens with astlinux-1.3.3 i686 - Asterisk 13.20.0 >>>> >>>> When it first happened I had recently done an in-place upgrade. >>>> Figuring that was why, I reverted out of that upgrade back to 1.3.3 >>>> and it happened again in a few days. >>>> >>>> I rebooted the FiOS fiber "MODEM" and the router for the heck of it >>>> and that had no effect. >>>> >>>> I found a few similar errors mentioned on Google but reading those >>>> posts didn't point me to any fix. >>>> >>>> Any ideas what to try? >>>> >>>> Bill >>> It has been many years since I have used IAX2, but guessing that looks like general network packet loss issues. >>> Is the "C*Net" network hosted at some central location ? Colocation, Hosted VM, or home internet ? >>> Lonnie >> >> Lonnie, >> >> C*Net uses a central service to lookup IP addresses. But the IAX2 connections are peer-to-peer. I would guess nearly all are on home >> internet (mine is). > > Hi Bill, > > Peer to peer, residential ISP to residential ISP, is probably not the most robust network quality. > > If the problem comes and goes, it is most likely general network packet loss issues. > > If AstLinux is not the edge router, then local traffic shaping (or lack of it) could allow bursts of data traffic to interfere with voice traffic. ...for the remote setup you don't control. > > Lonnie Well, after trying everything, I woke up and the intermittent problem had become a permanent failure of the network hardware. Motherboard went bad. So, that's that one fixed. :-) Bill |
|
From: Lonnie A. <li...@lo...> - 2019-06-22 13:46:07
|
Announcing Pre-Release Version: astlinux-1.3-4246-f527cd The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own. -- Asterisk 11.x, no longer included, officially EOL 2017-10-25 -- Asterisk 13.23.1 (new '13se' version) Older than latest Asterisk 13.x version but more tested, built --without-pjproject -- Asterisk 13.27.0 (version bump) and 16.4.0 (new version) Adds: res_mwi_devstate.so, MWI Device State Subscriptions -- Linux Kernel 3.16.69, security and bug fixes, including MDS (ZombieLoad) and SACK Panic mitigation support. -- busybox, *major* version bump to 1.30.1, security and bug fixes. -- WireGuard VPN, version bump to 0.0.20190601 Add "service wireguard reload" support. This allows WireGuard peers to be edited, added, and/or removed with minimal impact to active tunnels. Web Interface Network / Edit tabs, add "Reload WireGuard VPN" support. -- ne, new package, version 3.1.2, the nice editor, alternative to nano ne is easy to use for the beginner, but powerful and fully configurable for the wizard. Includes syntax checking for: asterisk, conf, ini, perl, sh More Info: http://ne.di.unimi.it/ -- Complete Pre-Release ChangeLog: https://s3.amazonaws.com/beta.astlinux-project/astlinux-changelog/ChangeLog.txt Updated Documentation Topics: Asterisk LTS Series Version - - https://doc.astlinux-project.org/userdoc:tt_asterisk_upgrade_version The "AstLinux Pre-Release ChangeLog" and "Pre-Release Repository URL" entries can be found under the "Development" tab of the AstLinux Project web site ... AstLinux Project -> Development https://www.astlinux-project.org/dev.html New "Development" tab feature for desktop browsers: Guest VM x86-64bit ISO: Download Pre-Release Guest VM Install ISO (Video Console) AstLinux Team |
|
From: Lonnie A. <li...@lo...> - 2019-06-21 18:10:41
|
> On Jun 21, 2019, at 12:58 PM, Bill Lewis <wr...@gm...> wrote: > > On 6/21/2019 1:38 PM, Lonnie Abelbeck wrote: >>> On Jun 21, 2019, at 11:02 AM, Bill Lewis <wr...@gm...> wrote: >>> >>> Hello all, >>> >>> Lately, for a few weeks, my system has randomly been acting up, with msgs like these in the log: >>> >>> Jun 20 21:12:52 pbx local0.warn asterisk[418]: WARNING[510]: chan_iax2.c:3591 in __attempt_transmit: Max retries exceeded to host 69.61.216.189 on IAX2/69.61.216.189:4569-10578 (type = 6, subclass = 11, ts=20019, seqno=3) >>> >>> This is on the C*Net network. >>> The incoming caller hears just dead air when this happens. >>> >>> It fixes itself eventually, and then comes back again in a few days. >>> >>> Happens with astlinux-1.3.3 i686 - Asterisk 13.20.0 >>> >>> When it first happened I had recently done an in-place upgrade. >>> Figuring that was why, I reverted out of that upgrade back to 1.3.3 >>> and it happened again in a few days. >>> >>> I rebooted the FiOS fiber "MODEM" and the router for the heck of it >>> and that had no effect. >>> >>> I found a few similar errors mentioned on Google but reading those >>> posts didn't point me to any fix. >>> >>> Any ideas what to try? >>> >>> Bill >> It has been many years since I have used IAX2, but guessing that looks like general network packet loss issues. >> Is the "C*Net" network hosted at some central location ? Colocation, Hosted VM, or home internet ? >> Lonnie > > Lonnie, > > C*Net uses a central service to lookup IP addresses. But the IAX2 connections are peer-to-peer. I would guess nearly all are on home > internet (mine is). Hi Bill, Peer to peer, residential ISP to residential ISP, is probably not the most robust network quality. If the problem comes and goes, it is most likely general network packet loss issues. If AstLinux is not the edge router, then local traffic shaping (or lack of it) could allow bursts of data traffic to interfere with voice traffic. ...for the remote setup you don't control. Lonnie |
|
From: Bill L. <wr...@gm...> - 2019-06-21 17:58:21
|
On 6/21/2019 1:38 PM, Lonnie Abelbeck wrote: > >> On Jun 21, 2019, at 11:02 AM, Bill Lewis <wr...@gm...> wrote: >> >> Hello all, >> >> Lately, for a few weeks, my system has randomly been acting up, with msgs like these in the log: >> >> Jun 20 21:12:52 pbx local0.warn asterisk[418]: WARNING[510]: chan_iax2.c:3591 in __attempt_transmit: Max retries exceeded to host 69.61.216.189 on IAX2/69.61.216.189:4569-10578 (type = 6, subclass = 11, ts=20019, seqno=3) >> >> This is on the C*Net network. >> The incoming caller hears just dead air when this happens. >> >> It fixes itself eventually, and then comes back again in a few days. >> >> Happens with astlinux-1.3.3 i686 - Asterisk 13.20.0 >> >> When it first happened I had recently done an in-place upgrade. >> Figuring that was why, I reverted out of that upgrade back to 1.3.3 >> and it happened again in a few days. >> >> I rebooted the FiOS fiber "MODEM" and the router for the heck of it >> and that had no effect. >> >> I found a few similar errors mentioned on Google but reading those >> posts didn't point me to any fix. >> >> Any ideas what to try? >> >> Bill > > It has been many years since I have used IAX2, but guessing that looks like general network packet loss issues. > > Is the "C*Net" network hosted at some central location ? Colocation, Hosted VM, or home internet ? > > Lonnie Lonnie, C*Net uses a central service to lookup IP addresses. But the IAX2 connections are peer-to-peer. I would guess nearly all are on home internet (mine is). Bill |
|
From: Lonnie A. <li...@lo...> - 2019-06-21 17:39:04
|
> On Jun 21, 2019, at 11:02 AM, Bill Lewis <wr...@gm...> wrote: > > Hello all, > > Lately, for a few weeks, my system has randomly been acting up, with msgs like these in the log: > > Jun 20 21:12:52 pbx local0.warn asterisk[418]: WARNING[510]: chan_iax2.c:3591 in __attempt_transmit: Max retries exceeded to host 69.61.216.189 on IAX2/69.61.216.189:4569-10578 (type = 6, subclass = 11, ts=20019, seqno=3) > > This is on the C*Net network. > The incoming caller hears just dead air when this happens. > > It fixes itself eventually, and then comes back again in a few days. > > Happens with astlinux-1.3.3 i686 - Asterisk 13.20.0 > > When it first happened I had recently done an in-place upgrade. > Figuring that was why, I reverted out of that upgrade back to 1.3.3 > and it happened again in a few days. > > I rebooted the FiOS fiber "MODEM" and the router for the heck of it > and that had no effect. > > I found a few similar errors mentioned on Google but reading those > posts didn't point me to any fix. > > Any ideas what to try? > > Bill It has been many years since I have used IAX2, but guessing that looks like general network packet loss issues. Is the "C*Net" network hosted at some central location ? Colocation, Hosted VM, or home internet ? Lonnie |
|
From: Bill L. <wr...@gm...> - 2019-06-21 16:02:12
|
Hello all, Lately, for a few weeks, my system has randomly been acting up, with msgs like these in the log: Jun 20 21:12:52 pbx local0.warn asterisk[418]: WARNING[510]: chan_iax2.c:3591 in __attempt_transmit: Max retries exceeded to host 69.61.216.189 on IAX2/69.61.216.189:4569-10578 (type = 6, subclass = 11, ts=20019, seqno=3) This is on the C*Net network. The incoming caller hears just dead air when this happens. It fixes itself eventually, and then comes back again in a few days. Happens with astlinux-1.3.3 i686 - Asterisk 13.20.0 When it first happened I had recently done an in-place upgrade. Figuring that was why, I reverted out of that upgrade back to 1.3.3 and it happened again in a few days. I rebooted the FiOS fiber "MODEM" and the router for the heck of it and that had no effect. I found a few similar errors mentioned on Google but reading those posts didn't point me to any fix. Any ideas what to try? Bill |
|
From: Lonnie A. <li...@lo...> - 2019-06-20 15:49:57
|
> On Jun 18, 2019, at 2:56 PM, Josh Alberts <jm...@ho...> wrote: > > I tried upgrading from astlinux-1.3.5.2 i686 to astlinux-1.3-4232-509fbe. When Asterisk receives a call, when a Dahdi channel goes off-hook, or basically in response to any other user-generated action, Asterisk immediately crashes and I see this in the dmesg output: > > segfault at 1 ip 40421dcd sp 4334a990 error 4 in libjansson.so.4.11.1[4041d000+b000] > > I reverted back to 1.3.5.2 (Thanks for the Revert to Previous feature!) but I could try the development build again if that would help you guys figure out what's going on. > > Josh We have identified the issue Josh reported. AstLinux fix to Asterisk: https://github.com/astlinux-project/astlinux/commit/ac93524dee89cd2917509a47756e43d4f0cf2504 Issue submitted upstream to Asterisk: https://issues.asterisk.org/jira/browse/ASTERISK-28457 Thanks Josh for the report and testing. Lonnie |
|
From: Josh A. <jm...@ho...> - 2019-06-19 19:08:19
|
> How about you try (with ast13 or ast16) include "res_timing_timerfd", comment out your noload: Just tried, I still get the segfault when I go off-hook on a Dahdi channel, or when a call comes into the Dahdi channel (from chan_sip or chan_pjsip). To confirm something I was uncertain of earlier, the last thing I see in the console when trying to call the Dahdi channel is the Dial command, then the segfault happens. Thanks for all the attention so far, everyone! It's always a really positive experience coming here for help. Josh ________________________________ From: Lonnie Abelbeck <li...@lo...> Sent: Wednesday, June 19, 2019 2:56 PM To: AstLinux Developers Mailing List Subject: Re: [Astlinux-devel] Segfault Crash on astlinux-1.3-4232-509fbe Hi Josh, > things seem to be working fine with 13se. Good clue. So it could be the Asterisk version 13se is 13.23.1 and "beta" 13 is 13.27.0, or since 13se does not contain PJSIP that could be related. How about you try (with ast13 or ast16) include "res_timing_timerfd", comment out your noload: -- ;noload => res_timing_timerfd.so -- BTW, your "show-union" results look OK. I'm trying to reproduce your DAHDI issue, but I don't have any DAHDI hardware ... though all the DAHDI modules (asterisk and linux) load fine. Lonnie > On Jun 19, 2019, at 1:40 PM, Josh Alberts <jm...@ho...> wrote: > > Lonnie, things seem to be working fine with 13se. > > From: Lonnie Abelbeck <li...@lo...> > Sent: Wednesday, June 19, 2019 12:13 PM > To: AstLinux Developers Mailing List > Subject: Re: [Astlinux-devel] Segfault Crash on astlinux-1.3-4232-509fbe > > Hi Josh, > > If you have the time, can you also test the ast13se version: > -- > upgrade-run-image upgrade https://s3.amazonaws.com/beta.astlinux-project/ast13se-firmware-1.x > -- > Granted chan_pjsip will not work with this version, but see if you are getting the same DAHDI crash. > > Thanks again for your testing help. > > Lonnie > > > > On Jun 19, 2019, at 8:47 AM, Josh Alberts <jm...@ho...> wrote: > > > > Lonnie, > > > > I'm running an HP t5740 thinclient (with a 32-bit CPU) with a Digium TE122P card (firmware 1.12). > > > > I never knew about the asterisk -c command. That's very helpful. Thanks! > > > > Unfortunately, I'm not getting too far: > > > > pbx ~ # asterisk -c > > Asterisk 16.4.0, Copyright (C) 1999 - 2018, Digium, Inc. and others. > > Created by Mark Spencer <mar...@di...> > > Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details. > > This is free software, with components licensed under the GNU General Public > > License version 2 and other licenses; you are welcome to redistribute it under > > certain conditions. Type 'core show license' for details. > > ========================================================================= > > XSLT support not found. XML documentation may be incomplete. > > PBX UUID: 79ef0c49-1727-4912-907a-a3954cb63520 > > [Jun 19 09:33:31] NOTICE[1642]: loader.c:2377 load_modules: 323 modules will be loaded. > > Segmentation fault > > > > I have a custom module that I suspect could be causing issues. That's really of no concern here - I'll just disable it if that prevents a roadblock to upgrade. When I throw a noload for it into modules.conf, I get all the way: > > > > pbx ~ # asterisk -c > > Asterisk 16.4.0, Copyright (C) 1999 - 2018, Digium, Inc. and others. > > Created by Mark Spencer <mar...@di...> > > Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details. > > This is free software, with components licensed under the GNU General Public > > License version 2 and other licenses; you are welcome to redistribute it under > > certain conditions. Type 'core show license' for details. > > ========================================================================= > > XSLT support not found. XML documentation may be incomplete. > > PBX UUID: 79ef0c49-1727-4912-907a-a3954cb63520 > > [Jun 19 09:39:43] NOTICE[2020]: loader.c:2377 load_modules: 322 modules will be loaded. > > [ Initializing Custom Configuration Options ] > > [Jun 19 09:39:47] WARNING[2020]: res_odbc.c:606 load_odbc_config: The 'pooling', 'shared_connections', 'limit', and 'idlecheck' options were replaced by 'max_connections'. See res_odbc.conf.sample. > > [Jun 19 09:39:47] WARNING[2020]: res_odbc.c:606 load_odbc_config: The 'pooling', 'shared_connections', 'limit', and 'idlecheck' options were replaced by 'max_connections'. See res_odbc.conf.sample. > > [Jun 19 09:39:47] WARNING[2020]: features_config.c:1533 unsupported_handler: Parkinglots are no longer configurable in features.conf; parking is now handled by res_parking.conf > > [Jun 19 09:39:47] WARNING[2020]: features_config.c:1537 unsupported_handler: The option 'parkext' is no longer configurable in features.conf. > > [Jun 19 09:39:47] WARNING[2020]: features_config.c:1537 unsupported_handler: The option 'parkpos' is no longer configurable in features.conf. > > [Jun 19 09:39:47] WARNING[2020]: features_config.c:1537 unsupported_handler: The option 'context' is no longer configurable in features.conf. > > [Jun 19 09:39:47] NOTICE[2020]: dnsmgr.c:493 do_reload: Managed DNS entries will be refreshed every 300 seconds. > > [Jun 19 09:39:47] ERROR[2020]: cel.c:428 ast_cel_str_to_event_type: Unknown event name 'BRIDGE_START' > > [Jun 19 09:39:47] ERROR[2020]: config_options.c:798 aco_process_var: Error parsing events=APP_START,CHAN_START,CHAN_END,ANSWER,HANGUP,BRIDGE_START,BRIDGE_END at line 76 of > > [Jun 19 09:39:47] ERROR[2020]: config_options.c:544 process_category: In cel.conf: Processing options for general failed > > [Jun 19 09:39:47] NOTICE[2020]: cel.c:1614 load_module: Failed to process CEL configuration; using defaults > > [Jun 19 09:39:47] NOTICE[2020]: cdr.c:4508 cdr_toggle_runtime_options: CDR simple logging enabled. > > [Jun 19 09:39:48] ERROR[2020]: res_resolver_unbound.c:417 unbound_config_preapply: Failed to set hosts file to 'system' in unbound resolver: syntax error > > [Jun 19 09:39:48] NOTICE[2020]: res_smdi.c:1424 load_module: No SMDI interfaces are available to listen on, not starting SMDI listener. > > [Jun 19 09:39:48] WARNING[2020]: res_phoneprov.c:1230 get_defaults: Unable to find a valid server address or name. > > SIP channel loading... > > [Jun 19 09:39:48] NOTICE[2020]: chan_sip.c:31843 build_peer: The 'username' field for sip peers has been deprecated in favor of the term 'defaultuser' > > [Jun 19 09:39:48] ERROR[2020]: chan_motif.c:2681 custom_connection_handler: Connection 'local-jabber-account' configured on endpoint 'jingle-endpoint' could not be found > > [Jun 19 09:39:48] ERROR[2020]: config_options.c:798 aco_process_var: Error parsing connection=local-jabber-account at line 81 of > > [Jun 19 09:39:48] ERROR[2020]: config_options.c:572 process_category: In motif.conf: Processing options for jingle-endpoint failed > > [Jun 19 09:39:48] ERROR[2020]: chan_motif.c:2756 load_module: Unable to read config file motif.conf. Module loaded but not running. > > [Jun 19 09:39:48] NOTICE[2072]: chan_sip.c:24881 handle_response_peerpoke: Peer 'joshcisco' is now Reachable. (12ms / 6000ms) > > [Jun 19 09:39:49] ERROR[2020]: ari/config.c:312 process_config: No configured users for ARI > > [Jun 19 09:39:49] NOTICE[2020]: confbridge/conf_config_parser.c:2326 verify_default_profiles: Adding default_menu menu to app_confbridge > > [Jun 19 09:39:49] ERROR[2020]: config_options.c:528 process_category: Could not find config type for category 'agents' in 'agents.conf' > > [Jun 19 09:39:49] ERROR[2020]: app_agent_pool.c:2693 load_module: Unable to load config. Not loading module. > > [Jun 19 09:39:49] NOTICE[2020]: cel_custom.c:95 load_config: No mappings found in cel_custom.conf. Not logging CEL to custom CSVs. > > [Jun 19 09:39:49] ERROR[2020]: codec_dahdi.c:813 find_transcoders: Failed to open /dev/dahdi/transcode: No such file or directory > > [Jun 19 09:39:49] WARNING[2020]: app_voicemail.c:14216 actual_load_config: maxsilence should be less than minsecs or you may get empty messages > > [Jun 19 09:39:49] WARNING[2020]: res_hep_rtcp.c:161 load_module: res_hep is disabled; declining module load > > [Jun 19 09:39:49] WARNING[2020]: res_hep_pjsip.c:236 load_module: res_hep is disabled; declining module load > > [Jun 19 09:39:49] WARNING[2020]: loader.c:2381 load_modules: Some non-required modules failed to load. > > [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: res_resolver_unbound declined to load. > > [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: chan_motif declined to load. > > [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: res_pjsip_transport_websocket declined to load. > > [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: app_agent_pool declined to load. > > [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: cel_sqlite3_custom declined to load. > > [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: cdr_sqlite3_custom declined to load. > > [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: res_hep_rtcp declined to load. > > [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: res_hep_pjsip declined to load. > > Asterisk Ready. > > > > But then as soon as I go off-hook on a Dahdi channel: > > > > *CLI> Segmentation fault > > > > It's really starting to seem (to me) like this is a Dahdi isssue. I'm able to place calls in and out through chan_sip and chan_pjsip. It's only Dahdi (going off-hook or trying to call a Dahdi channel) that seems to have issues. With ast16, Dahdi is triggering the same jansson error in dmesg: > > > > [ 732.177325] asterisk[2437]: segfault at 1 ip b73d2dcd sp b39f38e0 error 4 in libjansson.so.4.11.1[b73ce000+b000] > > > > From: Lonnie Abelbeck <li...@lo...> > > Sent: Wednesday, June 19, 2019 9:22 AM > > To: AstLinux Developers Mailing List > > Subject: Re: [Astlinux-devel] Segfault Crash on astlinux-1.3-4232-509fbe > > > > Hi Josh, > > > > Something is not right here... > > > > Testing tips: > > > > make sure asterisk is stopped (using CLI) > > -- > > service asterisk stop > > -- > > > > Then start via > > -- > > asterisk -c > > -- > > > > That will give you more context where the crash is occurring. > > > > BTW, what hardware are you using ? > > > > Lonnie > > > > > > > > > > > On Jun 19, 2019, at 8:15 AM, Josh Alberts <jm...@ho...> wrote: > > > > > > I tried the ast16 devel build, and this time, Asterisk is crashing before I get a chance to do anything. From dmesg (I tried restarting it twice): > > > > > > [ 44.698144] asterisk[1476]: segfault at 3c00 ip 081ee3f3 sp bfea5a10 error 4 in asterisk[8048000+2d2000] > > > [ 75.397478] asterisk[1621]: segfault at 3c00 ip 081ee3f3 sp bfae0140 error 4 in asterisk[8048000+2d2000] > > > [ 83.550674] asterisk[1671]: segfault at 3c00 ip 081ee3f3 sp bfdfff10 error 4 in asterisk[8048000+2d2000] > > > > > > > > > From: Lonnie Abelbeck <li...@lo...> > > > Sent: Tuesday, June 18, 2019 4:54 PM > > > To: AstLinux Developers Mailing List > > > Subject: Re: [Astlinux-devel] Segfault Crash on astlinux-1.3-4232-509fbe > > > > > > Hi Josh, > > > > > > As a mini-clue "libjansson.so" is only referenced by the "asterisk" binary, not by any of the asterisk modules. > > > > > > You might test again but use ast16 ... your Asterisk 13 configs should be fine for a quick test. > > > > > > Understand you have a somewhat unique setup using DAHDI, chan_sip and chan_pjsip all at the same time. And on 32-bit hardware. Agreed it should all work though. > > > > > > Lonnie > > > > > > > > > > > > > On Jun 18, 2019, at 3:16 PM, Lonnie Abelbeck <li...@lo...> wrote: > > > > > > > > Hi Josh, > > > > > > > > If you can, more clues would be great. > > > > > > > > Like if it is precisely reproducible, or if the crash varies ... and what is going on in the dialplan. > > > > > > > > Lonnie > > > > > > > > > > > > > > > > > > > >> On Jun 18, 2019, at 3:10 PM, Josh Alberts <jm...@ho...> wrote: > > > >> > > > >> I'm using both PJSIP and chan_sip (on different ports, of course). > > > >> > > > >> Come to think of it, all of the test calls that I generated either originated or terminated to/from the same Dahdi channel, so maybe Dahdi is playing into this? Wish I could have tested more but I had to get the system back up. Like I said, I would be glad to upgrade again and investigate further if that would help. > > > >> > > > >> From: Michael Keuter <li...@mk...> > > > >> Sent: Tuesday, June 18, 2019 4:06 PM > > > >> To: AstLinux Developers Mailing List > > > >> Subject: Re: [Astlinux-devel] Segfault Crash on astlinux-1.3-4232-509fbe > > > >> > > > >> > > > >>> Am 18.06.2019 um 21:56 schrieb Josh Alberts <jm...@ho...>: > > > >>> > > > >>> I tried upgrading from astlinux-1.3.5.2 i686 to astlinux-1.3-4232-509fbe. When Asterisk receives a call, when a Dahdi channel goes off-hook, or basically in response to any other user-generated action, Asterisk immediately crashes and I see this in the dmesg output: > > > >>> > > > >>> segfault at 1 ip 40421dcd sp 4334a990 error 4 in libjansson.so.4.11.1[4041d000+b000] > > > >>> > > > >>> I reverted back to 1.3.5.2 (Thanks for the Revert to Previous feature!) but I could try the development build again if that would help you guys figure out what's going on. > > > >>> > > > >>> Josh > > > >> > > > >> So that means: > > > >> > > > >> Asterisk 13.24.1 versus Asterisk 13.27.0 > > > >> > > > >> Are you using PJSIP already or chan_sip? > > > >> > > > >> I have been running that build on a few boxes successfully for a week, although none of my boxes uses DAHDI … > > > >> Does anyone else on this list is using Asterisk 13.27.0 together with DAHDI? > > > >> > > > >> Michael > > > >> > > > >> http://www.mksolutions.info > > > >> > > > >> > > > >> > > > >> > > > >> > > > >> _______________________________________________ > > > >> Astlinux-devel mailing list > > > >> Ast...@li... > > > >> https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > >> _______________________________________________ > > > >> Astlinux-devel mailing list > > > >> Ast...@li... > > > >> https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > > > > > > > > > > > > > > _______________________________________________ > > > > Astlinux-devel mailing list > > > > Ast...@li... > > > > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > > > > > > > > > > _______________________________________________ > > > Astlinux-devel mailing list > > > Ast...@li... > > > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > _______________________________________________ > > > Astlinux-devel mailing list > > > Ast...@li... > > > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > > > > > > _______________________________________________ > > Astlinux-devel mailing list > > Ast...@li... > > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > _______________________________________________ > > Astlinux-devel mailing list > > Ast...@li... > > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel _______________________________________________ Astlinux-devel mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Lonnie A. <li...@lo...> - 2019-06-19 18:56:50
|
Hi Josh, > things seem to be working fine with 13se. Good clue. So it could be the Asterisk version 13se is 13.23.1 and "beta" 13 is 13.27.0, or since 13se does not contain PJSIP that could be related. How about you try (with ast13 or ast16) include "res_timing_timerfd", comment out your noload: -- ;noload => res_timing_timerfd.so -- BTW, your "show-union" results look OK. I'm trying to reproduce your DAHDI issue, but I don't have any DAHDI hardware ... though all the DAHDI modules (asterisk and linux) load fine. Lonnie > On Jun 19, 2019, at 1:40 PM, Josh Alberts <jm...@ho...> wrote: > > Lonnie, things seem to be working fine with 13se. > > From: Lonnie Abelbeck <li...@lo...> > Sent: Wednesday, June 19, 2019 12:13 PM > To: AstLinux Developers Mailing List > Subject: Re: [Astlinux-devel] Segfault Crash on astlinux-1.3-4232-509fbe > > Hi Josh, > > If you have the time, can you also test the ast13se version: > -- > upgrade-run-image upgrade https://s3.amazonaws.com/beta.astlinux-project/ast13se-firmware-1.x > -- > Granted chan_pjsip will not work with this version, but see if you are getting the same DAHDI crash. > > Thanks again for your testing help. > > Lonnie > > > > On Jun 19, 2019, at 8:47 AM, Josh Alberts <jm...@ho...> wrote: > > > > Lonnie, > > > > I'm running an HP t5740 thinclient (with a 32-bit CPU) with a Digium TE122P card (firmware 1.12). > > > > I never knew about the asterisk -c command. That's very helpful. Thanks! > > > > Unfortunately, I'm not getting too far: > > > > pbx ~ # asterisk -c > > Asterisk 16.4.0, Copyright (C) 1999 - 2018, Digium, Inc. and others. > > Created by Mark Spencer <mar...@di...> > > Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details. > > This is free software, with components licensed under the GNU General Public > > License version 2 and other licenses; you are welcome to redistribute it under > > certain conditions. Type 'core show license' for details. > > ========================================================================= > > XSLT support not found. XML documentation may be incomplete. > > PBX UUID: 79ef0c49-1727-4912-907a-a3954cb63520 > > [Jun 19 09:33:31] NOTICE[1642]: loader.c:2377 load_modules: 323 modules will be loaded. > > Segmentation fault > > > > I have a custom module that I suspect could be causing issues. That's really of no concern here - I'll just disable it if that prevents a roadblock to upgrade. When I throw a noload for it into modules.conf, I get all the way: > > > > pbx ~ # asterisk -c > > Asterisk 16.4.0, Copyright (C) 1999 - 2018, Digium, Inc. and others. > > Created by Mark Spencer <mar...@di...> > > Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details. > > This is free software, with components licensed under the GNU General Public > > License version 2 and other licenses; you are welcome to redistribute it under > > certain conditions. Type 'core show license' for details. > > ========================================================================= > > XSLT support not found. XML documentation may be incomplete. > > PBX UUID: 79ef0c49-1727-4912-907a-a3954cb63520 > > [Jun 19 09:39:43] NOTICE[2020]: loader.c:2377 load_modules: 322 modules will be loaded. > > [ Initializing Custom Configuration Options ] > > [Jun 19 09:39:47] WARNING[2020]: res_odbc.c:606 load_odbc_config: The 'pooling', 'shared_connections', 'limit', and 'idlecheck' options were replaced by 'max_connections'. See res_odbc.conf.sample. > > [Jun 19 09:39:47] WARNING[2020]: res_odbc.c:606 load_odbc_config: The 'pooling', 'shared_connections', 'limit', and 'idlecheck' options were replaced by 'max_connections'. See res_odbc.conf.sample. > > [Jun 19 09:39:47] WARNING[2020]: features_config.c:1533 unsupported_handler: Parkinglots are no longer configurable in features.conf; parking is now handled by res_parking.conf > > [Jun 19 09:39:47] WARNING[2020]: features_config.c:1537 unsupported_handler: The option 'parkext' is no longer configurable in features.conf. > > [Jun 19 09:39:47] WARNING[2020]: features_config.c:1537 unsupported_handler: The option 'parkpos' is no longer configurable in features.conf. > > [Jun 19 09:39:47] WARNING[2020]: features_config.c:1537 unsupported_handler: The option 'context' is no longer configurable in features.conf. > > [Jun 19 09:39:47] NOTICE[2020]: dnsmgr.c:493 do_reload: Managed DNS entries will be refreshed every 300 seconds. > > [Jun 19 09:39:47] ERROR[2020]: cel.c:428 ast_cel_str_to_event_type: Unknown event name 'BRIDGE_START' > > [Jun 19 09:39:47] ERROR[2020]: config_options.c:798 aco_process_var: Error parsing events=APP_START,CHAN_START,CHAN_END,ANSWER,HANGUP,BRIDGE_START,BRIDGE_END at line 76 of > > [Jun 19 09:39:47] ERROR[2020]: config_options.c:544 process_category: In cel.conf: Processing options for general failed > > [Jun 19 09:39:47] NOTICE[2020]: cel.c:1614 load_module: Failed to process CEL configuration; using defaults > > [Jun 19 09:39:47] NOTICE[2020]: cdr.c:4508 cdr_toggle_runtime_options: CDR simple logging enabled. > > [Jun 19 09:39:48] ERROR[2020]: res_resolver_unbound.c:417 unbound_config_preapply: Failed to set hosts file to 'system' in unbound resolver: syntax error > > [Jun 19 09:39:48] NOTICE[2020]: res_smdi.c:1424 load_module: No SMDI interfaces are available to listen on, not starting SMDI listener. > > [Jun 19 09:39:48] WARNING[2020]: res_phoneprov.c:1230 get_defaults: Unable to find a valid server address or name. > > SIP channel loading... > > [Jun 19 09:39:48] NOTICE[2020]: chan_sip.c:31843 build_peer: The 'username' field for sip peers has been deprecated in favor of the term 'defaultuser' > > [Jun 19 09:39:48] ERROR[2020]: chan_motif.c:2681 custom_connection_handler: Connection 'local-jabber-account' configured on endpoint 'jingle-endpoint' could not be found > > [Jun 19 09:39:48] ERROR[2020]: config_options.c:798 aco_process_var: Error parsing connection=local-jabber-account at line 81 of > > [Jun 19 09:39:48] ERROR[2020]: config_options.c:572 process_category: In motif.conf: Processing options for jingle-endpoint failed > > [Jun 19 09:39:48] ERROR[2020]: chan_motif.c:2756 load_module: Unable to read config file motif.conf. Module loaded but not running. > > [Jun 19 09:39:48] NOTICE[2072]: chan_sip.c:24881 handle_response_peerpoke: Peer 'joshcisco' is now Reachable. (12ms / 6000ms) > > [Jun 19 09:39:49] ERROR[2020]: ari/config.c:312 process_config: No configured users for ARI > > [Jun 19 09:39:49] NOTICE[2020]: confbridge/conf_config_parser.c:2326 verify_default_profiles: Adding default_menu menu to app_confbridge > > [Jun 19 09:39:49] ERROR[2020]: config_options.c:528 process_category: Could not find config type for category 'agents' in 'agents.conf' > > [Jun 19 09:39:49] ERROR[2020]: app_agent_pool.c:2693 load_module: Unable to load config. Not loading module. > > [Jun 19 09:39:49] NOTICE[2020]: cel_custom.c:95 load_config: No mappings found in cel_custom.conf. Not logging CEL to custom CSVs. > > [Jun 19 09:39:49] ERROR[2020]: codec_dahdi.c:813 find_transcoders: Failed to open /dev/dahdi/transcode: No such file or directory > > [Jun 19 09:39:49] WARNING[2020]: app_voicemail.c:14216 actual_load_config: maxsilence should be less than minsecs or you may get empty messages > > [Jun 19 09:39:49] WARNING[2020]: res_hep_rtcp.c:161 load_module: res_hep is disabled; declining module load > > [Jun 19 09:39:49] WARNING[2020]: res_hep_pjsip.c:236 load_module: res_hep is disabled; declining module load > > [Jun 19 09:39:49] WARNING[2020]: loader.c:2381 load_modules: Some non-required modules failed to load. > > [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: res_resolver_unbound declined to load. > > [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: chan_motif declined to load. > > [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: res_pjsip_transport_websocket declined to load. > > [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: app_agent_pool declined to load. > > [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: cel_sqlite3_custom declined to load. > > [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: cdr_sqlite3_custom declined to load. > > [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: res_hep_rtcp declined to load. > > [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: res_hep_pjsip declined to load. > > Asterisk Ready. > > > > But then as soon as I go off-hook on a Dahdi channel: > > > > *CLI> Segmentation fault > > > > It's really starting to seem (to me) like this is a Dahdi isssue. I'm able to place calls in and out through chan_sip and chan_pjsip. It's only Dahdi (going off-hook or trying to call a Dahdi channel) that seems to have issues. With ast16, Dahdi is triggering the same jansson error in dmesg: > > > > [ 732.177325] asterisk[2437]: segfault at 1 ip b73d2dcd sp b39f38e0 error 4 in libjansson.so.4.11.1[b73ce000+b000] > > > > From: Lonnie Abelbeck <li...@lo...> > > Sent: Wednesday, June 19, 2019 9:22 AM > > To: AstLinux Developers Mailing List > > Subject: Re: [Astlinux-devel] Segfault Crash on astlinux-1.3-4232-509fbe > > > > Hi Josh, > > > > Something is not right here... > > > > Testing tips: > > > > make sure asterisk is stopped (using CLI) > > -- > > service asterisk stop > > -- > > > > Then start via > > -- > > asterisk -c > > -- > > > > That will give you more context where the crash is occurring. > > > > BTW, what hardware are you using ? > > > > Lonnie > > > > > > > > > > > On Jun 19, 2019, at 8:15 AM, Josh Alberts <jm...@ho...> wrote: > > > > > > I tried the ast16 devel build, and this time, Asterisk is crashing before I get a chance to do anything. From dmesg (I tried restarting it twice): > > > > > > [ 44.698144] asterisk[1476]: segfault at 3c00 ip 081ee3f3 sp bfea5a10 error 4 in asterisk[8048000+2d2000] > > > [ 75.397478] asterisk[1621]: segfault at 3c00 ip 081ee3f3 sp bfae0140 error 4 in asterisk[8048000+2d2000] > > > [ 83.550674] asterisk[1671]: segfault at 3c00 ip 081ee3f3 sp bfdfff10 error 4 in asterisk[8048000+2d2000] > > > > > > > > > From: Lonnie Abelbeck <li...@lo...> > > > Sent: Tuesday, June 18, 2019 4:54 PM > > > To: AstLinux Developers Mailing List > > > Subject: Re: [Astlinux-devel] Segfault Crash on astlinux-1.3-4232-509fbe > > > > > > Hi Josh, > > > > > > As a mini-clue "libjansson.so" is only referenced by the "asterisk" binary, not by any of the asterisk modules. > > > > > > You might test again but use ast16 ... your Asterisk 13 configs should be fine for a quick test. > > > > > > Understand you have a somewhat unique setup using DAHDI, chan_sip and chan_pjsip all at the same time. And on 32-bit hardware. Agreed it should all work though. > > > > > > Lonnie > > > > > > > > > > > > > On Jun 18, 2019, at 3:16 PM, Lonnie Abelbeck <li...@lo...> wrote: > > > > > > > > Hi Josh, > > > > > > > > If you can, more clues would be great. > > > > > > > > Like if it is precisely reproducible, or if the crash varies ... and what is going on in the dialplan. > > > > > > > > Lonnie > > > > > > > > > > > > > > > > > > > >> On Jun 18, 2019, at 3:10 PM, Josh Alberts <jm...@ho...> wrote: > > > >> > > > >> I'm using both PJSIP and chan_sip (on different ports, of course). > > > >> > > > >> Come to think of it, all of the test calls that I generated either originated or terminated to/from the same Dahdi channel, so maybe Dahdi is playing into this? Wish I could have tested more but I had to get the system back up. Like I said, I would be glad to upgrade again and investigate further if that would help. > > > >> > > > >> From: Michael Keuter <li...@mk...> > > > >> Sent: Tuesday, June 18, 2019 4:06 PM > > > >> To: AstLinux Developers Mailing List > > > >> Subject: Re: [Astlinux-devel] Segfault Crash on astlinux-1.3-4232-509fbe > > > >> > > > >> > > > >>> Am 18.06.2019 um 21:56 schrieb Josh Alberts <jm...@ho...>: > > > >>> > > > >>> I tried upgrading from astlinux-1.3.5.2 i686 to astlinux-1.3-4232-509fbe. When Asterisk receives a call, when a Dahdi channel goes off-hook, or basically in response to any other user-generated action, Asterisk immediately crashes and I see this in the dmesg output: > > > >>> > > > >>> segfault at 1 ip 40421dcd sp 4334a990 error 4 in libjansson.so.4.11.1[4041d000+b000] > > > >>> > > > >>> I reverted back to 1.3.5.2 (Thanks for the Revert to Previous feature!) but I could try the development build again if that would help you guys figure out what's going on. > > > >>> > > > >>> Josh > > > >> > > > >> So that means: > > > >> > > > >> Asterisk 13.24.1 versus Asterisk 13.27.0 > > > >> > > > >> Are you using PJSIP already or chan_sip? > > > >> > > > >> I have been running that build on a few boxes successfully for a week, although none of my boxes uses DAHDI … > > > >> Does anyone else on this list is using Asterisk 13.27.0 together with DAHDI? > > > >> > > > >> Michael > > > >> > > > >> http://www.mksolutions.info > > > >> > > > >> > > > >> > > > >> > > > >> > > > >> _______________________________________________ > > > >> Astlinux-devel mailing list > > > >> Ast...@li... > > > >> https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > >> _______________________________________________ > > > >> Astlinux-devel mailing list > > > >> Ast...@li... > > > >> https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > > > > > > > > > > > > > > _______________________________________________ > > > > Astlinux-devel mailing list > > > > Ast...@li... > > > > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > > > > > > > > > > _______________________________________________ > > > Astlinux-devel mailing list > > > Ast...@li... > > > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > _______________________________________________ > > > Astlinux-devel mailing list > > > Ast...@li... > > > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > > > > > > _______________________________________________ > > Astlinux-devel mailing list > > Ast...@li... > > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > _______________________________________________ > > Astlinux-devel mailing list > > Ast...@li... > > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Josh A. <jm...@ho...> - 2019-06-19 18:51:15
|
Perhaps it would have been better if I said that everything is working fine in 13se except PJSIP, which I knew wouldn't work. ________________________________ From: Michael Keuter <li...@mk...> Sent: Wednesday, June 19, 2019 2:49 PM To: AstLinux Developers Mailing List Subject: Re: [Astlinux-devel] Segfault Crash on astlinux-1.3-4232-509fbe Am 19.06.2019 um 20:40 schrieb Josh Alberts <jm...@ho...<mailto:jm...@ho...>>: Lonnie, things seem to be working fine with 13se. It uses an older Asterisk 13 version (13.23.1) and PJSIP is not included! From: Lonnie Abelbeck <li...@lo...<mailto:li...@lo...>> Sent: Wednesday, June 19, 2019 12:13 PM To: AstLinux Developers Mailing List Subject: Re: [Astlinux-devel] Segfault Crash on astlinux-1.3-4232-509fbe Hi Josh, If you have the time, can you also test the ast13se version: -- upgrade-run-image upgrade https://s3.amazonaws.com/beta.astlinux-project/ast13se-firmware-1.x -- Granted chan_pjsip will not work with this version, but see if you are getting the same DAHDI crash. Thanks again for your testing help. Lonnie On Jun 19, 2019, at 8:47 AM, Josh Alberts <jm...@ho...<mailto:jm...@ho...>> wrote: Lonnie, I'm running an HP t5740 thinclient (with a 32-bit CPU) with a Digium TE122P card (firmware 1.12). I never knew about the asterisk -c command. That's very helpful. Thanks! Unfortunately, I'm not getting too far: pbx ~ # asterisk -c Asterisk 16.4.0, Copyright (C) 1999 - 2018, Digium, Inc. and others. Created by Mark Spencer <mar...@di...<mailto:mar...@di...>> Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details. This is free software, with components licensed under the GNU General Public License version 2 and other licenses; you are welcome to redistribute it under certain conditions. Type 'core show license' for details. ========================================================================= XSLT support not found. XML documentation may be incomplete. PBX UUID: 79ef0c49-1727-4912-907a-a3954cb63520 [Jun 19 09:33:31] NOTICE[1642]: loader.c:2377 load_modules: 323 modules will be loaded. Segmentation fault I have a custom module that I suspect could be causing issues. That's really of no concern here - I'll just disable it if that prevents a roadblock to upgrade. When I throw a noload for it into modules.conf, I get all the way: pbx ~ # asterisk -c Asterisk 16.4.0, Copyright (C) 1999 - 2018, Digium, Inc. and others. Created by Mark Spencer <mar...@di...<mailto:mar...@di...>> Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details. This is free software, with components licensed under the GNU General Public License version 2 and other licenses; you are welcome to redistribute it under certain conditions. Type 'core show license' for details. ========================================================================= XSLT support not found. XML documentation may be incomplete. PBX UUID: 79ef0c49-1727-4912-907a-a3954cb63520 [Jun 19 09:39:43] NOTICE[2020]: loader.c:2377 load_modules: 322 modules will be loaded. [ Initializing Custom Configuration Options ] [Jun 19 09:39:47] WARNING[2020]: res_odbc.c:606 load_odbc_config: The 'pooling', 'shared_connections', 'limit', and 'idlecheck' options were replaced by 'max_connections'. See res_odbc.conf.sample. [Jun 19 09:39:47] WARNING[2020]: res_odbc.c:606 load_odbc_config: The 'pooling', 'shared_connections', 'limit', and 'idlecheck' options were replaced by 'max_connections'. See res_odbc.conf.sample. [Jun 19 09:39:47] WARNING[2020]: features_config.c:1533 unsupported_handler: Parkinglots are no longer configurable in features.conf; parking is now handled by res_parking.conf [Jun 19 09:39:47] WARNING[2020]: features_config.c:1537 unsupported_handler: The option 'parkext' is no longer configurable in features.conf. [Jun 19 09:39:47] WARNING[2020]: features_config.c:1537 unsupported_handler: The option 'parkpos' is no longer configurable in features.conf. [Jun 19 09:39:47] WARNING[2020]: features_config.c:1537 unsupported_handler: The option 'context' is no longer configurable in features.conf. [Jun 19 09:39:47] NOTICE[2020]: dnsmgr.c:493 do_reload: Managed DNS entries will be refreshed every 300 seconds. [Jun 19 09:39:47] ERROR[2020]: cel.c:428 ast_cel_str_to_event_type: Unknown event name 'BRIDGE_START' [Jun 19 09:39:47] ERROR[2020]: config_options.c:798 aco_process_var: Error parsing events=APP_START,CHAN_START,CHAN_END,ANSWER,HANGUP,BRIDGE_START,BRIDGE_END at line 76 of [Jun 19 09:39:47] ERROR[2020]: config_options.c:544 process_category: In cel.conf: Processing options for general failed [Jun 19 09:39:47] NOTICE[2020]: cel.c:1614 load_module: Failed to process CEL configuration; using defaults [Jun 19 09:39:47] NOTICE[2020]: cdr.c:4508 cdr_toggle_runtime_options: CDR simple logging enabled. [Jun 19 09:39:48] ERROR[2020]: res_resolver_unbound.c:417 unbound_config_preapply: Failed to set hosts file to 'system' in unbound resolver: syntax error [Jun 19 09:39:48] NOTICE[2020]: res_smdi.c:1424 load_module: No SMDI interfaces are available to listen on, not starting SMDI listener. [Jun 19 09:39:48] WARNING[2020]: res_phoneprov.c:1230 get_defaults: Unable to find a valid server address or name. SIP channel loading... [Jun 19 09:39:48] NOTICE[2020]: chan_sip.c:31843 build_peer: The 'username' field for sip peers has been deprecated in favor of the term 'defaultuser' [Jun 19 09:39:48] ERROR[2020]: chan_motif.c:2681 custom_connection_handler: Connection 'local-jabber-account' configured on endpoint 'jingle-endpoint' could not be found [Jun 19 09:39:48] ERROR[2020]: config_options.c:798 aco_process_var: Error parsing connection=local-jabber-account at line 81 of [Jun 19 09:39:48] ERROR[2020]: config_options.c:572 process_category: In motif.conf: Processing options for jingle-endpoint failed [Jun 19 09:39:48] ERROR[2020]: chan_motif.c:2756 load_module: Unable to read config file motif.conf. Module loaded but not running. [Jun 19 09:39:48] NOTICE[2072]: chan_sip.c:24881 handle_response_peerpoke: Peer 'joshcisco' is now Reachable. (12ms / 6000ms) [Jun 19 09:39:49] ERROR[2020]: ari/config.c:312 process_config: No configured users for ARI [Jun 19 09:39:49] NOTICE[2020]: confbridge/conf_config_parser.c:2326 verify_default_profiles: Adding default_menu menu to app_confbridge [Jun 19 09:39:49] ERROR[2020]: config_options.c:528 process_category: Could not find config type for category 'agents' in 'agents.conf' [Jun 19 09:39:49] ERROR[2020]: app_agent_pool.c:2693 load_module: Unable to load config. Not loading module. [Jun 19 09:39:49] NOTICE[2020]: cel_custom.c:95 load_config: No mappings found in cel_custom.conf. Not logging CEL to custom CSVs. [Jun 19 09:39:49] ERROR[2020]: codec_dahdi.c:813 find_transcoders: Failed to open /dev/dahdi/transcode: No such file or directory [Jun 19 09:39:49] WARNING[2020]: app_voicemail.c:14216 actual_load_config: maxsilence should be less than minsecs or you may get empty messages [Jun 19 09:39:49] WARNING[2020]: res_hep_rtcp.c:161 load_module: res_hep is disabled; declining module load [Jun 19 09:39:49] WARNING[2020]: res_hep_pjsip.c:236 load_module: res_hep is disabled; declining module load [Jun 19 09:39:49] WARNING[2020]: loader.c:2381 load_modules: Some non-required modules failed to load. [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: res_resolver_unbound declined to load. [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: chan_motif declined to load. [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: res_pjsip_transport_websocket declined to load. [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: app_agent_pool declined to load. [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: cel_sqlite3_custom declined to load. [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: cdr_sqlite3_custom declined to load. [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: res_hep_rtcp declined to load. [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: res_hep_pjsip declined to load. Asterisk Ready. But then as soon as I go off-hook on a Dahdi channel: *CLI> Segmentation fault It's really starting to seem (to me) like this is a Dahdi isssue. I'm able to place calls in and out through chan_sip and chan_pjsip. It's only Dahdi (going off-hook or trying to call a Dahdi channel) that seems to have issues. With ast16, Dahdi is triggering the same jansson error in dmesg: [ 732.177325] asterisk[2437]: segfault at 1 ip b73d2dcd sp b39f38e0 error 4 in libjansson.so.4.11.1[b73ce000+b000] From: Lonnie Abelbeck <li...@lo...<mailto:li...@lo...>> Sent: Wednesday, June 19, 2019 9:22 AM To: AstLinux Developers Mailing List Subject: Re: [Astlinux-devel] Segfault Crash on astlinux-1.3-4232-509fbe Hi Josh, Something is not right here... Testing tips: make sure asterisk is stopped (using CLI) -- service asterisk stop -- Then start via -- asterisk -c -- That will give you more context where the crash is occurring. BTW, what hardware are you using ? Lonnie On Jun 19, 2019, at 8:15 AM, Josh Alberts <jm...@ho...<mailto:jm...@ho...>> wrote: I tried the ast16 devel build, and this time, Asterisk is crashing before I get a chance to do anything. From dmesg (I tried restarting it twice): [ 44.698144] asterisk[1476]: segfault at 3c00 ip 081ee3f3 sp bfea5a10 error 4 in asterisk[8048000+2d2000] [ 75.397478] asterisk[1621]: segfault at 3c00 ip 081ee3f3 sp bfae0140 error 4 in asterisk[8048000+2d2000] [ 83.550674] asterisk[1671]: segfault at 3c00 ip 081ee3f3 sp bfdfff10 error 4 in asterisk[8048000+2d2000] From: Lonnie Abelbeck <li...@lo...<mailto:li...@lo...>> Sent: Tuesday, June 18, 2019 4:54 PM To: AstLinux Developers Mailing List Subject: Re: [Astlinux-devel] Segfault Crash on astlinux-1.3-4232-509fbe Hi Josh, As a mini-clue "libjansson.so" is only referenced by the "asterisk" binary, not by any of the asterisk modules. You might test again but use ast16 ... your Asterisk 13 configs should be fine for a quick test. Understand you have a somewhat unique setup using DAHDI, chan_sip and chan_pjsip all at the same time. And on 32-bit hardware. Agreed it should all work though. Lonnie On Jun 18, 2019, at 3:16 PM, Lonnie Abelbeck <li...@lo...<mailto:li...@lo...>> wrote: Hi Josh, If you can, more clues would be great. Like if it is precisely reproducible, or if the crash varies ... and what is going on in the dialplan. Lonnie On Jun 18, 2019, at 3:10 PM, Josh Alberts <jm...@ho...<mailto:jm...@ho...>> wrote: I'm using both PJSIP and chan_sip (on different ports, of course). Come to think of it, all of the test calls that I generated either originated or terminated to/from the same Dahdi channel, so maybe Dahdi is playing into this? Wish I could have tested more but I had to get the system back up. Like I said, I would be glad to upgrade again and investigate further if that would help. From: Michael Keuter <li...@mk...<mailto:li...@mk...>> Sent: Tuesday, June 18, 2019 4:06 PM To: AstLinux Developers Mailing List Subject: Re: [Astlinux-devel] Segfault Crash on astlinux-1.3-4232-509fbe Am 18.06.2019 um 21:56 schrieb Josh Alberts <jm...@ho...<mailto:jm...@ho...>>: I tried upgrading from astlinux-1.3.5.2 i686 to astlinux-1.3-4232-509fbe. When Asterisk receives a call, when a Dahdi channel goes off-hook, or basically in response to any other user-generated action, Asterisk immediately crashes and I see this in the dmesg output: segfault at 1 ip 40421dcd sp 4334a990 error 4 in libjansson.so.4.11.1[4041d000+b000] I reverted back to 1.3.5.2 (Thanks for the Revert to Previous feature!) but I could try the development build again if that would help you guys figure out what's going on. Josh So that means: Asterisk 13.24.1 versus Asterisk 13.27.0 Are you using PJSIP already or chan_sip? I have been running that build on a few boxes successfully for a week, although none of my boxes uses DAHDI … Does anyone else on this list is using Asterisk 13.27.0 together with DAHDI? Michael Michael http://www.mksolutions.info |
|
From: Michael K. <li...@mk...> - 2019-06-19 18:49:42
|
> > Am 19.06.2019 um 20:40 schrieb Josh Alberts <jm...@ho... <mailto:jm...@ho...>>: > > Lonnie, things seem to be working fine with 13se. It uses an older Asterisk 13 version (13.23.1) and PJSIP is not included! > From: Lonnie Abelbeck <li...@lo...> > Sent: Wednesday, June 19, 2019 12:13 PM > To: AstLinux Developers Mailing List > Subject: Re: [Astlinux-devel] Segfault Crash on astlinux-1.3-4232-509fbe > > Hi Josh, > > If you have the time, can you also test the ast13se version: > -- > upgrade-run-image upgrade https://s3.amazonaws.com/beta.astlinux-project/ast13se-firmware-1.x > -- > Granted chan_pjsip will not work with this version, but see if you are getting the same DAHDI crash. > > Thanks again for your testing help. > > Lonnie > > >> On Jun 19, 2019, at 8:47 AM, Josh Alberts <jm...@ho...> wrote: >> >> Lonnie, >> >> I'm running an HP t5740 thinclient (with a 32-bit CPU) with a Digium TE122P card (firmware 1.12). >> >> I never knew about the asterisk -c command. That's very helpful. Thanks! >> >> Unfortunately, I'm not getting too far: >> >> pbx ~ # asterisk -c >> Asterisk 16.4.0, Copyright (C) 1999 - 2018, Digium, Inc. and others. >> Created by Mark Spencer <mar...@di...> >> Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details. >> This is free software, with components licensed under the GNU General Public >> License version 2 and other licenses; you are welcome to redistribute it under >> certain conditions. Type 'core show license' for details. >> ========================================================================= >> XSLT support not found. XML documentation may be incomplete. >> PBX UUID: 79ef0c49-1727-4912-907a-a3954cb63520 >> [Jun 19 09:33:31] NOTICE[1642]: loader.c:2377 load_modules: 323 modules will be loaded. >> Segmentation fault >> >> I have a custom module that I suspect could be causing issues. That's really of no concern here - I'll just disable it if that prevents a roadblock to upgrade. When I throw a noload for it into modules.conf, I get all the way: >> >> pbx ~ # asterisk -c >> Asterisk 16.4.0, Copyright (C) 1999 - 2018, Digium, Inc. and others. >> Created by Mark Spencer <mar...@di...> >> Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details. >> This is free software, with components licensed under the GNU General Public >> License version 2 and other licenses; you are welcome to redistribute it under >> certain conditions. Type 'core show license' for details. >> ========================================================================= >> XSLT support not found. XML documentation may be incomplete. >> PBX UUID: 79ef0c49-1727-4912-907a-a3954cb63520 >> [Jun 19 09:39:43] NOTICE[2020]: loader.c:2377 load_modules: 322 modules will be loaded. >> [ Initializing Custom Configuration Options ] >> [Jun 19 09:39:47] WARNING[2020]: res_odbc.c:606 load_odbc_config: The 'pooling', 'shared_connections', 'limit', and 'idlecheck' options were replaced by 'max_connections'. See res_odbc.conf.sample. >> [Jun 19 09:39:47] WARNING[2020]: res_odbc.c:606 load_odbc_config: The 'pooling', 'shared_connections', 'limit', and 'idlecheck' options were replaced by 'max_connections'. See res_odbc.conf.sample. >> [Jun 19 09:39:47] WARNING[2020]: features_config.c:1533 unsupported_handler: Parkinglots are no longer configurable in features.conf; parking is now handled by res_parking.conf >> [Jun 19 09:39:47] WARNING[2020]: features_config.c:1537 unsupported_handler: The option 'parkext' is no longer configurable in features.conf. >> [Jun 19 09:39:47] WARNING[2020]: features_config.c:1537 unsupported_handler: The option 'parkpos' is no longer configurable in features.conf. >> [Jun 19 09:39:47] WARNING[2020]: features_config.c:1537 unsupported_handler: The option 'context' is no longer configurable in features.conf. >> [Jun 19 09:39:47] NOTICE[2020]: dnsmgr.c:493 do_reload: Managed DNS entries will be refreshed every 300 seconds. >> [Jun 19 09:39:47] ERROR[2020]: cel.c:428 ast_cel_str_to_event_type: Unknown event name 'BRIDGE_START' >> [Jun 19 09:39:47] ERROR[2020]: config_options.c:798 aco_process_var: Error parsing events=APP_START,CHAN_START,CHAN_END,ANSWER,HANGUP,BRIDGE_START,BRIDGE_END at line 76 of >> [Jun 19 09:39:47] ERROR[2020]: config_options.c:544 process_category: In cel.conf: Processing options for general failed >> [Jun 19 09:39:47] NOTICE[2020]: cel.c:1614 load_module: Failed to process CEL configuration; using defaults >> [Jun 19 09:39:47] NOTICE[2020]: cdr.c:4508 cdr_toggle_runtime_options: CDR simple logging enabled. >> [Jun 19 09:39:48] ERROR[2020]: res_resolver_unbound.c:417 unbound_config_preapply: Failed to set hosts file to 'system' in unbound resolver: syntax error >> [Jun 19 09:39:48] NOTICE[2020]: res_smdi.c:1424 load_module: No SMDI interfaces are available to listen on, not starting SMDI listener. >> [Jun 19 09:39:48] WARNING[2020]: res_phoneprov.c:1230 get_defaults: Unable to find a valid server address or name. >> SIP channel loading... >> [Jun 19 09:39:48] NOTICE[2020]: chan_sip.c:31843 build_peer: The 'username' field for sip peers has been deprecated in favor of the term 'defaultuser' >> [Jun 19 09:39:48] ERROR[2020]: chan_motif.c:2681 custom_connection_handler: Connection 'local-jabber-account' configured on endpoint 'jingle-endpoint' could not be found >> [Jun 19 09:39:48] ERROR[2020]: config_options.c:798 aco_process_var: Error parsing connection=local-jabber-account at line 81 of >> [Jun 19 09:39:48] ERROR[2020]: config_options.c:572 process_category: In motif.conf: Processing options for jingle-endpoint failed >> [Jun 19 09:39:48] ERROR[2020]: chan_motif.c:2756 load_module: Unable to read config file motif.conf. Module loaded but not running. >> [Jun 19 09:39:48] NOTICE[2072]: chan_sip.c:24881 handle_response_peerpoke: Peer 'joshcisco' is now Reachable. (12ms / 6000ms) >> [Jun 19 09:39:49] ERROR[2020]: ari/config.c:312 process_config: No configured users for ARI >> [Jun 19 09:39:49] NOTICE[2020]: confbridge/conf_config_parser.c:2326 verify_default_profiles: Adding default_menu menu to app_confbridge >> [Jun 19 09:39:49] ERROR[2020]: config_options.c:528 process_category: Could not find config type for category 'agents' in 'agents.conf' >> [Jun 19 09:39:49] ERROR[2020]: app_agent_pool.c:2693 load_module: Unable to load config. Not loading module. >> [Jun 19 09:39:49] NOTICE[2020]: cel_custom.c:95 load_config: No mappings found in cel_custom.conf. Not logging CEL to custom CSVs. >> [Jun 19 09:39:49] ERROR[2020]: codec_dahdi.c:813 find_transcoders: Failed to open /dev/dahdi/transcode: No such file or directory >> [Jun 19 09:39:49] WARNING[2020]: app_voicemail.c:14216 actual_load_config: maxsilence should be less than minsecs or you may get empty messages >> [Jun 19 09:39:49] WARNING[2020]: res_hep_rtcp.c:161 load_module: res_hep is disabled; declining module load >> [Jun 19 09:39:49] WARNING[2020]: res_hep_pjsip.c:236 load_module: res_hep is disabled; declining module load >> [Jun 19 09:39:49] WARNING[2020]: loader.c:2381 load_modules: Some non-required modules failed to load. >> [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: res_resolver_unbound declined to load. >> [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: chan_motif declined to load. >> [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: res_pjsip_transport_websocket declined to load. >> [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: app_agent_pool declined to load. >> [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: cel_sqlite3_custom declined to load. >> [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: cdr_sqlite3_custom declined to load. >> [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: res_hep_rtcp declined to load. >> [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: res_hep_pjsip declined to load. >> Asterisk Ready. >> >> But then as soon as I go off-hook on a Dahdi channel: >> >> *CLI> Segmentation fault >> >> It's really starting to seem (to me) like this is a Dahdi isssue. I'm able to place calls in and out through chan_sip and chan_pjsip. It's only Dahdi (going off-hook or trying to call a Dahdi channel) that seems to have issues. With ast16, Dahdi is triggering the same jansson error in dmesg: >> >> [ 732.177325] asterisk[2437]: segfault at 1 ip b73d2dcd sp b39f38e0 error 4 in libjansson.so.4.11.1[b73ce000+b000] >> >> From: Lonnie Abelbeck <li...@lo...> >> Sent: Wednesday, June 19, 2019 9:22 AM >> To: AstLinux Developers Mailing List >> Subject: Re: [Astlinux-devel] Segfault Crash on astlinux-1.3-4232-509fbe >> >> Hi Josh, >> >> Something is not right here... >> >> Testing tips: >> >> make sure asterisk is stopped (using CLI) >> -- >> service asterisk stop >> -- >> >> Then start via >> -- >> asterisk -c >> -- >> >> That will give you more context where the crash is occurring. >> >> BTW, what hardware are you using ? >> >> Lonnie >> >> >> >> >>> On Jun 19, 2019, at 8:15 AM, Josh Alberts <jm...@ho...> wrote: >>> >>> I tried the ast16 devel build, and this time, Asterisk is crashing before I get a chance to do anything. From dmesg (I tried restarting it twice): >>> >>> [ 44.698144] asterisk[1476]: segfault at 3c00 ip 081ee3f3 sp bfea5a10 error 4 in asterisk[8048000+2d2000] >>> [ 75.397478] asterisk[1621]: segfault at 3c00 ip 081ee3f3 sp bfae0140 error 4 in asterisk[8048000+2d2000] >>> [ 83.550674] asterisk[1671]: segfault at 3c00 ip 081ee3f3 sp bfdfff10 error 4 in asterisk[8048000+2d2000] >>> >>> >>> From: Lonnie Abelbeck <li...@lo...> >>> Sent: Tuesday, June 18, 2019 4:54 PM >>> To: AstLinux Developers Mailing List >>> Subject: Re: [Astlinux-devel] Segfault Crash on astlinux-1.3-4232-509fbe >>> >>> Hi Josh, >>> >>> As a mini-clue "libjansson.so" is only referenced by the "asterisk" binary, not by any of the asterisk modules. >>> >>> You might test again but use ast16 ... your Asterisk 13 configs should be fine for a quick test. >>> >>> Understand you have a somewhat unique setup using DAHDI, chan_sip and chan_pjsip all at the same time. And on 32-bit hardware. Agreed it should all work though. >>> >>> Lonnie >>> >>> >>> >>>> On Jun 18, 2019, at 3:16 PM, Lonnie Abelbeck <li...@lo...> wrote: >>>> >>>> Hi Josh, >>>> >>>> If you can, more clues would be great. >>>> >>>> Like if it is precisely reproducible, or if the crash varies ... and what is going on in the dialplan. >>>> >>>> Lonnie >>>> >>>> >>>> >>>> >>>>> On Jun 18, 2019, at 3:10 PM, Josh Alberts <jm...@ho...> wrote: >>>>> >>>>> I'm using both PJSIP and chan_sip (on different ports, of course). >>>>> >>>>> Come to think of it, all of the test calls that I generated either originated or terminated to/from the same Dahdi channel, so maybe Dahdi is playing into this? Wish I could have tested more but I had to get the system back up. Like I said, I would be glad to upgrade again and investigate further if that would help. >>>>> >>>>> From: Michael Keuter <li...@mk...> >>>>> Sent: Tuesday, June 18, 2019 4:06 PM >>>>> To: AstLinux Developers Mailing List >>>>> Subject: Re: [Astlinux-devel] Segfault Crash on astlinux-1.3-4232-509fbe >>>>> >>>>> >>>>>> Am 18.06.2019 um 21:56 schrieb Josh Alberts <jm...@ho...>: >>>>>> >>>>>> I tried upgrading from astlinux-1.3.5.2 i686 to astlinux-1.3-4232-509fbe. When Asterisk receives a call, when a Dahdi channel goes off-hook, or basically in response to any other user-generated action, Asterisk immediately crashes and I see this in the dmesg output: >>>>>> >>>>>> segfault at 1 ip 40421dcd sp 4334a990 error 4 in libjansson.so.4.11.1[4041d000+b000] >>>>>> >>>>>> I reverted back to 1.3.5.2 (Thanks for the Revert to Previous feature!) but I could try the development build again if that would help you guys figure out what's going on. >>>>>> >>>>>> Josh >>>>> >>>>> So that means: >>>>> >>>>> Asterisk 13.24.1 versus Asterisk 13.27.0 >>>>> >>>>> Are you using PJSIP already or chan_sip? >>>>> >>>>> I have been running that build on a few boxes successfully for a week, although none of my boxes uses DAHDI … >>>>> Does anyone else on this list is using Asterisk 13.27.0 together with DAHDI? >>>>> >>>>> Michael Michael http://www.mksolutions.info |
28 messages has been excluded from this view by a project administrator.
