Conduit no longer responds to network…

[Brian Wyld]

Hi,

Happily using my MC Conduit (in AEP mode) when I reset it (via the web interface), and now it refuses to respond to the network (ethernet wired).
No response to ping, http, etc.

Using the USB debug interface, all seems fine : network is up, has a IP address, can ping and ssh out to other systems on the local network.

Some messages:
1/ from time to time I see :
jffs2: notice: (161) check_node_data: wrong data CRC in data node at 0x0d0c81b4: read 0xab1afb5b, calculated 0x688afa09

2/ lots of attempts like this:
Sep 5 12:10:08 mtcdt daemon.info annexcd: [INFO] courier.cc:Open:1394: opening connection with ds-beta.devicehq.com:5798
Sep 5 12:10:08 mtcdt daemon.err annexcd: [ERR] courier.cc:Open:1408: gethostbyname_r: 2
Sep 5 12:10:08 mtcdt daemon.err annexcd: [ERR] courier.cc:RunnableCore:1211: Open failed
Sep 5 12:10:18 mtcdt daemon.err annexcd: [ERR] ./annex_transfer.h:SendqTimedout:70: transfer timeout

Somehow the network config is trashed….
A factory reset (long press) doesn’t fix it.

Any ideas?

[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

[Brandon Bayer]

Brian,

What network configuration are you using to try to connect to it (IPs, DHCP setup, etc)? Also, issue the ifconfig command and post the results.

By default, the Conduit is a DHCP server with an IP of 192.168.2.1

-Brandon

[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

[Brandon Bayer]

Which version of AEP do you have? If you don’t have 1.0.33 (just released), update to it, reset to factory defaults, and try again.

Upgrade file and instructions: http://www.multitech.net/developer/software/aep/upgrading-the-aep-firmware/

[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,

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

[Brandon Bayer]

Brian,

You’ll also need to update your mDots to 0.1.2
–> http://www.multitech.net/developer/software/mdot-software/mdot-firmware-upgrade/

Sorry about that!

-Brandon

[Brian Wyld]

Hi,

ok, that was the problem.

thanks

Brian

[Author]

Posts