[Alexandros Rapsomanikis]

You could try the curl command. It’s still HTTP but you would get command-line like output and the write your script according to that.

[Alexandros Rapsomanikis]

Hello,

I tried it on both a PC and a Conduit. Both replied my current IP address. Since it’s a third party service, which has nothing to do with Multitech, the only thing I can suggest is choosing another third party website/service which replies with your IP address. I believe there are plenty. For example you can try: checkip.dyndns.org

Best regards.

• This reply was modified 6 years, 5 months ago by Alexandros Rapsomanikis.

[Alexandros Rapsomanikis]

I believe you should configure a default gateway for both of your devices – PC and Conduit.

Are you trying to connect to your conduit remotely? I’m asking this because the address your ISP is giving out is a private subnet and unless you’re connected to the same router or port forwarding is not enabled, you won’t be able to access it.

[Alexandros Rapsomanikis]

Hello,

I’d recommend to insert your SIM card to a 3G/4G compatible device – preferably a smartphone – just to be sure your SIM card is working properly.
Additionally, check that your PIN is correct and probably try rebooting the gateway!
I had issues myself with the Cellular network – the same message displayed and couldn’t get the network to work properly.

You can also try manually starting the ppp interface by running this command: /etc/init.d/ppp start
I believe the output will help you determine the issue, since it’s log is more helpful.

Best regards.

[Alexandros Rapsomanikis]

Additionally, you can connect via SSH. You only need the IP address of your gateway and a software to connect (for Windows users I recommend Putty).

Best regards.

[Alexandros Rapsomanikis]

Hello,

you can connect to your gateway via serial interface, which means that even if you’re blocked outside, you can reverse or edit the rules.

Additionally, you can connect via SSH, test your iptable rules by typing them in and if anything goes wrong, just restart the device. The rules you type in manually aren’t saved on restart.

To permanently store your iptable rules, set them via the Web Interface. Login and navigate to Firewall > Settings. There you can add your custom Firewall rules, which will be saved on reboot.

Best regards.

[Alexandros Rapsomanikis]

Another way is by network discovery tools like NMap. You scan the network and look for a machine/IP that isn’t assigned to any of your existing machines. I wouldn’t recommend this though in a professional/working environment, since it can raise some flags – either on AVs or if your network is monitored.

This technique is also used to discover vulnerabilities – that’s the reason I recommend using it only in a personal or developing environment.
The best and safest approach is the one that Jeff proposed.

Best regards.

[Alexandros Rapsomanikis]

Hello,

have you tried reading and following the instructions on the “GPS on AEP“?

Best regards.

[Alexandros Rapsomanikis]

You can try adding nodes to your Node-Red installation that support MQTT over SSL/TLS.

[Alexandros Rapsomanikis]

Hello,

I haven’t used this custom node, but it seems pretty simple and probably will cover your needs.

It’s called node-red-contrib-https. I’d recommend experimenting with this one first and if you’re not satisfied, move to another.

Best regards.

[Alexandros Rapsomanikis]

We had issues when we upgrades from 1.3.3 to 1.4.3!
The best thing I can propose for now, is to downgrade to a previous version. It’s pretty simple via the WebUI interface.

[Alexandros Rapsomanikis]

Try to view the content of your “resolv.conf” file.

cat /etc/resolv.conf

If your nameserver shows 127.0.0.1 change it to another address, like 8.8.8.8 or any other public DNS.

• This reply was modified 6 years, 10 months ago by Alexandros Rapsomanikis.

[Alexandros Rapsomanikis]

Have you entered the PIN for your SIM Card? (I see in your 1st response that the box is empty).
Do you get any debugging message on the top of the Administrative interface? (“No SIM?” “SIM Card is Locked” etc?)

[Alexandros Rapsomanikis]

It is a great service to have to be honest. But I don’t consider ideal the 4 Hour minimum interval. I’d use a free backup solution like no-ip, just to feel safe.

[Alexandros Rapsomanikis]

I contacted my provider and kindly requested for a Public IP address for my SIM Card. They accepted right away and after 30mins I had a public IP available which means no more NAT. I can contact my gateway now via Cellular Network without a problem (you only need to know your current IP address – solved with DDNS Service or OVPN as I’ve mentioned before).

I believe you can request a Public IP. Although many providers prefer NATing, there should be an option for a public IP.
Be careful, the provider might misunderstand that you are requesting a Static IP and not a Public IP.

[Alexandros Rapsomanikis]

You can also connect via Serial (COM port and set speed to 115200), login using your credentials and then tail -f /var/log/app/node-red.log

[Alexandros Rapsomanikis]

I’ve contacted my network provider regarding this issue and I’m awaiting an answer – which will probably be same as yours.

I believe this issue can be bypassed using the OpenVPN solution – which I’m currently working on (no success yet). I’ll post any updates here.

[Alexandros Rapsomanikis]

The appropriate size for the SIM card is the Standard size. You can although fit any other size, but you’ll have to guess the correct place for the SIM card to work properly.

[Alexandros Rapsomanikis]

Hi!

I’m actually trying to do the same thing. I haven’t accomplished to connect directly yet. I’m currently working on a workaround using OVPN. If I have any success I’ll let you know.

If it’s not too much trouble, ask your cellular network provider, if they are blocking any ports on their network.

A.R.

[Alexandros Rapsomanikis]

Same thing happened to me. Instructions about how to recover your conduit have been addressed in previous comments, so I’d like to address the fact you wanted to include a script to start the LOR IOT binary.

I tried to include a script to start the Loriot binary at each Conduit reboot but it seems to have totally stuck the Conduit.

1. Create file /etc/init.d/start-loriot.sh
2. In here, put
#! /bin/bash
cd /home/root/ && ./loriot_multitech_conduit_mCard_USB_1.0.1
(or wherever you put the binary)
○ It’s important to cd into the folder first, otherwise LORIOT cannot find the certificate.
3. chmod +x /etc/init.d/start-loriot.sh
4. Link the script: ln -s /etc/init.d/start-loriot.sh /etc/rc5.d/S99start-loriot.sh
Now reboot, should start up automatically.

I hope this helped.

Source from Githbub

• This reply was modified 7 years, 3 months ago by Alexandros Rapsomanikis.
• This reply was modified 7 years, 3 months ago by Alexandros Rapsomanikis.
• This reply was modified 7 years, 3 months ago by Alexandros Rapsomanikis.
• This reply was modified 7 years, 3 months ago by Alexandros Rapsomanikis.
• This reply was modified 7 years, 3 months ago by Alexandros Rapsomanikis.
• This reply was modified 7 years, 3 months ago by Alexandros Rapsomanikis.

[Alexandros Rapsomanikis]

First of all, it’s a soft brick so no panic.

Secondly, as Brandon and Jeff mentioned, the best way to solve your problem is to create a support ticket at .
The process is quite simple after receiving the response mail. The procedure is actually flashing your device.
You’ll receive a text file with detailed instruction, a script which is essential and saves you a bit of time and of course all the necessary files to do the flashing.

A huge thank you to the guys at the support for providing the files and instruction.

In my case, I didn’t lose the Node-Red configuration/scheme (although I lost a plugin). After flashing, I chose to upgrade to the latest AEP version, just to address some previous issues.

[Alexandros Rapsomanikis]

I can confirm this error on the 1.1.2 version. I tried upgrading to the newest current version – 1.3.3 and failed via the WebUI.
I can also confirm that the method described above, using SCP and updating via SSH afterwards.

Notice that there might be some garbage files in the /var/tmp directory. Delete only the files and not any folders (if presented).

The device will upgrade and reboot.

[Author]

Posts