[Brian Wyld]

Hi all,

Trying to get my openvpn tunnel to come up/down in sync with the ppp.
Seems like to should be simple : just create 2 scripts in /etc/ppp/ip-up.d and ip-down.d, to do /etc/init.d/openvpn start / stop….

However… my script in ip-up.d never seems to be called? Is there something special about the Conduit’s ppp install/operation?

thanks

Brian

[Brian Wyld]

Hi,

less than 20 nodes; basically just a LoRa-in -> https REST API backend and http-in -> LoRa-out pair.

Nothing that should stress it!

My current AEP version is 1.0.33 : when will 1.1.x be available?

thx

[Brian Wyld]

I received some info earlier this week which included a datasheet for a 9dbi antenna : should be a significant improvement over the usual 3dbi 20cm jobs.

Anyone got any hard data on this?

Brian
“your mileage may vary” seems appropriate here..

[Brian Wyld]

Hi,

I’m also experiencing a certain amount of ‘instability’ from the nodeRED environment (stops updating the web interface, stops processing inbound messages after a while).

Might be better just having a custom process in java to connect the MQTT queues to my backend….

thanks for the infos

[Brian Wyld]

Hi,

Ok, thanks Brandon, I have logged my support case this morning.

Brian

[Brian Wyld]

Hi Brandon,

I just checked back with this forum (was very occupied with ‘stuff’) as re-testing range, and discovered your reply about the bad card issue!!!

I’ll open a support call tomorrow to get that RMA’d. However, this will mean I’m down a gateway in the meantime? How long does it typically take to get the replacement card out?

thanks

Brian

[Brian Wyld]

Hint for anyone else trying this : the default iptables setup on the conduit doesn’t allow inbound connections (eg http, ssh, icmp) over non-lan interfaces….
Took a while to work out that this was why I couldn’t ping it via the openvpn tunnel….
Currently running without the iptables in place until I add the magic to let ping, ssh, and http via openvpn tun interfaces…

[Brian Wyld]

Hi,

Thanks Jason, OpenVPN installed no problem; config ok. Had to create a init.d script for it but otherwise no issues to get it to work.

Noted for the firmware upgrade issue.

Thanks for the pointers!

Now to try getting it to work over the ppp over 4G interface….

A+

Brian

[Brian Wyld]

Actually, I see the multitech package repositry (http://www.multitech.net/mlinux/feeds/3.1/arm926ejste/) seems to have openVPN packages….
[ ] openvpn_2.1.3-r0.0_arm926ejste.ipk 22-Jul-2015 16:23 207K

Anyone tried using these?

cheers

Brian

[Brian Wyld]

Any ideas on what is required to install packages on the Conduit?
Will I need to build them from source (aie aie)?

cheers

Brian

[Brian Wyld]

Tried again, with both the standard 3Dbi antenna and with a wide band 7DBi one..

The problem is that the rssi reported by AT+PING varies between -13 and -28, for approx 1m of separation and no change in the environment….

Any ideas why the rssi would not be stable?
thanks

Brian

[Brian Wyld]

Hi,

I’m trying pretty much the same setup, and had exactly the same range issues (I would expect a factor of 20x what I actually see..)

With the gateway and the mdot on ajacent desks, the RSSIs (as reported by AT+PING and AT+RSSI) are -37 on the gateway and between -40 and -50 on the mDot.
Gateway tx power is 26, and mDot is 20….. ie the max for both…

this is with SPF 9 on the mDot.
mDot is version 0.1.4 and conduit is 1.0.33 ie the latest versions from the web site.

Andrew, did the change to your setup increase range?

thanks

Brian

[Brian Wyld]

Hi,

ok, that was the problem.

thanks

Brian

[Brian Wyld]

Hi,

Ok, update to 1.0.33 went ok, no reset issues…

Had to reboot again to get RED to talk to me again, but seems ok now.

However, its now refusing all join requests from the mDot (which hasn’t changed):
Sep 18 15:04:37 mtcdt user.info lora-network-server: Parsing 1 rx packets
Sep 18 15:04:37 mtcdt user.info lora-network-server: Received join request
Sep 18 15:04:37 mtcdt user.warn lora-network-server: Tossing join request, invalid NET EUI

I’ve tried with both a name/passphrase and with direct hex EUIs : no difference. This used to work…

Any ideas?
thanks for the help.

Brian

[Brian Wyld]

Ok, its running 1.0.25-Beta 2015-06-03T13:28:21

I’ll go for the upgrade tomorrow!

thanks

Brian

[Brian Wyld]

Hi Brandon,

I have managed to get the conduit to respond again via login over the front panel USB and forcing the IP address.

I then restarted, got the web page up and re-enabled DHCP client (and disabled DHCP server)

After using it for a while, when I again reset it (power off to move it to another location), I had the same problem : apparently working but no response to ping or web, login possible only via front USB.
This time, by logging in thru the USB port and just doing a shutdown -r, it then brought the system back up and responded to the IP just fine!

ifconfig and curl output below : these are from just now when its working ok : but were the same when it wasn’t!! (hence the reason I was wondering firewall problem…)

ifconfig :
root@mtgw1:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:08:00:4A:01:B6
inet addr:192.168.127.44 Bcast:192.168.127.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:25132 errors:0 dropped:1079 overruns:0 frame:0
TX packets:6017 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2325203 (2.2 MiB) TX bytes:2606147 (2.4 MiB)
Interrupt:23 Base address:0xc000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:92669 errors:0 dropped:0 overruns:0 frame:0
TX packets:92669 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:8064236 (7.6 MiB) TX bytes:8064236 (7.6 MiB)

root@mtgw1:~# curl -s 127.0.0.1/api/ni
{
“code” : 200,
“result” : {
“nis” : [
{
“available” : true,
“ipv4” : {
“dns1” : “”,
“dns2” : “”,
“gateway” : “”,
“ip” : “192.168.127.44”,
“mask” : “255.255.255.0”,
“mode” : “DHCP”
},
“name” : “eth0”,
“nitype” : “ETHER”,
“type” : “LAN”
},
{
“available” : true,
“ipv4” : {
“dns1” : “”,
“dns2” : “”,
“gateway” : “”,
“ip” : “”,
“mask” : “”,
“mode” : “PPP”
},
“name” : “ppp0”,
“nitype” : “PPP”,
“type” : “WAN”
}
]
},
“status” : “success”
}

cheers

Brian

[Brian Wyld]

an error at boot :
sam9x5: ap2 eeprom read failed: -110
(but it continues anyway)

also, the dhcp setup fails to get the gateway/dns info although it gets an IP ok. could this break the firewalling?

Brian

[Author]

Posts