Jeff Hatch
Forum Replies Created
-
AuthorPosts
-
Jeff Hatch
KeymasterCould you perform an “inadyn –version” to verify which version of inadyn is on AEP 1.4.3 (I don’t have a unit running that version at the moment). The error code #42 corresponds to the following error in inadyn for version 1.99.3:
RC_DYNDNS_INVALID_RSP_FROM_IP_SERVER
From what I can tell, this means inadyn doesn’t like the server’s response.
Jeff
Jeff Hatch
KeymasterWhich ddns service are you using? On the DDNS page in the Configuration section, after you save and restart is the Enabled check-box still checked? Does the Conduit have Internet access?
I do not currently have a valid ddns account so when I run inadyn at the command line I get:
admin@mtcdt:/var/run# inadyn -V –config /var/run/inadyn.conf
Tue Apr 10 13:07:48 2018: Error parsing option -V
admin@mtcdt:/var/run# inadyn –config /var/run/inadyn.conf
Tue Apr 10 13:07:57 2018: Missing username in account 1
Tue Apr 10 13:07:57 2018: Missing password in account 1
Tue Apr 10 13:07:57 2018: No valid DDNS setup exists.The inadyn process does not seem to be logging any of these messages, so you will not get any feedback without running it by hand. Here is my inadyn.conf after configuring:
admin@mtcdt:/var/run# cat inadyn.conf
background
verbose 1
startup-delay 0
logfile /var/log/ddns.log
pidfile /var/run/ddns.pid
forced-update 2419200
system default@dyndns.org
alias multitech.com
ip_server_name checkip.dyndns.org:80 /The inadyn process appears to be reaching out to dyndns, but since I don’t have anything set up I am getting the “No valid DDNS setup exists.”
Jeff
Jeff Hatch
KeymasterAsier,
Let’s start with the simple stuff:
Assuming you enabled through the Web UI, did you hit the Submit button, and do a Save and Restart?
Jeff
Jeff Hatch
KeymasterI should have said MTR in the previous statement.
Jeff Hatch
KeymasterSteve,
The max number of recipients is 100. Not sure that is documented anywhere. As for the rate, that would have to be empirically tested. It depends on the radio, provider, signal, how busy the Conduit is, and whether the provider is throttling or not.
I do not have any information on whether it will queue up requests or be able to handle things in any sort of batch mode.
Jeff
Jeff Hatch
KeymasterSteve,
There was a sales announcement here (though I can see the confusion about the multiple user support):
The following link is the User Manual (See Chapter 12 for user administration information):
https://www.multitech.com/documents/publications/manuals/s000566.pdf
On MTR 4.0.5 you can add three different users (even more if you want to). As for the simultaneous login of three different users, I have not tested that so I cannot confirm that is fully supported.
Jeff
Jeff Hatch
KeymasterSteve,
One way to make sure that you have the correct firmware to upgrade is to file a support portal case at https://support.multitech.com/support. I believe what you’re looking for can be downloaded from https://www.multitech.com/models/92507399LF under the DOWNLOADS drop-down menu.
Jeff
March 15, 2018 at 8:48 am in reply to: Unable to get wlan0 to show in MultiConnect Conduit – AEP – v1.4.4 #22853Jeff Hatch
KeymasterPatrik,
A support person came to me late yesterday, so he is starting to work on this case. We are trying to either find or re-generate the rs9113 driver package at the moment.
Jeff
March 15, 2018 at 8:48 am in reply to: Unable to get wlan0 to show in MultiConnect Conduit – AEP – v1.4.4 #22852Jeff Hatch
KeymasterPatrik,
A support person came to me late yesterday, so he is starting to work on this case. We are trying to either find or re-generate the rs9113 driver package at the moment.
Jeff
Jeff Hatch
KeymasterSteve,
There is now support for multiple different users in the MTR 4.0.5 release. There are still some limitations on multiple concurrent user sessions, etc., however you can now log in with different users. I’m not sure whether the IP restriction has been removed or not.
Jeff
March 15, 2018 at 8:42 am in reply to: Unable to get wlan0 to show in MultiConnect Conduit – AEP – v1.4.4 #22849Jeff Hatch
KeymasterPatrik,
Did you re-install the device firmware or the modem firmware? Currently there isn’t a version beyond 1.4.4 for the IP67. However, we are in the process of releasing 1.4.13 that might work. It won’t fix your problem with the WiFi module driver though.
Jeff
March 14, 2018 at 12:53 pm in reply to: Unable to get wlan0 to show in MultiConnect Conduit – AEP – v1.4.4 #22844Jeff Hatch
KeymasterPatrik,
That has more to do with the fact that gpsd is not running, and even if it was, I am not sure that the rule that is causing that is valid anymore. I’ve seen that on devices that are successfully reporting their location. Something that should get addressed, though.
Jeff
March 14, 2018 at 7:52 am in reply to: Unable to get wlan0 to show in MultiConnect Conduit – AEP – v1.4.4 #22839Jeff Hatch
KeymasterPatrik,
There were a number of bugs in the gps related code that have been fixed since AEP 1.4.4 that is on the IP67 you have. The driver level gps functionality works. It is at the application level where there were a large number of bugs due to the fact that the code used to work with a GPS module, and the module was upgraded to a GNSS module, the difference being in a lot of cases that NMEA strings began with GN instead of GP.
Jeff
March 13, 2018 at 11:43 am in reply to: Unable to get wlan0 to show in MultiConnect Conduit – AEP – v1.4.4 #22835Jeff Hatch
KeymasterPatrik,
We can provide you with a package to install to put the rs9113 driver back on your device. There will be a couple of other steps to follow we will give you through the support portal.
Jeff
March 13, 2018 at 11:26 am in reply to: Unable to get wlan0 to show in MultiConnect Conduit – AEP – v1.4.4 #22834Jeff Hatch
KeymasterPatrik,
I have figured out the problem. It is in a script /etc/init.d/remove-rs9113. It is removing the rs9113 driver because the hardware ID is not “MTCDT-0.1”. The intent of the script is to make sure that the rs9113 driver not be installed on hardware that doesn’t have the wifi module (licensing). The MTCDT-0.0 hardware doesn’t have the rs9113 module on-board. The MTCDTIP-0.0 does.
Your serial number (deviceId) looks like it is a later model with wifi so the capa-wifi value is set correctly. I believe that something is messed up coming out of production on this unit (they changed the hw-version). I think that the hw-version being set to MTCDTIP-0.0 has caused a bug when the device first boots, and the aforementioned script is incorrectly removing the rs9113 driver. Please file a portal case at https://support.multitech.com. This is an issue that needs to be fixed. In the mean time, I am not sure that there is a workaround.
Jeff
Jeff
March 13, 2018 at 10:28 am in reply to: Unable to get wlan0 to show in MultiConnect Conduit – AEP – v1.4.4 #22826Jeff Hatch
KeymasterPatrik,
Was this Conduit upgraded from mLinux? What is the output of the following command:
get-eeprom-device-info
or
get-eeprom-device-configJeff
March 13, 2018 at 8:51 am in reply to: Unable to get wlan0 to show in MultiConnect Conduit – AEP – v1.4.4 #22824Jeff Hatch
KeymasterPatrik,
On the Conduit, could you list the contents of /opt/rs9113? That is where those modules should be (initially). If they are in that directory, then something is going wrong with the rs9113 initialization (obviously).
Jeff
Jeff Hatch
KeymasterJulien,
Do you have access to the logs on any of the Conduits? There may be more information in the Conduit logs as to what is failing.
Jeff
Jeff Hatch
KeymasterNicola,
We are planning on upgrading OpenVPN to at least 2.3.12 in an upcoming release. I can’t say which one, but it will be a 1.5.x release of AEP Conduit, and a mLinux 4.x release. Sorry I can’t be more specific at this time.
Jeff
Jeff Hatch
KeymasterNicola,
Can you confirm when this bug was supposed to be fixed in OpenVPN? I have not found any place where this bug may have been fixed, and I have not seen it on the Conduit myself (not saying there isn’t a bug in the version of OpenVPN on the Conduit). I don’t know what revision of OpenVPN may have fixed this. Since I have not been able to reproduce the issue, and I have no idea when it may have been fixed in OpenVPN, I cannot answer your question.
Jeff
Jeff Hatch
KeymasterNicola,
The two errors you have identified should be “innocuous”. The “ap1 eeprom” one is correct to the effect that there is no card plugged into accessory port #1. If there is actually a card plugged in, then there must be a contact issue or a problem with the card. The “jffs2” warning is innocuous.
To figure out what is going wrong with the “ppp call gsm” command, you need to look in the /var/log/messages and any other pertinent log files to determine what is going wrong with the chat script. That will be the best place to start to debug the connection problem.
Jeff
Jeff Hatch
KeymasterMing,
I recommend opening a support portal case with Multitech at https://support.multitech.com. You will most likely need to re-flash the device to get it out of that state.
Jeff
Jeff Hatch
KeymasterKenneth,
What is your u-boot environment (output of print at the U-Boot> prompt)?
Jeff
Jeff Hatch
KeymasterMassimiliano,
I don’t think that firmware should be on that site. Use it with discretion. In other words, I think it was something custom for a specific customer. However, I may be incorrect.
Jeff
January 25, 2018 at 7:41 am in reply to: Unable to use HTTP config UI on MTCDT-LVW2-247A v1.4.3 via WAN static IP #22479Jeff Hatch
KeymasterAlbert,
Thank you for sharing what you found. This is excellent information for people having similar problems.
Jeff
Jeff Hatch
KeymasterTaeHyeong,
I am confused by a couple of things in your described setup. Are you trying to connect to the MTCAP via SSH from your PC using Tera Term? Also, I am not sure what you are referring to by UNUNSPEC.
What is the routing state of your PC? Do you have two NICs on your PC with one to a company or personal LAN used for Internet access, and a second connected to the MTCAP? Are you able to access the MTCAP using the Web UI? Have you configured your MTCAP Ethernet interface as WAN? If so, have you enabled access via WAN for SSH?
Jeff
Jeff Hatch
KeymasterUsman,
Do you have the GPS antenna attached? Is the device inside a building? Where is it located? GPS/GNSS signals can vary greatly depending on exactly where the device is located.
Jeff
Jeff Hatch
KeymasterFernando,
Please talk with Multitech support about this at https://support.multitech.com
Thank You,
Jeff
Jeff Hatch
KeymasterMartin,
The mLinux 4 toolchain should help you avoid compatibility issues with libraries and other things. The compiler made a significant jump between the 3.x line and 4. So, if you are doing mLinux 4 based work, using that toolchain is highly recommended. Use the corresponding 3.x toolchain for any 3.x based development.
As for the mLinux 4.x release and toolchain, there will be a 4.x toolchain available soon, hopefully within the next month. It will correspond to AEP 1.5.1 that is based off of mLinux 4 and which will be available upon request in the Multitech Support Portal.
Jeff
January 18, 2018 at 3:28 pm in reply to: Unable to use HTTP config UI on MTCDT-LVW2-247A v1.4.3 via WAN static IP #22397Jeff Hatch
KeymasterAlbert,
Happy to hear that you are making progress as I was stumped as to what may be going on on the Conduit end. Hopefully the provider can get you a solution. Let us know if you need any more help.
Jeff
-
AuthorPosts