[Jeff Hatch]

Dave,

One way to “stop” iptables would be to follow the instructions here:

https://www.cyberciti.biz/faq/debian-iptables-stop/

Make sure to save off your rules in case you want to restore them. and then use the shell script to open things wide. Be aware that this could lead to vulnerabilities. You could compare the two output files of the iptables-save on each device and see what the difference is. There must be something different on the system with the problem.

Jeff

[Jeff Hatch]

Milan,

How are you building the MTCAP firmware. What bitbake command are you using?

Jeff

[Jeff Hatch]

Martijn,

To get the information on how to flash from AEP to mLinux file a support portal case at https://support.multitech.com

Jeff

[Jeff Hatch]

JC,

Are you saying that the boot just stops at that point? Are you running an AEP or mLinux Conduit? The jffs2 output is just a notice so I don’t think that is related to any problems.

Jeff

[Jeff Hatch]

Mr Attar

Have you connected to the debug console port to look at the output? If you were using anything beside the factory default IP the upgrade may have wiped out that configuration.

Jeff

[Jeff Hatch]

Andrey,

The old MTAC-LORA-868 is still supported so you can upgrade. Just don’t plug in any of the new cards until you have upgraded to 1.4.3 otherwise you will fail to upgrade among other things.

Jeff

[Jeff Hatch]

Ajay,

There is an effort to develop a new Conduit (to be called Conduit 2.0), however, progress is going slowly.

Jeff

[Jeff Hatch]

Srinivas,

You will need to copy the tar file into /opt/node-red/nodes, and untar it there. Then run npm install in any of the sub-folders that you want to install the nodes for. See Installation under https://github.com/node-red/node-red-nodes.

Jeff

[Jeff Hatch]

Srinivas,

Have you either downloaded and extracted the tar archive or cloned the git repo for the node-red-nodes package in /opt/node-red first? It might also be possible that you need to update the version of npm.

Jeff

[Jeff Hatch]

Ajay,

The AEP 1.5 release will be out in early Q1 2018 for general consumption. The version of node-js will not change since 0.10.x is the last version that supports armv5.

Jeff

[Jeff Hatch]

Boyko,

The upcoming AEP 1.5 release will have Node-RED 0.15.3. That is the last version of Node-RED the Conduit hardware will be able to run due to no more support for the armv5 instruction set.

Jeff

[Jeff Hatch]

Charlie,

There are a couple of ways to determine the IP. You could hook up the debug console port and use the ‘ifconfig’ command or if it is possible to get the assigned addresses from the DHCP server you could try that.

Jeff

[Jeff Hatch]

Yoshihiro,

Without your test.c code I can only speculate. As to why it didn’t break at line 12, there are a couple of possibilities: A statement at line 11 caused the execution to skip line 12, or it is quite possible that line 12 was optimized out.

As for the gdb server error, it appears to think that the incorrect target for the host side. Make sure that the correct target is being specified when building the gdbserver for the target.

Jeff

[Jeff Hatch]

Srinivas,

What is the npm install command you’re using? Is the package you’re talking about located at https://github.com/node-red/node-red-nodes?

Cross-compilation is sometimes required for node-red nodes. The Conduit does not support cross-compilation natively. Conduit is based off of mLinux (http://www.multitech.net/developer/software/mlinux/) so you can download mLinux or the mLinux SDK (http://www.multitech.net/developer/software/mlinux/mlinux-software-development/mlinux-c-toolchain/) and cross-compile the code if necessary.

Jeff

[Jeff Hatch]

Srinivas,

Are you using the lora network server or the packet forwarder?

Jeff

[Jeff Hatch]

Srinivas,

The Conduit has Bluez 5 installed on it. The easiest way to create an app would probably be to use Python. The gattool utility is also available for communicating with BLE devices.

Jeff

[Jeff Hatch]

Homas,

The iptables rules are overwritten by the AEP Conduit API on boot using the firewall utility. User defined rules can be created through the AEP Web UI and saved that way. The API will then create these rules on boot.

Jeff

[Jeff Hatch]

Wout,

There is a good chance that your inittab is corrupted or that the filesystem is corrupt. I’m afraid that your only choice is to re-flash the device from u-boot. For help with that you can file a support case on https://support.multitech.com.

Jeff

[Jeff Hatch]

George,

Javascript provides the Date.now() method is being used by the inject node. I’m assuming that you are using the inject and seeing the UTC timestamp. By definition from the documentation on the Date object:

Date.now()
Returns the numeric value corresponding to the current time – the number of milliseconds elapsed since 1 January 1970 00:00:00 UTC, with leap seconds ignored.

This means that you are always going to get a UTC time unless you convert the value through some other function to the local time you are in.

Jeff

[Jeff Hatch]

Shankar,

File a Multitech Support Portal case at https://support.multitech.com and say exactly what you did here. They can help you re-flash the device through tftp to get it back to working.

Jeff

[Jeff Hatch]

George,

Which timestamp are you referring to?

Jeff

[Jeff Hatch]

Lawrence,

Which session key are you asking about? LoRa, AEP API? I don’t think either of those will hold on to keys through a reboot. Not positive about LoRa.

Jeff

[Jeff Hatch]

Boyko,

The 0.10.x restriction applies to node-js, not to the node you’re trying to add. I did not see any minimal version of node-js required for the s7comm node.

Jeff

[Jeff Hatch]

Boyko,

You can use the “npm install node-red-contrib-s7comm” with the –prefix option to point to /opt/node-red/node_modules. ie.

npm install node-red-contrib-s7comm –prefix /opt/node-red/node_modules

From the little bit of investigation it appears that this node and it’s dependencies are pure javascript so I believe that this node will install and work without the necessity of cross compilation or anything.

Jeff

[Jeff Hatch]

Milan,

Check out these topics:

setting static DNS

mlinux resolv.conf issue

Static DNS

There’s a few ways to address DNS in mLinux.

Jeff

[Jeff Hatch]

Nicola,

Have you tried putting a nameserver entry in /etc/resolv.conf?

Jeff

[Jeff Hatch]

Nicola,

You should be able to specify the DNS nameservers in /etc/network/interfaces like so:

dns-nameservers 1.1.1.1 2.2.2.2

Jeff

[Jeff Hatch]

Nicola,

You will need to configure the default gateway and other settings in the /etc/network/interfaces file. For example:

auto eth0
iface eth0 inet static
address 10.0.0.100
netmask 255.255.255.0
gateway 10.0.0.1

This configures the Ethernet eth0 interface to be brought up automatically with an address of 10.0.0.100 and the default gateway of 10.0.0.1. This information would go into /etc/network/interfaces.

Jeff

[Jeff Hatch]

Gokhan,

Try checking the /var/log/app/node-red.log file and see what it says.

Jeff

[Jeff Hatch]

Eric,

Due to the armV5 architecture of the CPU on the current Conduit, nodejs does not support that instruction set beyond 0.10.x. We do have plans for a new Conduit with updated hardware, but that is a ways out yet.

Jeff

[Author]

Posts