Make networking independent from app

[danielkucera]

Hello,
I'd like to make networking independent from the packet forwarder app.
I see it happen in following steps:

• webserver: start allways - don't wait for network #18
• move network configuration handling to a separate file: wip: main...danielkucera:esxp1302:networking
• create a separate thread for network state changes handling
• add additional network connections (using e.g. esp internal mac for ethernet, GPRS with SIM800 via uart, usb-cdc, ...)

The sockets for packet forwarder can be created even without working connection (as with the webserver). The only relevant parts are DNS resolving during connection (solved in wip) and sending status/uplink packets - this has to be tested how it behaves during missing connection (if it drops after start and resolving server) but IMO it should be fine - we should just ignore a potential error during UDP packet send. Once the connection reestablishes it should continue sending.

What do you think about this?

[dennis4lora]

@danielkucera

Thanks for this proposal, it paves the way to support multi types of network interface.

In fact, there is a problem in the original sx1302_hal: after pkt-fwd runs, if you disconnect the Ethernet cable then connect it again, pkt-fwd keeps run, but the packets won't be sent out to NS any more (I guess this is caused by how the sockets are created or configured but I didn't investigate).

I think esxp1302 pkt-fwd doesn't have this problem because: if Wi-Fi fails for a few seconds then re-connected, there is no logic to restart the pkt-fwd (I guess I tested this situation).

Of course, it needs careful thinking about the network state changes and some tests to make sure no mistake, but I think this idea is doable. 😄