[Robert Macklin]

Done

[Robert Macklin]

Hi Jeff,

I’ve run a few more tests and can’t get the failover mode working correctly. The cell connection is setup for dial on demand. I tried with Ethernet set to LAN and cell set to WAN. It properly dialed when needed, then disconnected shortly after the request was completed. When I set Ethernet to WAN, and the highest WAN priority, I get the same resolution problem that requires the daemon restart to fix.

There’s lots of stuff in the log file. I filtered out the LoRa communications, here’s a link to what remained:

https://drive.google.com/open?id=1KDLyM8CRnv-_1ur5lPdOnIRVaIZZ3l8I

Thanks,
Rob

• This reply was modified 5 years, 11 months ago by Robert Macklin.

[Robert Macklin]

Hi Jeff,

Thanks for the info. I was able to get resolution after restarting the daemon. I’ve tried restarting the entire system a few times and this didn’t fix the issue, why does this restart work?

I am trying to setup a Conduit with a Verizon LTE modem installed. I started with the Ethernet interface set to LAN and the cell interface set to WAN. This didn’t work, so I set the Ethernet interface to WAN to give access to the DNS and gateway settings. This also didn’t work until restarting the daemon.

My goal is to have the Conduit use Ethernet for cloud access until it cannot make a connection, then use the cell as backup. What is the best configuration to achieve this functionality?

Thanks,
Rob

[Robert Macklin]

I just found that as well. I checked another Conduit I have with the older firmware. It uses version 0.1.24 of the email node. I removed the latest 0.1.29 and installed the older version and the node shows in the sidebar.

[Author]

Posts